Requirements Management
« Go back
Requirements are the business-oriented documentation of process details. Use cases and scenarios are an exceptionally effective means to capture completely specified business-oriented requirements in a way that flows directly into technical analysis & design.
An example would be a use case "Purchase an airline ticket". Scenarios might include:
- Purchase over the phone
- Purchase using the internet
- Purchase using mobile devices
- Purchase at an airport ticket counter
Scenarios typically define requirements in terms of an action and a response. Example:
- Action: select origin and destination cities and dates of travel
- Response: available flights are presented
It is imperative that all business rules and exceptions be documented. Business rules may center around pricing and exceptions would include an incorrect or rejected credit card.
It is important to note that business requirements do not include references to databases, tables, queries, or other implementation details.
With inputs, outputs, rules, and exceptions defined, technical implementation may begin and direct traceability to requirements established.
Other Links
