|
Environment |
The environment discipline focuses on the activities necessary to
configure the process for a project. It describes the activities
required to develop the guidelines in support of a project.
The purpose of the environment activities is to provide the software
development organization with the software development environment (both
processes and tools) that will support the development team.
The following documents describe a method for applying the project
management discipline activities to Rational Analyst Studio tools.
When opening a document template, MS Word may prompt you to update
linked files. If so, click on 'No'. |
RequisitePro models
MoveToDB |
The first zip file contains three ReqPro projects that were used to
take the screen shots in these documents. They unzip to:
- C:\Rational\RequisitePro\Projects\Matter
Transporter- the Matter Transporter
project.
- C:\Rational\RequisitePro\Projects\Dematerializer -
the Dematerializer application.
- C:\Rational\RequisitePro\Projects\Glossary - the glossary of terms.
Simply unzip to your C:\ drive and the project files
will automatically be placed in the correct location.
If prompted for a username, login as guest .. there is no
password.
The second zip file contains two files that you will need in order to
be able to move requirements from a document to the database. Unzip
and move these 2 files to the following directory 'C:\Rational\RequisitePro\RequisitePro\bin\'
[Yes, I messed up my ReqPro installation.]
|
|
Working with styles and properties |
In this presentation you
will learn:
- the purpose of an artifact’s properties.
- how to set the value of a property.
- how to use a property.
- how to create a custom property.
- how to use styles to format a paragraph,
- how to use styles to format individual words.
- how to use styles to format several blocks of text.
- how to use styles to delete text from a document.
|
| Vision template |
This is the document
template that defines the scope and reasons for a new project. Its
purpose is to:
- define the boundaries of the business modeling effort.
- develop a vision of the future target organization.
- gain agreement on potential improvements and new goals of the
target organization.
- describe primary objectives of the target organization.
|
|
Business use case
template |
This is the
document template that details a business use case. It includes:
- a description of the BUC.
- the goals of the BUC.
- the workflow steps of the BUC.
- risks associated with the BUC.
- supporting requirements associated with the BUC.
|
|
A notation for
activity and use case diagrams |
In this presentation you will learn:
- semantics for activity and use case diagrams.
- the different types of use case diagram.
- examples diagrams from Rational Software Modeler.
- what are the different components of an activity and
use case
diagram.
- what are the relationships between the different components on
each diagram.
- what these diagrams are used for.
- how to represent a use case using an activity diagram.
|
|
Introduction to ReqPro |
In this presentation you will learn:
- the different parts of the user interface.
- the commands for managing requirements.
- how to manage a requirement’s properties.
- how to use views to manage several requirements.
- how to manage traceability between requirements.
|
|
Administrators Guide To ReqPro |
In this presentation you will learn:
- how to manage ReqPro projects.
- how to manage ReqPro
documents.
- how to manage ReqPro requirements and their attributes.
- how to manage ReqPro project security.
- how to link ReqPro projects.
|
|
The requirements
management plan template |
This is the document
template that is used to manage your requirements. It defines:
- the organization and responsibilities for requirements on the
project.
- the tools and environment used to manage the requirements.
- requirements configuration management.
- requirements traceability.
- requirement attributes.
- reports to assist management of the requirements.
- requirements change management.
- training and resources needed to manage the requirements.
|
|
The application use case template |
This is the document template that details an AUC. It describes:
- an overview of the AUC.
- the details of the steps of the AUC.
- may include supplementary requirements impacting the AUC.
This is the AUC template
used in the examples. |
|
Use case
storyboard template |
This is the document
template that details a use case storyboard. It describes:
- how the AUC is realized by the application user interface.
- how the application screens are mapped to each other.
- how the screens are realized by the system
objects.
|
| |
Note: Concerning the templates, you may notice that
the templates on this site are missing some standard document
information, such as:
Version History, References, Acronyms and Abbreviations.
Hands-up if you know of anyone that reads this stuff? How many times
have you opened a document and had to wade through umpteen pages of
non-interested information before you actually reach the document
contents?
Version History - If you are serious about maintaining version history,
buy a document versioning tool and maintain the information there. If
you are not using a versioning tool, you are not serious about
maintaining version history.
References - If you must do this, maintain all of you project references
in a separate document and attach as an appendix to each document that
requires it. Better still just put a single hyperlinked reference to
where your references are kept, in the document.
Acronyms and Abbreviations - I maintain these in a separate ReqPro
project and reference the project from within the document. If you are
using ReqWeb, all of your users have access to a view that you may
hyperlink to from within your document. If not using ReqWeb, export a
view displaying the relevant terms and attach it as an appendix. |
| |
The following diagram will show where each of the
environment documents maps to a RUP activity. The mapping is not
1 to 1, and some presentations may encompass several activities. |
