6.3. Requirements

6.3. Requirements
	Chapter 6. Define

6.3.1. Overview Page
6.3.2. Details Page

A requirement is a predefined condition to be fulfilled that specifies and describes the properties or performance to be achieved by a product, a process or a system. This chapter shows how to create and edit requirements.

6.3.1. Overview Page

6.3.1.1. Creating a new Requirement
6.3.1.2. Action
6.3.1.3. Bulk Actions
6.3.1.4. Table Operations
6.3.1.5. Remote Synchronization

The overview page displays all existing requirements in the selected project in a table. New requirements are created here.

Figure 6.19. The “Requirements” Page

The table shows the following values:

ID	Assigned automatically.
Additional Information	A tooltip appears when the cursor is placed over the icon shown here.
Revision	The revision of the requirement.
Name	The name of the requirement.
Priority	The priority of the requirement. Possible values are Low, Medium, High.
State	The state of the requirement. Possible values are Locked, Approved, Draft and Skip.
Test Cases	The number of test cases assigned to this requirement.
Action	The executable actions.

Name, Priority and Status can be edited directly in the table rows.

6.3.1.1. Creating a new Requirement

By clicking on the button New a new empty table row will appear. Now, Name, Priority and Status can be defined.

With Save the new requirement is created and saved. The ID of the requirement (R00001) is automatically assigned by Klaros-Testmanagement. Click on the ID R00001 to get to the detail page of the requirement.

With New several table rows can be created and edited at the same time. Only when clicking on Save the data is stored in the database.

With Discard all changes are undone.

	Unsaved Changes
	All rows marked with red IDs contain changes that have not yet been saved.

6.3.1.2. Action

The following actions can be performed in the action column:

Edit
Duplicate
Open print view
Delete

If a requirement has been deleted, it is initially marked with a deletion marker and is only visible to administrators. For deleted requirements, the following actions are available instead of Delete:

Restore (only Administrator)
Irrecoverably remove the requirement from the database

6.3.1.3. Bulk Actions

On the Requirement page, one or more requirements can be selected for bulk actions. Bulk actions are described in Section 5.2.3.1.5, “Bulk Actions”.

The following bulk actions are supported for requirements:

Edit
Duplicate
Create new Revision
Open print view
Delete
Restore (only Administrator)
Irrecoverably remove the requirement from the database (only Administrator).

For additional information, see Section 5.2.3.1.5, “Bulk Actions”.

6.3.1.4. Table Operations

The following operations can be performed in the line above the table on the right:

Categorize
Filter / Sort
Show all / Only active (only Administrator)
Search
Export
Column selection

All operations are described in detail in Section 5.2.3.1, “Overview Page”.

6.3.1.5. Remote Synchronization

If the active project is connected to a remote requirement management system, editing of requirements is disabled for all users. An icon will be shown on the upper right side of the requirements list screen. Clicking on it will start a background synchronization of all requirements from the requirement management system to the project.

Figure 6.20. The “Requirements Page” Using Remote Synchronization

6.3.2. Details Page

6.3.2.1. Actions
6.3.2.2. Overview
6.3.2.3. Properties
6.3.2.4. User-Defined
6.3.2.5. Attachments
6.3.2.6. Iterations
6.3.2.7. Test Cases
6.3.2.8. Revisions
6.3.2.9. Results
6.3.2.10. Changes

Each requirement has its own detail page with several additional tabs. Clicking on the ID of the respective requirement or on the icon on the right in the action column takes you to the tab that was selected last. When called for the first time, this is the Overview tab.

The following tabs are available: Overview, Properties, User Defined, Attachments, Iterations, Test Cases, Revisions, Results and Changes.

6.3.2.1. Actions

On the detail pages there are more icons in the upper right corner. The following actions can be performed here:

Synchronize	Synchronizes the local requirement with the external source.
Open external link	Shows the requirement in the external source.
Open print view	A print-ready view of the requirement can be created here. With a click on the icon this opens in a new browser tab. Print views are described in detail in Section 5.2.3.2.1, “Print Pages”.
Create Bookmarks	Requirements may be linked to from outside of Klaros-Testmanagement using the link on the icon. By clicking on the icon this link will be copied to the clipboard. Weitere Informationen hierzu finden Sie unter Section 5.2.3.2.2, “Bookmarks”.
Browse	Use the green arrows at the very top right to switch between the requirements present on the previous page.

6.3.2.2. Overview

Figure 6.21. The “Overview” Tab

The following values are displayed on the overview tab:

Compliance	The conformance rate shows how many test cases assigned to this requirement were performed with the result Passed.
Coverage	The coverage rate shows how many test cases assigned to this requirement have already been executed.
Automation Rate	The automation level indicates the percentage of test cases that can be executed automatically.
Priority	The priority of the requirement. Possible values are Low, Medium and High.
Status / External Status	The status of the requirement. If the requirement is synchronized from an external system, the externally managed status is displayed here. Otherwise, the possible values are Locked, Approved, Draft and Skip.
Compliance History Chart	This diagram shows the compliance and coverage rate of this requirement for the combination of revision, system under test and test environment set here. This graph shows how the conformance and coverage for this requirement has changed since it was defined. The timeline is automatically adjusted to reflect the available information.

In the lower area there is a table with the overview of the last executed test cases.

6.3.2.3. Properties

In this tab ( Figure 6.22) the following attributes of the requirements are displayed and can be edited if the user has the appropriate permission:

ID	Assigned automatically.
Name	The name of the requirement.
Priority	Die Priorität der Anforderung. Possible values are Low, Medium and High
Status / External Status	The status of the requirement. If the requirement is synchronized from an external system, the externally managed status is displayed here. Otherwise, the possible values are Locked, Approved, Draft and Skip.
Summary	The brief summary of the requirement.
Description	The detailed description of the requirement.

Figure 6.22. The “Properties” Tab

6.3.2.4. User-Defined

You can create your own fields to meet individual requirements. For further information please refer to Section 5.2.3.2.4, “User Defined Properties”.

6.3.2.5. Attachments

You can add any files as attachments to a requirement. For more information, see Section 5.2.3.2.6, “Attachments”.

6.3.2.6. Iterations

If you want to associate the requirement with an iteration, click the Assign button and select one or more requirements.

6.3.2.7. Test Cases

The coverage rate of requirements is tested by test cases. Test cases can be linked to requirements in the Test Cases tab. The test results of linked test cases count towards the coverage and compliance rates of the requirement.

Figure 6.23. The “Test Cases” Tab

Test cases can be assigned to the requirement by clicking the Assign button. This opens up a dialog, where multiple test cases can be selected at once.

The following bulk actions are supported for requirements:

Remove

The detail page of a test case shows a list of all requirements that are covered by it, as shown in section Section 6.7.2.7, “Revisions”.

6.3.2.8. Revisions

Requirements may exist in different revisions. For more information, see Section 5.2.3.2.5, “Revisions”.

Figure 6.24. The “Revisions” Tab

6.3.2.9. Results

The results tab is further divided into a Test Runs, Test Case Results and a Test Suite Results tab, showing the test results related to this requirement as described in Section 5.2.3.2.7, “Test Runs and Results”.

6.3.2.10. Changes

The tab Changes shows the change history of this requirement.

For a detailed description of the Changes view, see Section 5.2.3.2.8, “Change History”.


6.2. Iterations		6.4. Test Environments