From Project to Requirement to Code
PTC recognizes that traceability is not just for requirements. Requirements traceability is vital, but extending traceability across disciplines is where the true value of a software development lifecycle solution lies. This is why requirements traceability is a central part of the unified data model inherent within Integrity and it is leveraged to improve coordination, collaboration and compliance.
Integrity's sophisticated and configurable traceability functionality provides organizations with the tools they need to function more efficiently and effectively. It simplifies tasks such as:
- tracing test cases back to the business or system requirements, a design specification or (in an agile environment) a user story/change request to ensure 100% test-requirement coverage
- breaking down test suites into sets of test cases
- assessing the impact of a proposed requirement change across disciplines and product lines
- producing compliance reports that demonstrate a design history, complete with risks, the requirements that satisfy them and the tests that verify them
Traceability is also critical when developing variants and software product lines. In a complex software or system development environment with extensive use of reuse and variants, measuring impact across projects, components. subsystems and libraries surfaces the true cost of change to the organization. Traceability across reused assets is also essential in quality assurance. When a software defect is found and fixed in one product, Integrity's traceability enables the organization to ensure the same defect is addressed in other related software product lines.