Status View
The status view of the requirements structure browser shows administrative
data about the requirements. This is the default view.
The left side of the Requirements table consists of a navigation tree
that shows the selected requirement as the top node. This node can be
expanded to view sub requirements, which can also be expanded until there
are no further sub requirements. You can click on any requirement name
to view the Properties page of that requirement.
The right side of the Requirements table contains the following column
details for each requirement:
Status. Shows an icon depending on the lifecycle
state of the requirement:
Propose
Approve, Validate, Review
Release
Obsolete
Active Engineering Change. The icon is present when
the object is related to an active Engineering Change (EC) that is not
in the Complete, Rejected or Closed state. For details about ECs, see Working with Engineering Changes.
Higher Revision. The icon is present when
a higher revision of the requirement exists.
Relationship Type. The type of relationship
between the child requirement and its parent. For example, a child might
have a "Derived Requirement" or "Sub Requirement" relationship.
Status. The status of the relationship.
Type. The name that defines the type of requirement:
requirement, customer requirement, or user requirement.
Title. A descriptive identifier for the requirement.
Owner. The person who is currently responsible
for the requirement. This can be edited within the cell in Edit mode.
State. Current state of the requirement in
its lifecycle.
Priority. How important the requirement is:
Low, Medium, or High priority.
Difficulty. How difficult the requirement would
be to implement: Low, Medium, or High.
Classification. The user classification of
the requirement: None, Functional, Non-functional, or Constraint. Structure Effectivity. The effectivity defined for this object. You can edit the effectivity in this cell in edit mode. See Edit the Effectivity. Item Effectivity. Not used.
Actions in the Requirements Structure Browser
This section describes actions on the Requirements Structure Browser for any view.
Use the Actions menu or page toolbar to work
with the requirement:
- Create New. Click to add one of the following
objects to the requirement:
- Add Existing. Click to connect one of the
following types of existing objects to the selected requirement:
- Reference Document
- Requirement
- Specification
- Test Case
- Use Case
The Search page opens, where you can define criteria to search for objects
that currently exist in the database. After you select one or more objects
in the search results page, they will be connected to the context object.
See Running a Search.
- Structure Content Editor. Click to open the requirement
in the Structure Content Editor. See Structure & Content Editor
- Documentation Structure. Click to open the
requirement in the Requirement Documentation Structure Browser. See Using the Requirement Structure Browser.
- Subscribe. Click to select the events for
which you would like to be notified for the selected requirement(s).
See Working with Subscriptions.
- Revision. Click to create revisions for one
or more selected objects. See Creating Requirement Revisions.
- Remove. Click to removes the relationship
between all checked items and the parent. It does not delete the items
from the database.
- Delete. Click Delete > Selected
Objects to delete only the selected objects, or click Delete
> Delete Selected Objects and Children to recursively
delete the selected object and its children.
If there is a failure during the delete operation, the Delete Report is
displayed, which shows how many objects were deleted along with details
about which objects could not be deleted. For the rules that are checked
before an object is deleted, see Object Deletion Rules.
Edit Commands
This section describes the edit options available in all views.
To edit the details of a requirement, click the Enable Edit button on the toolbar. Click the Edit
button and select one of the following options: Undo. Reverts the current changes for the selected
row to the previous condition. A form opens for confirming the undo.
If a row was edited using cut and paste, then undo must be applied to
both rows in order to fully reverse the operation. Select undo for the
pasted row, green, and then the cut row is displayed in red strike-through.
Cut. The selected row is copied and marked
for disconnect with a red strike through. Used with the paste commands
to move one or more rows to a new location.
Copy. Copies the content a selected row(s)
for pasting to another location. You can use copy and paste to replace
a cut row, which is indicated with red strike-through.
Paste As Child. Pastes cut, or copied, row(s)
beneath the selected row as a child. Child rows are indented beneath
the parent. The pasted content is highlighted green. Multiple rows can
be pasted.
Paste Above. Pastes a cut, or copied, row(s)
above the selected row as a sibling, at the same level. The text in the
pasted rows is highlighted green. Multiple rows can be pasted.
Paste Below. Pastes cut, or copied, row(s)
below the selected row as a sibling, at the same level. The text in the
pasted rows is highlighted green. Multiple rows can be pasted.
Content View
The Content view is the only view available for candidate
requirements under a model.
The left side of the table consists of a navigation tree that shows
the selected product or requirement as the top node. This node can be
expanded to view sub requirements, which can also be expanded until there
are no further sub requirements. You can click on any requirement name
to view the Properties page of that requirement.
The right side of the Requirements table contains the following column
details for each requirement:
The right side of the table contains the following column details
for each requirement:
Relationship Type. The type of relationship
between the child requirement and its parent. For example, a child might
have a "Derived Requirement" or "Sub Requirement" relationship.
Status. The status of the relationship.
Type. The name that defines the type of requirement:
requirement, customer requirement, or user requirement.
Title. A descriptive identifier for the requirement.
Priority. How important the requirement is:
High, Low, Medium, Pre-assigned, or Urgent priority.
Difficulty. How difficult the requirement would
be to implement: Low, Medium, or High.
Classification. The user classification of
the requirement: None, Functional, Non-functional, or Constraint. Structure Effectivity. The effectivity defined for this object. You can edit the effectivity in this cell in edit mode. See Edit the Effectivity. Item Effectivity. Not used.
Each requirement entry has a row that describes the user or system
needs.
Use the Actions menu or page toolbar to work
with the requirement. See Actions in the Requirements Structure Browser.
WhereUsed View
The WhereUsed view shows where the requirement is used. This
includes: all decisions pertaining to the requirement/requirement relationship
or the requirement object, the specification in which the requirement
is used, and any requirements to which this requirement is linked.
The right side of the table contains the following column details
for each requirement:
Relationship Type. The type of relationship
between the child requirement and its parent. For example, a child might
have a "Derived Requirement" or "Sub Requirement" relationship.
Decisions. Any decisions involved in the relationship.
Type. The name that defines the type of requirement:
requirement, customer requirement, or user requirement.
Specifications. The specifications that contain
this requirement.
Decisions. The decisions that are linked to
this requirement.
Other Requirements. Any other requirements
that are linked to this requirement. Structure Effectivity. The effectivity defined for this object. You can edit the effectivity in this cell in edit mode. See Edit the Effectivity. Item Effectivity. Not used.
Use the Actions menu or page toolbar to work
with the requirement. See Actions in the Requirements Structure Browser.
|