
Agile Model-Based Systems Engineering Cookbook
Improve system development by applying proven recipes for effective agile systems engineering
Packt Publishing Limited
2nd Edition
Published on 30. December 2022
600 pages
978-1-80323-430-4 (ISBN)
System requirements
for ePUB without DRM
E-Book Single Licence
You are acquiring a single user licence for this eBook, which you might not transfer. [L]
Available for download
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
Get up to date with the latest recipes for applying agile methodologies and techniques in model-based systems engineering (MBSE) and manage the growing complexity of systems in your organization with ease. Purchase of the print or Kindle book includes a free eBook in PDF format.Key Features - Use this updated edition to learn how Agile and MBSE work iteratively and overcome system complexity
- Develop key systems engineering products and achieve enterprise objectives with step-by-step recipes
- Build efficient system engineering models using tried and trusted best practices
Book DescriptionAgile MBSE can help organizations manage change while ensuring system correctness and meeting customers' needs. But deployment challenges have changed since our first edition. The Agile Model-Based Systems Engineering Cookbook's second edition focuses on workflows - or recipes - 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. In this 2nd edition, the Cameo MagicDraw Systems Modeler tool - the most popular tool for MBSE - is used in examples (models are downloadable by readers). Written by a world-renowned expert in MBSE, this book will take you through systems engineering workflows in the Cameo Systems Modeler SysML modeling tool and show you how they can be used with an agile and model-based approach. You'll start with the key concepts of agile methods for systems engineering. Next, each recipe will take you through initiating a project, outlining stakeholder needs, defining and analyzing system requirements, specifying 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 learn how to implement systems engineering workflows and create systems engineering models.What you will learn - Learn how to apply modelling to create and manage important engineering data
- Apply agile methods to develop systems engineering specifications
- Communicate decisions with downstream subsystem implementation teams
- Coordinate with engineers from other disciplines
- Apply MBSE practices to problems within simple systems or large systems
- Ensure accurate systems models via tests, simulation, and verification
Who this book is forIf you are a systems engineer who wants to pursue model-based systems engineering in an agile setting, this book will show you how you can do that without breaking a sweat. Fundamental knowledge of SysML is necessary; the book will teach you the rest.
- Develop key systems engineering products and achieve enterprise objectives with step-by-step recipes
- Build efficient system engineering models using tried and trusted best practices
Book DescriptionAgile MBSE can help organizations manage change while ensuring system correctness and meeting customers' needs. But deployment challenges have changed since our first edition. The Agile Model-Based Systems Engineering Cookbook's second edition focuses on workflows - or recipes - 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. In this 2nd edition, the Cameo MagicDraw Systems Modeler tool - the most popular tool for MBSE - is used in examples (models are downloadable by readers). Written by a world-renowned expert in MBSE, this book will take you through systems engineering workflows in the Cameo Systems Modeler SysML modeling tool and show you how they can be used with an agile and model-based approach. You'll start with the key concepts of agile methods for systems engineering. Next, each recipe will take you through initiating a project, outlining stakeholder needs, defining and analyzing system requirements, specifying 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 learn how to implement systems engineering workflows and create systems engineering models.What you will learn - Learn how to apply modelling to create and manage important engineering data
- Apply agile methods to develop systems engineering specifications
- Communicate decisions with downstream subsystem implementation teams
- Coordinate with engineers from other disciplines
- Apply MBSE practices to problems within simple systems or large systems
- Ensure accurate systems models via tests, simulation, and verification
Who this book is forIf you are a systems engineer who wants to pursue model-based systems engineering in an agile setting, this book will show you how you can do that without breaking a sweat. Fundamental knowledge of SysML is necessary; the book will teach you the rest.
More details
Language
English
Place of publication
Basel/Berlin/Boston
United Kingdom
Publishing group
De Gruyter
Target group
Professional and scholarly
Edition type
Digital original
Product notice
Reflowable
File size
324,04 MB
ISBN-13
978-1-80323-430-4 (9781803234304)
Schweitzer Classification
Other editions
Previous edition

Dr. Bruce Powel Douglass
Agile Model-Based Systems Engineering Cookbook
Improve system development by applying proven recipes for effective agile systems engineering
E-Book
03/2021
1st Edition
Packt Publishing Limited
from
€33.59
Available for download
Content
- Intro
- Contributors
- Table of contents
- Preface
- Chapter 1: Basics of Agile Systems Modeling
- What's agile all about?
- Model-Based Systems Engineering (MBSE)
- Managing your backlog
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Measuring your success
- How to do it
- Example
- Some considerations
- Managing risk
- Purpose
- Inputs and proconditions
- Outputs and postconditions
- How to do it
- Example
- Product roadmap
- Purpose
- Inputs and preconditions
- How to do it
- Example
- Release plan
- Purpose
- Inputs and preconditons
- Outputs and postconditions
- How to do it
- Example
- Iteration plan
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Estimating Effort
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- How it works
- Example
- Work item prioritization
- Purpose
- Inputs and preconditions
- How to do it
- How it works
- Example
- Iteration 0
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Architecture 0
- Subsystem and component view
- Concurrency and resource view
- Distribution view
- Dependability view
- Deployment view
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Additional note
- Organizing your models
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- How it works
- Example
- Managing change
- Purpose
- Inputs and preconditions
- How to do it
- Example
- Chapter 2: System Specification
- Recipes in this chapter
- Why aren't textual requirements enough?
- Definitions
- Functional Analysis with Scenarios
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Functional analysis with activities
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Functional analysis with state machines
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Functional Analysis with User Stories
- A little bit about user stories
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Model-Based Safety Analysis
- A little bit about safety analysis
- Some Profiles
- Hazard analysis
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Model-Based Threat Analysis
- Basics of Cyber-Physical Security
- Modeling for Security Analysis
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Specifying Logical System Interfaces
- A Note about SysML Ports and Interfaces
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Creating the Logical Data Schema
- Definitions
- Example
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Chapter 3: Developing System Architectures
- Recipes in this chapter
- Five critical views of architecture
- General architectural guidelines
- Architectural trade studies
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Architectural merge
- Example
- Pattern-driven architecture
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Subsystem and component architecture
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Architectural allocation
- Creating subsystem interfaces from use case scenarios
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Specializing a reference architecture
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Chapter 4: Handoff to Downstream Engineering
- Recipes in this chapter
- Activities for the handoff to downstream engineering
- Starting point for the examples
- Preparation for Handoff
- Federating Models for Handoff
- Logical to Physical Interfaces
- Deployment Architecture I: Allocation to Engineering Facets
- Deployment Architecture II: Interdisciplinary Interfaces
- Chapter 5: Demonstration of Meeting Needs: Verification and Validation
- Recipes in this chapter
- Verification and validation
- Model simulation
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Model-based testing
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Computable constraint modeling
- Purpose
- Inputs and preconditions
- How to do it
- Example
- Traceability
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Effective Reviews and walkthroughs
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Managing Model Work Items
- Purpose
- Inputs and preconditions
- How to do it
- Example
- Test Driven Modeling
- Purpose
- Inputs and preconditions
- Outputs and postconditions
- How to do it
- Example
- Appendix A: The Pegasus Bike Trainer
- Overview
- Pegasus High-Level Features
- Highly customizable bike fit
- Monitor exercise metrics
- Export/upload exercise metrics
- Variable power output
- Gearing emulation
- Controllable power level
- Incline control
- User interface
- Online training system compatible
- Configuration and OTA firmware updates
- Packt page
- Other Books You May Enjoy
- Index
System requirements
File format: ePUB
Copy protection: without DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Use a reader that can handle the file format ePUB, such as Adobe Digital Editions or FBReader – both free (see eBook Help).
- Tablet/Smartphone (Android; iOS): Install the free app Adobe Digital Editions or the app PocketBook (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (not Kindle).
The file format ePUB works well for novels and non-fiction books – i.e., 'flowing' text without complex layout. On an e-reader or smartphone, line and page breaks automatically adjust to fit the small displays.
This eBook does not use copy protection or Digital Rights Management
For more information, see our eBook Help page.