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)

Chapter 1: The Basics of Agile Systems Modeling

For the most part, this book is about systems modeling with SysML, but doing it in an Agile way. Before we get into the detailed practices of systems modeling with that focus, however, we're going to spend some time discussing important project-related Agile practices that will serve as a backdrop of the modeling work.

Almost all of the Agile literature focuses on the "3 people in a garage developing a simple application" scope. The basic assumptions of such projects include the following:

  • The end result is software that runs on a general-purpose computing platform (in other words, it is not embedded software).
  • Software is the only truly important work product. Others may be developed but they are of secondary concern. Working software is the measure of success.
  • The software isn't performance-, safety-, reliability-, or security-critical.
  • It isn't necessary to meet regulatory standards...