Simulink

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

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,

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

Since its introduction, Syndeia has supported Model-Based Engineering (MBE). Syndeia has enabled users to create connections between models in different tools and to use those connections to compare and update those models, but it has only displayed the connections in simple tabular formats. Syndeia 3.0 provides some important new options for visualizing the model connections.

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

The human cardiovascular system is extremely complex. The heart pumps blood into arteries, which subdivide into a finer and finer network of capillaries that supply oxygen and fuel and carry away waste products from the body’s tissues, and then recombine into veins that return the blood to the heart. A second loop sends blood through

In this fifth and final installment, we look at two examples from the important domains of CAD and simulation to illustrate the “Internet-of-Tools” concept as applied to our Smart Home Internet-of-Things model. In the first example, a CAD model is linked to structural blocks in the SysML model of the 4 Room Smart Home, so that changes

Healthcare, in the US and globally, faces a challenge: how to offer a broader range of preventative, diagnostic and therapeutic services to a greater number of consumers without a proportionate increase in cost or decline in quality. Systems Engineering can help address this challenge, but only if we accept that healthcare involves a wide range

A crucial thread in enabling model-based systems engineering (MBSE) for next-generation complex systems is to analyze system architecture by means of simulations and verify requirements continuously during design and development phases. The general steps in this iterative simulation-based design approach are as follows: Define system architecture (design model) Create a simulation model Run the simulation

The Model-Based Systems Engineering (MBSE) workshop held at the INCOSE International Workshop in Torrance, CA, USA (Jan 24-25, 2015) hosted a tool vendor challenge in the Model Lifecycle Management track. The challenge problem was the design of a configurable UAV platform that can be used for developing UAVs for different missions, ranging from security and