More Agile than Agile SEDC 2014 April 5

More Agile than Agile SEDC 2014 April 5, 2014 Zane Scott, VP for Professional Services Vitech Corporation

THESIS: A layered approach to model-based systems engineering promotes the concepts and principles of agile development and is arguably even MORE AGILE THAN AGILE! Vitech Corporation 2

The Agile Manifesto • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan Vitech Corporation 3

The Agile Manifesto • Individuals and interactions over processes and tools • Working solutions over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan Vitech Corporation 4

Agile Principles • • • • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly Vitech Corporation 5

Agile Principles • • • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly Vitech Corporation 6

Principles • • • Our highest priority is to satisfy the customer We welcome changing requirements Deliver working solutions frequently. Stakeholders and solution designers must work together daily Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. Working solutions are the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. Vitech Corporation 7

WHAT IS LAYERED MBSE? Vitech Corporation 8

Begin High • Innovation • Vision • Alternatives Vitech Corporation 9

Innovation Ideation Validation Number of Prototypes Inspiration Time Spent Developing Prototypes

Vision Vitech Corporation 11

Vision Vitech Corporation 12

Alternatives Q Vitech Corporation 13

Alternatives Q Vitech Corporation 14

Alternatives Q Vitech Corporation 15

EXCURSUS What about middle-out? • Get high! Vitech Corporation 16

MBSE Activities Timeline – Top Down 0. Define Need & System Concept 1. Capture & Analyze Orig. Requirements Activity bars represent movement of “center of gravity” of systems engineering team. 2. Define System Boundary Concurrent engineering is assumed. 3. Capture Originating Architecture Constraints 4. Derive System Threads 5. Derive Integrated System Behavior 6. Derive Component Hierarchy 7. Allocate Behavior to Components 8. Define Internal Interfaces SCHEDULE 9. Select Design 10. Perform Effectiveness & Feasibility Analyses 11. Define Resources, Error Detection, & Recovery Behavior 12. Develop Validation Requirements/Validation Plans 13. Generate Documentation and Specifications Vitech Corporation 17

MBSE Timeline – Reverse/Middle Out 8. Update System Boundary Find the top, 7. Derive As-Built System Requirements 6. Derive As-Built System Threads 7 a. Modify Reqts & Arch. Constraints 6 a. Modify System Threads 5. Aggregate to As-Built System Behavior 3 a. Refine Component Hierarchy 3. Capture Component Hierarchy 2. Capture Interfaces 5 a. Modify & Decompose System Behavior 4 a. Allocate Behavior to Components 4. Derive As-Built Behavior of Components SCHEDULE 1. Define System Boundary Then modify top-down. 2 a. Define Interfaces 9. Select Design 10. Perform Effectiveness & Feasibility Analyses 11. Capture Error Detection, Resource, & Recovery Behavior 12. Develop Test Plans 13. Generate Documentation and Specifications Vitech Corporation 18

Work In All 4 Domains • Don’t forget • Eliminate rework Vitech Corporation 19

Work In All 4 Domains All four domains At every layer Vitech Corporation 20

It’s All About Relationships Requirements are the basis of Behavior is allocated to Components basis of allocated to Requirements Components Behavior performs based on Behavior is based on Requirements Components perform Behavior Verify and Validate Vitech Corporation 21

Advance Granularity • Orderly decisions • Completeness at every layer Vitech Corporation 22

Increasing Granularity Dgn V&V BEH Source Documents REQ ARCH Dgn V&V REQ ARCH Docs LAYER 2 Dgn V&V BEH Docs Layer Of Detail LAYER 1 LAYER BEH Docs REQ ARCH Docs LAYER n Vitech Corporation 23

SOME ISSUES AROUND MODELS Vitech Corporation 24

What is a Model? • What is NOT a model? • What is a model? Vitech Corporation 25

Views Are NOT a Model • Views flow from the model Vitech Corporation 26

What is a View? • A structured answer to a request for a particular subset of information from the model Vitech Corporation 27

What is a View? que ry Model r e w s n a Vitech Corporation 28

What is a View? query Model ans w er Vitech Corporation 29

Many Models? NO! Architecture Testing Behavior Requirements Vitech Corporation 30

Power in the Interactions MODEL Architecture Testing Behavior Requirements Vitech Corporation 31

The Testing Problem As Designed As Reported Vitech Corporation As Heard As Tested 32

