Connecting Requirements and Design Evidence with Reqtify

Overview

This demonstration shows how CATIA Magic, SOLIDWORKS, and Reqtify work together to assess a design change against system requirements. CATIA Magic defines the requirements and system model, while SOLIDWORKS provides the assembly and mass values for three Unmanned Aerial Vehicle (UAV) configurations. Reqtify connects to the two tools, traces each mass requirement to its CAD evidence, and uses an evaluation rule to report whether the configuration meets the requirement. 

The UAV is a simple example for the demonstration. The same workflow can support other products where teams need to evaluate design variants using requirements and measurements maintained in different engineering tools. 

Solution Context

Reqtify: Connects the CATIA Magic system model and SOLIDWORKS assembly, linking requirements to the corresponding design measurements.

CATIA Magic: Contains the example UAV model with sample mass requirements.

SOLIDWORKS: Contains the UAV assembly with three configurations, along with their associated mass values.

OTScript Evaluation Rules: Runs within Reqtify to submit requirements marked External AI and their linked measurements for review, then store and display the returned results.

External AI Service: Company-hosted AI service that evaluates the supplied measurements against requirement text and returns a verdict with an explanation.

Solution Context BDD

 

 

Solution Context IBD

 

CATIA Magic

UAV Physical System Context

The P6000 UAV System contains Take Off Mass and Cargo Mass value properties for additional model context and traceability. The external review evaluates the requirement text against the mass value imported from the linked SOLIDWORKS item.

UAV Physical System Context BDD

 

Sample Requirements

The demonstration focuses on the following two requirements:

  • SPS-3400: The UAV System shall have a total takeoff mass no greater than 2.8 kg, including installed equipment and cargo.
  • SPS-3403: The UAV System shall transport a cargo item with a mass no greater than 0.6 kg. 
Requirement IDs, Text, Type and Stereotype

 

Reqtify

Connecting The Tools Together

The Reqtify project reads the two source documents: the CATIA Magic SysML model and the SOLIDWORKS assembly. The model import is scoped to the relevant system model package by setting Variable to Package and entering the path into the Value field. 

The updated Type of Analysis recognizes the custom specRequirement stereotype and uses Object Type = Requirement to distinguish individual requirements from specification headings. The configuration also defines how links are resolved to CATIA Magic Value Properties.

Project Configuration

 

Organizations may use custom requirement profiles in CATIA Magic. The example below shows how Reqtify's XML analysis configuration is adapted to recognize the requirement stereotype and map its fields.

Defining the specRequirement XML

 

SOLIDWORKS

UAV Assembly and Design Configurations

The SOLIDWORKS assembly represents the physical UAV used in this demonstration. It includes the aircraft structure, propulsion components, onboard camera, and removable cargo. The camera remains installed while the cargo and mounting arrangement change between configurations.

Three configurations illustrate how a design change affects the total takeoff mass and cargo mass:

ConfigurationTake Off Mass LimitCargo Mass LimitUAV ExampleDescription
A2.49 kg0.50 kgBase assembly with original cargo
B2.80 kg0.80 kgLarger and heavier cargo with original mounting
C2.85 kg0.80 kgLarger cargo with revised mounting

 

Exposing Values to Reqtify

Sensors are used to monitor properties (e.g mass) of parts and assemblies and provide configuration-specific measurements.

Reqtify imports the following items and their associated Parameter values. These values are later used for requirement evaluation.

ConfigurationSensors Property
A
B
C

 

Defining References for Reqtify

Comments associated with the mass items contain references that Reqtify uses to establish connections to the CATIA Magic model. The demonstrations uses the two keywords below:

KeywordPurposeExample
CoversConnects SOLIDWORKS item to a requirement using a Requirement ID[Covers: SPS-3400]
LinksConnects a SOLIDWORKS item to a CATIA Magi Value Property[Links: Take Off Mass]

 

The coverage reference provides the path used by the evaluation rule to retrieve the SOLIDWORKS measurement for each requirement. The value-property link provides additional traceability to the system model. The current evaluation does not directly read the CATIA Magic value-property defaults.

The following is an example comment onto a Parameter in SOLIDWORKS

Establishing References on SOLIDWORKS for Reqtify using Comments and Keywords

 

Refreshing the Design Evidence

After selecting a configuration, the assembly is rebuilt and saved. Reqtify then reloads the source to read the updated mass values.

The requirement references remain the same across configurations. The imported measurements change, allowing the same requirements to be assessed against each design variant. For the external AI review demonstrated in the video, a changed measurement makes the previous review stale; running the review again produces a result for the updated evidence.

 

Requirement Traceability and Evaluation

Reviewing the Links

After importing the sources, Reqtify’s Coverage Analysis View shows the connections established by the SOLIDWORKS comments. Selecting SPS-3400 displays the linked total takeoff mass item, text and downstream linkage.

These links identify the design evidence associated with each requirement. The imported mass values provide the inputs for evaluation.

Coverage Analysis View with Requirement Linked to a SOLIDWORKS Parameter

 

Running the External AI Review

The demonstration uses a custom OTScript rule to review requirements marked External AI. Selecting Tools -> Validate Requirements with External AI sends each marked requirement’s ID, text, and linked SOLIDWORKS mass value to the configured AI service.

The integration uses an OpenAI-compatible Chat Completions API. The endpoint URL, API key, and model are configured through environment variables, allowing the rule to connect to an organization’s internally hosted model or agent service that supports the same request and response format.

The service returns PASS, FAIL, or UNKNOWN, together with a short explanation. Reqtify saves the results and displays them in a consolidated dialog.

 

Results Review

The external AI review determined the following results:

ConfigurationTake Off Mass Limit (≤ 2.80 kg)Cargo Mass Limit (≤ 0.60 kg)Screenshot
A2.49 kg - PASS0.50 kg - PASS
B2.80 kg - PASS0.80 kg - FAIL
C2.85 kg - FAIL0.80 kg - FAIL

Configuration B demonstrates that a total mass within its limit does not guarantee that the cargo requirement is satisfied. Configuration C exceeds both limits.

 

Video

The video demonstrates the following:

  • An example UAV System with 2 mass requirements
  • Configuring Reqtify to read the CATIA Magic SysML model
  • Configuring Reqtify to read the SOLIDWORKS UAV assembly
  • Tracing the requirements to the corresponding SOLIDWORKS mass values
  • Switching amongst the 3 UAV configurations and seeing which mass limits pass or fail
  • Running an optional external AI review along with results
  • Reqtify rule checks with FAIL or stale data

 

 

Resources

The DELIVERABLES.zip contains the CATIA Magic SysML model, the Reqtify project and the UAV Assembly for SOLIDWORKS.

Comments 0