Click here for an overview of the workflow configuration. Click here to see the artifacts used in the configuration. Click here to see the reports used in the configuration. Click here to see the additional review procedures. Click here to see any issues related to the process configuration. Click here for more information about configuring the workflow.

Discipline To top of page

There are no formal changes to the Requirements discipline - it is used as is (see the RUP: Requirements Overview).


Artifacts To top of page

Artifacts How to use Review Details Tools Used/ Templates/ Examples
Incep Elab Const Trans
Glossary Must Must Must Must Formal-
External
Template: Glossary
Requirements Attributes Must Must Must Must Formal-
Internal
Template: Requirements Attributes
Requirements Management Plan Must Must Must Must Formal-
External
Template: Requirements Management Plan
Software Requirements Specification Should Must Must Must Formal-
External
Template: Software Requirements Specification

Supplementary Specification

Should Must Must Must Formal-
External
Template: Supplementary Specification

Use-Case Model

Should Must Must Must Formal-
External
Template: Use-Case Model

Actor

Should Must Must Must Formal-
External
Embedded

Use Case

Should Must Must Must Formal-
External
Embedded

Use-Case Specification

Should Must Must Must Formal-
External
Template: Use-Case Specification

Use-Case Package

Could Could Could Could Informal Embedded
Stakeholder Requests Must Must Must Must Formal-
External
Template: Stakeholder Requests
Use-Case Storyboard Could Could Could Could Informal Embedded in the Analysis Model (see Template: Analysis Model).

Boundary Class

Could Could Could Could Informal  Embedded.
User-Interface Prototype Could Should Could Could Formal-
External
Template: User Interface Prototype
Vision Must Must Must Must Formal-
External
Template: Vision

Notes on the Artifacts To top of page

None

Reports To top of page

Reports How to Use Tools Used/ Templates/ Examples
Actor Could  Template: Actor Report
Use-Case Should - Use for review purposes as needed.

Template: Use Case Report

Use-Case Model Survey Must - Used as final documentation. 

Template: Use-Case Model Survey

Use-Case Storyboard Could Template: Use-Case Storyboard Report

Notes on the Reports To top of page

The Use-Case Model Survey is base lined as part of the Requirements Baseline.

Additional Review Procedures To top of page

None

Other Issues To top of page

None.

Configuring The Discipline To top of page

For guidance on the purpose of, and how to complete, the sections and tables used on this page see RUP Overview: Discipline Configuration.

When configuring the Requirements Discipline help can be found in:

You should also familiarize yourself with:

 

Display Organization Process Web using frames

Copyright  © 1987 - 2001 Rational Software Corporation 

Wylie College Process Web Example
Version 2001.02