0%

Discover recipes for addressing the growing complexity of modern systems by applying agile methodologies and techniques in model-based systems engineering (MBSE)

Key Features

  • Learn how Agile and MBSE can work iteratively and collaborate to overcome system complexity
  • Develop essential systems engineering products and achieve crucial enterprise objectives with actionable recipes
  • Implement best practices for building efficient system engineering models

Book Description

Model-based systems engineering provides an integrated approach to creating verifiable models of engineering data, rather than relying on traditional and vague natural language descriptions that are difficult to verify. This enables you to work on accurate specifications and rapidly design reliable and effective products for the marketplace. Agile MBSE integrates the value proposition of agile methods in systems development, most notably, for managing constant change and uncertainty while continuously ensuring system correctness and meeting customers' needs.

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 by covering the key concepts of agile methods for systems engineering. The book then takes you through initiating a project, defining stakeholder needs, defining and analyzing system requirements, designing system architecture, performing model-based engineering trade studies, and handing 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.

What you will learn

  • Apply agile methods to develop systems engineering specifications
  • Perform functional analysis with SysML
  • Derive and model systems architectures from key requirements
  • Model crucial engineering data to clarify systems requirements
  • Communicate decisions with downstream subsystem implementation teams
  • Verify specifications with model reviews and simulations
  • Ensure the accuracy of systems models through model-based testing

Who this book is for

If 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.

