Requirements are descriptions of the end-result of your project.? They are a way to gain consensus on exactly what it should do, and impose some constraints as well.
Good requirements DO NOT impose a particular solution unless there is a valid business reason.? Let me explain.
A Tale Of Two Requirements
- Perform [function] with less than [some constraint or specification] delay using [specific software program or system].
- Perform [function] with less than [some constraint or specification] delay.
I am NOT saying these are great examples of requirements, I could do a whole training course just on the topic of requirements.? Just note that in the first example, the requirement mandates a particular solution.? This may be valid, but watch for it like a hawk.
Many times, the solution is assumed.? Instead, it should be up to the experts on the project team to figure out the best solution.
Oh, and if you want some more info on this topic, keep the following in mind and click through to the article: