The purpose of this workflow detail is to begin converging on the scope of the high-level requirements by outlining the breadth of the detailed requirements for the system.

Topics

Develop Vision Manage Dependencies Capture a Common Vocabulary Find Actors and Use Cases Business Rule Stakeholder Requests Vision Supplementary Specifications Requirements Management Plan Requirements Attributes Use-Case Model (refined) Use-Case Model Use-Case (outlined) Vision (refined) Glossary (refined) Glossary System Analyst Requirements Managemetn Plan


Description To top of page

The workflow detail addresses:

  • Aligning the project team in their understanding of the system.
  • Performing a high-level analysis on the results of collected stakeholder requests.
  • Refining the Vision to capture the key features that characterize the system.
  • Refining the use-case model to include outlined use cases.
  • Beginning to capture the results of the requirements elicitation activities in a more structured manner.

The activities that focus on problem analysis and understanding stakeholder needs create early iterations of key system definitions including the features defined in the Vision and a first outline of the detailed requirements. In defining the system you will focus on identifying actors and use cases more completely, and expand the global non-functional requirements as defined in the supplementary specifications.
(See also: Guidelines: Going from Business Models to Systems, business use-case model).

Typically, this is primarily performed in iterations during the Inception and Elaboration phases, however it may be revisited as needed when managing scope and responding to changing requirements, as well as other changes in the project conditions.

Related Information To top of page

This section provides links to additional information related to this workflow detail.

Timing To top of page

This work normally begins part-way into each iteration.

Optionality To top of page

Should be performed in each iteration where the requirements will be defined.

How to Staff To top of page

While it encourages team ownership and commitment to have all members of the project team participate in defining the system, this work is primarily coordinated and conducted by staff playing the System Analyst role. Because this work often requires making tradeoff's between multiple requirements to make best use of the finite development resources, diplomacy, negotiation and mediation are important skills for the system analyst conducting this work.

Work Guidelines To top of page

See the Related Information section for additional guidance that will help you in performing this work.



© Copyright IBM Corp. 1987, 2004. All Rights Reserved.

Rational Unified Process   2003.06.13