Requirements
Program Coverage
See which items of a project are linked from items in other projects, such as subsystem requirements and tests that trace to program requirements, and which links no longer resolve.
On this page
Overview
A program often splits into several projects: a system project with the program's requirements, and subsystem or contractor projects whose requirements and tests trace to them with links to other projects. Those links are stored in the projects that make them. Program Coverage collects them for the project they point to: for each of its items, which items in which projects link to it, and which items have no links yet.
The page also lists the project's own links to other projects whose target is deleted, gone, or in a project you cannot open.
Program Coverage is part of the Team plan, like links to other projects.
Concepts
What the page reads
| Mode | Projects read |
|---|---|
| app.holarch.app | The projects you are a member of, any role |
| Desktop | The other projects in the storage folder |
The page reads the 100 most recently changed of those projects and says so when there are more. It shows the number, name and class of each linking item, which you can read in that project anyway. Nothing is stored in the project: the page reads the links each time it opens or when you click Refresh.
Relations
Each link is shown from this project's side: a test in another project that verifies a requirement here appears as verified by TC.1 Speed test on the requirement's row. Point at a link to see it from the other side.
How to use it
Check a program's coverage
- Open the program project, then Verification → Program Coverage.
- Items starts with Requirement. Choose another class, or All linked items to list only items that have links.
- Read the summary, for example "12 of 40 items have links from other projects (30%)". Each row lists the linking items by project; click one to open it in its project.
- Tick Only items without links to see the gaps.
- Click Export CSV for one row per item and link.
Find broken links
The card Links From This Project That Do Not Resolve lists this project's own links whose target is deleted, gone, or in a project you cannot open, with the item that holds each link. Open the item and use Trace → Other projects to fix or remove the link.
Worked example: a rover program
- The project Rover holds the requirement RQ.1 Drive speed.
- The project Drive Subsystem holds the test TC.1 Speed test. In its Trace → Other projects, add verifies → Rover → RQ.1 Drive speed.
- In Rover, open Program Coverage. The row RQ.1 Drive speed shows Drive Subsystem: verified by TC.1 Speed test, and the summary reads "1 of 1 item has links from other projects (100%)".
Tips and good practice
- Agree on the relations the subprojects use, such as satisfies for requirements and verifies for tests, so the rows read the same everywhere.
- Review Only items without links before each design review.
- Combine with the Traceability Matrix for links inside the project.
Common mistakes
| Problem | Cause | Fix |
|---|---|---|
| A subproject's links are missing | You are not a member of that project, or it is not among the 100 most recently changed | Ask for access to the project, or open it once so it counts as recently changed |
| "Links to items in other projects are part of the Team plan." | The project's owner is not on the Team plan | Upgrade in Account Settings → Plan & Billing |
The Program Coverage page
| Part | Contents |
|---|---|
| Items | A class (Requirement first) or All linked items |
| Search | Number or name |
| Only items without links | Shows the gaps |
| Table | Item, class, Linked from (project, relation from this side, linking item), number of links |
| Links From This Project That Do Not Resolve | Item, relation and state of each broken link |
| Top bar | Refresh, Export CSV |
Limits
| Limit | Value |
|---|---|
| Projects read | The 100 most recently changed |
| Links listed per project | 5,000 |
| Rows shown | 2,000 (narrow the search to see others) |