Is2016 Intro To The Aselcm Pattern v1.4.8

Introduction to the Agile Systems
Engineering Life Cycle MBSE Pattern

3. System of Innovation (SOI)
Learning & Knowledge 2. Target System (and Component) Life Cycle Domain System
Manager for LC Managers
of Target System Life Cycle Manager of
LC Managers Bill Schindel Rick Dove
Learning & Knowledge
Manager for Target
Systems LC Manager of
schindel@ictt.com rick.dove@parshift.com
Target System
1. Target System
1.4.8
(Substantially all the ISO15288 processes are included in all four Manager roles) Target
Environment Copyright © 2016 by W. D. Schindel and R.Dove. Permission granted to INCOSE to publish and use.
Abstract
Engineered and other systems are under pressure to adapt, from opportunities or competition,
predators, changing environment, and physical or cyberattack. Ability to adapt well enough as
conditions change, especially in presence of uncertainty, is valued. Systems (including
developmental and life cycle management) that adapt well enough, in time, cost, and
effectiveness, are sometimes called “agile”. As environmental change or uncertainty increase,
agility can mean survival.
Agile systems and agile systems engineering are subjects of an INCOSE 2015-16 discovery
project, described elsewhere. This paper introduces the underlying MBSE-based Agile Systems
Engineering Life Cycle Pattern being used to capture, analyze, and communicate key aspects of
systems being studied. More than an ontology, this model helps us understand necessary and
sufficient conditions for agility, different approaches to it, and underlying relationships,
performance couplings, and principles.
This paper introduces the framework, while specific findings about methods and practicing
2
enterprises studied will be reported separately.
Copyright © 2016 by W. D. Schindel and R. Dove. Permission granted to INCOSE to publish and use.
Contents
• What is the INCOSE Agile Systems Engineering Life Cycle
Model Discovery Project?
• What are Agile Systems, and why do they matter?
• How are Agile Systems related to MBSE?
• What is the Agile Systems Engineering Life Cycle Pattern?
• Example: Applying the ASELCM Pattern to Plan Agility
Improvement
• Where can I learn more?
• Discussion
• References 3
Copyright © 2016 by W. D. Schindel and R.Dove. Permission granted to INCOSE to publish and use.
What is the INCOSE Agile Systems Engineering Life Cycle
Model Discovery Project?
• During 2015-16, the INCOSE parent society is sponsoring the Agile
Systems Engineering Life Cycle Model (ASELCM) Discovery Project,
based on a series of workshop clinics being held at host example
discovery sites across the U.S. and Europe.
• This project, now underway, will provide INCOSE inputs to a future
version of ISO 15288, to improve explicit understanding of principles
and practices of agility as applicable to systems engineering across
different domains.
http://www.parshift.com/ASELCM/Home.html
4
What is the INCOSE Agile Systems Engineering
Life Cycle Model Discovery Project?
• Announced at IW2015
• Built around discovery clinics being conducted by example host sites during 2015-16.
• Discovery clinics in 2015:
– Navy SpaWar/MITRE, San Diego, CA,
– Northrop Grumman, Vienna, VA,
– Rockwell Collins, Cedar Rapids, IA,
– Lockheed Martin, Ft. Worth, TX,
• You and your company can host or participate in 2016!
• Support from INCOSE Agile Systems WG and Patterns WG:
– R. Dove, project lead, co-leads K.Forsberg, H. Lawson, J. Ring, G. Roedler, B. Schindel
5
What are Agile Systems? Why do they matter?
Longer history than just Agile Software Development Methods :
Agile
General Agile
Enterprise
Agile Systems
Systems—
Software Engineering
Origins
Methods (c. 201x)
(c. 199x)
(c. 200x)
– For history and background, see Dove and LaBarge, 2014
– Agile software methods, by far better known, are related.
– General Agile Systems Engineering is the related broader subject
of the INCOSE ASELCM Project.
– Problem space: Challenges of uncertainty and rates of change in
environment, stakeholders, competition, technologies, capacities,
capabilities. Not just “going faster”. 6
Is this your tomorrow, or a distant vision?
From “The Hardware Renaissance Arrives: A New Dawn for Gadgets”,
The Wall Street Journal, March 23, 2015:
“Recently, as I gazed into the prototype of a smart breast pump, I had a vision of the future. I
saw an age in which new products—actual, physical electronics products—will go from idea to
store shelves in a matter of months. A future in which warehouses and distribution centers
cease to exist, because factories produce finished goods from raw materials on demand, and
they never stop moving through the supply chain. Only it turns out all of this is possible today.
The “hardware renaissance” that began in Silicon Valley in just the last five years, born of
rapid prototyping technologies, has become something much larger and more important. It
has been a sea change in every stage of producing physical objects, from idea to
manufacturing to selling at retail . . .”
-- Christopher Mims, The Wall Street Journal, p B1,6, March 23, 2015
-- emphasis added 7
Copyright © 2016 by W. D. Schindel and Rick Dove. Permission granted to INCOSE to publish and use.
Agile Systems Architecture Pattern (R. Dove)
The S*ASELCM Pattern captures (in a formal S*Model) the key ideas
associated with the pre-MBSE Agile System Architecture:
– As in (Dove and LaBarge, 2014)
8
Optimized Feedback & Correction Cycle Rate:
A Hallmark of Agile Methods & Problem Space
An Apollo 11 Mission Question: Why was the Saturn V rocket
engines’ directional gimbals update cycle period throughout the
Ascent Phase ~ 2 seconds, but the update cycle period of course
direction during the Free Flight Phase was ~ 26 hours?
Ascent Phase Updates:
Saturn V Launch Vehicle
Engine Gimbal Feedback
Control Loop Update Period
Δt ~ 2 seconds
E
TLI Ascent
Free Flight Phase Updates:

Time to Mid-Course Correction:
Δt ~ 26 hours, 44 minutes
MCC 9
System Life Cycle Trajectories in S*Space
• Configurations change over life cycles, during development and subsequently
• Trajectories (configuration paths) in S*Space
• Effective tracking of trajectories
• History of dynamical paths in science and math
• Differential path representation: compression, equations of motion
10
Simple Geometric/Mathematical Idea: Subspace Projections
11
System Life Cycle Trajectories in S*Space, and S*Subspaces
Stakeholder Feature Subspace Sub-subspaces

Feature Feature Feature
attribute attribute attribute
attribute attribute

Summary of S*Metamodel attribute attribute

attribute
attribute
Defines System Configuration Space Feature Feature Feature

Stakeholder
Stakeholder
Requirement Stakeholder Feature
World
Language Statement
attribute attribute
Continuous Subspace
Functional Technical Behavior Subspace
Interaction State System
High Level (Interaction) attribute
Requirements
Functional Functional Functional
System of Role Role Role attribute “A” Coupling
Interface attribute attribute

Access attribute
attribute attribute
“A” Functional Functional Functional
Coupling Input/ Role Role
Role
Technical Output attribute attribute attribute
attribute attribute
World
Language Functional Functional Functional
BB (logical system) Role Role Role
Technical attribute attribute
Functional attribute
Detail Level Requirement attribute
Requirements WB Role
Statement
attribute attribute
Discrete Subspace
(physical system) “B”
Design
High Level Design Coupling
Constraint
Design Component
Statement
attribute attribute Physical Architecture Subspace
Design Design Design
Component Component Component
attribute attribute
System Configuration Space Design

