Tool Mentor: Managing Dependencies Using Rational RequisitePro«

Purpose

This tool mentor describes how to use Rational RequisitePro to manage dependencies by using requirement attributes and traceability.

Related Rational Unified Process activity:

In the Requirements Workflow:

• Manage Dependencies

Overview

RequisitePro enables you to create and maintain a clear organization of requirements which groups them according to user-defined attributes, such as function, priority, risk, cost, or other factors. In addition, you can establish hierarchical relationships that represent requirements in logical parent/child groups. Finally, you can create a traceability relationship between two requirements that establishes dependency from one requirement to the other.

Click one of the following to examine these requirements management concepts and procedures in more detail.

• Organize Requirements
• Create Requirement Hierarchies
• Create Requirement Traceability
• Query Requirements

Functional organization can be expressed in requirement types. A requirement type is simply a class of requirements that enable teams to organize large numbers of requirements into meaningful and more manageable groups. Establishing different types of requirements in a project helps team members classify requirements and communicate more clearly.

Usually, one type of requirement can be decomposed into other types. For example, business rules and vision statements typically include high-level requirements from which teams derive user needs, features, and product requirement types. Use cases drive design requirements that can be used to define software requirements. Test requirements are derived from the software requirements and break down into specific test procedures.

When there are hundreds, thousands, or even tens of thousands of requirements in a given project, classifying requirements into types makes the project more manageable. Using RequisitePro, you can create requirements of a given type in a requirements document or directly into the project database. Each requirement type has specific attributes that are unique to that requirement.

Tool Steps

To create requirement types:

1. Select Project > Open, select the project and check the "Exclusive" checkbox. (The project must be opened in exclusive mode to create new requirement types). Click OK.
2. Select Project > Properties. Click the Requirement Types tab. Click Add. Enter the requirement type information (name, description, tag prefix, color and style of the requirement format). Click OK.

To create requirements in a document:

1. In the document, select the text to define the requirement.
2. In the Word Workplace, do one of the following:
   • right-click and select Create Requirement.
   • click RequisitePro > Requirement > Create.
     The Requirement Properties dialog box appears.
3. Click the tabs to enter the appropriate information to define the requirement. Click OK.

To create requirements in the Views Workplace:

1. In the Views Workplace, open an attribute matrix based on the requirement type for the requirement you want to create.
2. Do one of the following:
   • click in the field marked <Click here to create a requirement>.
   • click Requirement > Create.
     The Requirement Properties dialog box appears.
3. Type a description of the requirement.
4. Press the Tab key to move across the matrix. Enter attribute values, as needed, in the matrix.
5. Tab through the end of the matrix or click elsewhere to enter the requirement.

You can also open an existing requirement in an attribute matrix by double-clicking on its description or selecting the requirement and clicking  Requirement > Properties. The Requirement Properties dialog box appears. On the General tab, you can modify the text for the requirement. Click the Attributes tab and select the appropriate values for the attributes.

For More Information

Refer to the following help topics in the RequisitePro online help:

• Creating and modifying requirement types (Index: requirement types > creating)
• Creating requirements in a document (Index: requirements > creating)
• Creating requirements in a view (Index: requirements > creating)

Manage dependencies in hierarchical relationships. Hierarchical requirement relationships are parent-child relationships that reflect a logical grouping between requirements. These associations provide helpful tools for organizing requirements.

Use hierarchical relationships to subdivide a general requirement into more explicit requirements. Parent requirements are upper-level, more general requirements; child requirements are lower-level, more specific requirements. Each child requirement can only have one parent, but a requirement can be both a parent and a child.

Note: Hierarchical requirement relationships should not be confused with traceability relationships. This latter represents relationships often
between different types of requirements, like software and test requirements, while hierarchical relationships group requirements of the same type, at the same level of the requirement traceability tree

To create child requirements in a document:

1. In the requirements document, select the information to define the requirement.
2. In the Word Workplace,  do one of the following:
   • right-click and select Create Requirement.
   • click RequisitePro > Requirement > Create.
     The Requirement Properties dialog box appears.
3. Click the tabs and enter the appropriate information to define the requirement.
4. On the Hierarchy tab, select a parent from the Parent list. If the parent is not displayed in the list, select <choose parent...>. Click OK.

