Gathering, analyzing, documenting, and
controlling a project's requirements are key to the project's success.
Delighting the customer with the end product requires clearly understanding what
the customer wants and needs from the outset. Careful and thorough study
of the requirements is necessary. This is accomplished by various means,
not least of which is the customer interview process. Regardless of how
effectively the initial requirements have been collected, analyzed, and
documented, there will be change. It is critical to the successful completion of
a project that requirements changes be a controlled activity.
At the end of a project, once measure of success is
that all requirements were correctly implemented. From the
customer's perspective the project is successful with the deliverable that is
on-time, in-budget, and fulfills all requirements. From the provider's
perspective, add to these criteria that only the agreed upon requirements were
fulfilled. Extras that consume project resources clearly come at a cost.
Requirements-based testing is a method by which the
customer and the provider can agree on project exit criteria: the
deliverable meets the requirements.
Collection, analysis,
documentation, and management of requirements.
Use
cases and UML.
Sequence diagrams
Requirements control process