Component
attribute
Design
Component
attribute
Design
Component
attribute
attribute
(S*Space) attribute attribute
Design Design Design

Sub-subspaces
12
Agility as Optimal Control in S*Space:
Finding the Best Next Increment “Direction”
Stakeholder Feature Subspace
attribute attribute

attribute

Technical Behavior Subspace

Role Role Role
attribute
Role Role Role
attribute attribute
Role Role Role
attribute
S1 Attribute Physical Architecture Subspace

2. Target System (and Component) Life Cycle Domain System S1 Attribute
S1 Attribute Design Design Design
attribute attribute
Optimal S2 (Actor) Attribute Design Design Design
S2 (Actor) Attribute
Control S2 (Actor) Attribute
Component
attribute
Component
attribute
Component
attribute
Learning & Knowledge Manager Provides attribute
attribute attribute
for Target Systems Coupling Design Design Design

Knowledge to LC Manager Attribute Component Component Component
Pattern Repository, Manages LC Manager Attribute
LC Manager of Life Cycle of LC Manager Attribute
Knowledge of Families of:
Target System
1. Target System
Target
System
Target System Life
Cycle Domain Actor
Configured Models Repository,
Target
System Configuration Subspace
Configured Instances of:
Target System
System for Target System
Component Target Target System Life
System Cycle Domain Actor Trajectory Options—
Provides Target System Current Next Increment
Observations to Target System Component
Component Confguration
Observes
Target System Life
Observes
Cycle Domain Actor
Backlog Item
Series of System Configurations, 13
Along (Possibly Agile) Trajectory
How are Agile Systems Related to MBSE?
1. Basics: Using explicit models, MBSE/PBSE adds clarity to pre-model descriptions
of Agile Systems and Agile SE-- improves understanding of Agile Systems.
2. More important: MBSE/PBSE complements and improves the capability of Agile
Systems and Agile Systems Engineering—
• Agility requires persistent memory & learning—being forgetful/not learning impacts
agility.
• Patterns capture & retain learning, as persistent, re-usable, configurable, models,
updated as experience accumulates.
• S*Patterns are configurable, reusable S*Models.
“PBSE as Agile MBSE” emerges as essential when competing on agility becomes

reality for competing, competent players:
– Improved: “Where are we?”
– Improved: “Where are we going?” Vital for Scrum, other approaches
– Improved: “We’ve been here before.”
– Improved: Understanding of response.
– Improved: Understanding of mission envelopes.
Vital for Response Situation
– Improved: Ability to assess agility Analysis (RSA)
– Improved: Ability
Copyright ©to
2016plan agility
by W. D. Schindel and Rick Dove. Permission granted to INCOSE to publish and use.
14
Maps vs. Itineraries -- SE Information vs. SE Process
• The SE Process consumes and produces information.

• But, SE historically emphasizes process over information. (Evidence: Ink & effort spent
describing standard process versus standard information.)
• Ever happen?-- Junior staff completes all the process steps, all the boxes are checked,
but outcome is not okay.
• Recent discoveries about ancient navigators: Maps vs. Itineraries.
• The geometrization of Algebra and Function spaces (Descartes, Hilbert)
• Knowing where you are, not just what you are doing.
• Knowing where you are going, not just what you are doing.
• Distance metrics, inner products, projections, decompositions.
15
Maps vs. Itineraries -- SE Information vs. SE Process
• Model-based Patterns in S*Space.

• Interactions as the basis of all laws of physical sciences.
• Relationships, not procedures, are the fruits of science used by engineers: Newton’s laws,
Maxwell’s Equations.
• Immediate connection to Agility: knowing where you are--starting with better definition of
what “where” means. There is a minimal “genome” (S*Metamodel) that provides a practical
way to capture, record, and understand—the “smallest model of a system”.
• Not giving up process: MBSE/PBSE version of ISO/IEC 15288. 16
What is the Agile Systems Engineering Life Cycle Pattern?
LC Managers

Manager for Target
Target System
1. Target System
Environment
• A key subset of the ASELCM Pattern is--

the system reference boundaries . . .
17
The Agile System Domain Model
• We will particularly refer to three major system
boundaries:
– To avoid a confusion bog of loaded terms, we could have
just named them “System 1”, “System 2”, and “System 3”
and proceeded to define them behaviorally.
– The definitions are behavioral because these are logical
systems, performing defined roles.
– However, we will also give them more specific names —
but make sure you understand the definitions of these
systems, which are more important than their names . . .
18
System 1: The Target System (and Components): (Definition) The logical
system of interest, which results from, or is subject to, innovation.
– Its behavior, characteristics, or performance are targets of the innovation
(change, adaptation) process we’ll introduce later.
– It is potentially agile. (Assertion: for SE to be fully agile, so must its target)
– Examples potentially include aircraft, automobiles, satellites, the human
population, software, restaurants.
LC Managers

Manager for Target
Target System
1. Target System
Environment 19
System 1: The Target System (and Components): (Definition) The logical
system of interest, which results from, or is subject to, innovation.
– The Components maintained for integration into a Target System, but not
yet integrated, are included in this domain.
– Notice that this idea can apply at multiple additional levels (e.g., System of
Systems, System, Subsystem, Component, etc.)
LC Managers

Manager for Target
Target System
1. Target System
Environment
20
System 2: The Target System (and Component) Life Cycle Domain System:
(Definition) The logical system within which the Target System will exist during its life
cycle, when “in service” or otherwise. This domain includes all actors with which the
Target System will directly interact during its life cycle:
– This includes (among others) any system that directly manages the life cycle of an instance
of a Target System (or a Component)—production and integration systems, maintenance,
support, and operations systems, and others.
LC Managers

Manager for Target
Target System
1. Target System
Environment
21
The System 2 model recognizes three systems besides the Target System:
• Target Environment: Target System Life Cycle Domain Actors
• LC Manager of Target System (also manages Target System Components)
• Learning & Knowledge Managers for Target System (and Components)

LC Managers

Manager for Target
Target System
1. Target System
Environment
22
• Target System Life Cycle Domain Actors: All actors with which the Target System will
directly interact during its life cycle—those in its operational domain as well as all
other direct actors.
• The next system is a special case of those actors . . .
LC Managers

Manager for Target
Target System
1. Target System
Environment
23
• LC Manager of Target System: Manages all life cycle aspects of the Target System, as recognized by
ISO 15288. Note that this is more than just development or systems engineering—it includes
manufacturing or acquisition, operations, maintenance, configuration management, and all the ISO
System Management Functional Areas.
– However, it addresses only “already known” aspects of System 1 and Domain Actors—it does not
include responsibility of learning new things about them . . .
LC Managers

Manager for Target
Target System
1. Target System
Environment
Copyright © 2016 by W. D. Schindel and Rick Dove. Permission granted to INCOSE to publish and use. 24
• Learning & Knowledge Manager for Target System (and Components): Responsible for learning new
things about the Target System, its Components, and its Environment. This may include extraction of
patterns or other knowledge from observations, planning experiments and extracting conclusions from
their results, and other forms of learning. It also includes responsibility for accumulation and
persistent memory of those learnings, and for providing the resulting knowledge for use by the LC
Managers of the Target System.
LC Managers

