Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Agile Model-Based Systems Engineering Cookbook

You're reading from   Agile Model-Based Systems Engineering Cookbook Improve system development by applying proven recipes for effective agile systems engineering

Arrow left icon
Product type Paperback
Published in Mar 2021
Publisher Packt
ISBN-13 9781838985837
Length 646 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Author (1):
Arrow left icon
Dr. Bruce Powel Douglass Dr. Bruce Powel Douglass
Author Profile Icon Dr. Bruce Powel Douglass
Dr. Bruce Powel Douglass
Arrow right icon
View More author details
Toc

Table of Contents (8) Chapters Close

Preface 1. Chapter 1: The Basics of Agile Systems Modeling 2. Chapter 2: System Specification FREE CHAPTER 3. Chapter 3: Developing System Architectures 4. Chapter 4: Handoff to Downstream Engineering 5. Chapter 5: Demonstration of Meeting Needs: Verification and Validation 6. Other Books You May Enjoy Appendix A – The Pegasus Bike Trainer

Preparation for handoff

Once the system's model has all the data necessary for the downstream engineering teams to work, it is necessary to manipulate it for the transition from systems engineering. This recipe prepares the model for this transition process to begin

Purpose

The purpose of this recipe is to facilitate the handoff from systems engineering to downstream engineering. This will consist of a review of the handoff specifications for adequacy and organizing the information to facilitate the handoff activities. Ideally, each subsystem team needs to access system model information in specific and well-defined locations and they only see information that is necessary in order for them to perform their work.

Inputs and preconditions

The precondition for this recipe is that the architecture is defined well enough to be handed off to subsystem teams for design and development. This means that the following preconditions are necessary:

  1. The system requirements...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image