Tip:
Highlight text to annotate it
X
Video 1, How are requirements represented in RRC? This video explains how requirements
and information about requirements are represented in IBM Rational Requirements Composer, v3.0.1.1.
The topics addressed include: Artifacts and Artifact Types, Attributes and Links, and
Artifact History.
This project, Learning Project-Use Cases was migrated from RequisitePro to Rational Requirements
Composer. In Rational Requirements Composer, requirements are stored or represented as
artifacts. Artifact is a general term for objects that are stored within a repository.
An artifact in Requirements Composer can be an individual requirement, such as a particular
Product Feature requirement.
Or, an artifact can be a requirements-related object, such as a business process diagram,
an image, storyboard, or a document. In the project migration, Requirements in the RequisitePro
project were converted to artifacts in the Requirements Composer project. Requirements
documents in the RequisitePro project were also converted to artifacts.
As requirements in RequisitePro are organized in a project within packages, artifacts in
Requirements Composer are organized in folders. Folders are actually filters. They provide
a visual way to organize project artifacts. When you migrate a RequisitePro project, the
package structure is preserved as a folder structure in Requirements Composer.
When you select a folder, you view requirements artifacts filtered by the folder on the View
All Artifacts page.
The initial view of the View All Artifacts page is similar to the Attribute Matrix view
in RequisitePro. Here, you can create different views of the requirements and requirements
related artifacts.
You can collapse the sidebars to view more information in the list of artifacts.
Notice that as in RequisitePro, each artifact has a name and a unique identifier, which
is analogous to a tag in RequisitePro. Just as requirements in RequisitePro have a requirement
type, artifacts in Requirements Composer are based on defined artifact types.
The artifact types are defined at the project level, just like Requirement Type and Document
Type in RequisitePro. Certain artifact types are created automatically when you use a template
to create a project. Project administrators can add custom artifact types.
When you create an artifact, you must specify the artifact type.
As in RequisitePro, artifacts have associated attributes that are defined by attribute type.
Some attributes are system generated; others can be set by the user.
You can customize the columns in the list on the View All Artifacts page to view specific
attributes and link type relationships. For example, you can add a column to the grid
to easily see the Priority assigned to these Product Features.
You can also view information about an artifact by hovering over it. .
Notice that you can see the content of the artifact and its location.
And, you can see the artifact�s associated attributes and attribute values. Notice that
the RequisitePro requirement tag is retained as an attribute of the artifact in Requirements
Composer.
Finally, you can see any links that this artifact has to other artifacts. In Requirements Composer,
links are used to create relationships between artifacts just as �Parent/Child� and �Trace
To/Trace From� links do in RequisitePro. If you are working on requirements in the
context of a Collaborative Lifecycle Management project, the links may be to Development or
Test artifacts.
These links allow you to navigate between related artifacts.
You can open an artifact by clicking its name on the View All Artifacts page.
The artifact opens in the Artifact Editor.
Notice that the artifact content displays in a window below the unique identifier and
the artifact Name. The right sidebar contains information about the artifact, including
its attributes, comments, and links. The information contained in the right sidebar is the information
that you would see in Requirement Properties in RequisitePro.
In RequisitePro, this Product Feature requirement, "Search by multiple criteria", was located
in a Vision document, which was a Microsoft Word document. As a result of the migration,
the requirement was converted to a stand-alone artifact in Requirements Composer. The Vision
document was converted to a document artifact. The new Search by multiple criteria artifact
maintains a relationship with the migrated rich-text Vision document as an embedded link
in the document.
If you click the link, you navigate to the Vision document and can view the embedded
requirement text.
You can view information about the embedded artifact from within the Vision document artifact.
You can maximize and minimize embedded artifact content.
And you can navigate back to the embedded artifact.
Notice that other requirements documents that were in the RequisitePro project were converted
to rich-text document artifacts in Requirements Composer.
Individual requirements that were located within those documents are now individual
requirement artifacts that are represented as embedded links in the document.
You can view the history of an artifact by clicking the Open History icon. In RequisitePro
you view this history in requirement Properties.
Each time you save an artifact, Requirements Composer creates a revision. You can view
the details of changes that were made to an artifact over time, or you can restore a previous
version.
When a RequisitePro project is migrated to Requirements Composer, the first revision
contains history information.
A second revision contains the artifact content.
For requirements located in documents, a third revision is created that shows the rich text
of the embedded artifact in the document artifact.
From within the Artifact Editor, you can navigate back to the View All Aritifacts page by using
the breadcrumb.