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 5: Demonstration of Meeting Needs: Verification and Validation

This chapter is all about demonstrating that the system meets the needs of the stakeholders. There are a number of aspects to this, such as providing important information necessary for certification and system maintenance (for example, traceability), showing stakeholders what's in the work product(s) (walk-throughs and simulations), supporting analysis (simulation and analysis), demonstrating that the design satisfies the requirements (verification), and showing that the system meets the needs of the stakeholders (validation). This is not done just at the end but frequently or even continuously throughout the systems development process.

The recipes in this chapter are as follows:

  • Model simulation
  • Model-based testing
  • Computable constraint modeling
  • Traceability
  • Effective reviews and walk-throughs
  • Test-driven modeling

George Box famously said that all models are wrong, but...