Manager for Target
Target System
1. Target System
Environment
25
– Again, remember that these are logical (behavioral) roles. In realized systems, a
single physical system may behave as both a Target System and a system that
produces, modifies, reconfigures, or otherwise manages a Target System, by
having roles from each allocated to it.
– For purposes of this logical roles description, they have been identified separately.
– We introduce the physical components into the model later.
LC Managers

Manager for Target
Target System
1. Target System
Environment
26
System 3: The System of Innovation: (Definition) The logical system
responsible for managing the life cycles of instances of any (System 2)
Target System LC Manager.
• (Recall that those System 2 Target System LC Managers include Target
System development, production, integration, maintenance, operations,
and other management systems.)

LC Managers

Manager for Target
Target System
1. Target System
Environment
27
The System 3 model recognizes two sub-systems of System 3:
• Life Cycle Manager of LC Managers
• Learning & Knowledge Managers for LC Managers of Target Systems

LC Managers

Manager for Target
Target System
1. Target System
Environment
28
• Life Cycle Manager of LC Managers: Manages all life cycle aspects of the LC Managers of Target
Systems, as recognized by ISO 15288. Note that this is more than just development or systems
engineering—it includes their design or acquisition, maintenance, configuration management, and all
the ISO System Management Functional Areas.
– However, it addresses only “already known” aspects of the LC Managers in System 2—it does not
include responsibility of learning new things about them . . .
LC Managers

Manager for Target
Target System
1. Target System
Environment 29
• Learning & Knowledge Managers for LC Managers of Target Systems: Responsible for learning new
things about the LC Managers in System 2. This may include extraction of patterns or other
knowledge from observations, planning experiments and extracting conclusions from their results,
and other forms of learning. It also includes responsibility for accumulation and persistent memory
of those learnings, and for providing the resulting knowledge for use by the Life Cycle Manager of
the LC Managers.
LC Managers

Manager for Target
Target System
1. Target System
Environment
30
• Summary so far:
– System 2, the Target System Life Cycle Domain System produces and modifies
instances of System 1, the Target Systems (and Components), and also learns
new things about System 1 and its environment.
– System 3, the System of Innovation, produces and modifies instances of System
2, the Target LC Managers, and also learns new System 2 things.
LC Managers

Manager for Target
Target System
1. Target System
Environment
31
Behind the “iconic” diagram, there is a formal
MBSE model that describes the ASELCM Pattern
Learning & Knowledge Manager for
Provides
LC Managers of Target System
Knowledge to
2. Target System (and Component) Life Cycle Domain System
(substantially all ISO15288 processes)
Life Cycle Manager of LC Managers Manages
Pattern Repository, Describing Manages Life Cycle of
Knowledge of Families of: Life Cycle of
LC Managers of Target Target Systems (and Components) Provides
System Configured Models Repository, Knowledge to
(all ISO15288 processes) (substantially all ISO15288 processes)
Describing Configured Instances of:
Pattern Repository,
LC Managers of Target LC Manager of Target System
System
Describing Knowledge of Families of: (and Components) Manages
(all ISO15288 processes) Life Cycle of
Provides Observations to Target System
Target System Life Cycle Domain
Actor Configured Models Repository,
1. Target System
Target System
Observes Component Target System
Target System
Actor
Provides Observations to
Target System
Target System Component
Component
Observes
Observes
Target System
Observes Life Cycle Domain
Actor
Some of these life cycle management roles may be assigned
to the same physical system as the Target System
32
Example: Applying the ASELCM Pattern to Plan
Agility Improvement in Health Care Systems
LC Managers

Manager for Target
Target System
1. Target System
Environment
(From INCOSE 2016 Agile Health Care Systems Conference) 33

3. Health Care System of Innovation (SOI)
Provides
Health Care Delivery Systems
Knowledge to
2. Patient Health Life Cycle Domain System
Life Cycle Manager of Health Care Delivery Manages
System Manages Life Cycle of
Pattern Repository, Describing
Health Care Delivery Target Systems (and Components) Provides
Health Care Delivery System
Pattern Repository, Manages
Health Care Delivery Describing Knowledge of Families of: (Health Care equivalents of Agile (extended) Life Cycle of
System ISO15288 Model, including HC equivalents of
Observes Performance, Fault, Configuration, Accounting,
Provides Observations to and Security Management Processes)
Patient
Patient
Environment
1. Target System
Pharma Molecule Best Medical
Database Practices Database
Practice Health Care Delivery Patient Describing Configured Instances of:
Management Investor Component
System Supplier Patient
Health Care
Evidence-Based Pharmaceutical
Research Web Site Patient
Medicine Repository Medical School Supplier Patient
Environment
Crowd-Sourced
Medical Devices and
Health Care Web Site Contract Research Nursing School Observes Patient
Equipment Supplier Patient Subsystem
Organization (CRO) Component
Orthopedics
Health Care Expert Teaching Hospital Observes
Manufacturer
Life Scientist
Medical Information Genetics
Health Care
Technologies Database Health Care
Organizational Medical Caregiver
Change Consultant
Supplier
Journal Organization Observes Patient
Life Sciences HC Education Health Care Environment
Contractual Medical Repository
Medical Practice Life Sciences Service Practitioner
Trials Business Hospital
Consultant Textbook Medical Records Home
Health Care Payer
Contractual Medical System Environment
Health Care Private Practice
Products Developer Insuring Diagnostic
Delivery Holding Occupational
Employer Service System
Company Contract Medical Clinic Environment
Manufacturer Care Plan
Health Care Insuring Family Development School
Systems Therapeutic Environment
Health Care Systems
Engineering, Business Office Service System Extracurricular
Maintenance &
Fabrication, Environment
Support Facilities and
Construction & Pharmacy
Installation Infrastructure
Health Care Regulator Transcription
HR Role
Provider Insurer Service System
Health Care Domain Reference Boundaries:
Health Care Licenser Health Services
Health Care Coding Process Agile System Life Cycle Management Perspective
Marketing
Certification Agent Medical Products
Safety, Quality Health Care
Marketing
Equipment
INCOSE Patterns Working Group
Assurance
V1.3.1 10.28.2015
34
Example: Health care domain, top level Copyright © 2016 by W. D. Schindel and Rick Dove. Permission granted to INCOSE to publish and use.
Medical Device
A Breakout Exercise at the INCOSE 2016 Agile Health Care Systems Conference:
Assessing and Planning Agility Improvements in Health Care Systems
• Directions:
– Break into teams and discuss the following, then . . .
– In the domain model, identify the 5 highest cases of:
• Needs for improved future agility (even if most difficult)
Sticky Dots
• Opportunities for improved future agility (low-hanging fruit)

