|
Requirements |
The purpose of the Requirements discipline is:
- to establish and maintain agreement with the customers and other
stakeholders on what the system should do.
- to provide system developers with a better understanding of the
system requirements.
- to define the boundaries of (delimit) the system.
- to provide a basis for planning the technical contents of
iterations.
- to provide a basis for estimating cost and time to develop the
system.
- to define a user-interface for the system, focusing on the needs
and goals of the users.
The following documents describe a method for applying the
requirements discipline activities to Rational Analyst Studio tools.
|
|
Example Application Use Case |
This document is an example of a partially
completed application use case template that is used in some of the
exercises in the training material: |
|
Maintaining a glossary with RequistePro |
In this presentation you
will learn:
- why we maintain a glossary on a project.
-
when we maintain a glossary on a project.
-
what is in the glossary.
-
where the glossary is located.
-
how to maintain the glossary entries.
- how to access the glossary from your projects.
|
|
Managing requirements
with a RMP |
In this presentation you
will learn:
- the purpose of the Requirements Management Plan(RMP).
- how a RMP is used to control project requirements.
- the contents of the different sections of the RMP.
- the purpose of the attributes of a requirement.
- the processes used to manage project requirements.
|
|
Working with application use case documents |
In this presentation you
will learn:
- the purpose of the different sections of the AUC document.
- the information that goes into each section.
- when to import an AUC document into
RequisitePro.
- how to review a document that is in RequisitePro,
- how to manage supplementary requirements.
|
|
Managing AUC
requirements with ReqPro |
In this presentation you
will learn:
- how to realize the Requirements Management Plan, with a
requirements management tool.
- what is the difference between a project and an application
requirements repository.
- the difference in the process for managing requirements on a new
application versus managing requirements on an existing application.
|
|
Moving from the
BUC to the AUC |
In this presentation you
will learn:
- what is the difference between a BUC and an AUC.
- the purpose of the candidate AUC.
- a process for transitioning your BUCs into AUCs.
- how to manage traceability between BUCs and AUCs.
- how to trace use cases in ReqPro to use cases in Rational
Software Modeler.
|
|
Using the use case
storyboard template |
In this presentation you
will learn:
- the purpose of the different sections of the Use Case
Storyboard.
- how to populate the Use Case Storyboard.
- how the Use Case Storyboard fits into the analysis process.
|
|
|
The following diagram shows where each of the
requirements documents maps to a RUP activity. The mapping is not
1 to 1, and some presentations may encompass several activities. |
