Leveraging CI/CD Infrastructure to Automate Compliance

Building on years of progress in Model-Based Systems Engineering that has resulted in wider adoption of digital tooling, SysGit’s innovative approach enables organizations to finally realize agile hardware development. This is delivered through SysGit’s post-cloud data architecture, which is compliant with open standards and existing infrastructure investments.

SysGit’s use of the open standard SysML v2 and integration with an organization’s Git provider enables organizations to immediately leverage the same CI/CD infrastructure that is already used by an organization’s software engineers to accelerate hardware development, and support a diverse set of user personas. 

In software development, it is already common practice to package a set of proposed code changes together into a deliverable and subject it to a set of tests to ensure that changes won’t have negative repercussions on the application as a whole when deployed. These tests are automated through continuous integration and continuous deployment (CI/CD) pipelines, providing consistency to the process of building and minimizing human error, while in turn ensuring the delivery of a higher quality product, more rapidly.

Hardware engineering teams seeking to support early validation and verification of models for acquisitions submissions can similarly benefit from packaging proposed changes as digital deliverables, and subjecting them to a series of tests that assess their impact on the overall model. In particular, DIB organizations stand to make significant gains in speed and quality through the automation of repetitive, time-consuming, and error-prone tasks involved in coordinating changes across distributed teams, many of which are completed using manual typing, email, and disparate data formats that vary by toolset. Teams have lacked a standard format for digital deliverables that behaves with the consistency and interoperability of code, and a framework that extends industry-standard software development workflows to hardware development.

SysGit inherits the CI/CD pipelines of an organization’s Git provider, and tailors to hardware personas. This adapted workflow automates the packaging and testing of proposed model changes, just like code changes, without architecting and configuring a new infrastructure or creating a new data ontology. Instead, it blends the two worlds — hardware engineers and software engineers, models and code.

Through SysGit, systems engineers perform their usual work, while DevOps & DevSecOps Engineers administer workflows in GitLab or GitHub.

Software developers are already working with Git and Git providers, while SysGit stores all data in SysML v2 Textual Notation, an open standard that digital deliverables, allowing models to be paired with code.

Changes made to the software are verified against the model, and in turn, changes to the model are propagated into the software.

In both directions, CI/CD pipelines are a bulwark to unforeseen impacts, and human error, while ensuring compliance with safety and security standards are maintained.