• Already accomplished examples of improved agility progress
(e.g., defense theater medicine, device software, etc.)
Sticky
– note In the domain model, identify potential corrections
or improvements to the model
35
3. Health Care System of Innovation (SOI)
Provides
Health Care Delivery Systems
Knowledge to
2. Patient Health Life Cycle Domain System
Life Cycle Manager of Health Care Delivery Manages
System Manages Life Cycle of
Pattern Repository, Describing
Health Care Delivery Target Systems (and Components) Provides
Health Care Delivery System
Pattern Repository, Manages
Health Care Delivery Describing Knowledge of Families of: (Health Care equivalents of Agile (extended) Life Cycle of
System ISO15288 Model, including HC equivalents of
Observes Performance, Fault, Configuration, Accounting,
Provides Observations to and Security Management Processes)
Patient
Patient
Environment
1. Target System
Pharma Molecule Best Medical
Database Practices Database
Practice Health Care Delivery Patient Describing Configured Instances of:
Management Investor Component
System Supplier Patient
Health Care
Evidence-Based Pharmaceutical
Research Web Site Patient
Medicine Repository Medical School Supplier Patient
Environment
Crowd-Sourced
Medical Devices and
Health Care Web Site Contract Research Nursing School Observes Patient
Equipment Supplier s or Patient Subsystem
ialtie Component
Organization (CRO) Spec ividuals etics
Orthopedics or e
Ind lved Gen
Health Care Expert
M
s of onal
Teaching Hospital Manufacturer Type Are Invo Pers Limited Observes
Is
ral That Life Scientist
Fede Medical Information
e of & Health Care Genetics
Cod lations Technologies Database Health Care
Regu ances Organizational Medical Caregiver
Gu id Change Consultant
Supplier
Journal Organization Observes Patient
Life Sciences HC Education Health Care Environment
Contractual Medical Repository
Medical Practice Life Sciences Service Practitioner
Trials Business Hospital
Consultant Textbook Medical Records Home
Health Care Payer
Contractual Medical System Environment
Health Care Private Practice
Products Developer Insuring Diagnostic
Occupational
Delivery Holding nefit Service System
y Be Employer Environment
UP Company Contract Medical r mac ment Clinic
T GRO P ha Care Plan
Manufacturer age
R E AK OU E HEALTH Health Care Ma n Insuring Family Development School
FB IL
L TS O 16 AG It Therapeutic to Environment
Systems Plan s
RESU , MAY 20 ERENCE Engineering,
Health Care Systems
h Care ISO Business Office Service System
ome
Outc ses Inter
face
Extracurricular
CIS E
C ON F Maintenance & He a lt
ld B e ly tient h Care
E XE R na Pa
CARE
A
Fabrication,
Support Shou 5288 Facilities and Healt ding Environment
Construction & 1
Care
Pharmacy (inclu nce)
odic Infrastructure ra
Installation
Health Care Regulator Epis Follow IS
O insu
It Transcription
Provider Insurer Does 15288 HR Role
Service System
Health Care Domain Reference Boundaries:
Health Care Licenser Health Services
Health Care Coding Process Agile System Life Cycle Management Perspective
Marketing
Certification Agent Medical Products
Safety, Quality Health Care
Marketing
Equipment
INCOSE Patterns Working Group
Assurance
ppor
t V1.3.1 10.28.2015
n Su Medical Device
De cisio
y
Polic
h Care
Healt R3 1 2
s CF
Drug logics
Bio
36
Concluding Discussion, Q&A
• The ASELCM Pattern also contains a lot more detail levels
• The ASELCM Pattern is a work in process
• Being validated and used in the ASELCM Project
• You are invited to participate!
•
•
•
•
37
Primary References
1. Rick Dove, Ralph LaBarge, “Fundamentals of Agile Systems Engineering—Part 1” and “Part 2”, INCOSE IS2014, July, 2014.
2. Rick Dove, “Agile Systems 101”, “102” and “103”, Paradigm Shift, International, http://www.parshift.com/s/AgileSystems-
101.pdf
3. ----------------, Response Ability: The Language, Structure, and Culture of the Agile Enterprise, Wiley, 2001.
4. Martin Fowler and Jim Highsmith. “The Agile Manifesto”. Dr. Dobb's Journal, August, 2001. www.drdobbs.com/open-
source/the-agile-manifesto/184414755 .
5. J. Highsmith. Agile Software Development Ecosystems. Addison-Wesley Professional, 2002.
6. W. Schindel, “What Is the Smallest Model of a System?”, Proc. of the INCOSE 2011 International Symposium,
International Council on Systems Engineering (2011).
7. Bill Schindel, Troy Peterson, “Introduction to Pattern-Based Systems Engineering (PBSE): Leveraging MBSE Techniques”,
in Proc. of INCOSE 2013 International Symposium, Tutorial, June, 2013.
8. W. Schindel, “Maps or Itineraries?: A Systems Engineering Insight from Ancient Navigators”, to appear in Proc. of INCOSE
International Symposium 2015, July, 2015.
9. ----------------, “System Life Cycle Trajectories: Tracking Innovation Paths Using System DNA”, to appear in Proc. of INCOSE
International Symposium 2015, July, 2015.
10. Schindel and Beihoff: “Systems of Innovation I: Models of Their Health and Pathologies”, Proc. of INCOSE International
Symposium, 2012.
11. W. Schindel, “Systems of Innovation II: The Emergence of Purpose”, Proceedings of INCOSE 2013 International
Symposium (2013)
38
Secondary References
1. Rick Dove, “Agile Systems and Processes—Driving Architecture with ConOps and Response Situation Analysis (Agile 102)”, Paradigm Shift,
International, September 16, 2013.
2. Rick Dove, “Security R Us: Systems Engineering is the High Ground”, INCOSE Biomedical Healthcare Working Group, April 24, 2014.
3. W. Schindel, “Requirements statements are transfer functions: An insight from model-based systems engineering”, Proceedings of INCOSE 2005
International Symposium, (2005).
4. “OMG Systems Modeling Language, Version 1.3”, Object Management Group, June, 2012.
5. W. Schindel, and V. Smith, “Results of applying a families-of-systems approach to systems engineering of product line families”, SAE International,
Technical Report 2002-01-3086 (2002).
6. W. Schindel, “Pattern-Based Systems Engineering: An Extension of Model-Based SE”, INCOSE IS2005 Tutorial TIES 4, 2005.
7. J. Bradley, M. Hughes, and W. Schindel, “Optimizing Delivery of Global Pharmaceutical Packaging Solutions, Using Systems Engineering Patterns”
Proceedings of the INCOSE 2010 International Symposium (2010).
8. W. Schindel, “The Impact of ‘Dark Patterns’ On Uncertainty: Enhancing Adaptability In The Systems World”, in Proc. of INCOSE Great Lakes 2011
Regional Conference on Systems Engineering, Dearborn, MI, 2011
9. INCOSE/OMG Patterns Working Group 2013-14 http://www.omgwiki.org/MBSE/doku.php?id=mbse:patterns:patterns
10. W. Schindel, S. Peffers, J. Hanson, J. Ahmed, W. Kline, “All Innovation is Innovation of Systems : An Integrated 3-D Model of
Innovation Competencies ”, Proc. of ASEE 2011 Conference, American Association for Engineering Education, (2011).
11. ISO/IEC 15288: Systems Engineering—System Life Cycle Processes. International Standards Organization (2014).
12. INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities, Version 4, International Council on Systems
Engineering (2014).
13. “A World in Motion: Systems Engineering Vision 2025”, INCOSE, 2014.
14. “Instrument Unit Fact Sheet: Saturn V News Reference”, IBM Federal Systems Division, 1968.
15. W. David Woods, Kenneth D. MacTaggart and Frank O'Brien, “Apollo 11 Flight Journal: Day 2, Part 1: Mid Course Correction”,
http://history.nasa.gov/ap11fj/05day2-mcc.htm , updated 2009.
39
Back Up
See --
http://www.omgwiki.org/MBSE/doku.php?id=mbse:incose_mbse_iw_2015:breakout_out_session_agile_modeling
40
What is the INCOSE MBSE Patterns Working Group?
http://www.omgwiki.org/MBSE/doku.php?id=mbse:patterns:patterns
MBSE Patterns Working Group’s PBSE Methodology Summary for INCOSE includes overview and many references:
“Pattern-Based Systems Engineering (PBSE), Based On S*MBSE Models”, INCOSE Patterns Challenge Team, 2015.
41
Introduction to
INCOSE MBSE Patterns Working Group
• Started in 2013, meeting several times a year, membership across domains.
• Team Co-chairs: Bill Schindel, Troy Peterson
• Eleven accepted IS2015+IS2016 Patterns Team member papers.
• Re-usable, configurable, MBSE models (“Patterns”).
• Based on S*Metamodel.
• Language and tool independent—frequently in SysML.
• Methodology practiced across domains ~ 20 years.
• For more information . . .
http://www.omgwiki.org/MBSE/doku.php?id=mbse:patterns:patterns
42
Cooperative
cross-team/working group projects
• The Patterns Working Group has been reaching
out to other INCOSE and industry working groups:
– Joint projects of interest.
• Examples:
• SoS Working Group
• Agile Systems Working Group
• PLE Working Group
• Others in discussion for 2016-2017
43
S*Models, S*Patterns
Stakeholder
Stakeholder
World Requirement Stakeholder Feature
Language Statement
attribute attribute
Functional
S*Metamodel for Interaction State System
S*Pattern Hierarchy for High Level (Interaction)
Pattern-Based Systems Model-Based Systems Requirements
Engineering (PBSE) Engineering (MBSE) System of

