CLOUD | DATA CENTER AND SERVER
Coverage View
Overview
The Coverage View provides an overview of project requirements or subsets of requirements from the point of view of completeness. The view helps answer questions such as how well high-level requirements can be traced to lower-level requirements, or other types of issues such as test cases. It helps identify gaps in coverage that may require attention.
The view displays a customizable chain of linked requirements or other issue types, organized into columns. This arrangement helps users assess the extent to which these requirements cover the entire domain. A completeness calculation aids in this assessment. For example, you can determine if customer-level features are appropriately broken down into technical requirements, and whether these are in turn covered by test cases.
To navigate to the coverage view, open an easeRequirements project and select Coverage in the easeRequirements menu bar.
The effective use of the coverage view depends on the practices of your organization and its development process. You need to take into account how different types of requirements or other types of issues are structured, as well as how they are linked together and used. An organization might have different practices for different situations, so different coverage views can be defined and saved in the Coverage View.
The sheer number of requirements in a project may also be a challenge to understanding the coverage, so identifying significant subsets of the requirements and organizing them in different views is also an effective practice.
- 1 Overview
- 2 User Interface
- 3 Saved Coverage Views
- 4 Coverage View Operations
- 4.1 Open saved coverage view
- 4.2 Create new coverage view
- 4.3 Update level configuration
- 4.4 Add level
- 4.5 Remove level
- 4.6 Refresh coverage view
- 4.7 Create new coverage view from saved view
- 4.8 Delete coverage view
- 4.9 Export coverage view to Excel
- 4.10 Data Center Export coverage view to Excel using a template
- 4.11 Copy coverage view link to clipboard
- 4.12 Sort saved coverage views
- 4.13 Change position of saved coverage view in list
- 4.14 CLOUD Enable column filter for uncovered issues
- 4.15 DATACENTER Enable first column folder filter for issues part of selected tree parts
- 4.16 Disable column filter
- 4.17 Link or unlink issues
- 4.18 DATACENTER Review suspect link
- 4.19 Open issue
- 4.20 Display as graph
- 4.21 Configure display fields
- 5 How to select link descriptions
- 6 Formula for coverage completeness percentage
- 7 Known issues
User Interface
A coverage view is displayed as a table whose cells contain requirements or other types of issues. The columns, called “levels”, indicate relationships between the requirements. For example, the first column might contain high-level Customer Requirements, while the second column contains lower-level Functional Requirements, representing a relationship between the two sorts of requirements. The relationship is defined by links between the requirements.
By default, the relationship involves adjacent columns, but it is possible to have a relationship between non-adjacent columns. This is indicated with the option Column Basis in the coverage view configuration.
By inspecting the table, users can quickly identify gaps in coverage by the appearance of cells labeled “Not covered”. For example, a Customer Requirement that has no related Functional Requirement is easily spotted by that label appearing in an adjacent cell in the Functional Requirement level. Each level except for the first also displays a completeness percentage.
Saved Coverage Views
A panel on the left of the coverage view provides a list of saved views and context menu operations to manage the views. The views are organized into two folders:
Personal Views: These views are only available to the user that created them. By default, a newly created view is personal.
Public Views: These views are available to everyone who has access to the Jira project.
Coverage View Operations
Purpose | Operation | Comment |
|---|---|---|
Open saved coverage view |
|
|
Create new coverage view |
| As of the third level, the option Column Basis becomes available, making it possible to select a different level as the anchor of the relationship rather than the level immediately to the left. |
Update level configuration |
|
|
Add level |
| As of the third level, the option Column Basis becomes available, making it possible to select a different level as the anchor of the relationship rather than the level immediately to the left. |
Remove level |
| Only the rightmost level can be removed. |
Refresh coverage view |
|
|
Create new coverage view from saved view |
|
|
Delete coverage view |
|
|
Export coverage view to Excel |
| Export is handled as a background task since the operation may take some time. It is possible to continue working while the task is executing. A save file dialog will appear when the task is complete. While coverage completeness is being calculated, export is disabled. |
Data Center Export coverage view to Excel using a template |
| |
Copy coverage view link to clipboard |
|
|
Sort saved coverage views |
|
|
Change position of saved coverage view in list |
| This is how to change a view from private to public or vice-versa. Only the owner of the view can do this. |
CLOUD Enable column filter for uncovered issues |
| This only shows issues in the other columns that are not covered by an issue in the column to which the filter is applied. |
DATACENTER |
| It obviously makes no sense to select a project that is not one of the projects used in the view. |
Disable column filter |
|
|
Link or unlink issues |
|
|
DATACENTER Review suspect link |
|
|
Open issue |
|
|
Display as graph |
|
|
Configure display fields |
|
How to select link descriptions
In the configuration of the second and any further columns, you are able to restrict the issues in the column (call it B) to those that are linked to issues in the basis column (call it A) by specifying one or more link descriptions. You select a link description by viewing the issues in column B as the subject of the relationship and the issues in column A as the object, and then selecting the link description accordingly. For example, let’s suppose 1) column B issues are Specifications (S) and column A issues are Requirements (R) and 2) the link type is Specification with the outward description “specifies” and the inward description “is specified by”. Then you would select the outward link description “specifies”, because “S specifies R”.
Multiple link descriptions can be selected. Select “<any>” if you want no restrictions.
Formula for coverage completeness percentage
given
a = number of rows in previous column
b = number of issues not covered
(a - b) / a * 100Known issues
Cloud There is a possibility of encountering a 429 Error in the coverage view. Read more here: Rate Limiting in Jira Cloud.