Artifacts are identified and linked in MATLAB®, ensuring traceability over extended periods of time.
The Connector
The ReQonsult MATLAB® Connector connects MATLAB® with ALM/PLM systems and creates bidirectional traceability. This allows requirements, tests, and changes to be linked efficiently. This saves time, reduces manual work, and makes it easier for teams to collaborate in the development process.
The connector also supports compliance with regulatory standards and certifications: It seamlessly integrates external systems, makes changes traceable, and promotes structured work—ideal for industries with high compliance requirements.
Applications
Development projects pose challenges in terms of traceability, changes, and scaling. The connector addresses these application scenarios—from audit preparation and test coverage to series production readiness.
Scattered missing documentation
Audit approaching: requirements, models, and tests are distributed. The connector bundles all links—full traceability without last-minute documentation.
Requirements change late
Shortly before the milestone, a critical requirement changes. The connector immediately highlights affected models, tests, and functions.
Project overview is lost
Engineering uses MATLAB®, management uses the ALM system. The connector bridges the gap: overview of implementation and testing without workflow interruptions.
Missing tests remain undetected
Tests are there, but coverage remains vague. The connector links requirements with tests and results for secure acceptance.
Multiple tools, multiple teams
Requirements in Jira, models in Simulink, tests elsewhere—our MATLAB® Connector creates traceability with consistent data for everyone.
Change requests cause uncertainty
After change requests, it often remains unclear whether everything has been adjusted. The connector shows inconsistencies and changes are systematically checked.
Developer onboarding takes time
New team members lose time because they lack context. The Connector shows all requirements, functions, and tests in the model.
Make documentation reproducible
Certifications require long-term commitment and traceability. The connector links tests, requirements, and implementation.
Scaling from prototype to series production
From prototype to series production, complexity increases. The connector scales accordingly and keeps requirements, variants, and tests transparent and manageable.
Arrange a demo
Request a no-obligation demo now and get to know the ReQonsult MATLAB® Connector. Our experts will advise you on industry-specific issues and demonstrate live how you can sustainably increase efficiency and compliance.
Nick Entin – Head of Research & Development
Benefits
The connector creates greater efficiency, consistent compliance, and cross-system collaboration. Project changes thus become manageable, traceability becomes reliable, and processes are supported flexibly.
Efficiency through usability
Compliance and auditability
End-to-end traceability is enabled, which is required for regulatory standards, audits, and certifications.
Cross-system work
Teams can work in their familiar tools and still track requirements, tests, and changes across systems.
Mastering requirements
Those who recognize affected tests, codes, or documentation can respond more quickly to market, customer, and regulatory changes.
Medium discontinuity reduction
Requirements, models, and tests are linked across systems in the connector—without changing tools or losing information.
Flexible architecture
Benefit from the flexible architecture that seamlessly connects MATLAB® with ALM/PLM systems and supports individual processes.
Technical highlights
Our connector combines native MATLAB® integration, deep linking, universal ALM/PLM connectivity, and bidirectional traceability ensured by automated synchronization, offline capability, and scalability.
Native integration
Our connector runs as a genuine MATLAB® toolbox with direct access to Simulink®, System Composer®, and Stateflow® artifacts.
Bidirectional traceability
MATLAB® artifacts are published as surrogates in ALM/PLM systems. This links traceability and makes it semantically evaluable.
Combined scenarios
The connector supports local ReqSets and true remote linking. This enables a mix of import, remote linking, and hybrid scenarios.
Automation and maintenance
Links are automatically synchronized and cleaned up. On the roadmap: support for test management and integration into CI/CD workflows.
Offline traceability
Requirements are imported into MATLAB® so teams can work offline, see changes, and have context data.
Universal integration
The ReQonsult Connector seamlessly connects MATLAB® and Simulink® to various ALM and PLM systems, creating universal traceability.
Surrogate objects
Our connector creates surrogates for MATLAB® artifacts and enables traceability reports and analyses in target systems.
Deep linking mechanism
Each Simulink® artifact is assigned an addressable URL. External systems can navigate directly to individual blocks, subsystems, or states.
Multi-server capability
Multiple remote servers—such as Jira instances or PLM environments—can be connected in parallel and configured specifically for each project.
Downloads
Download our ReQonsult MATLAB® Connector product data sheet and discover how seamless traceability between MATLAB® and ALM/PLM systems enables you to work efficiently and in compliance with audits.
Interfaces
MATLAB® and Simulink® are connected to target systems such as Jira®, GitHub®, Trello®, and easeRequirements®. This creates consistency between requirements, code, and models – flexibly expandable for additional tools.
Jira®
The connector links MATLAB® to Jira® to link issues, epics, and stories, ensure traceability, and synchronize changes.
GitHub®
MATLAB® is integrated with GitHub®, linking code, commits, and issues, ensuring traceability, and supporting review and merge processes.
Trello®
MATLAB® is connected to Trello®, Simulink® elements are linked to cards and lists, and agile workflows are supported through tracking.
easeRequirements®
MATLAB® is connected to easeRequirements®, Simulink® artifacts are linked to Jira® requirements, and hierarchy and traceability are better utilized.
DevRhythm®
Right-click, no additional tools required, efficient, intuitive, and audit-ready: link, verify, and track requirements directly in Simulink®.
Upon request
The connector can be flexibly expanded. Upon request, we will be happy to check whether your desired tool can be integrated if it is not yet supported.
Onboarding
Onboarding can be planned: technical requirements, step-by-step implementation, defined roles, and stable updates enable a quick start, sustainable use, and long-term traceability.
Technical requirements
Requires a current MATLAB® environment with Simulink® and Requirements Toolbox®. System connection is established via standardized APIs.
Implementation
Installed as a native MATLAB® toolbox, the connector integrates into existing workflows and is activated step by step without interrupting processes.
Supported target systems
The architecture allows common ALM and PLM systems to be connected via REST, GraphQL, or SOAP—without structural restrictions.
Roles in the project
For developers, system engineers, tool administrators, and project managers, MATLAB® Connector creates a clear separation of roles and responsibilities.
Success factors
A clearly defined traceability target and the targeted selection of import or linking strategies ensure the long-term success of your project.
Update and maintenance
Regular updates ensure security, compatibility, and functional enhancements—while fully preserving existing links.
Stay up to date
Stay up to date on the latest developments from ReQonsult MATLAB® Connector and gain exclusive insights into new features, releases, and technical innovations in ALM and PLM integration.
Why ReQonsult?
Traceability designed with practical application in mind: Drawing on decades of consulting experience, we develop solutions that integrate into real-world processes, offer high usability, and ensure long-term, reliable quality.
Developed from practical experience
The connector addresses challenges from regulated development environments – tested under audit pressure and high system complexity.
20+ years of ALM experience
Over two decades of experience and expertise gained from demanding industrial projects are incorporated into the architecture and usability.
Focus on usability
We make traceability not just documentable, but usable. The connector emphasizes efficiency, UX, and everyday usability.
Deep MATLAB® expertise
ReQonsult knows MATLAB® and Simulink® inside out. The connector integrates natively and future-proof into the modeling environment.
Technology follows the process
The connector adapts to real workflows. Traceability is supported flexibly, without methodological restrictions.
Sustainable design
Stability, clean architecture, and continuous development ensure traceability across project and product generations.
FAQ
Detailed answers to frequently asked questions about the ReQonsult MATLAB® Connector. Learn how to use the connector to optimize traceability, simplify processes, and make development projects more efficient.
What is the ReQonsult MATLAB® Connector and what is it used for?
The ReQonsult MATLAB® Connector is an integration solution that connects MATLAB® and Simulink® models bidirectionally with external ALM and PLM systems to create end-to-end traceability throughout the development cycle. It addresses the typical challenges of distributed development artifacts by contextualizing and linking requirements, tests, code, and model information. Users gain seamless, semantically evaluable traceability without media breaks between tools. This connection facilitates auditability, reduces manual rework, and supports compliance in regulated development environments.
How does traceability work with ALM/PLM systems?
Traceability is achieved by creating so-called surrogate objects, which represent MATLAB® artifacts such as Simulink® models, subsystems, or requirements and are referenced in the ALM/PLM system. These surrogates can be used to link requirements, tests, bugs, or tasks bidirectionally. In addition, the connector generates addressable links down to the model level, allowing external systems to navigate directly to individual blocks or states. The result is semantically evaluable traceability that can be used consistently in both engineering and the ALM/PLM tool.
What types of artifacts are linked?
The ReQonsult MATLAB® Connector allows you to link a wide range of MATLAB® artifacts such as Simulink® models, blocks, test cases, data dictionary elements, and source code with external objects in ALM or PLM systems. This creates end-to-end traceability between requirements, tests, defects, and implementation.
How do imported requirements differ from remote linking?
Imported requirements are fully integrated into MATLAB® and enable offline work, context viewing, and change tracking. Remote linking only creates references to external ALM or PLM objects without local import, which keeps administration lean but provides less direct information and no change notifications.
What are the advantages of using surrogates?
When using the “Surrogates” option, linked MATLAB® artifacts are created as “proxy” elements in the corresponding ALM/PLM system. For example, if the user links a System Composer port to a requirement in Jira®, an additional ticket is created there and linked to the requirement. The target requirement remains unchanged and can even be read-only. The surrogate contains all information from MATLAB®, an image of the context, and the link back to it. When using the option without surrogates, the target requirement is extended with a link to MATLAB® so that Jira® users can navigate directly to MATLAB® to check the linked object. The Jira® administrator can specify which issue type is used for the surrogate and what type of link is used between surrogates and requirements to facilitate semantic traceability.
How does bidirectional traceability work with the connector?
The links from MATLAB® to ALM or PLM systems are maintained on the MATLAB® side using the Requirements Toolbox infrastructure. In the case of the connector, this includes the URL of the target container and the ID of the specific element within that container. For example, the URL of a project and the element within the project. On the ALM/PLM side, the corresponding links use the RMI notation of the link to MATLAB®—you can see the URL that MATLAB® provides for the artifacts by right-clicking on the block and then selecting Requirements → Copy URL to Clipboard. Please note that in other contexts, the menu may look like “Requirements at This Level.”
Which ALM and PLM systems are currently supported?
The connector offers an open integration architecture and supports the connection of common ALM and PLM systems via standardized APIs such as REST, GraphQL, or SOAP. Examples include systems such as Jira®, GitHub®, Trello®, easeRequirements®, and DevRhythm®. The architecture is designed so that additional target systems can be flexibly added, even if they are not yet directly supported. This makes the connector suitable for heterogeneous tool landscapes and enables project- or company-specific integrations without rigid lock-in.
What restrictions apply to Jira®?
Regardless of whether certain ease requirements apply, the following restrictions must be observed:
Links to MATLAB® artifacts:
If no surrogates are used, MATLAB® links are stored directly in the description of the respective issue. Since fields such as “URLField” do not support multiple values and “Remote Links” are not searchable, this can affect consistency checks and performance – especially because the connector has to search through all issues to check the validity of existing links.
Editing the issue description:
Jira® uses the complex Atlassian Document Format (ADF), which is only available as a JSON variant via the REST API. This makes automatic adjustment of the description technically challenging. Therefore, the use of surrogate issues is recommended for integration.
Necessary Jira® administration:
The setup of surrogate issue types, user-defined fields, and link types cannot be performed by regular users. This configuration must be done in advance by Jira® administrators so that the connector can be used effectively.
What limitations apply to GitHub®?
The following limitations apply when using GitHub® with the connector:
No support for surrogates:
Due to the specific workflow for issues in GitHub®, the connector does not support the creation of surrogate issues there.
Focus on bug fixing scenarios:
The intended use cases focus on supporting bug fixing processes reported via GitHub®, while ensuring direct traceability to the implementation artifacts in MATLAB®.
Are there any restrictions for Trello®?
When using Trello® in conjunction with the connector, the following restrictions apply:
No support for surrogates:
No additional Trello® cards are created to represent MATLAB® artifacts, as this is not desired. Instead, links are added directly to the description of existing Trello® cards and updated accordingly when changes are made.
Display of card IDs:
Trello® uses long internal identifiers (IDs) for cards, which are normally invisible to end users (visible only in the URLs in the browser). In MATLAB®, however, these IDs are displayed in certain views as the target of the trace link. Since MATLAB® currently does not offer any way to customize the display of these links and additional queries to Trello® could affect performance, this display remains in place for technical reasons.
Display of the link description:
Instead of visual highlighting directly on diagrams, MATLAB® provides access to further information via the context menu of the corresponding block under “Requirements >”. The description of the link is displayed there, for example, the title of the linked object.
How is the connector technically installed and configured?
The ReQonsult MATLAB® Connector adds a ReQonsult toolbar to the corresponding model views and registers callbacks for the MATLAB® Requirements Toolbox, installing the connector as a native MATLAB® toolbox and integrating it directly into the existing MATLAB® environment. The target systems are then connected via configuration dialogs, credentials are entered, and linking rules are defined. The architecture allows for step-by-step activation, so teams can test the integration in a pilot or sub-area before rolling it out project-wide. This approach minimizes risk and learning effort.
How are connector configurations shared within the team?
The connector provides a comprehensive user interface for configuring connections and settings for each system. However, due to traceability requirements and for security and authorization reasons, each connection to the server is unique—users typically need a personal authentication token or user credentials to gain access. Therefore, each user should configure the servers individually, while the settings for each system can be shared across the team. Copy the “preferences.json” file from the connector installation folder on one computer to the connector installation folder on another computer. Use the “Reset All Caches” option in the “Settings” dialog box if you change the file after the connector has already been initialized.
How does uninstalling and cleaning up the connector work?
To uninstall the connector from MATLAB®, simply uninstall the corresponding add-in. No uninstallation is necessary in the ALM/PLM systems, as no additional components were installed.
The following steps can be considered for data cleanup:
• Remove all links from the MATLAB® artifacts to the ALM/PLM objects.
• Remove all ReqSets with imported ALM/PLM artifacts.
• Delete all surrogate items from your ALM or PLM system, or delete the links from the original artifacts to MATLAB® if you prefer the non-surrogate option. The easiest way to find all MATLAB® links is to search for the pattern “http://127.0.0.1:31415/matlab/”.
• Remove the configuration of the corresponding work item type and link type in your ALM or PLM system if they are no longer needed.
How does the connector meet current security requirements?
The connector is continuously being developed to ensure the highest security standards. This includes regular updates to prevent known vulnerabilities and meet current legal requirements. In particular, compliance with the EU Cyber Resilience Act (CRA) is taken into account so that customers can rest assured that the connector can not only be operated securely today, but is also prepared for future regulatory requirements. This ensures that data protection and the integrity of integrations are always guaranteed.
What are the advantages of offline traceability?
Offline traceability means that requirements and metadata are imported into MATLAB® and made available locally. This allows developers to link requirements and models and track changes even without a permanent server connection. When they are back online, the links are synchronized. This is particularly relevant in isolated environments, phases with limited connectivity, or when teams are distributed and decentralized. In combination with central online synchronization, traceability remains both robust and up to date.
What future enhancements are planned for the connector?
Several important enhancements are planned for the connector to further expand its performance and flexibility. Optional AI-supported functions are planned, including an intelligent setup wizard supported by AI models such as ChatGPT® or Claude® to simplify configuration with ALM/PLM systems. An AI-based PDF import is also planned to make it easier to transfer content (one-way, without bidirectional traceability). In addition, seamless integration with CI/CD pipelines is planned so that traceability updates can be automatically incorporated into development workflows. Finally, the possibility of allowing user-defined scripts and functions to customize the connector to individual needs is also being considered.
How does the connector support audit and compliance capabilities?
Regulated development projects require complete documentation of requirements, implementation, and test coverage. The connector automatically collects, links, and synchronizes these artifacts without developers having to compile them manually. This allows audit reports with complete traceability to be generated. During audits, it can be verified which requirements were implemented by which models and tests. This not only improves auditability, but also significantly reduces effort and sources of error in compliance documentation.
How does the connector scale in large projects or companies?
The connector’s architecture supports multiple remote servers and project configurations in parallel. This means that teams can connect different instances of ALM or PLM systems and still maintain consistent traceability across all projects. This scalability is particularly important for large companies with heterogeneous tool landscapes or multiple development teams that need to work on different branches, variants, or compliance domains in parallel.
How is the quality of the links ensured?
The connector automatically synchronizes links between MATLAB® and external systems and regularly checks them for consistency. It suggests cleanup options for orphaned or inconsistent links. This not only creates traceability, but also maintains it, preventing media breaks and inconsistencies in the long term that can lead to hidden errors or compliance risks in complex projects.
How does the connector handle changes in requirements?
Changes in requirements, test cases, or model structures are tracked transparently via bidirectional links. As soon as a change is detected, the connector displays the dependent artifacts in the other system. This greatly simplifies impact analyses, as teams can immediately see which models, tests, or documentation are affected and how they need to be prioritized for adjustment—without time-consuming manual analyses.
Does the connector support versioning and variants?
Yes. Through integration with version and branch systems in ALM tools and models in MATLAB®, traceability can also be displayed in relation to versions and variants. Artifacts retain their links across versions, which is particularly important in large development landscapes with multiple releases or product lines in order to track changes in a controlled manner and avoid regressions.
Does the connector adapt to customer-specific workflows?
Yes. The connector’s open architecture makes it possible to connect additional tools or support customer-specific workflows if these are not already integrated as standard. ReQonsult will check on request whether a desired target system can be integrated. This also makes the connector suitable for use in special or proprietary IT landscapes and enables tailor-made integration solutions.
