I need to generate the design traceability report, to prove that each requirement has been accounted for in both Software Architecture and Design. Ive create a project which is holding all requirements in there (lets 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. Requirement No Tasks 3 - Medium Requested Feature Requirements [RQ:2234] My Requirement No Tasks 3 - Medium Requested Feature Requirements [RQ:1790] Very hard requirement Not Covered No Tasks 3 - Medium Requested Feature Requirements [RQ:1789] Great requirement Not Covered No Tasks 3 - Medium Requested Feature Requirements [RQ:2218] Easy requirement Not Covered No Tasks 3 - Medium Requested Feature Requirements [RQ:2228] Just some requirement Not Covered No Tasks 3 - Medium Requested Feature Requirements [RQ:3148] Architecture Not Covered No Tasks 3 - Medium Requested Feature Architecture [RQ:3152] Physical View Not Covered No Tasks 3 - Medium Requested Feature Architecture [RQ:3149] Logical View Not Covered No Tasks 3 - Medium Requested Feature Architecture [RQ:3150] User View Not Covered No Tasks 3 - Medium Requested Feature Architecture [RQ:3151] Design Not Covered No Tasks 3 - Medium Requested Feature Design [RQ:3262] HAL: I2C Not Covered No Tasks 3 - Medium Requested Feature Design [RQ:3263] HAL:SPI Not Covered No Tasks 3 - Medium Requested Feature Design [RQ:3264] Safety features Not Covered No Tasks 3 - Medium Requested Feature Design [RQ:3265] Startup Sequence Not Covered No Tasks 3 - Medium Requested Feature Design [RQ:3266] Powerdown Sequence 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 Name Architecture Design My Requirement Physical view HAL: SPI Very hard requirement Physical view HAL: I2C Great requirement Logical View Safety Features Easy requirement User View Startup Sequence Just some requirement User View Powerdown 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 cant 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? en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/reports/3026.aspxthreadId=3026Vladimir Plotkin (vladimir@inmarsys.com) I need to generate the design traceability report, to prove that each requirement has been accounted for in both Software Architecture and Design. Ive create a project which is holding all requirements in there (lets 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. Requirement No Tasks 3 - Medium Requested Feature Requirements [RQ:2234] My Requirement No Tasks 3 - Medium Requested Feature Requirements [RQ:1790] Very hard requirement Not Covered No Tasks 3 - Medium Requested Feature Requirements [RQ:1789] Great requirement Not Covered No Tasks 3 - Medium Requested Feature Requirements [RQ:2218] Easy requirement Not Covered No Tasks 3 - Medium Requested Feature Requirements [RQ:2228] Just some requirement Not Covered No Tasks 3 - Medium Requested Feature Requirements [RQ:3148] Architecture Not Covered No Tasks 3 - Medium Requested Feature Architecture [RQ:3152] Physical View Not Covered No Tasks 3 - Medium Requested Feature Architecture [RQ:3149] Logical View Not Covered No Tasks 3 - Medium Requested Feature Architecture [RQ:3150] User View Not Covered No Tasks 3 - Medium Requested Feature Architecture [RQ:3151] Design Not Covered No Tasks 3 - Medium Requested Feature Design [RQ:3262] HAL: I2C Not Covered No Tasks 3 - Medium Requested Feature Design [RQ:3263] HAL:SPI Not Covered No Tasks 3 - Medium Requested Feature Design [RQ:3264] Safety features Not Covered No Tasks 3 - Medium Requested Feature Design [RQ:3265] Startup Sequence Not Covered No Tasks 3 - Medium Requested Feature Design [RQ:3266] Powerdown Sequence 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 Name Architecture Design My Requirement Physical view HAL: SPI Very hard requirement Physical view HAL: I2C Great requirement Logical View Safety Features Easy requirement User View Startup Sequence Just some requirement User View Powerdown 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 cant 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? Thu, 13 Mar 2025 14:57:33 -04002025-03-17T06:54:33-04:00/Support/Forum/spirateam/reports/3026.aspxmessageId=7150Vladimir Plotkin (vladimir@inmarsys.com) Sorry about formatting, Ive thought that a copy from Spira screen would work nicely... :( Thu, 13 Mar 2025 14:59:14 -04002025-03-13T14:59:14-04:00/Support/Forum/spirateam/reports/3026.aspx#reply7150messageId=7151Victoria D (nino.diasamidze@inflectra.com) Hello, I think article KB:542 about Creating a Custom Report with Grouped Headings is describing something very similar to what youre trying to achieve with XSLT. It helps to group the data in a report by a sub-heading, to show a table of associated requirements under each available Component. What you need to modify is to display the component name as a column instead of the main heading as section. Another options are: - ODATA that lets you run custom reports in other tools such as PowerBI and Excel365 - use ESQL query to extract the required data Regards, Victoria - Mon, 17 Mar 2025 06:54:33 -04002025-03-17T06:54:33-04:00/Support/Forum/spirateam/reports/3026.aspx#reply7151