Create and manage requirements
Define, manage, and track requirements at all stages of your project, from conception to delivery.
Note: If your project enables version control, you can only view requirements of the current checked-in version. You cannot create or edit requirements.
Requirements overview
Requirements describe in details what needs to be solved or achieved to meet the objectives of your application under development.
Clearly and correctly defining requirements at the front end of a project provides the following advantages:
-
Provides guidelines of what the priorities are to stakeholders.
-
Sets clear expectations among stakeholders.
-
Cuts waste and eliminates unnecessary expenditure.
Create requirement folders
Before you create requirements, you create requirement folders to create a framework of high-level requirements.
Note: To create a requirement folder, you can also create a requirement of the Folder type.
| Create a requirement folder |
To create a new requirement folder:
|
| Create a requirement folder by copy/cut |
To create a requirement folder by copy/cut:
|
| Rename a requirement folder |
To rename a requirement folder:
|
| Delete a requirement folder |
To delete a requirement folder:
|
Create requirements
You can create requirements under any existing requirement folders, or create sub-requirements under any existing requirements.
To create a new requirement:
-
In Details view, select the requirement folder or requirement under which you want to create the new requirement.
-
Click New Requirement (
), and enter the required information.Alternatively, you can hover over the folder or requirement and select More Actions > New Requirement.
Tip: You can also create a requirement by copying or cutting an existing requirement. To copy or cut a requirement, select the requirement, click Copy or Cut, select the requirement folder where you want to add the requirement, and click Paste.
UI Element Description Name Enter a name for the new requirement.
A requirement name cannot include the following characters: \ ^ *
Requirement Type Select a requirement type.
Available options are:
-
Business. A business process requirement. By default, you cannot add coverage to this requirement. -
Folder. A folder for organizing requirements. By default, you cannot add coverage to this requirement. -
Functional. A system behavioral requirement. -
Group. A collection of related requirements. -
Testing. A system verification requirement. -
Business Model. A requirement representing a business process model entity. -
Undefined. An undefined requirement. -
Performance. A system performance requirement.
You can customize the default types and create your own requirement types. For details on customizing requirement types, see Customize requirement types.
Details tab In the Details tab, fill in other requirement fields as necessary.
In Details view, the Name and ID fields are displayed at the top of the entity details.
Click the Name field to switch it to editable mode.
Rich Text tab Describe the requirement in rich text using the HTML editor. Attachments tab Add attachments to the requirements.
See Entity attachments.
-
- Click Submit.
Requirements views
You can work with requirements in either Grid or Details view. From the upper right corner of the Requirements tab, select the view you want.
| View | Description |
|---|---|
Details view
|
Displays a requirements tree in the left panel and requirement folder or requirement details in the right panel. This view is particularly helpful when you want to do the following:
|
Grid view
|
Displays all requirements in a grid. This view is particularly helpful when you want to do the following:
|
Assign requirements to releases or cycles
You can assign a requirement to releases and cycles.
To assign a requirement to releases or cycles:
| From the requirements tree |
|
| From the Details tab |
|
Create test coverage
Create test coverage by linking tests to requirements. In addition to covering requirements at the level of test, you can also cover requirements by test configurations.
Coverage mode
Coverage mode indicates whether a requirement is covered by selected test configurations or all test configurations of a test.
-
All Configurations. If a test, including all its test configurations, is added to coverage, the coverage mode is All Configurations.
-
Selected Configurations. If selected test configurations of a test are added to coverage, the coverage mode is Selected Configurations.
To link tests to a requirement:
-
Select the target requirement. Go to the Test Coverage tab.
-
Click Select to open the Test Plan tree.
-
Select the target tests and click Add to Coverage.
To select multiple tests grouped in the same folder, select the folder and click Add To Coverage.
To select test configurations of a test, select the test, at the bottom of the test plan tree, expand the Test Configurations section, and select target test configurations.
To remove test coverage:
From the test coverage grid, select the test coverage and click Remove
.
To remove certain test configurations:
-
Change the Coverage Mode of the test coverage to Selected Configurations.
-
Expand the Test Configuration Status section, select target test configurations, and click Remove
.
See also:

), and enter a name.
) or Cut (
).
).