Interface Access
“A” Matrix Input/

Couplings
Technical
Output
World
Language BB
General BB (logical system)
System Technical
Functional
WB
Pattern Detail Level
WB
Requirement
Role
Requirements
Statement
attribute
Configure, attribute
Improve
Specialize
Pattern Product Lines or (physical system)
Pattern Design
System Families Design
High Level Constraint “B” Matrix
Design Component Couplings
Statement
attribute attribute
Individual Product
or System Configurations
System Pattern
Class Hierarchy
System Containment Hierarchy

44
45
Extracts from Vehicle Pattern in 2013 INCOSE PBSE Tutorial
Relating Scrum and ISO 15288 Process Models
• More Than One Representation (Model View) of the Same

Underlying (Process) Reality . . .
46
ISO15288
Reference Processes
ISO15288 Technical Processes appear in 3. System of Innovation (SOI)

Provides
System 2 (for target) and System 3 (for LC

Knowledge to
managers), as (potentially concurrent) “Vee”

Pattern Repository,
Describing Knowledge of Families of: Manages
processes, and learning sources.

System (and Components)
1. Target System
Target System
Target System
Actor
Target System
Component
Observes
Observes
Target System

Actor
47
48
Agile Scrum Model
(See IW2015 MBSE Workshop Attachment I for more.)
Traditional Scrum Sprint Perspective
(Summary State Machine)
Project
Initiated
Planning Project
Project
“Perform Developmental Task” may include, as appropriate,
any team-selected task from the ISO 15288 Technical
Processes that could be performed by the internal team
(Simplified Model of Managed Information)
Initiate Product Backlog (e.g., Requirements, Design, Implementation, Verification
Planned
Testing, etc.)
Performing a Sprint (Time Limited)
text
text
text
text
text Is Approved For
text text
text
text
text
text
Performing Sprint Development
text
Planning Sprint
Sprint Time
Review Priority Items & Attend Daily Scrum Window Ends
Set Sprint Thematic Goal Sprint
Planned Perform
Forecast Sprint Developmental Task
Content Items Potentially Shippable
Track Daily Progress Development
Product Release Product Backlog Product Increment
Resource
(Definition of Done)
Capacity Load Backlog Version Sprint ID
Release ID
Refining Future Sprint Backlog Release Date Allocated Schedule
Analyze Future Item Remaining Sprint Burn Down
Requirements Is Allocated To
Is Responsible Sprint Technical Risk
Split, Merge, Rescope Backlog Item Describes
Future Items Sprint Time For
Estimate Future Items Window Ends
Cost Estimate
Technical Risk Estimate
Priority
Deliverable
Status
Inspected Product
Not Ready for Release Requirement
Retrospective Conducting Sprint
Process Retrospective (not “Done”) Conducting Sprint
Completed
Review Process & Product Review Requirement Attribute
Environment
Inspect Product Non-Feature Item Feature Item
Adapt Process &
Environment Update Product
Inspected Product Backlog Feature Attribute
Project
Ready for Release
Termination
(“Done”)
Is Allocated To
Subsequent Life Cycle of
Product Release
Release Performing
Life Cycle Perform Target Product Product Release
Ended Interaction Released Release Product
Provide In-Service Copyright 2015, ICTT System Sciences
Feedback
Traditional Scrum Sprint Perspective Traditional Scrum Sprint Perspective

(ActivityCopyright
Diagram,2015,
with Swim Lane Roles) (Activity Diagram, with Swim Lane Roles)
ICTT System Sciences
Target Target
Stakeholder Product Scrum Development Development Target Stakeholder Product Scrum Development Development Target
System System
(incl. Customer) Owner Master Team Environment System (incl. Customer) Owner Master Team Environment System
Environment
Environment
Planning Project
Planning Project Project
Project Initiated Initiate Product Backlog
Initiated Initiate Product Backlog
Project Performing a Sprint (Time Limited)

Project Performing a Sprint (Time Limited)
Planned Planning Sprint
Review Priority Items & Set Sprint Thematic Goal
Forecast Sprint Content Items

Forecast Sprint Content Items

Performing Sprint Development Sprint
Sprint Planned Attend Daily Scrum Sprint Time
Planned Attend Daily Scrum Sprint Time Window Ends
Window Ends Perform Developmental Task
Perform Developmental Task
Track Daily Progress
Track Daily Progress Scrum-Scrum
Refining Future Sprint Backlog
Feedback Loop
Refining Future Sprint Backlog Analyze Future Item Requirements
Analyze Future Item Requirements Sprint Time
Split, Merge, Rescope Future Items Window Ends
Sprint Time
Split, Merge, Rescope Future Items Window Ends
Estimate Future Items
Conducting Sprint Product Review

