systems modelling language

Part 1 and Part 2 of this blog series have focused on the SysML models of energy systems (and system-of-systems). In this part (Part 3), we will describe the MBE graphs created when the SysML-based architecture model is connected with discipline-specific models such as CAD models, simulation models, PLM models, requirements model of energy system

Introduction It is common to say that “Everything is a System” or even “a System-of-Systems”, but the consequences of that are becoming increasingly alarming to the energy industry. In cases from the earthquake-triggered Fukushima disaster to (possible) foreign hacking of the electrical grid, the vulnerabilities of the energy supply to the physical, economic and political

Intercax is a leader in helping organizations adopt best practices for Model-Based Systems Engineering (MBSE). Both by itself and in collaboration with the Georgia Institute of Technology, it has been providing training in MBSE and SysML to working engineers since 2008 in live, onsite and online classes, with 4000+ participants. Intercax is now offering an

I recently had a thought-provoking discussion with a Computer-Aided Design (CAD) expert about Model-Based Systems Engineering (MBSE).  While I was prepared to show Syndeia’s features for connecting SysML models with NX or Creo, his concerns were more fundamental.  First, he pointed out that our examples in the introductory videos were “trivial” and not how people

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