 |
 |
|
 |
 |
 |
 |
|
Rational
Requirements Frameworks are an industry first for the requirements
management market. A requirements framework provides you a set of
pre-configured analysis artifacts, namely for use in Rational Rose
and Rational Requisite Pro. Rational reuse maven, Grant Larsen,
walks you through this downloadable and reusable framework in this
landmark item. |
|
 |
 |
 |
|
This is a complete
Requirements Management Plan for a large real-life project. It
contains complete descriptions of requirement types, attributes
and their values, artifacts, and RequisitePro view descriptions.
This is a good place to look to see how complete one can make a
requirements management plan, even if you do not plan on making
yours this large. |
|
 |
 |
 |
|
A requirements
framework saves time not only for front-end business modeling and
requirements, but also throughout the development lifecycle, by
giving architects, designers, and testers a head start, too.
Download the Rational Net Market Edition Requirements Framework to
check out a Rational Rose model that holds the business model and
the use case model, and a Rational RequisitePro project that
contains requirements and documents that detail the business and
system use cases. Originally published in The Rational Edge. |
|
 |
 |
 |
|
In a RUP environment,
it is primarily up to the software architect to consider technical
risk along with other economic, teaming, and political factors,
and then decide exactly what functionality to develop within each
iteration. Architects can use the BAR technique provides extra
control in situations where it's really needed for the small cost
of an extra requirement type and some up-front planning. Read this
Rational Edge article for the specifics. |
|
 |
 |
 |
|
If you have a question
about some aspect of running Rational RequisitePro, you may find
it answered here. We've compiled frequently asked questions from
the Tech Notes on the Rational Software site about such topics as
working with documents, configuring databases, and managing
requirements in RequisitePro. RequisitePro/ClearCase integration
issues are also covered. |
|
 |
 |
 |
|
Running Rational
RequisitePro is simple and straightforward, but if you get into
trouble, you may be able to find help here. This list of
frequently encountered problems was compiled from the Tech Notes
on the Rational Software site. |
|
 |
 |
 |
|
Requirements management
is critical to the success of today's software projects. This
paper describes a use-case-driven approach for specifying and
managing software requirements. |
|
 |
 |
 |
|
This whitepaper
explores the traceability strategies available to organizations
adopting use case modeling techniques as part of their
requirements management strategy. |
|
 |
 |
 |
|
Like art, software is
subject to bursts of creativity and individual genius rather than
teamwork and engineering discipline. Key in keeping increasingly
complex software projects under control is the implementation of
tighter requirements management. Alan Davis and Dean Leffingwell
discuss how to bring your requirements under control. |
|
 |
 |
 |
|
AnalystStudio is a set
of business modeling and requirements management tools. This paper
focuses on using these tools to bridge the communication gap
between business modeling and system design. |
|
 |
 |
 |
|
How does a user go
about versioning a Rational RequisitePro project and making a
baseline? This paper describes the purpose and major user steps
required to perform the key baseline functions. |
|
 |
 |
 |
|
Create Test Cases in TestManager from Test
Requirements in ReqPro. This tool also looks to see if you've
defined tracebility links; e.g. from Test Case Requirements to Use
Cases. These "Traces To" will be added as "Test
Inputs" to Test Cases in TestManager. |
|
 |
 |
 |
|
The
RoseReqproBuilder2000v32 add-in allows users to create a
RequisitePro project structure using the UML and automatically
populate requirement types (including attributes), and document
types in a blank RequisitePro project. |
|
 |
 |
 |
|
The TraceToolSet
includes tools that allow a user of Rose and RequisitePro to
establish and maintain traceability between DESIGN requirements (a
special requirement type) and Rose Elements (classes, operations,
diagrams, etc.) |
|
 |
 |
 |
|
This script populates a
designated attribute of each requirement of type A with the text
(or name) of the requirement(s) of type B that trace to (or from)
the requirement. |
|
 |
 |
 |
|
This is a VisualBasic
application that periodically walks through all requirements in a
Rational RequisitePro project and sends an e-mail to discussion
participants when a requirement has changed. Download and find out
how to install it here. |
|
|
 |
|