Blog

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