Scribd
Upload
7 views

Requirement Overflow

Uploaded by

dummytester500
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views

Requirement Overflow

Uploaded by

dummytester500
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Requirement workflows

A Requirements workflow is a state transition model in which you define the state that
artifacts of a specified type can be in and the actions that users can select to move these
artifacts from one state to another. You can find topics that are in a specific state by creating
a filter.

You can use the default workflow that comes with the Requirements Management (RM)
application or you can create your own custom workflows.

In the default workflow, an artifact begins its life cycle in the New state, but users can
select actions that move the artifact to In Progress, Under Review, Approved, Rejected,
and Complete. The following diagram shows all the actions and states in the default
workflow:

You can use the default workflow as is, or you can modify it for your particular needs.

Associating a workflow with an artifact type

Before you can use the default workflow or a custom workflow, you must first associate the
workflow with an artifact type. To make this association:

1. Click Administration > Manage Project Properties.


2. In the Artifact Type tab, click an artifact type.
3. Select a workflow in the Workflow field.

After a workflow is associated with an artifact type, users with the proper permission can
select actions that move artifacts through the states that are defined in the workflow.

Creating or modifying workflows


You can create or modify a workflow in the workflow editor. To open the workflow editor,
click Administration > Manage This Project Area > Requirements > Workflows.
The Requirements - Workflows window appears with on-screen instructions on how to
create a workflow.

Using Workflows

After a work flow is created and is associated with an artifact type, users with the proper
permission can use workflows by changing the state of artifacts in the artifact editor and in
the Artifacts window.

To change an artifact state in the artifact editor, open the artifact in the artifact editor,
click Edit, and in the Overview section of the sidebar, select a state in the State field, as
shown in this example:

To change the artifact state in the Artifacts window, first configure the Artifacts window to
display the State column, and then select a state from the State drop down menu, as shown
in this example:
Artifacts are deployed on nodes and specify the physical pieces of information that
the deployment and operation of a system uses or produces. Artifacts can be supported
for deployment on several kinds of nodes. In diagrams, compartments display information
about the attributes and operations of the artifact.

Tip: You can create a filter that displays artifacts that are in a specific state, as shown in this
example:

Workflow Permissions

By setting permissions on workflow actions, you can control which user roles can move or
transition an artifact to a particular state. To set permissions for workflow actions:

1. From the Administration menu, click Manage this project area.


2. Click the project name.
3. Click Permissions.
4. Select a role.
5. Expand Modify Requirements Resources > Save artifact > Modify
artifact > Trigger a workflow action and under the work flow name, click either
the Grant access button or the Revoke access buttons for a particular action.

Note: You can also set permissions that define which roles can modify artifact content,
attributes, and tags in each state of a workflow.

You might also like