Let us learn 10 cosmic truths about software requirements that are universally applicable.
1. If you don’t get the requirements right, it does not matter how well you execute the rest of the project.
2. Requirements development is discovery and invention process, not just a collection process.
3. Change happens.Accept to this fact and adapt to change with rationale.
4. The interests of all project stakeholders intersect in the requirement process.
5. Customer involvement is the most critical contributor to software quality.
6. The customer is not always right, but the customer always has a point.
7. The first question an analyst should ask about a proposed requirement is, “Is this requirement in scope?”.
8. Even the best requirements document cannot- and should not – replace human dialogue.
9. The requirements might be vague, but the product will be specific.
10. You are never going to have perfect requirements.
[Source: Software requirements – Karl E Wiegers]
1. If you don’t get the requirements right, it does not matter how well you execute the rest of the project.
2. Requirements development is discovery and invention process, not just a collection process.
3. Change happens.Accept to this fact and adapt to change with rationale.
4. The interests of all project stakeholders intersect in the requirement process.
5. Customer involvement is the most critical contributor to software quality.
6. The customer is not always right, but the customer always has a point.
7. The first question an analyst should ask about a proposed requirement is, “Is this requirement in scope?”.
8. Even the best requirements document cannot- and should not – replace human dialogue.
9. The requirements might be vague, but the product will be specific.
10. You are never going to have perfect requirements.
[Source: Software requirements – Karl E Wiegers]