Workflow Detail: Refine the System Definition
|
The purpose of this workflow detail is to further refine the requirements in order to capture the consensus understanding of the system definition. |
|
|
|
Description
The workflow detail addresses:
- Describing the use case flow of events in detail.
- Detailing Supplementary Specifications.
- Developing a Software Requirements Specification, if more detail is needed,
This workflow detail furthers the understanding of project scope reflected in the set of prioritized product features (often described in the Vision) that it is believed can be achieved by fairly firm budgets and dates. The output is a more in-depth understanding of system functionality expressed in refined, detailed requirements in specification artifacts and outlined behavioral prototypes. The specification artifacts can take the form of detailed use cases and Supplementary Specifications and in some cases a formal Software Requirements Specification may be developed. This work typically starts by reviewing the existing actor definitions and if necessary least briefly describing the actors, then continues with detailing the use cases that have been previously outlined for each actor.
Whenever the requirements specifications are changed, regular reviews and updates to the associated requirements attributes should be done as shown in the Manage Changing Requirements workflow detail.
Related Information
This section provides links to additional information related to this workflow detail.
Timing
This work is normally started part way into the iteration and continues until iteration end.
Optionality
Should be performed in each iteration where the requirements will be further refined.
How to Staff
The Requirements Specifier role is primarily involved in performing this work. The most important skills required to conduct this work include information elicitation & communication. Staff responsible for specifying requirements should be skilled in expressing themselves in writing, and need to develop a good understanding of the problem domain.
While most of the resource for this work will be expended in Elaboration, some resource will typically need to be allocated to this work from late Inception through Construction.
Work Guidelines
Although much of the work is done individually, frequent reviews (i.e. walk-throughs) should be performed to calibrate work products across team members and ensure the team is in sync.
See the Related Information section for additional guidance that will help you in performing this work.