Conducting Sprint Product Review
Release-Release
Inspect Product
Feedback Loop
Inspect Product
Update Product Backlog
Inspected Product
Update Product Backlog Not Ready for Release
Inspected Product Conducting Sprint Process Retrospective (not “Done”) Inspected Product
Not Ready for Release Retrospective Ready for Release
Conducting Sprint Process Retrospective (not “Done”) Inspected Product Completed Review Process & Environment (“Done”)
Retrospective Ready for Release
Completed Review Process & Environment (“Done”)
Adapt Process & Environment
Adapt Process & Environment
Performing Product Release
Product
Performing Product Release Release Product Released
Product
Release Product Released
Release
Subsequent Life Cycle of Product Release Life Cycle
Release Ended
Subsequent Life Cycle of Product Release Life Cycle Perform Target Interaction
Ended
Perform Target Interaction
Provide In-Service Feedback

Provide In-Service Feedback
49
Copyright 2015, ICTT System Sciences
More Than One Representation
(Model View) of the Same Underlying Reality
We are dealing with four different representations of the same underlying reality:
1. The Scrum Pattern: Emphasizes time-bound outputs and feedback, focusing on processes for learning from
produced outputs, and management of risk
2. The ISO15288 Pattern: Emphasizes types of processes, focusing on management of processes
3. The Agile Systems Engineering Life Cycle Pattern : Shows how (1) and (2) above may be seen as one
4. The S*Metamodel: Emphasizes the information flowing through all three of them: (1), (2), and (3)
Project
Initiated

Planning Project
Project Processes that could be performed by the internal team
Planned
Testing, etc.)
text
text
text
text
text
text text
text
text
text
text
ISO15288 Pattern
text
Scrum Pattern
Planning Sprint
Sprint Time
Planned Perform
Content Items
Analyze Future Item

Requirements
Split, Merge, Rescope
Future Items Sprint Time
Inspected Product
Not Ready for Release
Completed
Review Process & Product Review
Environment
Inspect Product
Adapt Process &
Inspected Product Backlog
Project
Ready for Release
Termination
(“Done”)

Product Release
Release Performing
Provide In-Service
Feedback
3. System of Innovation (SOI) S*Metamodel for Stakeholder

Stakeholder
Learning & Knowledge Manager for Model-Based Systems World Requirement Stakeholder Feature
Provides Language Statement
Knowledge to
2. Target System (and Component) Life Cycle Domain System Engineering (MBSE) attribute attribute
ASELC Pattern S*Metamodel

Pattern Repository, Describing (substantially all ISO15288 processes)
Manages Life Cycle of S*Pattern Hierarchy for Functional
Knowledge of Families of: Life Cycle of Interaction State System
Pattern-Based Systems High Level (Interaction)
LC Managers of Target
System
Target Systems (and Components) Provides Engineering (PBSE) Requirements
Configured Models Repository, Knowledge to
Describing Configured Instances of: System of
Interface Access
Pattern Repository,
System
(substantially all ISO15288 processes) “A” Matrix Input/
Provides Observations to Target System Couplings
Target System Life Cycle Domain 1. Target System Technical
Output
World
Describing Configured Instances of: Language BB
Observes
Target System
Component Target System General BB (logical system)
Target System
System Technical
Functional
WB
Actor Pattern Detail Level
WB
Requirement
Role
Provides Observations to Requirements
Statement
Target System attribute attribute
Component
Observes
Product Lines or (physical system)
Design
Observes High Level Constraint “B” Matrix
Target System Design Component Couplings
Statement
Actor attribute attribute
50
Individual Product
or System Configurations
System Pattern
Class Hierarchy
• The Scrum Model is actually an abstraction of the more complex-looking multiple
Processes of the ISO15288 System Life Cycle reference model:
– As indicated in the Agile literature, nothing about the Scrum Model is intended to
prevent things like Requirements Analysis, Verification (Test), or even aspects of
Project Management, . . .
– But those activities are shared by the small team members who play many
individual roles, and the simpler-looking Scrum model “gives us permission” to “do
what is needed” in a given situation, in an “agile way”.

Project
Initiated

Planning Project
Planned
Testing, etc.)
text
text
text
text
text
text text
text
text
text
text
text
Planning Sprint
Sprint Time
Sprint
Scrum Pattern ISO15288 Pattern

Set Sprint Thematic Goal
Planned Perform
Content Items
Analyze Future Item

Requirements
Inspected Product
Completed
Environment
Inspect Product
Adapt Process &
Project
Ready for Release
Termination
(“Done”)

Product Release
Release Performing
Provide In-Service
Feedback
51
• The Scrum Model also abstracts complex learning behavior, into simple-looking
form—but it is still strongly expected to occur as part of the Agile Process, and is
more explicitly represented in the ASELC Pattern, as capture of Pattern
information—not assumed to be only in human minds.
Project
Initiated
Learning
Planning Project
Project
Initiate Product Backlog
Planned
Planning Sprint Performing Sprint Development
Scrum Pattern
Sprint Time
text
Sprint
text
text
Set Sprint Thematic Goal
Planned Perform text
text

Content Items
text text
Track Daily Progress text

text
text
text
text
Analyze Future Item Sprint Time

Requirements
Window Ends
Future Items
Inspected Product
Completed
Environment
Inspect Product
Adapt Process &
Project
Ready for Release
Termination
(“Done”)

Release Performing
Product Release Product Release
Life Cycle Product
Ended Perform Target Released Release Product
Interaction
ASELC Pattern S*Metamodel for

Stakeholder
Stakeholder
3. System of Innovation (SOI) Model-Based Systems World Requirement Stakeholder Feature
Language Statement
Engineering (MBSE) attribute attribute
Provides
Knowledge to
S*Metamodel
(substantially all ISO15288 processes) S*Pattern Hierarchy for Functional
Pattern-Based Systems Interaction State System
Pattern Repository, Describing Manages Life Cycle of High Level (Interaction)
Life Cycle of Engineering (PBSE) Requirements
Learning & Knowledge Manager for System of

LC Managers of Target Target Systems (and Components) Provides Interface Access
Pattern Repository, “A” Matrix Input/
LC Managers of Target LC Manager of Target System Couplings
Describing Knowledge of Families of: (and Components) Manages Technical
Output
System
(all ISO15288 processes) Life Cycle of World
(substantially all ISO15288 processes) Language BB
Provides Observations to Target System General BB (logical system)
1. Target System System Technical
Functional
WB
Actor Pattern Detail Level
WB
Requirement
Role
Describing Configured Instances of: Requirements
Statement
Target System attribute attribute
Target System
Target System Life Cycle Domain Product Lines or
Actor (physical system)
Design
Provides Observations to System Families Design
Target System
Design Component Couplings
Target System Component Statement
Component attribute attribute
Observes
Individual Product
Observes or System Configurations
Target System
Actor
to the same physical system as the Target System System Pattern
Class Hierarchy
Learning often in upper-most S1,2,3 Pattern, but can also be in specializations and configurations below it. 52
• Notice that the division of the System 2&3 learning roles in the ASELCM Pattern
corresponds to the Scrum division of (review and learning about target system)
versus (review and learning about development process):
Pattern: Learnings about Target System
Project
Initiated
Planning Project
Project
Processes that could be performed by the internal team
(Product & Its Environment)
Planned
Testing, etc.)
text
text
text
text
text
text text
text
text
text
text
text
Planning Sprint
Sprint Time
Scrum Pattern
Planned Perform
Content Items
Analyze Future Item

Requirements
Pattern: Learnings about Development /

Inspected Product
(not “Done”)
Fielding System & Its Environment

