Syndeia 3.0 offers a new option for a DOORS NG interface for MagicDraw and Rhapsody SysML modeling tools. The integration of requirements databases with system architecture modeling (SysML) is of high value to the practitioners in the field of MBE/MBSE. Although several solutions have been offered in the past, they address only the basic use case(s). Syndeia addresses a variety of scenarios for requirements-architecture integration, as elaborated in this blog post (Part 1) and Part 2 to follow.

Let’s start by watching a quick video introduction to the DOORS NG capabilities in Syndeia 3.0.

Any SysML element can be connected to an existing DOORS NG requirement in Syndeia using a Reference connection (see the middle panel in Figure 1). Using the Syndeia dashboard, a simple drag-and-drop operation, from the SysML element on the left on top of the DOORS NG element on the right, or vice versa, creates and stores such a connection.

Figure 1: Syndeia Dashboard showing SysML model on left, DOORS NG repository on right

Once the connection has been created, the Syndeia user can view the connected DOORS NG artifact in the native web interface, as shown in Figure 2, directly from the SysML element in the model browser, model diagrams, or the Syndeia dashboard. In the DOORS NG web interface, the requirement can be viewed or edited, assuming the user has the right permissions.

Figure 2: DOORS NG web interface opened to connected requirement

A more complex use case makes use of the Data Map connection. A DOORS NG requirement can be dragged and dropped into a SysML package in the Syndeia dashboard (Figure 3) and a SysML requirement is created with the same id and text. The same process works in reverse, although, in this case, DOORS NG assigns a new requirement id, which is written back to the SysML requirement.

Figure 3: Syndeia Dashboard showing Speed requirement in SysML generated from DOORS NG with a Data Map connection

Figure 4 shows the new requirement in the SysML model. In the model, it can participate in satisfy, verify and the full range of dependency relationships and linked to elements in other tools. For example, Syndeia could link the same requirement to an issue in the JIRA issue tracking system, a CAD design in NX or Creo, or a simulation in Simulink.

Figure 4: New Speed requirement in SysML showing Id and Text fields populated from DOORS NG Speed requirement

Syndeia maintains the link between the DOORS NG and SysML requirements. A change in the requirement text, name, or id at either end can be recognized using Syndeia, which generates a difference table as shown in Figure 5. Since the original connection was made, the velocity value in DOORS NG Speed requirement was changed from 200 to 250 kph. The difference table highlights the same. The same connection can be used to update the SysML requirement from DOORS NG, or the reverse, assuming the user has the appropriate write permissions.

Figure 5: Comparison of SysML and DOORS NG requirements, after DOORS NG Speed requirement description changed

Intercax is a member of the OSLC community. Syndeia consumes the OSLC services exposed by DOORS NG for several of its capabilities. However, OSLC does not support all the use cases and the interface needs to be augmented with other connection technologies in those situations. In Part 2 of this blog series, we will look at some of those, involving groups and hierarchies of requirements.

Related posts:

• Video introduction to Syndeia DOORS NG interface
• Syndeia with DOORS NG, Part 1 (this post)
• Syndeia with DOORS NG, Part 2

Tweet