november 2, 2016 model based systems engineering with no magic, inc. model based systems engineering...
TRANSCRIPT
![Page 1: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/1.jpg)
No Magic, Inc.
Model Based Systems Engineering with
MagicGrid
November 2, 2016
![Page 2: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/2.jpg)
System Model as an Integration Framework – Need
for Ecosystem
2© 2012-2014 by Sanford Friedenthal
19
![Page 3: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/3.jpg)
The modeling language
is just the language,
and must be combined
with a methodology to
be useful
5
![Page 4: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/4.jpg)
Need for a Method/Framework
This opens discussions of:
how to structure the model
what views to build
which artifacts to deliver
and in what sequence
Every company deals with the same issue differently. Some use:
• defense architecture frameworks: DoDAF, NAF, MODAF
• MBSE methods: OOSEM, Harmony, SYSMOD, FAS; however, saying there is no need for an architectural framework just doesn’t work.
77© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 5: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/5.jpg)
You always end-up using an
architecture framework
whether you want one or
not, or whether you intend
to or not
© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 6: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/6.jpg)
MagicGrid
99
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Sp
ecific
atio
n
Co
nce
pt
Stakeholder
Needs
Use
Cases
System
Context Measurements
of
Effectiveness
Pro
ble
m
System
Requirements
Functional
Analysis
Logical
Subsystems
Communication
De
sig
n
So
lutio
n
Component
Requirements
Component
Behavior
Component
Structure
Component
Parameters
© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 7: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/7.jpg)
1010© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 8: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/8.jpg)
MagicGrid – Problem Domain Definition
1111
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Co
nce
pt C1
Stakeholder
Needs
C2
Use Cases
C3
System Context
C4-P4
Measurements
of Effectiveness
Pro
ble
m P1
System
Requirements
P2
Functional
Analysis
P3
Logical
Subsystems
Communication
So
lutio
n S1
Component
Requirements
S2
Component
Behavior
S3
Component
Structure
S4
Component
Parameters
© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 9: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/9.jpg)
Case Study of Hybrid Automobile
• The Hybrid Automobile case study follows the
MagicGrid approach to describe the concept and
problem of a hybrid plug-in gas/electric powered
vehicle
• The model of the case study is based on SysML 1.4
and created with MagicDraw CASE tool
1212© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 10: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/10.jpg)
Stakeholder Needs
1313
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Co
nce
pt C1
Stakeholder
Needs
C2
Use Cases
C3
System Context
C4-P4
Measurements
of Effectiveness
Pro
ble
m P1
System
Requirements
P2
Functional
Analysis
P3
Logical
Subsystems
Communication
So
lutio
n S1
Component
Requirements
S2
Component
Behavior
S3
Component
Structure
S4
Component
Parameters
© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 11: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/11.jpg)
Stakeholder Needs
• The cell represents information gathered from all the
stakeholders of the system
• It includes primary user requirements, government
regulations, policies, procedures, etc.
• The later refinements in the model make these
stakeholder needs structured and formalized
1414© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 12: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/12.jpg)
Use Cases
1515
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Co
nce
pt C1
Stakeholder
Needs
C2
Use Cases
C3
System Context
C4-P4
Measurements
of Effectiveness
Pro
ble
m P1
System
Requirements
P2
Functional
Analysis
P3
Logical
Subsystems
Communication
So
lutio
n S1
Component
Requirements
S2
Component
Behavior
S3
Component
Structure
S4
Component
Parameters
© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 13: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/13.jpg)
Use Cases
• Functional use cases that provide measurable value
to the user
• Definitions of system contexts, wherein these use
cases are performed
• Use case scenarios on how the system interacts with
the user in the form of action/event flows
1616© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 14: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/14.jpg)
Use Cases
1717© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 15: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/15.jpg)
System Context
1818
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Co
nce
pt C1
Stakeholder
Needs
C2
Use Cases
C3
System Context
C4-P4
Measurements
of Effectiveness
Pro
ble
m P1
System
Requirements
P2
Functional
Analysis
P3
Logical
Subsystems
Communication
So
lutio
n S1
Component
Requirements
S2
Component
Behavior
S3
Component
Structure
S4
Component
Parameters
© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 16: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/16.jpg)
System Context
• Shows how the system interacts with the actors,
external and internal environment
• System context is modeled in the high level of
abstraction
• The purpose of this cell is to identify high level
interfaces needed for the system to communicate
with its environment
1919© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 17: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/17.jpg)
System Context
2020© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 18: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/18.jpg)
Measurements of Effectiveness (MoEs)
2121
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Co
nce
pt C1
Stakeholder
Needs
C2
Use Cases
C3
System Context
C4-P4
Measurements
of Effectiveness
Pro
ble
m P1
System
Requirements
P2
Functional
Analysis
P3
Logical
Subsystems
Communication
So
lutio
n S1
Component
Requirements
S2
Component
Behavior
S3
Component
Structure
S4
Component
Parameters
© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 19: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/19.jpg)
Measurements of Effectiveness (MoEs)
• Measurements of Effectiveness (MoE) are a traditional
term widely used in systems engineering and
describing how well a system carries out a task within
a specific context
• Represents non-functional stakeholder needs or
objectives for the system expressed in numerical
format
• In this abstraction layer it serves as the high level key
performance indicators that would be automatically
checked when the Solution layer is specified
2222© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 20: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/20.jpg)
Measurements of Effectiveness (MoEs)
2323© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 21: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/21.jpg)
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Co
nce
pt C1
Stakeholder
Needs
C2
Use Cases
C3
System Context
C4-P4
Measurements
of Effectiveness
Pro
ble
m P1
System
Requirements
P2
Functional
Analysis
P3
Logical
Subsystems
Communication
So
lutio
n S1
Component
Requirements
S2
Component
Behavior
S3
Component
Structure
S4
Component
Parameters
System Requirements
2424© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 22: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/22.jpg)
System Requirements
• Goals are long-term and global statements that
explain what systems engineers' want to achieve and
objectives define specific, quantifiable, time-
sensitive strategies or implementation steps to attain
the identified goals
• The goal and objective texts should follow agreed
guidelines or standards
2525© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 23: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/23.jpg)
System Requirements
2626© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 24: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/24.jpg)
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Co
nce
pt C1
Stakeholder
Needs
C2
Use Cases
C3
System Context
C4-P4
Measurements
of Effectiveness
Pro
ble
m P1
System
Requirements
P2
Functional
Analysis
P3
Logical
Subsystems
Communication
So
lutio
n S1
Component
Requirements
S2
Component
Behavior
S3
Component
Structure
S4
Component
Parameters
Functional Analysis
2727© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 25: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/25.jpg)
Functional Analysis
• Continuation of functional use case analysis, where
focus is internal system functions in some of the
techniques known as processes
• Action flows definition requires and stimulates the
identification of logical subsystems
2828© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 26: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/26.jpg)
Functional Analysis
2929© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 27: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/27.jpg)
Functional Analysis
30© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 28: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/28.jpg)
Functional Analysis
31© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 29: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/29.jpg)
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Co
nce
pt C1
Stakeholder
Needs
C2
Use Cases
C3
System Context
C4-P4
Measurements
of Effectiveness
Pro
ble
m P1
System
Requirements
P2
Functional
Analysis
P3
Logical
Subsystems
Communication
So
lutio
n S1
Component
Requirements
S2
Component
Behavior
S3
Component
Structure
S4
Component
Parameters
Logical Subsystems Communication
3232© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 30: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/30.jpg)
Logical Subsystems Communication
• Identified logical subsystems, based on the control and
resource flows captured in the functional analysis
model, are connected with one another in terms of
logical interfaces
• Logical interfaces are identified and defined
• Interface control documents (ICD) can be generated
3333© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 31: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/31.jpg)
Structure
<#>
![Page 32: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/32.jpg)
Logical Subsystems Communication
3535© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 33: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/33.jpg)
Magic Grid: Solution
3636© 2016 No Magic, Inc. Exclusively for No Magic Use
Pillar
So
lutio
n
Requirements Behavior Structure Parametrics
Syste
m
System
Requirements
System
Behavior
System
Assembly
Measurements
of Effectiveness
(MoEs)
Su
bsyste
m
Subsystem
Requirements
Subsystem
Behavior
Subsystem
Assembly
MoEs for
Subsystems
Co
mp
on
en
t
Component
Requirements
Component
Behavior
Component
Assembly
Physical
Component
Characteristics
![Page 34: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/34.jpg)
Solution Project Structure
<#>
![Page 35: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/35.jpg)
MagicGrid (2)
3838
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Sp
ecific
atio
n
Co
nce
pt
Stakeholder
Needs
Use
Cases
System
Context Measurements
of
Effectiveness
(MoEs)
Pro
ble
m
Goals &
Objectives
Functional
Analysis
Logical
Subsystems
De
sig
n
So
lutio
n
Component
Requirements
Component
Behavior
Component
Assembly
Component
Parameters
![Page 36: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/36.jpg)
Traceability - Concept
3939
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Co
nce
pt
Stakeholder
Needs
Use
Cases
System
ContextMeasurements
of Effectiveness
Pro
ble
m
System
Requirements
Functional
Analysis
Logical
Subsystems
Communication
So
lutio
n
Component
Requirements
Component
Behavior
Component
Structure
Component
Parameters
Refine Subject Containment
RefineRefine
© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 37: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/37.jpg)
Traceability - Problem
4040
Pillar
La
ye
ro
f A
bstr
actio
n
Requirements Behavior Structure Parametrics
Co
nce
pt
Stakeholder
Needs
Use
Cases
System
ContextMeasurements
of Effectiveness
Pro
ble
m
System
Requirements
Functional
Analysis
Logical
Subsystems
Communication
So
lutio
n
Component
Requirements
Component
Behavior
Component
Structure
Component
Parameters
Derive Composition
Refine
Composition
Allocate
© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 38: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/38.jpg)
Traceability
4141
![Page 39: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/39.jpg)
Conclusions
4343
• MagicGrid proposes a simplified framework
• Clearly defines the modeling process
• Reveals what models should be produced going from the highest to the
lowest abstraction layers of the system analysis and design
• Gives rules for managing relations among these layers
• Successful adopted on real-world projects
© 2016 No Magic, Inc. Exclusively for No Magic Use
![Page 40: November 2, 2016 Model Based Systems Engineering with No Magic, Inc. Model Based Systems Engineering with MagicGrid November 2, 2016](https://reader030.vdocuments.us/reader030/viewer/2022040401/5e76c93a045b8a09d56551a2/html5/thumbnails/40.jpg)
Questions and Answers
44