XERTIFY™ TRACE
X-Trace the full path from requirement to verification.
X-Trace the full path from requirement to verification.
X-Trace is the backbone for engineering activities, it is the single source of truth for requirement management, being a central point for verification, reviews, and change.
HOW X-TRACE WORKS
One connected workflow from setup to sign-off.
1
ID & Naming
2
Layers
3
Relationships
4
Summary
Connect layers
Define how your layers relate to each other.
Select parent layer(s) for each row. Duplicate and invalid combinations are blocked while you edit.
Select layer...
PRD
Requirement
Select layer...
HW_RS
Requirement
PRD
×
HW_ARCH_SPEC
Requirement
HW_RS
×
HW_DES_SPEC
Requirement
HW_ARCH_SPEC
×
HW_DES_TEST_SPEC
Verification
HW_DES_SPEC
×
HW_ARCH_TEST_SPEC
Verification
HW_ARCH_SPEC
×
HW_REQ_TEST_SPEC
Verification
HW_RS
×
VALIDATION
Validation
PRD
×
1
ID & Naming
2
Layers
3
Relationships
4
Summary
Connect layers
Define how your layers relate to each other.
Select parent layer(s) for each row. Duplicate and invalid combinations are blocked while you edit.
Select layer...
PRD
Requirement
Select layer...
HW_RS
Requirement
PRD
×
HW_ARCH_SPEC
Requirement
HW_RS
×
HW_DES_SPEC
Requirement
HW_ARCH_SPEC
×
HW_DES_TEST_SPEC
Verification
HW_DES_SPEC
×
HW_ARCH_TEST_SPEC
Verification
HW_ARCH_SPEC
×
HW_REQ_TEST_SPEC
Verification
HW_RS
×
VALIDATION
Validation
PRD
×
Start with a structure built around your project.
Define your requirement, verification and validation layers, map the relationships between them and assign clear roles across the team.
Traceability CheckS
REQ
Requirements
Forward (F)
Are all reqs traced forward?
Passed
Backward (B)
Are all reqs traced back?
!
Warning
VER
Verification
Forward (F)
Are all ver. items traced forward?
Failed
Backward (B)
Are all ver. items traced back?
–
Not checked
Passed
!
Warning
Failed
–
Not checked
Traceability CheckS
REQ
Requirements
Forward (F)
Are all reqs traced forward?
Passed
Backward (B)
Are all reqs traced back?
!
Warning
VER
Verification
Forward (F)
Are all ver. items traced forward?
Failed
Backward (B)
Are all ver. items traced back?
–
Not checked
Passed
!
Warning
Failed
–
Not checked
Keep every engineering item connected.
Manage requirements and test specifications across connected layers while X-Trace maintains the relationships between them.
Status Workflow
Document lifecycle states and review transitions.
Draft
Set ready for peer review
Send for verification review
Peer review passed
Peer review NOT passed
Verification review passed
Verification review NOT passed
Legend
Action / State
Passed
Not passed
Status Workflow
Document lifecycle states and review transitions.
Draft
Set ready for peer review
Send for verification review
Peer review passed
Peer review NOT passed
Verification review passed
Verification review NOT passed
Legend
Action / State
Passed
Not passed
Move work forward with clear review controls.
Take requirements and test specifications through peer review and verification review with defined responsibilities at every stage.
Traceability Matrix
Coverage Analysis
Impact Analysis
Traceability Matrix Controls
Select one or more requirement layers, then generate the matrix for the current baseline.
Total requirements
18
Requirement rows returned for the selected layer set.
Traceability Matrix
Review the selected requirements as a flat report with their trace origins and linked items.
3 selected layers
Excel (.xlsx)
Export matrix
Requirement ID
Req layer
Description
Origin
Origin layer
Traces To
Forward layer
MS2_LAYER_11_006
HW_SAFETY_REQUIREMENT
Fisheye image correction shall be protected by a frame counter
MS2_PR_007
PRD
MS2_AR_068
MS2_AR_043
HW_ARCH_SPEC
MS2_LAYER_11_007
HW_SAFETY_REQUIREMENT
Raw fisheye input from sensor A shall be corrected into straight frame
MS2_PR_007
PRD
MS2_AR_038
HW_ARCH_SPEC
MS2_LAYER_11_008
HW_SAFETY_REQUIREMENT
There shall be a mechanism to apply the didgital gain to an entire frame
MS2_PR_008
PRD
MS2_AR_041
MS2_AR_070
HW_ARCH_SPEC
MS2_LAYER_11_009
HW_SAFETY_REQUIREMENT
Supported digital gain range is from 0 to 255
MS2_PR_008
PRD
-
-
MS2_LAYER_11_010
HW_SAFETY_REQUIREMENT
Provide a mechanism to perform statistical analysis in bayer raw image domain.
MS2_PR_009
PRD
MS2_AR_042
MS2_AR_069
HW_ARCH_SPEC
Traceability Matrix
Coverage Analysis
Impact Analysis
Traceability Matrix Controls
Select one or more requirement layers, then generate the matrix for the current baseline.
Total requirements
18
Requirement rows returned for the selected layer set.
Traceability Matrix
Review the selected requirements as a flat report with their trace origins and linked items.
3 selected layers
Excel (.xlsx)
Export matrix
Requirement ID
Req layer
Description
Origin
Origin layer
Traces To
Forward layer
MS2_LAYER_11_006
HW_SAFETY_REQUIREMENT
Fisheye image correction shall be protected by a frame counter
MS2_PR_007
PRD
MS2_AR_068
MS2_AR_043
HW_ARCH_SPEC
MS2_LAYER_11_007
HW_SAFETY_REQUIREMENT
Raw fisheye input from sensor A shall be corrected into straight frame
MS2_PR_007
PRD
MS2_AR_038
HW_ARCH_SPEC
MS2_LAYER_11_008
HW_SAFETY_REQUIREMENT
There shall be a mechanism to apply the didgital gain to an entire frame
MS2_PR_008
PRD
MS2_AR_041
MS2_AR_070
HW_ARCH_SPEC
MS2_LAYER_11_009
HW_SAFETY_REQUIREMENT
Supported digital gain range is from 0 to 255
MS2_PR_008
PRD
-
-
MS2_LAYER_11_010
HW_SAFETY_REQUIREMENT
Provide a mechanism to perform statistical analysis in bayer raw image domain.
MS2_PR_009
PRD
MS2_AR_042
MS2_AR_069
HW_ARCH_SPEC
Turn traceability into actionable project insight.
Use built-in reporting to understand requirement coverage, trace relationships and the downstream impact of change.
AI-READY TRACEABILITY
Bring your AI agents into the workflow.
X-Trace connects with your organisation’s own AI agents, helping teams automate repetitive traceability tasks while keeping project information within a structured engineering workflow.
Connect through MCP to create, update and retrieve X-Trace items directly through your AI.
Create HW Product requirements
AI Agent
HW Safety Requirements
0
0
0
0
REQ
Create
Turn inputs into X-Trace items
Use your connected AI agent to create items directly within X-Trace, bringing AI-assisted work into the same environment as your project activity.
HW Safety Requirements
0
0
0
0
REQ
HW Arch Requirements
0
0
0
0
REQ
Design Requirements
0
0
0
0
REQ
Ready to update
Update
Keep project information moving
Connected agents can update X-Trace items as work develops, helping teams spend less time on repetitive manual entry.
Retrieve
Get the project context you need
Let your AI agent retrieve information from X-Trace so engineers can access relevant project data through the tools they already use.
Manage Requirements
Build Traceability
Link Verification
Track Changes
Run Impact Analysis
Measure Coverage
Manage Baselines
Compare Versions
Summarize emails
Structure Reviews
Control Sign-off
Connect AI Agents
MCP Integration
Manage Requirements
Build Traceability
Track Changes
Streamline processes
1. ID & Naming
2. Layers
3. Relationships
4. Summary
Configuration summary
Review the current setup before saving.
Project Settings
Current configuration values for ID generation.
Project Type
HW
Requirement ID Digits
3
Test ID Digits
3
Layers Configuration
Total Layers: 8
1
PRD
This is a description
Layer Name
PRD
ID Pattern
HWDEV13_PRD_001
Approver
R Layer Responsible AlexR
Reviewers
W Reviewer AlexR
2
HW_RS
This is a description
Layer Name
HW_RS
ID Pattern
HWDEV13_HW_RS_001
Approver
R Layer Responsible AlexR
Contributors
C Layer Contributor AlexR
Reviewers
W Reviewer AlexR
TRACE IN ACTION
From project setup to sign-off in three clear steps.
Set up your project
01
Configure your project structure, define requirement and V&V layers, map relationships, assign roles and establish the baseline your team will work from.
Build and verify
02
Create and connect requirements and test specifications, move work through peer and verification reviews, and keep traceability checks visible as development progresses.
Sign off and continue
03
Use reporting and automated checks to confirm project readiness, sign off the baseline and archive it as a controlled snapshot while development continues in the next version.
1. ID & Naming
2. Layers
3. Relationships
4. Summary
Configuration summary
Review the current setup before saving.
Project Settings
Current configuration values for ID generation.
Project Type
HW
Requirement ID Digits
3
Test ID Digits
3
Layers Configuration
Total Layers: 8
1
PRD
This is a description
Layer Name
PRD
ID Pattern
HWDEV13_PRD_001
Approver
R Layer Responsible AlexR
Reviewers
W Reviewer AlexR
2
HW_RS
This is a description
Layer Name
HW_RS
ID Pattern
HWDEV13_HW_RS_001
Approver
R Layer Responsible AlexR
Contributors
C Layer Contributor AlexR
Reviewers
W Reviewer AlexR
TRACE IN ACTION
From project setup to sign-off in three clear steps.
Set up your project
01
Configure your project structure, define requirement and V&V layers, map relationships, assign roles and establish the baseline your team will work from.
Build and verify
02
Create and connect requirements and test specifications, move work through peer and verification reviews, and keep traceability checks visible as development progresses.
Sign off and continue
03
Use reporting and automated checks to confirm project readiness, sign off the baseline and archive it as a controlled snapshot while development continues in the next version.
0
Req
PRD
Relationships
1
2
3
4
5
6
7
8
9
Connect the layer
Type here...
4
Design Req.
5
HW Verification
6
Validation
1
Requirement
HW_RS
Relationships
1.1
1.2
1.3
1.1
Requirement
HW_ARCH_SPEC
Relationships
1.1.1
1.1.1
Verification
ARC_TES
Relationships
1.2
Verification
HW_DES_TEST_SPEC
Relationships
1.3
Validation
VALIDATION
Relationships
TRACE IN ACTION
From project setup to sign-off in three clear steps.
Set up your project
01
Configure your project structure, define requirement and V&V layers, map relationships, assign roles and establish the baseline your team will work from.
Build and verify
02
Create and connect requirements and test specifications, move work through peer and verification reviews, and keep traceability checks visible as development progresses.
Sign off and continue
03
Use reporting and automated checks to confirm project readiness, sign off the baseline and archive it as a controlled snapshot while development continues in the next version.
FAQs
Have questions? Find answers.
Have more questions?
Reach out to our friendly support team
Which standards are most relevant for semiconductor vendors working in the automotive industry?
ISO 26262 – Functional Safety for automotive electronics and semiconductors. ASPICE – Automotive SPICE for software and systems process maturity. ISO 21434 – Cybersecurity for automotive systems. ISO 9001 – Quality Management Systems. ISO 27001 / TISAX – Information Security and data protection requirements, especially for OEM and Tier 1 collaboration. Our consultancy helps align your processes and documentation with these standards, ensuring compliance and competitiveness in the automotive supply chain.
What does “pre-certification readiness” mean for semiconductor design organisations?
Pre-certification readiness ensures that your organization, development processes, and semiconductor products (such as IPs and SoCs) meet the requirements of key automotive and security standards before formal certification. It helps identify and close process gaps, reduce audit risk, and streamline the eventual certification with bodies for standards like ISO 26262, ASPICE, or ISO 21434.
How do you help semiconductor companies prepare for these certifications?
We perform a detailed gap analysis of your current processes, documentation, and engineering practices against relevant standards. Then, we provide a pragmatic improvement roadmap, including process design, documentation templates, training, and toolchain recommendations. Our approach is tailored to semiconductor design environments (RTL, verification, physical design, IP development), ensuring minimal disruption while achieving compliance efficiently.
Can smaller or Tier 2 vendors realistically achieve compliance with these standards?
Absolutely. Compliance is not limited to large organisations. With the right guidance, even small or mid-sized semiconductor vendors can implement scalable, right-sized processes that satisfy auditor expectations without excessive overhead. Our team specialises in helping Tier 2 and niche semiconductor companies adopt practical, value-driven approaches that meet both customer and certification requirements.
What are the benefits of being pre-certified or compliant with automotive standards?
Pre-certification readiness enhances your credibility with Tier 1 and OEM customers, accelerates design-in opportunities, and reduces business risk. It also improves internal efficiency, traceability, and product quality. Many automotive customers now require suppliers to demonstrate process maturity and compliance as part of the sourcing process—so readiness can be a key differentiator in winning business.
FAQs
Have questions? Find answers.
Have more questions?
Reach out to our friendly support team
Which standards are most relevant for semiconductor vendors working in the automotive industry?
ISO 26262 – Functional Safety for automotive electronics and semiconductors. ASPICE – Automotive SPICE for software and systems process maturity. ISO 21434 – Cybersecurity for automotive systems. ISO 9001 – Quality Management Systems. ISO 27001 / TISAX – Information Security and data protection requirements, especially for OEM and Tier 1 collaboration. Our consultancy helps align your processes and documentation with these standards, ensuring compliance and competitiveness in the automotive supply chain.
What does “pre-certification readiness” mean for semiconductor design organisations?
Pre-certification readiness ensures that your organization, development processes, and semiconductor products (such as IPs and SoCs) meet the requirements of key automotive and security standards before formal certification. It helps identify and close process gaps, reduce audit risk, and streamline the eventual certification with bodies for standards like ISO 26262, ASPICE, or ISO 21434.
How do you help semiconductor companies prepare for these certifications?
We perform a detailed gap analysis of your current processes, documentation, and engineering practices against relevant standards. Then, we provide a pragmatic improvement roadmap, including process design, documentation templates, training, and toolchain recommendations. Our approach is tailored to semiconductor design environments (RTL, verification, physical design, IP development), ensuring minimal disruption while achieving compliance efficiently.
Can smaller or Tier 2 vendors realistically achieve compliance with these standards?
Absolutely. Compliance is not limited to large organisations. With the right guidance, even small or mid-sized semiconductor vendors can implement scalable, right-sized processes that satisfy auditor expectations without excessive overhead. Our team specialises in helping Tier 2 and niche semiconductor companies adopt practical, value-driven approaches that meet both customer and certification requirements.
What are the benefits of being pre-certified or compliant with automotive standards?
Pre-certification readiness enhances your credibility with Tier 1 and OEM customers, accelerates design-in opportunities, and reduces business risk. It also improves internal efficiency, traceability, and product quality. Many automotive customers now require suppliers to demonstrate process maturity and compliance as part of the sourcing process—so readiness can be a key differentiator in winning business.
FAQs
Have questions? Find answers.
Have more questions?
Reach out to our friendly support team
Which standards are most relevant for semiconductor vendors working in the automotive industry?
ISO 26262 – Functional Safety for automotive electronics and semiconductors. ASPICE – Automotive SPICE for software and systems process maturity. ISO 21434 – Cybersecurity for automotive systems. ISO 9001 – Quality Management Systems. ISO 27001 / TISAX – Information Security and data protection requirements, especially for OEM and Tier 1 collaboration. Our consultancy helps align your processes and documentation with these standards, ensuring compliance and competitiveness in the automotive supply chain.
What does “pre-certification readiness” mean for semiconductor design organisations?
Pre-certification readiness ensures that your organization, development processes, and semiconductor products (such as IPs and SoCs) meet the requirements of key automotive and security standards before formal certification. It helps identify and close process gaps, reduce audit risk, and streamline the eventual certification with bodies for standards like ISO 26262, ASPICE, or ISO 21434.
How do you help semiconductor companies prepare for these certifications?
We perform a detailed gap analysis of your current processes, documentation, and engineering practices against relevant standards. Then, we provide a pragmatic improvement roadmap, including process design, documentation templates, training, and toolchain recommendations. Our approach is tailored to semiconductor design environments (RTL, verification, physical design, IP development), ensuring minimal disruption while achieving compliance efficiently.
Can smaller or Tier 2 vendors realistically achieve compliance with these standards?
Absolutely. Compliance is not limited to large organisations. With the right guidance, even small or mid-sized semiconductor vendors can implement scalable, right-sized processes that satisfy auditor expectations without excessive overhead. Our team specialises in helping Tier 2 and niche semiconductor companies adopt practical, value-driven approaches that meet both customer and certification requirements.
What are the benefits of being pre-certified or compliant with automotive standards?
Pre-certification readiness enhances your credibility with Tier 1 and OEM customers, accelerates design-in opportunities, and reduces business risk. It also improves internal efficiency, traceability, and product quality. Many automotive customers now require suppliers to demonstrate process maturity and compliance as part of the sourcing process—so readiness can be a key differentiator in winning business.