Completed Process Retrospective Conducting Sprint
Environment
Inspect Product
Adapt Process &
Project
Ready for Release
Termination
(“Done”)

Product Release
Release Performing
Provide In-Service
Feedback
ASELC Pattern
Stakeholder
Model-Based Systems World Requirement Stakeholder Feature
Learning & Knowledge Manager for Language Statement
LC Managers of Target System Provides
Knowledge to
S*Metamodel
Life Cycle Manager of LC Managers Manages S*Pattern Hierarchy for Functional
Pattern Repository, Describing Manages Life Cycle of Interaction State System
Life Cycle of Pattern-Based Systems High Level (Interaction)
Learning & Knowledge Manager for Engineering (PBSE) Requirements

System System of
Configured Models Repository, Knowledge to Interface Access
Pattern Repository,
System
Describing Knowledge of Families of: (and Components) Manages “A” Matrix Input/
Couplings
(all ISO15288 processes) Life Cycle of Output
Technical
World
Provides Observations to Target System Language BB
1. Target System General BB (logical system)
Describing Configured Instances of: System Technical
Functional
WB
Target System Pattern Detail Level
WB
Requirement
Role
Observes Component Target System Requirements
Statement
Target System attribute
attribute
Actor
Provides Observations to Product Lines or (physical system)
Target System Design
Component
Design Component
Observes Statement Couplings
attribute attribute
Observes Individual Product

Target System
Observes Life Cycle Domain or System Configurations
Actor
System Pattern
Class Hierarchy
53
• Notice that the division of the System 2&3 learning roles in the ASELCM Pattern
corresponds to the Scrum division of (review and learning about target system)
versus (review and learning about development process):
Pattern: Learnings about Target System
Project
(Product & Its Environment)
Initiated

Planning Project
Planned
Testing, etc.)
text
text
text
Scrum Pattern
text
text
text text
text
text
text
text
text
Planning Sprint
Sprint Time
Planned Perform
Content Items
Pattern: Learnings about Development /

Analyze Future Item

Requirements
Retrospective
Completed
Conducting Sprint
Process Retrospective
Review Process &
Environment
Inspected Product
(not “Done”) Conducting Sprint
Product Review
Inspect Product
Fielding LC Management System(s) &
Its Environment
Adapt Process &
Project
Ready for Release
Termination
(“Done”)
ASELC Pattern
Product Release
Release Performing
Provide In-Service
Feedback

Stakeholder
Model-Based Systems World Requirement Stakeholder Feature
Learning & Knowledge Manager for Language Statement
LC Managers of Target System Provides
Knowledge to
S*Metamodel
Life Cycle Manager of LC Managers Manages S*Pattern Hierarchy for Functional
Pattern Repository, Describing Manages Life Cycle of Interaction State System
Life Cycle of Pattern-Based Systems High Level (Interaction)
Learning & Knowledge Manager for Engineering (PBSE) Requirements

System System of
Configured Models Repository, Knowledge to Interface Access
Pattern Repository,
System
Describing Knowledge of Families of: (and Components) Manages “A” Matrix Input/
Couplings
(all ISO15288 processes) Life Cycle of Output
Technical
World
Provides Observations to Target System Language BB
1. Target System General BB (logical system)
Describing Configured Instances of: System Technical
Functional
WB
Target System Pattern Detail Level
WB
Requirement
Role
Observes Component Target System Requirements
Statement
Target System attribute
attribute
Actor
Provides Observations to Product Lines or (physical system)
Target System Design
Component
Design Component
Observes Statement Couplings
attribute attribute
Observes Individual Product

Target System
Observes Life Cycle Domain or System Configurations
Actor
System Pattern
Class Hierarchy
54
Learning & Knowledge Provides 2. Target System (and Component) Life Cycle Domain System
Manager for LC Managers Knowledge to
of Target System
Pattern Repository
Life Cycle Manager of
LC Managers
Configured Models
Manages
Life Cycle of
Manages
Life Cycle of
Learning & Knowledge Provides

System 2
Manager for Target Systems Knowledge to
LC Managers of
Target System
Repository,
Configured Instances of:
Performs most of these ISO
Pattern Repository LC Manager of
LC Managers of Knowledge of Families of: Target System
Manages
Life Cycle of
processes, to manage what is
Target System Target System
Provides
Observations to
Target
System
Life Cycle Domain
Actor
Configured Models
Repository,
1. Target System being learned about S1 space.
Target System Configured Instances of: Target
Observes System Life Cycle Management System
Component Target System
Target System (Adapted from ISO/IEC 15288:2015)
Life Cycle Domain
System 3 Observes
Provides
Observations to
System
Actor
Target System
Component
Target System
Component
Project Planning
Risk Management
Project Processes
Project Assessment
and Control
Configuration
Management
Decision Management
Information
Management
Quality Assurance
Process
Measurement
Manages
Technical Processes
Design: Top System
Business, Mission
Substantially all the ISO15288 processes

Analysis
Target
Stakeholder Needs, Realization: Top System
Requirements
Observes Requirements
Definition
Validation
are included in all four Manager roles. Target System

System
Requirements
Verification Solution
Definition
(by Test) Validation Transition
Observes Organizational Project-

Architecture
Life Cycle
Definition
Enabling Processes
System
Project Portfolio Design Definition Integration Operation Maintenance
Management
Logical only: Some Manager roles may be allocated Domain Actor Infrastructure
Management
System
Analysis
Verification
(by Analysis &
Simulation)

Disposal
Life Cycle Model
Management Design: Subsystem 3 Realization: Subsystem 3
Human Resource Design: Subsystem 2 Realization: Subsystem 2

Management
Family
Design: Subsystem 1 Realization: Subsystem 1
Business, Mission
Quality Analysis
Management
Stakeholder Needs,
Requirements Verification
Requirements Solution Validation
Knowledge Validation (by Test)
Definition
Management

Process
System
Requirements
Definition
Agreement Processes Integration
Patterns
Architecture
Definition
Acquisition
Design Definition
processes, to manage S1
Supply Verification
System
System Life Cycle Management System Analysis

(by Analysis &
Simulation)
Component Level Design,
Acquisition, Fabrication
(Adapted from ISO/IEC 15288:2015)

Implementation
instances , using S1 patterns Project Planning

Project Processes
Project Assessment
and Control
Decision Management Quality Assurance
Process
Configuration Information
Risk Management Measurement
Management Management
Technical Processes
Design: Top System
Business, Mission
Analysis
Requirements
Requirements
Validation
Definition
System
Requirements
Manages LC Management
Definition
Architecture
Organizational Project- Definition
Enabling Processes

Management
Verification
System
Infrastructure (by Analysis &
Analysis
Management Simulation)
System Family Patterns

Disposal
Life Cycle Model

Business, Mission
Quality Analysis
Management
Stakeholder Needs,
Management
Process
Definition
System
System Life Cycle Management System
Requirements
Definition
Agreement Processes
Architecture
Integration (Adapted from ISO/IEC 15288:2015)
Definition
Acquisition
Design Definition
Supply Project Processes