Table of Contents

  1. Agile Model-Based Systems Engineering Cookbook
  2. Contributors
  3. About the author
  4. About the reviewer
  5. Preface
    1. Who this book is for
    2. What this book covers
    3. To get the most out of this book
    4. Download the example models
    5. Where to go from here
    6. Download the color images
    7. Conventions used
    8. Sections
    9. Getting ready
    10. How to do it…
    11. Example
    12. Get in touch
    13. Reviews
  6. Chapter 1: The Basics of Agile Systems Modeling
    1. What's Agile all about?
    2. Incremental development
    3. Continuous verification
    4. Continuous integration
    5. Avoiding big design up front
    6. Working with stakeholders
    7. Model-based systems engineering (MBSE)
    8. Managing your backlog
    9. Purpose
    10. Inputs and preconditions
    11. Outputs and post conditions
    12. How to do it…
    13. Example
    14. Measuring your success
    15. Purpose
    16. Inputs and preconditions
    17. Outputs and post conditions
    18. How to do it…
    19. Managing risk
    20. Purpose
    21. Inputs and preconditions
    22. Outputs and post conditions
    23. How to do it…
    24. Example
    25. Product roadmap
    26. Purpose
    27. Inputs and preconditions
    28. Outputs and post conditions
    29. How to do it…
    30. Example
    31. Release plan
    32. Purpose
    33. Outputs and post conditions
    34. How to do it…
    35. Example
    36. Iteration plan
    37. Purpose
    38. Inputs and preconditions
    39. Outputs and post conditions
    40. How to do it…
    41. Example
    42. Estimating effort
    43. Purpose
    44. Inputs and preconditions
    45. Outputs and post conditions
    46. How to do it…
    47. How it works…
    48. Each team member selects one card to represent their estimate and places it face down
    49. Example
    50. Work item prioritization
    51. Purpose
    52. Inputs and preconditions
    53. Outputs and post conditions
    54. How to do it…
    55. How it works…
    56. Example
    57. Iteration 0
    58. Purpose
    59. Outputs and post conditions
    60. How to do it…
    61. Example
    62. Architecture 0
    63. Purpose
    64. Inputs and preconditions
    65. Outputs and post conditions
    66. How to do it…
    67. Example
    68. Organizing your models
    69. Purpose
    70. Inputs and preconditions
    71. Outputs and post conditions
    72. How to do it…
    73. How it works…
  7. Chapter 2: System Specification
    1. Why aren't textual requirements enough?
    2. Definitions
    3. Functional analysis with scenarios
    4. Purpose
    5. Inputs and preconditions
    6. Outputs and postconditions
    7. How to do it
    8. Functional analysis with activities
    9. Purpose
    10. Inputs and preconditions
    11. Outputs and postconditions
    12. How to do it…
    13. Example
    14. Functional analysis with state machines
    15. Purpose
    16. Inputs and preconditions
    17. Outputs and postconditions
    18. How to do it…
    19. Example
    20. Functional analysis with user stories
    21. Purpose
    22. Inputs and preconditions
    23. Outputs and postconditions
    24. How to do it…
    25. Example
    26. Model-based safety analysis
    27. A little bit about safety analysis
    28. Purpose
    29. Inputs and preconditions
    30. Outputs and postconditions
    31. How to do it…
    32. Example
    33. Model-based threat analysis
    34. Basics of cyber-physical security
    35. Modeling for security analysis
    36. Purpose
    37. Inputs and preconditions
    38. Outputs and postconditions
    39. How to do it…
    40. Example
    41. Specifying logical system interfaces
    42. A note about SysML ports and interfaces
    43. Purpose
    44. Inputs and preconditions
    45. Outputs and postconditions
    46. How to do it…
    47. Example
    48. Creating the logical data schema
    49. A quick example
    50. Purpose
    51. Inputs and preconditions
    52. Outputs and postconditions
    53. How to do it…
    54. Example
  8. Chapter 3: Developing System Architectures
    1. Five critical views of architecture
    2. General architectural guidelines
    3. Architectural trade studies
    4. Purpose
    5. Inputs and preconditions
    6. Outputs and post conditions
    7. How to do it…
    8. Understanding architectural merging
    9. What to merge
    10. Issues with merging specifications into a single architecture
    11. Purpose
    12. Inputs and preconditions
    13. Outputs and postconditions
    14. How to do it…
    15. The pattern-driven architecture
    16. Dimensions of patterns
    17. Pattern roles
    18. Patterns in an architectural context
    19. Purpose
    20. Inputs and preconditions
    21. Outputs and postconditions
    22. How to do it…
    23. Subsystem and component architecture
    24. Purpose
    25. Inputs and preconditions
    26. Outputs and postconditions
    27. How to do it…
    28. Architectural allocation
    29. Purpose
    30. Inputs and preconditions
    31. Outputs and postconditions
    32. How to do it…
    33. Creating subsystem interfaces from use case scenarios
    34. Purpose
    35. Inputs and preconditions
    36. Outputs and postconditions
    37. How to do it…
  9. Chapter 4: Handoff to Downstream Engineering
    1. Activities regarding the handoff to downstream engineering
    2. Starting point for the examples
    3. Preparation for handoff
    4. Purpose
    5. Inputs and preconditions
    6. Outputs and postconditions
    7. How to do it…
    8. Federating models for handoff
    9. Purpose
    10. Inputs and preconditions
    11. Outputs and postconditions
    12. How to do it…
    13. Example
    14. Logical to physical interfaces
    15. Purpose
    16. Inputs and preconditions
    17. Outputs and postconditions
    18. How to do it…
    19. Example
    20. Deployment architecture I – allocation to engineering facets
    21. Purpose
    22. Inputs and preconditions
    23. Outputs and postconditions
    24. Example
    25. Deployment architecture II – interdisciplinary interfaces
    26. Purpose
    27. Inputs and preconditions
    28. Outputs and postconditions
    29. How to do it…
    30. Example
  10. Chapter 5: Demonstration of Meeting Needs: Verification and Validation
    1. Verification and validation
    2. Model simulation
    3. Purpose
    4. Inputs and preconditions
    5. Outputs and postconditions
    6. How to do it…
    7. Model-based testing
    8. Purpose
    9. Inputs and preconditions
    10. Outputs and postconditions
    11. How to do it…
    12. Computable constraint modeling
    13. Purpose
    14. Inputs and preconditions
    15. Outputs and postconditions
    16. How to do it…
    17. Traceability
    18. Types of trace links
    19. Purpose
    20. Inputs and preconditions
    21. Outputs and postconditions
    22. How to do it…
    23. Effective reviews and walk-throughs
    24. Purpose
    25. Inputs and preconditions
    26. Outputs and postconditions
    27. How to do it…
    28. Test-driven modeling
    29. Purpose
    30. Inputs and preconditions
    31. Outputs and postconditions
    32. How to do it…
  11. Appendix A – The Pegasus Bike Trainer
    1. Pegasus high-level features
    2. Highly customizable bike fit
    3. Monitoring exercise metrics
    4. Export/upload exercise metrics
    5. Variable power output
    6. Gearing emulation
    7. Controllable power level
    8. Incline control
    9. User interface
    10. Online training system compatibility
    11. Configuration and Over-the-Air (OTA) firmware updates
    12. The Wahoo Kickr Bike
    13. Why subscribe?
  12. Other Books You May Enjoy
    1. Packt is searching for authors like you
    2. Leave a review - let other readers know what you think
3.144.251.72