The interoperability inherent in an open source tool such as SysON is a cornerstone for collaborative design of complex systems. In the context of Model-Based Systems Engineering - MBSE, where diverse teams contribute to different facets of a project, having an open source tool becomes a unifying force. It allows seamless collaboration and information exchange among stakeholders, regardless of their preferred tools or methodologies.

1. Seamless transition between representations

SysON empowers users to seamlessly transition between graphical and textual representations, accommodating diverse modeling preferences and the specific demands of the systems under analysis. This flexibility is crucial in MBSE, where the ability to articulate and refine models in different modalities is instrumental in capturing the complexity inherent in modern system designs.

2. Tailoring to domain-specific requirements

The extensibility of SysML v2 within SysON is a key aspect that reinforces its adaptability to diverse industries and complex project landscapes. In MBSE, where each domain might have unique requirements and specifications, having a tool that can be tailored to meet these specific needs is invaluable. SysON’s extensibility ensures that it remains a dynamic and adaptable resource for system engineers working across various domains.

3. Evolution guided by SysML v2 principles

As SysON evolves, guided by the principles of SysML v2, it positions itself as more than just a tool; it evolves into a comprehensive and standardized environment for MBSE endeavors. The commitment to open source and interoperability serves as a cornerstone for future developments, ensuring that SysON continues to meet the evolving needs of the MBSE community.

In essence, SysON stands as an open source enabler, promoting collaboration, flexibility, and adaptability—fundamental principles in the ever-evolving landscape of MBSE.

4. Import and export

4.1. JSON format

SysON extends its utility by introducing the capability to import and export projects in JSON format. This feature enhances interoperability, allowing users to seamlessly exchange project data and collaborate with external tools or platforms.

SysON doesn’t support the SysML v2 Standard JSON format for import/export.

For detailed instructions on downloading projects, downloading models, uploading projects, and uploading models, please refer to the respective sections in the documentation. These sections provide step-by-step guidance on how to perform these actions within the SysON environment.

4.2. SysML v2 textual format

SysON support SysML v2 textual specifications as an exchange format in order facilitate smooth transitions between tools. This intent reflects SysON’s dedication to staying aligned with evolving industry standards.

Add-on has been developed to enable import/export capability to and from SysML v2 textual syntax. This feature provides users with additional flexibility in their modeling workflows.

Before importing a file, you need to make sure that all the dependences of this file are also imported, and this, recursively. Otherwise some relationship won’t be resolved.

For example if you want to import a file that uses third party libraries, you will need to import the third party libraries before the actual file, otherwise you might have unreferenced relations.

Most important SysML v2 concepts can be translated from the imported file, some concept are still under development to enable complete import/export capability from and to SysML v2 textual syntax. Stay tuned for updates on its availability in the project.

The following example shows an example of SysML v2 content file to import:

package PictureTaking {
    part def Exposure;

	action def Focus { out xrsl: Exposure; }
	action def Shoot { in xsf: Exposure; }

	action takePicture {
		action focus: Focus[1];
		flow focus.xrsl to shoot.xsf;
		action shoot: Shoot[1];