Development Case: Requirements
For an high level overview of the activities done in the Requirements Discipline, see the Requirements Workflow Detail diagram in the organizational Development Case. This page describes the deviations to the Requirements Discipline Configuration in the Requirements section of the underlying Organizational Development Case.
Topics
Artifacts used 
Here is a list of artifacts this project must produce for the Requirements Discipline. The Review Details indicate the formality in the review procedure for a particular artifact. To see the corresponding artifact list for the organizational process, follow this link.
| Artifacts |
Deliverables |
Review Details | Tools used | |||
| Incep | Elab | Const | Trans | |||
| Glossary | X | X | X | Formal-Internal | Microsoft Word | |
| Vision Document | X | X | X | Formal-External | Microsoft Word | |
| Use Case Model | X | X | X | Formal-External | Rational Rose | |
| Supplementary Specifications | X | X | Formal-External | Microsoft Word | ||
| User Interface Prototype | X | Formal-External | MS Visual Basic | |||
Notes on the Artifacts
- The Use Case Specifications are considered part of the Use Case Model, hence not listed as a separate artifact.
- This project will not produce a separate Requirements Management Plan, we use Wylie College Standard Requirements Management Plan as is.
Reports
| Reports | When to produce | Tools Used |
| Use Case Model Survey | For every baselined version of the use-case model | Rational SoDA Report Generation |
Additional Review Procedures
Other Issues
None.