Book Image

Agile Model-Based Systems Engineering Cookbook

By : Dr. Bruce Powel Douglass
Book Image

Agile Model-Based Systems Engineering Cookbook

By: Dr. Bruce Powel Douglass

Overview of this book

Agile MBSE can help organizations manage constant change and uncertainty while continuously ensuring system correctness and meeting customers’ needs. But deploying it isn’t easy. Agile Model-Based Systems Engineering Cookbook is a little different from other MBSE books out there. This book focuses on workflows – or recipes, as the author calls them – that will help MBSE practitioners and team leaders address practical situations that are part of deploying MBSE as part of an agile development process across the enterprise. Written by Dr. Bruce Powel Douglass, a world-renowned expert in MBSE, this book will take you through important systems engineering workflows and show you how they can be performed effectively with an agile and model-based approach. You’ll start with the key concepts of agile methods for systems engineering, but we won’t linger on the theory for too long. Each of the recipes will take you through initiating a project, defining stakeholder needs, defining and analyzing system requirements, designing system architecture, performing model-based engineering trade studies, all the way to handling systems specifications off to downstream engineering. By the end of this MBSE book, you’ll have learned how to implement critical systems engineering workflows and create verifiably correct systems engineering models.
Table of Contents (8 chapters)

General architectural guidelines

As we learned in Chapter 1, Basics of Agile System Modeling, in Figure 1.27, a good architecture has the following properties:

  • It is architected early.
  • It evolves frequently.
  • It is as simple as possible (but no simpler than that).
  • It is based on patterns.
  • It integrates into project planning via technical work items.
  • It optimizes important system properties.
  • It is written down (specifically, it is modeled).
  • It is kept current.

The Architecture 0 recipe in Chapter 1, Basics of Agile System Modeling, concentrated on creating an early model of the architecture so that more detailed engineering work had a structural context. Nevertheless, the expectation is that the architecture progresses as more development work is done, and as more functionality is added to the evolving system design.

This chapter provides some important recipes that cover defining architectures, whether this is done as a big design up-front...