To create child requirements in the Views Workplace:

1. In the Views Workplace, open an attribute matrix based on the requirement type for the requirement you want to create. Select the requirement that you want to be the child's parent.
2. Click Requirement > Create Child. Note: You can create a child requirement in the Views Workplace only if the selected requirement (which will become the child's parent) is also located in the Views Workplace (i.e., it is not a document-based requirement).
3. Type a description for the child requirement.
4. Press the Tab key to move across the matrix. Enter attribute values, as needed, in the matrix.
5. Tab through the end of the matrix or click elsewhere to enter the requirement.

For More Information

Refer to the following help topics in the RequisitePro online help:

• Hierarchical requirement relationships overview (Index: hierarchical requirements>overview)
• Creating child requirements in documents (Index: hierarchical requirements>creating child requirements)
• Creating child requirements in a view (Index: hierarchical requirements>creating child requirements)
• Reparenting a hierarchical requirement (Index: hierarchical requirements>overview)

Manage dependencies with traceability. As implied in the description of requirement types, no single expression of a requirement stands alone. The process of decomposing user needs into derived requirements implies relationships between high-level expectations and subsequent artifacts needed for implementation and validation. In effect, one traces to many or vice versa.

For example, stakeholder requests are related to the product features proposed to meet them. Product features are traced to individual requirements for specific functional behavior. Test cases are traced from the requirements they verify and validate.

In order for teams to determine the impact of changes and feel confident that the system conforms to expectations, these traceability relationships must be understood, documented, and maintained. Traceability is an essential tool for accommodating change and ensuring complete coverage. Establishing clear requirement types can help make traceability easier to implement and maintain.

Tool Steps

To create requirement traceability:

1. In the Views Workplace, click File > New View. Select the Traceability Matrix view type. Select one requirement type for the rows and one for the columns of the matrix.
2. Select a cell that intersects the two requirements for which you want to create a traceability relationship. (Use a multiple select action to select multiple cells.)
3. Click Requirement > Trace To or Trace From. (Or, right-click on the cell and select Trace To or Trace From.)

For More Information

Refer to the following help topics in the RequisitePro online help:

• Trace to/trace from overview (Index: trace to/trace from relationship>overview)
• Creating traceability relationships in the Views Workplace (Index: traceability feature>creating relationships in traceability matrix)

Suspect Relationships. A relationship between requirements becomes questionable or suspect if RequisitePro detects that one of the requirements in the relationship has been modified. If a requirementÆs text is modified, all direct relationships to and from it become suspect. Additionally, you can define attributes that, when modified, cause traceability relationships to become suspect.

Query to retrieve and organize requirements by attribute values or traceability. The RequisitePro query features provide a method for filtering and sorting requirements in views by limiting the values of one or more attributes or by limiting traceability, and specifying the order in which the filtered requirements display. Filtering restricts the information being displayed. Sorting determines the order in which information is displayed. For example, in an attribute matrix, you may want to use filter criteria to view only those requirements assigned to you; you can also use sorting criteria to arrange the requirements from highest to lowest priority.

RequisitePro allows you to save and rerun queries with user-defined views in the Views Workplace. You can dynamically rerun queries to update a requirements collection, or refresh the returned data with updated values at any time.

Tool Steps

To create a query:

1. In the Views Workplace, open an attribute matrix, traceability matrix, or traceability tree view.
2. Click View > Query [Row/Column/Root] Requirements. If you have not yet added any query criteria, the Select Attribute dialog box appears.
3. Select the attribute and attribute value that you want to use to query, and click OK.
4. For list-type attributes, select one or more values. The logical operator OR is assumed for list-type attributes. For entry-type attributes, select an operator and specify the values.
5. To create compound queries (with multiple attributes), click Add and select additional query criteria.
6. Click OK.

To save a view:

1. In the Views Workplace, click File > Save View.
2. Type a name for the view.
3. Click either:
   Project-wide, which saves the view so other users can open it; or
   Personal, which saves the view so that only the user who created the view can open it.
4. Click OK.

For More Information

Refer to the following help topics in the RequisitePro online help:

• Creating views (Index: Views Workplace > saving views)
• Creating queries (Index: queries > creating)
• Modifying queries (Index: queries > modifying)

Rational Unified Process