Traceability between requirements, implementations, tests and more

Trace and report on linked work artifacts to help you verify that the end product is based on the requirements and meets customer demands.

Range of Traceable Project Artifacts: The Vivid Trace proposition is traceability between project artifacts, currently defined as issues inside JIRA. Source code commits, test case information, Confluence objects, and other project artifacts housed in systems outside of JIRA are not within direct range at this time (See the Product Roadmap for planned expansions). Vivid Trace excels at searching for linked project artifacts as long as those artifacts are JIRA issues.

Confirm requirements satisfaction and ship the right thing

Prove to yourself and your stakeholders that the end product is based exactly on the requirements.

Report on Requirements Satisfaction
Instantly trace requirements and monitor the results or process them for reporting, even in large quantities. Save time by re-running saved traces on live data.
Realtime Progress Tracking
At any stage in your development cycle, see which requirements are approved and are thoroughly implemented and tested, and which are still under development.
Assess Individual Requirements
Objectively assess each requirement's evolution into design and work artifacts, and through to implementation, validation, verification, and deployment.
Prevent Late-Cycle Surprises
Ensure that no requirements are missed. Guard against unrequested work artifacts (costly overproduction) escaping into the deliverables.

Open-ended exploration of issues and relations

Explore issues and relations using the Trace Studio in Vivid Trace
Trace Studio
Interactively trace saved filters, issues, and free-form JQL queries with the Trace Studio. Further process results with features provided by JIRA and your other add-ons.
Process Execution Transparency
Swiftly produce relevant and accurate traceability reports to verify work at key steps in your processes.
Reporting
Export trace reports and share updates with cross-functional teams and stakeholders. The graphs are simple enough that you can even use them to quickly explain situations to anybody.

Trace in any direction between project artifacts

Express full coverage of tests over a release.

Forward traceability
Map requirements to work products and the tests that verify their functionality to confirm that the correct set of requirements are being developed into the correct product.
Backward traceability
Find the originating requirements that correspond to code and architectural components. Trace even further upstream to sources like marketing input and customer feedback to determine raison d'être.
Bidirectional traceability
Ensure all requirements and defects are fully covered by test cases in preparation for a quality gate.
Figure: Requirements traced to their implementations and tests.

Demonstrate regulatory compliance

Compliance Assurance
Assure compliance with industry regulations and contracts to increase customer satisfaction while defending against criticism and reducing legal exposure.
Pre-Market Submission Package
Output traceability analysis reports that demonstrate compliance for inclusion into pre-market submission packages.
  • CMMI-DEV V1.3 REQM SP1.4 (Requirements Management Specific Practice 1.4)
  • FDA Medical Device Software Traceability Analysis
  • ISO 15504 SPICE (Various Process Outcomes and Base Practices)

Next

Visualization of Issue Relations