How to write good requirements

Well apparently I don’t get to do this job any more and the new person isn’t very good at it. So i am going to write out a few tips and pray that they learn something just by sitting “near” the Internet. This discovery has made me very sad as this is one of those things that I am good at.

Requirements must be testable Requirmenets should be concise and clearly written, there should be no question as to what you mean Requirements should include error handling, no really Requirements should include all system functionality including system time outs and validation requirements You should include such items as log . . . → Read More: How to write good requirements