Blog

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

The careful modeling of the system described in the first four parts of this series requires a great deal of effort by multiple contributors, but one of the benefits is that it enables us to investigate the security vulnerabilities of the system in a complete and systematic fashion. FMEA stands for Failure Mode Effect and

The careful modeling of the system described in the first four parts of this series requires a great deal of effort by multiple contributors, but one of the benefits is that it enables us to investigate the security vulnerabilities of the system in a complete and systematic fashion. FMEA stands for Failure Mode Effect and