Models in MBSE • Models – Are limited representations of a system or process – Can be migrated into a cohesive unambiguous representation of a system • In model-based systems engineering – The ‘model’ is the system specification; conversely the system specification is the model – The visualizations are derived from the model – The model rests on the logical architecture (function) Vitech Corporation 33

MBSE MEETS AGILE Vitech Corporation 34

Principle 1 • The customer is key • Validation at every layer • Traceability Highest priority = satisfy the customer Vitech Corporation 35

Full Traceability (Bi-directional) REQUIREMENT: The system shall provide previously collected images/products, if appropriate. IS BASED ON IS THE BASIS OF FUNCTION: The system shall provide previously collected images/products, if appropriate. PERFORMS IS ALLOCATED TO ARCHITECTURE Vitech Corporation 36

Principle 2 • Changing requirements don’t disrupt the orderly layer-to-layer transitions • Model holds everything in relationship Welcome changing requirements Vitech Corporation 37

Model Behavior Requirements Change Physical Architecure V & V Vitech Corporation 38

Principle 3 • The end result of each layer is a complete model Deliver working solutions frequently Vitech Corporation 39

Increasing Granularity Dgn V&V BEH Source Documents REQ ARCH Dgn V&V REQ ARCH Docs LAYER 2 Dgn V&V BEH Docs Layer Of Detail LAYER 1 LAYER BEH Docs REQ ARCH Docs LAYER n Vitech Corporation 40

Principle 4 • By surfacing the model everyone can see it • Choosing the appropriate view Stakeholders and designers work together Vitech Corporation 41

Which View? • Who are they and what will speak to them? • What do they need (want) to know? • What do we need them to know? Vitech Corporation 42

Principle 5 • Teams can collaborate in real time • Model provides the discipline • Team focuses on problem solving MODEL Give teams needed environment & support Vitech Corporation 43

Principle 6 • Verify and validate at every layer Requirements Behavior Components V&V Requirements Behavior Components Measure of progress is working solutions Vitech Corporation 44

Principle 7 • Work is orderly • Model manages complexity • Problem does not become overwhelming Maintain a constant, supportable pace Vitech Corporation 45

Consistency MODEL Independent drawings v. Consistent views Vitech Corporation 46

Principle 8 • Model insures integrity and completeness • Design decision are intentional Technical excellence & good design Vitech Corporation 47

One Integrated Model Behavior Domain Originating requirements trace to behavior Data c Source Requirements Domain verified by Behavior is allocated to physical components V&V Domain Architecture Domain Data verified by Originating requirements trace to physical components Vitech Corporation 48

Principle 9 • Because views and documentation are generated by querying the model there is no need for repetitious clerical work • Pieces of the model can be reused Maximize the amount of work not done Vitech Corporation 49

Vitech Corporation 50

MANIFESTO VALUES Vitech Corporation 51

Values • Model focuses the work on design tasks instead of repetition and documentation work • Engineers are freed to be engineers • Communication is enhanced Individuals and interactions Vitech Corporation 52

Values • Focus is problem solving- not drawing views or creating documents Working solutions Vitech Corporation 53

Values • Views can be generated that: – Show the state of the model in real time – Are tailored to the audience Customer collaboration Vitech Corporation 54

Values • Model holds everything in relationship • Impact of change is immediately traceable Responding to change Vitech Corporation 55

SUMMARY Vitech Corporation 56

MBSE Benefits to the Enterprise • Enhanced communication – Shared understanding – Rich representations • Reduced development risk – Early identification of requirements issues – Faster requirements cycle – Improved cost estimates – Early/on-going requirements validation & design verification – Disciplined basis for decision making Vitech Corporation 57

MBSE Benefits to the Enterprise • Improved quality – Enhanced system design integrity – Improved specification of allocated requirements to HW/SW – Fewer errors during integration and test – More rigorous traceability from need through solution • Increased productivity – Improved impact analysis of requirements changes – Rapid analysis of design changes – Reuse of existing models to support design/technology evolution – Auto-generation of work products Vitech Corporation 58

MBSE Benefits to the Enterprise • Increased scope – Incorporation of domains – Integration of models – Extension of representations and audiences • Provides a structure to capture and communicate all aspects of the system Vitech Corporation 59

Thank You! For additional information: Zane Scott Vitech Corporation 2270 Kraft Drive, Suite 1600 Blacksburg, VA, 24060, USA zscott@vitechcorp. com www. vitechcorp. com Vitech Corporation 60