Agile Systems Engineering

Chapter 1: What is Systems Engineering? o Overview o Primary roles, o Primary responsibilities o Key work products o Systems Engineering Lifecycles o Waterfall o V-Cycle o Model-Based Systems Engineering  The Modeling Advantage  High-Precision Modeling with SysML and UML • Properties of good models (scope, intent, purpose, stakeholder, usage, precision, fidelity)  Modeling is essential for Agile Systems Engineering  Migrating from traditional SE to MBSE  The Rules
Chapter 2: What are Agile Methods and Why Should I Care? o Applying the Agile Manifesto to Systems Engineering o Agile Best Practices for Systems Engineering  Incremental development of work products  Continual verification of work products  Executable requirements models  Model-based specification  Continuous dependability assessment  Active project risk management  Model-based hand off to downstream engineering  Dynamic Planning o Dec Sec Ops  What is Dev Sec Ops and how does it differ from Agile  How do I apply modeling in Dev Sec Ops?  Detailed Dev Sec Ops workflows
Chapter 3: Brief Introduction to SysML v2 o Principles of good modeling o Differences between SysML v1 and SysML v2  Requirements and capabilities  Structural Modeling  Computations and analyses  Verification cases o Key SysML v2 views  Textual Notation  General View  Interconnection View  Action Flow View  State Transition View  Sequence View  Geometry View  Grid View  Browser View o Minimal SysML Profile – 80% of the capability with 20% of the complexity o Organizing your models for systems engineering
Chapter 4: Agile Stakeholder Requirements Engineering o Making requirements engineering agile - overview o Identification of stakeholder needs o Dependability analysis  Hazard analysis  Fault Tree Analysis  FMEA and FMECA  Model-Based Security Analysis o Performance analysis & non-functional requirements o Mapping requirements to Use Cases and User stories o Creating the system requirements  Functional requirements are verbs  Non-functional requirements are adverbs o The importance of traceability o When to stop
Chapter 5: System Requirements Specification & Functional Analysis o Making functional analysis agile - overview o Why are my requirements so inadequate? o Functional Analysis – finding the missing requirements o Scenario Analysis o Control Flow Analysis o Data Flow Analysis o Ensuring good requirements with executable requirements o Updating the dependability requirements o Requirements consistency analysis o When to stop
Chapter 6: Architectural Tradeoff Analysis o Make trade studies agile - overview o What is the Systems architecture? o Architectural evaluation and tradeoffs
Chapter 7: Architectural Design o Making architectural design agile - overview o Creating the systems architecture o Allocation of requirements  In the small – operational contracts  In the large – use case decomposition  Performance allocation o Updating the dependability analysis o Verifying your architectural model through simulation/execution o When to stop
Chapter 8: Handoff to Downstream Engineering and Test o Handing off to Downstream engineering in an agile way  1-shot Hand off  Incremental Hand off o Allocation to engineering disciplines o Specifying cross-discipline interfaces o Transforming logical interfaces to physical reality o Allocation to Verification and Validation Testing o Moving on to Development Engineering
Chapter 9: Summary and Overview o Overview of the Agile Lifecycle o Overview of the MDDSO Lifecycle o Table mapping practices, tasks, and work products o FAQs Appendix: Example: The T-Wrecks Semiautonomous Mechadroid