Blog Archives

In Part 1 and Part 2 of this series, we focused entirely on possible visualizations of inter-model connections, i.e. connections created by Syndeia between elements in different tools. But many use-cases require us to trace connections across the system model where the sequences include both inter-model and intra-model connections. Syndeia 3.0 can show many of these,

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

Modern systems are heavily software-intensive. Model-Based Engineering (MBE) must incorporate software configuration management systems (also called application lifecycle management systems or ALM) into the total system model in its goal to bring all system information into a common structure. Syndeia 3.0 offers our first interface into this domain with an interface to GitHub. GitHub is

The International Council on Systems Engineering (INCOSE) and the Project Management Institute (PMI) have been working together for several years exploring the connection between systems engineering and program/project management (link to INCOSE and PMI Survey), but relatively little attention has been paid to integrating the software tools popular in the two domains. Syndeia is trying