mbse

Consider a healthcare facility with independent software systems for each department. A system engineer is tasked with developing a message exchange system between the departments based on the HL7 Version 2 standards. She begins by describing the interfaces and content exchanged between departments based on SysML interface blocks. The flow properties of these interface blocks are typed

In Part 1 of the blog series on Syndeia-JIRA interface, we described how Syndeia can connect to and browse JIRA repositories, and generate and connect SysML blocks from JIRA issues so that the block’s value properties mirror the issue characteristics like status, last update, etc. In Part 2, we showed how a multi-level SysML structure (e.g.

In Part 1 of this series, we connected individual requirements in DOORS NG to requirements and other elements in SysML. Greater challenges arise when we need to map requirement structure and organization between tools, because different tools organize requirements in significantly different ways. SysML tends to organize requirements in simple tree hierarchies using containment relationships.

Introduction Every system development project has both product-specific and project-specific considerations: Product-specific includes product requirements (market, technical, regulatory), product function and hardware and software design Project-specific includes organization structure, project requirements, and product development methodology The intersection of these two domains is often the Work Breakdown Structure (WBS) which captures the product-specific tasks in the

Of all the use cases potentially supported by Syndeia, links between systems engineering and project management are among the most intriguing. With Syndeia 3.0, a new interface to JIRA’s issue tracking repository offers a window into some of these possibilities. JIRA, widely used in agile software development, is organized by project and issue. As well as

As a project moves from architecture definition to component design, new software tools, such as mechanical computer-aided design (MCAD), become part of the engineering process. The impact of component design decisions needs to be continuously evaluated at the system level. The Syndeia interface for PTC Creo supports a number of use cases from either MagicDraw

In Part 1 of this series, we explored how Syndeia 3.0 generates global displays of connections between various engineering software tools. While these global displays (e.g. Figure 1) provide a snapshot of graph complexity, some very important use cases require us to trace out chains of individual connections and identify those model elements that may

The Object Management Group (OMG) held its Technical Meeting in Chicago last week, Sep 12-16, 2016. We had the opportunity to present Syndeia at the Systems Engineering Domain Special Interest Group (SE DSIG) meeting on Sep 13. In the presentation, we dived into the motivation and the technical philosophy behind Syndeia – to build a Total System Model that

One area in the biomedical and healthcare domain where MBSE has made significant progress is in medical device design and manufacture. At the same time, device suppliers use modern PLM (product lifecycle management) and CAD (computer-aided design) like other organizations engaged in complex engineering problems. The first figure below shows the SysML structural decomposition of

This blog post introduces the second installment in our series of notes outlining different scenarios for using Syndeia 2.0 to generate, connect, and compare Simulink and SysML models. Part 1 showed how SysML block and activity structures can be used to generate Simulink model reference structures, including both atomic and multi-signal ports. Part 2 will describe how