Verification
System
(by Analysis &
Analysis Project Assessment Quality Assurance
Simulation) Project Planning Decision Management
and Control Process
Configuration Information
Risk Management Measurement
Management Management
Implementation
Technical Processes
Design: Top System
Business, Mission
Analysis
Requirements
Requirements
Validation
Definition
System
Requirements
Definition
Architecture
Organizational Project- Definition
Enabling Processes

Management
Verification
System
Analysis
Disposal
Life Cycle Model

Business, Mission
Quality Analysis
Management
Stakeholder Needs,
Definition
Management
Process
System
Requirements
Definition

ASELCM Pattern: System 1

Architecture
Definition
Acquisition
Design Definition
Supply Verification
System
System Life Cycle Management System Analysis

(by Analysis &
Simulation)
processes, to manage S2
(Adapted from ISO/IEC 15288:2015)

Implementation
(Target System) agility, instances , using S2 patterns Project Planning
Risk Management
and Control
Project Processes
Project Assessment
Configuration
Management
Decision Management
Information
Management
Technical Processes
Quality Assurance
Process
Measurement
driven by System 2 (Life
Design: Top System
processes, to manage what is

Business, Mission
Analysis
Requirements
Requirements
Validation
Definition
System
Requirements
Definition
Organizational Project-
Enabling Processes
Architecture
Definition
being learned about S2 space.

Cycle Management) and
Management
Verification
System
Analysis
Disposal
Life Cycle Model

System 3 (System of
Business, Mission
Quality Analysis
Management
Stakeholder Needs,
Definition
Management
Process
System
Requirements
Definition
Architecture
Definition
Acquisition
Innovation).
Design Definition
Supply Verification
System
(by Analysis &
Analysis
Simulation)
55
Implementation
(Simplified Model of Managed Information)
Is Approved For
Potentially Shippable
Development
Product Release Product Backlog Product Increment
Resource
(Definition of Done)
Capacity Load Backlog Version Sprint ID
Release ID
Release Date Allocated Schedule
Remaining Sprint Burn Down

Is Allocated To
Is Responsible Sprint Technical Risk
Backlog Item Describes
For
Cost Estimate
Technical Risk Estimate
Priority
Deliverable
Status
Requirement
Requirement Attribute
Non-Feature Item Feature Item
Feature Attribute
Is Allocated To

56
Agile Scrum Specialization of the ASELCM Pattern Traditional Scrum Sprint Perspective
(Activity Diagram, with Swim Lane Roles)
Target
Stakeholder Product Scrum Development Development Target
System
(incl. Customer) Owner Master Team Environment System
Environment
Planning Project
Project
Initiated Initiate Product Backlog System Life Cycle Manager: Logical Architecture
Project Performing a Sprint (Time Limited) (Adapted from ISO/IEC 15288:2014)
Project Processes
Project Quality
Forecast Sprint Content Items Project Decision
Assessment Assurance
Planning Management
and Control Process
Risk Configuration Information

Measurement
Performing Sprint Development Management Management Management
Sprint
Planned Attend Daily Scrum Sprint Time
Window Ends
Perform Developmental Task
Technical Processes
Design: Top System
Track Daily Progress Business, Mission
Analysis
Scrum-Scrum
Feedback Loop Requirements
Requirements
Validation
Definition
Analyze Future Item Requirements System
Requirements
Sprint Time Verification Solution
Window Ends Definition
Split, Merge, Rescope Future Items (by Test) Validation
Architecture
Estimate Future Items Organizational Project- Definition
Enabling Processes
Service
Project
Portfolio Design Definition Integration
Management Transition
Verification
System
Conducting Sprint Product Review Infrastructure
Analysis
(by Analysis &
Release-Release Management Simulation)
Inspect Product
Feedback Loop
Life Cycle Model
Update Product Backlog Operation Maintenance
Inspected Product
Not Ready for Release Human Design: Subsystem 2 Realization: Subsystem 2
Conducting Sprint Process Retrospective (not “Done”) Inspected Product Resource
Retrospective Ready for Release Management Design: Subsystem 1 Realization: Subsystem 1
Completed Review Process & Environment (“Done”) Business, Mission Disposal
Quality Analysis
Adapt Process & Environment Management
Stakeholder Needs,
Requirements Verification Solution
Knowledge Requirements
Validation (by Test) Validation
Performing Product Release Management Definition
Product
Process
Release Product Released System
Requirements
Definition
Release Integration
Subsequent Life Cycle of Product Release Life Cycle Agreement Processes
Architecture
Ended Definition
Perform Target Interaction Acquisition
Design
Definition
Provide In-Service Feedback Supply Verification
System
(by Analysis &
Analysis
Simulation)
Implementation
4 Instances
Provides
Knowledge to
Pattern Repository,
System
1. Target System
Target System
Target System
Actor
Target System
Component
Observes
Observes
Target System
Actor
to the same physical system as the Target System 57

Is2016 Intro To The Aselcm Pattern v1.4.8

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Is2016 Intro To The Aselcm Pattern v1.4.8

Uploaded by

Copyright:

Available Formats

Introduction to the Agile Systems

Engineering Life Cycle MBSE Pattern

Free Flight Phase Updates:

Stakeholder Feature Subspace Sub-subspaces

Feature Feature Feature

Summary of S*Metamodel attribute attribute

Defines System Configuration Space Feature Feature Feature

Interface attribute attribute

System Configuration Space Design

(S*Space) attribute attribute

Design Design Design

Feature Feature Feature

Feature Feature Feature

Technical Behavior Subspace

S1 Attribute Physical Architecture Subspace

for Target Systems Coupling Design Design Design

“PBSE as Agile MBSE” emerges as essential when competing on agility becomes

• The SE Process consumes and produces information.

• Model-based Patterns in S*Space.

Learning & Knowledge

• A key subset of the ASELCM Pattern is--

Learning & Knowledge

Learning & Knowledge

Learning & Knowledge

3. System of Innovation (SOI)

Learning & Knowledge

Learning & Knowledge

Learning & Knowledge

Learning & Knowledge

Learning & Knowledge

3. System of Innovation (SOI)

Learning & Knowledge

3. System of Innovation (SOI)

Learning & Knowledge

Learning & Knowledge

Learning & Knowledge

Learning & Knowledge

Learning & Knowledge

(From INCOSE 2016 Agile Health Care Systems Conference) 33

• Opportunities for improved future agility (low-hanging fruit)

Engineering (PBSE) Engineering (MBSE) System of

“A” Matrix Input/

System Containment Hierarchy

• More Than One Representation (Model View) of the Same

ISO15288 Technical Processes appear in 3. System of Innovation (SOI)

System 2 (for target) and System 3 (for LC

managers), as (potentially concurrent) “Vee”

processes, and learning sources.

Some of these life cycle management roles may be assigned

Performing a Sprint (Time Limited)

Traditional Scrum Sprint Perspective Traditional Scrum Sprint Perspective

Project Performing a Sprint (Time Limited)

Forecast Sprint Content Items

Performing Sprint Development

Conducting Sprint Product Review

Provide In-Service Feedback

“Perform Developmental Task” may include, as appropriate,

Performing a Sprint (Time Limited)

Refining Future Sprint Backlog

Analyze Future Item

Subsequent Life Cycle of

Copyright 2015, ICTT System Sciences

3. System of Innovation (SOI) S*Metamodel for Stakeholder