Link to Items in Other Projects

Trace an item to a requirement, function or test in another project, such as a subsystem requirement to the system specification it comes from. On app.holarch.app this is part of the Team plan.

1. Select the item. In the inspector's Trace section, find the Other projects group and click + (Add Link to Another Project…).
2. Choose the Relation (such as traced from or satisfies) and the Project. Search by number or name, narrow by Class if needed, click the item, then click Add Link. The link is one undo step.
3. The group shows the item's number, name and project. Click the name to open the item in its project. A ⚠ means the relation does not usually point to that class.
4. The project stores only ids. Each person sees the linked item's name only when they can open its project; everyone else sees Item in a project you can't open. Deleted in <project> means the item is in that project's Trash; Deleted means it is gone, and ⋯ → Remove Broken Links removes those links.
5. To link to an item of a library release, choose the library's Version (Release 1.1) in the dialog; the row then shows the release label instead of current. Change requests can stage links: Add Change ▾ → Add a Link to Another Project… or Remove a Link to Another Project….
6. The project you link to sees these links on its Verification → Program Coverage page. The links also appear below the Traceability Matrix (Other projects) and as dashed boxes on the Spider (Options → Other projects). The RTM report, matrix exports and ReqIF name them with your access; XMI leaves them out and counts them in its report. The API and MCP return ids; their resolve calls name items with the token's own access.

Related

Trace Requirements and Find Gaps · Traceability Matrix · Spider Diagram · Program Coverage · Libraries