Design traceability report

Thursday, March 13, 2025
Avatar

I need to generate the design traceability report, to prove that each requirement has been accounted for in both Software Architecture and Design.

I've create a project which is holding all requirements in there (let's assume that the project consists of only one product for the matter of the question)

In this project I have 3 components:

1. Requirement
2. Architecture
3. Design

The design and architecture are written in semi-Word way: each "requirement" (header in Word) contain text, diagrams and is associated with real requirements as Depends On.

  
 
No Tasks
3 - Medium
Requested
 
Feature
Requirements  
[RQ:2234]
 
 
  
 
No Tasks
3 - Medium
Requested
 
Feature
Requirements
[RQ:1790]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Requirements
[RQ:1789]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Requirements
[RQ:2218]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Requirements
[RQ:2228]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Requirements
[RQ:3148]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Architecture
[RQ:3152]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Architecture
[RQ:3149]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Architecture
[RQ:3150]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Architecture
[RQ:3151]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Design
[RQ:3262]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Design
[RQ:3263]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Design
[RQ:3264]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Design
[RQ:3265]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Design
[RQ:3266]
 
 
  
Not Covered
No Tasks
3 - Medium
Requested
 
Feature
Design
[RQ:3267]

 

In the end I want to get something like this:

Design Traceability Report

Requirement NameArchitectureDesign
My RequirementPhysical viewHAL: SPI
Very hard requirementPhysical viewHAL: I2C
Great requirementLogical ViewSafety Features
Easy requirementUser ViewStartup Sequence
Just some requirementUser ViewPowerdown Sequence

 

The idea is to check for Component name of the artifact linked to the requirement and then decide if it belongs to Architecture or Design column (or something else). So... if the Component is Architecture, then place the linked name into Architecture column. if it is Design, then it belongs to Design column. And if it is anything else, it should be ignored.

I can't seem to find a way to get the Component from linked Artifact using XSLT., so not sure how to achieve my goal. 

Can anyone please help?

1 Replies
Thursday, March 13, 2025
Avatar
re: inmarsys Thursday, March 13, 2025

Sorry about formatting, I've thought that a copy from Spira screen would work nicely... :(

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885

 

Statistics
  • Started: Thursday, March 13, 2025
  • Last Reply: Thursday, March 13, 2025
  • Replies: 1
  • Views: 24