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 out, return and back button requirements
- Your terminology should be consistent and accurate, once again NO really this is important
- Use cases alone are not requirements
When you write requirements you need to stop and think like different users. First like a really dumb user who’s AFRAID of the internet and then like a moderate user and then like a power user like me who doesn’t want to be bothered. Once you find a happy medium write nice requirements.
This message was brought to you by your unhappy Systems Anlayst.
Leave a Reply