CATIA Reqtify traces requirements across the tools a project already uses. It reads documents, models, code and test results where they are, links them by requirement ID, and reports what is covered and what a change would affect.
I went through the Reqtify Product Overview and modeled every interface it lists as a SysML v2 architecture in CATIA Magic. This post is the short version: why the interfaces matter, the four use cases I expect most teams to start with, and the two architecture views.
Title image: the Reqtify Management View of a project with specification, design, code and test documents (CATIA Reqtify Product Overview).
Business Case
Requirements are written in one tool, designed in a second, implemented in a third and tested in a fourth. Each tool is the right one for its job, and none of them knows what the others contain. Before a review or an audit, someone collects the trace from a requirement to its design, its code and its test result by hand.
Reqtify does that collection for you and leaves every tool the owner of its data. The Product Overview counts more than 100 interfaces. Nothing is migrated: Reqtify captures what it needs from each source, so a team can add traceability to a running project without changing how people work.
Four Main Use Cases
1. Trace Requirements Across Documents, Models, Code and Tests
A Reqtify project is a set of documents and the cover arrows between them. A document can be a Word specification, a DOORS module, a CATIA Magic model, a source folder or a test campaign. Reqtify captures the requirements and the references to them, and matches the two by ID.
Project editor: four documents and the arrows that say who covers whom | Graphical View: every link between the documents |
2. See Coverage and Impact Before the Review
The Management View gives the overall score and the coverage of each arrow. The Coverage Analysis View shows one element with what it covers upstream and what covers it downstream. An uncovered requirement is shown in red, so a gap is visible without reading a report.
Coverage Analysis View on a Simulink design, with the model diagram of the selected element | Impact of one requirement across specification, design, tests and code |
3. Connect the System Model to the CAD Design
The DEV Pack reads CATIA Magic and Teamwork Cloud models, and the Core connectors for Dassault Systèmes tools include SOLIDWORKS. With both, a requirement in the SysML model can be followed to the part that implements it. A comment on a SOLIDWORKS component with the requirement ID is the whole link, and a double-click in Reqtify selects the element in the tool it came from.
System requirements in CATIA Magic | The covering part, selected in SOLIDWORKS from Reqtify |
4. Exchange, Report and Qualify
The ReqIF Gateway exchanges ReqIF 1.2 files with requirements tools that have no direct connector. Regulations such as CFR and EASA texts can be imported as requirements. Reports go to Word, Excel, HTML, PDF and XML, and they can be scheduled. The analysis also runs from the command line, which makes it a step in a Jenkins job. For safety programmes there is a Qualification Kit for the tool itself.
Report editor with a traceability matrix template | Requirement Details View: requirements and attributes as a table |
Reqtify in Use
Link Details View | Impact of a single requirement |
Reviewer: review status and checklists | Requirement quality analysis |
Partner projects merged into one view | Features and release plans |
Product images: CATIA Reqtify Product Overview. The project editor, CATIA Magic and SOLIDWORKS pictures above are from a small universal-joint sample.
Capabilities
- Core (RQS): document editors such as Word, Excel, PDF and FrameMaker, requirements tools such as DOORS, DOORS Next, Polarion and Traceable Requirements Management, project and change management tools, development environments, Dassault Systèmes tools, source code and databases
- DEV Pack (RQD): design and authoring tools, among them CATIA Magic (Cameo), Teamwork Cloud, CATIA V5, AUTOSAR Builder, Rhapsody, Enterprise Architect, Capella, Simulink and SCADE
- TEST Pack (RQT): test tools, among them ALM/Quality Center, TestStand, VectorCAST, TESSY and SIMULIA Test Manager
- Accesses: document stores and repositories such as Git, GitHub, Bitbucket, Subversion, ENOVIA, OneDrive and Google Drive
- Plug-ins: Tagger, Reviewer, Collaborative Project Management, ReqIF Gateway and the Qualification Kit
- Analysis: coverage and impact views, baselines and snapshots, change tracking with suspicious links, variants, requirement quality analysis, reports and notifications
Solution Architecture
Each Reqtify interface is a port. The connected tools are grouped by the interface they use, and each line is the data that flows in that direction.
Reqtify Interfaces at a Glance
All Interfaces, Connected Tools and Supported Use Cases
References
- CATIA Reqtify product page
- Reqtify datasheet: requirement traceability and impact analysis
- CATIA Reqtify Product Overview, the document the interface list comes from
- Reqtify in the CATIA MBSE Cyber Systems community
- Success Path: CATIA Reqtify
- Reqtify Customization Guide and Coupling Notes: installed with the product in its
docfolder, so there is no web link
