Blog

Effective systems development begins with a clear set of objectives, captured as requirements. In terms of building a model, we must consider several different types of requirements: Model Architecture requirements – which urban systems should be part of the model Model Simulation requirements – which performance factors should be calculated Urban System requirements – what

Effective systems development begins with a clear set of objectives, captured as requirements. In terms of building a model, we must consider several different types of requirements: Model Architecture requirements – which urban systems should be part of the model Model Simulation requirements – which performance factors should be calculated Urban System requirements – what

Modeling urban communities has been designated as a high priority target for improved systems engineering . World population is increasingly urbanized. In the US, the percentage of the population in metropolitan areas has shifted from 7% in 1820 to 51% in 1920 to 82% today. China looks to make the same shift

In Parts 5 – 9 of this blog series, we have built an expanded model of an autonomous vehicle while demonstrating how a federation of models in different software tools can become a unified specification of the system. Figure 1 shows the types of model elements and the types of connections that Syndeia has used

As the project proceeds, extensive effort will be put into both the physical architecture and simulation and analysis and new software tools will come into play. In this part, we build the initial models in SysML and use them to generate models in Teamcenter PLM (Siemens) and Simulink (The MathWorks). These models remain connected for

Just as testing is an important part of the system development, the test software package is an important part of the project software architecture. In our example, test management is handled by TestRail (Gurock Software GMBH). The general schema for TestRail is shown in Figure 1. Figure 1 TestRail intra-model connectivity and schema A Test

Having initiated the requirements management process, the systems engineering team frequently moves on to a functional architecture of the system.  For our AV, the top-level “classifier” behavior has been captured in the simple state machine in Figure 1. The Initiation state involves the passenger entering a destination and the AV calculating an optimal route, before

In Part 2 of our blog series on MBSE for Autonomous Vehicles, we used a set of requirements based on DOT guidelines (“Automated Driving System 2.0: A Vision for Safety”, September 2017) and managed in a Jama Connect repository (Jama Software). Using Syndeia, this requirements model was transformed into a SysML model with connections linking

Few other systems have the potential for significant social impact as autonomous or driverless vehicles. They are expected to change Employment opportunities, as truck, bus and taxi drivers take other roles Urban land use patterns, as parking garages and roadways are reconfigured and repurposed Health and safety, as traffic accidents due to distracted and impaired

As we have built our SysML models over the previous five parts of this series, we have created a lot of model elements and a lot of connections. It’s reasonable to ask how we can use this network effectively as it grows to thousands or millions of parts, especially when we want to go beyond