EMS703: Introduction to Systems Engineering
Lecture 4
Model Based Systems Engineering
Instructor: Dr Mohammad Hassannezhad
17 October 2023
Module V-Model
1 Fundamentals of Applying Systems 12
Systems Engineering Engineering
4
2 Systems modelling Engineering project 11
Stakeholder analysis
language (SysML) management
2 Requirement definition Operations and 10
and analysis lifecycle management
De
f in
n
io
itio System architecture 9
3
sit
Verification and
n
po
an Concept generation Validation
m
d
co
De
Re
co
m
d
5 Tradespace exploration System integration 8
an
po
sit Concept selection Interface management
n
io
io
at
n
gr
te
In
6 Design definition
Numbers indicates the Multidisciplinary optimisation
session # in this course
EMS703
Model-Based Systems Engineering 2
Agenda
• What is a model?
- Why need models? What are benefits? What are different types?
- Quality of good models, model curation
- Model Fidelity vs. Model Credibility
- Joining models together
• What is MBSE?
- Moving from document centric to model-centric SE
- Philosophy, scope, purpose, users, and use in lifecycle
- What is a System Model?
• Introduction to SysML
- Requirements, use-case, behaviour, structure diagrams
EMS703
Model-Based Systems Engineering 3
Agenda
• What is a model?
- Why need models? What are benefits? What are different types?
- Quality of good models, model curation
- Model Fidelity vs. Model Credibility
- Joining models together
• What is MBSE?
- Moving from document centric to model-centric SE
- Philosophy, scope, purpose, users, and use in lifecycle
- What is a System Model?
• Introduction to SysML
- Requirements, use-case, behaviour, structure diagrams
EMS703
Model-Based Systems Engineering 4
What is a Model? Join at [Link]; User code: 4955 0083
EMS703
Model-Based Systems Engineering 5
What is a Model?
Physical representation Mathematical representation Logical representation
EMS703
Model-Based Systems Engineering 6
Model vs. Simulation
• An abstraction of reality by eliminating unnecessary components.
• A simplified version of a concept, phenomenon, relationship, structure or system.
• A graphical, mathematical or physical representation.
• Model can predict the behaviour of a real system under a
set of defined operating conditions and simplifying
assumptions with some degree of fidelity.
• Simulation is the implementation of a model over time.
• It is the process of exercising a model for a particular
instantiation of the system and specific set of inputs in
order to predict the system response.
EMS703
Model-Based Systems Engineering 7
Purpose of models
• To help with making system-level decisions
• To provides a framework for analysis and simulation
• To facilitate how we communicate and exchange information with stakeholder
• To examine 'what if' scenarios
• e.g., through balancing competing priorities to maximize stakeholder value
• To support testing and verification
• To explain, control, and predict events
• Optimisation
EMS703
Model-Based Systems Engineering 8
Views on modelling
Source: Hassannezhad et al . [2017]
EMS703
Model-Based Systems Engineering 9
Example of JLR virtual engineering tools
• “Just take the highly sophisticated electronics in a modern Jaguar, which could add up to 100
electronic control units, 100 million lines of software and 10,000 different product requirements on
each model."
• Tools such as Computational Fluid Dynamics (CFD) software and Computer Aided Engineering (CAE)
can be used to virtually model many different areas of a car – from aerodynamics and thermal
management, to powertrain development and durability.
EMS703
Model-Based Systems Engineering 10
Example of Airbus Helicopter Simulation
EMS703
Model-Based Systems Engineering 11
A taxonomy of models
Law & Kelton (2000), Simulation Modeling and Analysis 3rd ed.
EMS703
Model-Based Systems Engineering 12
A taxonomy of models
Law & Kelton (2000), Simulation Modeling and Analysis 3rd ed.
EMS703
Model-Based Systems Engineering 13
Common types of simulation models
• Monte Carlo / Risk Analysis Simulation
• Agent-Based Modelling and Simulation
• Discrete Event Simulation
• System Dynamics Simulation
EMS703
Model-Based Systems Engineering 14
Question
• What type of models have your worked on?
Join at [Link]; User code: 4955 0083
EMS703
Model-Based Systems Engineering 15
Use of models in Systems Engineering
Stakeholder needs Functions / Behaviours Structure / Form
(purpose) (what it does) (what it is)
Stakeholder needs Stakeholder needs Stakeholder needs
(problem space) (solution space) (solution space)
EMS703
Model-Based Systems Engineering 16
Use of models in Systems Engineering
• We can use models to answer questions:
• The questions may be about the system itself
- What is it?
- How does it work?
- Is the performance adequate?
- What happens if something breaks?
• The questions may be about the model
- Is it complete?
- Is it consistent?
- Does it support required analyses?
EMS703
Model-Based Systems Engineering 17
Space shuttle
hardware flow
EMS703
Model-Based Systems Engineering 18
Space shuttle
hardware flow
diagram
EMS703
Model-Based Systems Engineering 19
Use of models in Systems Engineering
• We use models to optimise design to find suitable, and not necessarily the best solution.
• We use model to explore reasonable options.
- How this has been done before?
- What is available commercially?
- What does research tell us?
Source: Matlab tech talk
EMS703
Model-Based Systems Engineering 20
Use of models in Systems Engineering
• We use models to optimise design to find suitable, and not necessarily the best solution.
• We use model to explore reasonable options.
- How this has been done before?
- What is available commercially?
- What does research tell us?
• We use model to aid with decision-making.
- Build a list of options
- Develop selection criteria
- Approximate each option
- Make a decision
Source: Matlab tech talk
EMS703
Model-Based Systems Engineering 21
Model Fidelity vs. Credibility
I II
Model is poor Model is
Decision
but DM trusts good and DM
Maker’s
it regardless believes it
perceived
quality
III IV
Model is poor Model is
and DM good but DM
knows it don’t trust it
regardless
Model quality
Source: Flanagan [2012]
EMS703
Model-Based Systems Engineering 22
Model Fidelity vs. Credibility
Model fidelity
• is the quality of the model's output,
the degree to which the model acts as
a sufficient representation of the real- I II
Model is poor Model is
world system. Decision
but DM trusts good and DM
Maker’s
it regardless believes it
perceived
Model credibility quality
• is the amount of trust that people have in the IV
III
model’s Model is poor Model is
output to make decisions based upon it. and DM good but DM
knows it don’t trust it
regardless
4 Box model
Model quality
• I – leads to failure
Source: Flanagan [2012]
• III, IV – leads to delay
EMS703
Model-Based Systems Engineering 23
Quality of ‘good’ models
Model Fidelity
• More fidelity than necessary can make it difficult to evaluate the model and can waste resources.
• Less fidelity than necessary can result in poor decisions or overconfidence.
• The choice of fidelity depends upon the system requirements and operating conditions.
Model Credibility
• If models are not credible, decision-makers will not make decisions based on the model's output,
which might waste precious time and resources, or worse still result in incorrect decisions that might
put the project at risk.
• There are many ways in which to build model credibility -- one of which is having a set of standards
and processes that guide the evaluation and validation of the model.
Linked to Decision Support
The real value of models lies in using them in the decision-making process, particularly where we have
to trade-off between a lot of parameters. The best models make evident how their outputs are to be
used.
EMS703
Model-Based Systems Engineering 24
NASA Standard for Models and Simulations
• Following the Columbia Accident (STS-107 in 2003) NASA developed a standard for
quantifying the credibility of Modelling & Simulation (M&S)
• NASA-STD-7009 NASA Standard for Models and Simulations Link.
• Credibility scale has levels 04
• Based on results: ok to use, caution, do not use
EMS703
Model-Based Systems Engineering 25
NASA Standard for Models and Simulations
• Credibility can be increased by:
- Validation and verification to detect and fix issues
- Running the model on historic data
- Adding more input parameters doesn’t affect quality
- Creating a bigger model does not relate to its credibility
EMS703
Model-Based Systems Engineering 26
Joining models together: Federated system model
• The system model exchanges information
with discipline specific models to form the
authoritative, up-to-date source of
information at the system level
• Institutional policy may prevent having
one model to rule them all
• Have to understand where all
authoritative sources reside and have
process/policy for integration
EMS703
Model-Based Systems Engineering 27
Agenda
• What is a model?
- Why need models? What are benefits? What are different types?
- Quality of good models, model curation
- Model Fidelity vs. Model Credibility
- Joining models together
• What is MBSE?
- Moving from document centric to model-centric SE
- Philosophy, scope, purpose, users, and use in lifecycle
- What is a System Model?
• Introduction to UML and SysML
- Requirements, user-case, behaviour, structure diagrams)
EMS703
Model-Based Systems Engineering 28
Traditional view on Systems Engineering
• Traditional Systems Engineering produces documents:
- Such as Requirements Document, Interface Control Document etc.
• Written in natural language and graphics
• Many downsides:
- Changes do not propagate easily,
- Ambiguous interpretations,
- Different levels of abstraction,
- Large volume of information.
Source: [Fosse2016]
EMS703
Model-Based Systems Engineering 29
Traditional view on Systems Engineering
EMS703
Model-Based Systems Engineering 30
Moving from Document-centric to Model-centric SE
• The use of models has generally been limited in scope to support specific types of
analysis or selected aspects of system design. The individual models have not been
integrated into a coherent model of the overall system.
(A Practical Guide to SysML)
• Modelling is not new
- Flight projects have a strong legacy of modelling (structural, thermal, circuit design, mission
design)
• What is new is...
- the availability of a formal modelling languages which can describe systems, and
- the information engineering standards and tools which enable integration of a system model
with existing discipline models.
EMS703
Model-Based Systems Engineering 31
Moving from Document-centric to Model-centric SE
EMS703
Model-Based Systems Engineering 32
Towards Model-Based Systems Engineering
• The aim is to replace documents with (executable)
models.
• Integrated (federated) system model with multiple
views, connected to discipline models
• Authoritative source of information
• Exchanges information to/from analysis and
stakeholders via projections of model information
• Information accessible to all members of the project
EMS703
Model-Based Systems Engineering 33
Towards Model-Based Systems Engineering
• Shifting to model-based systems engineering (MBSE)
enables engineering teams to:
- understand design change impacts more readily,
- communicate design intent, and
- analyse a system design before it is built.
EMS703
Model-Based Systems Engineering 34
What is MBSE?
• MBSE doesn’t replace traditional Systems Engineering, rather MBSE formalises part of
Systems Engineering
• MBSE combines traditional methods and best practices with rigorous modelling techniques
• MBSE uses modelling languages that support rigorous modelling techniques and
integration of various systems engineering disciplines (structural, electrical, mechanical,
software, etc.) and stakeholders
EMS703
Model-Based Systems Engineering 35
What is MBSE?
• “Model-based systems engineering (MBSE) is the formalized application of modelling to
support system requirements, design, analysis, verification and validation activities
beginning in the conceptual design phase and continuing throughout development and
later life cycle phases.”
(INCOSE SE Vision 2020)
• “Model-Based Engineering (MBE): An approach to engineering that uses models as an
integral part of the technical baseline that includes the requirements, analysis, design,
implementation, and verification of a capability, system, and/or product throughout the
acquisition life cycle.”
Final Report, Model-Based Engineering Subcommittee, NDIA, Feb. 2011
EMS703
Model-Based Systems Engineering 36
MBSE benefits
Increased ability to manage System Complexity
Improved communications
Model can be viewed from multiple Enhanced knowledge capture and transfer
perspectives Training Support
Supports concurrent and distributive teams
Improved design quality
Traceability Decreased ambiguity
Supports impact/change analysis Increased precision
Supports evaluation of Consistency,
Complex development lifecycles:
Incremental, iterative, parallel
Correctness & Completeness
Supports evaluation of trade space
EMS703
Model-Based Systems Engineering 37
MBSE benefits
• A single, consistent, unambiguous
system representation ensures integrity
and traceability throughout the SE
process
• Provides the ability to codify institutional
knowledge using formal methods,
allowing for reuse and broad exposure
• Captures information in a durable,
evolvable format
• Focusing on information integration
rather than document generation allows
for decimation of artifact inconsistency
EMS703
Model-Based Systems Engineering 38
MBSE Scope
• MBSE is broad in scope: it includes
multiple modelling domains across life
cycle from a System of Systems to a
component.
• In the Life cycle supports system
requirements, design, analysis,
verification, and validation activities
beginning in the conceptual design phase
and continuing throughout development
and later life cycle phases.
Source: Hart [2015]
EMS703
Model-Based Systems Engineering 39
MBSE Users
• Different users need to understand/work with the model on different levels
Source: Fosse [2016]
EMS703
Model-Based Systems Engineering 40
MBSE implementation
• Program buy-in - “If not in the model, it’s not in the project”
• Doing System Engineering in the MBSE paradigm
- Analytical validation of the architecture model
- Analytical verification of the system architecture
- Customer artifacts generated directly from the model
- Detailed design features applied directly from the model System life cycle
• Product, test, production, and sustainment
- Program effectiveness and suitability
- Early and continuous accounting for quality attributes
• Program transitions to MBSE
- Representation of the information model
- MBSE environment and related training
- Phased capability deployment - data conversion and generation
EMS703
Model-Based Systems Engineering 41
Emerging challenges facing MBSE
• Poor integration of models across the life cycle, hard to get coherent, checkable model of
the whole system.
• Complexity is growing faster than our ability to manage it
• System design emerges from the pieces, not from an architecture, resulting in systems
which are brittle, difficult to test, and complex and expensive to operate.
• Knowledge and investment are lost at project lifecycle phase boundaries, increasing
development cost and risk of late discovery of design problems.
• Limited reuse of models between programs, increasing cost and risk; damping the
potential for true product lines
• Technical and programmatic sides of projects are poorly coupled , hampering effective
project decision-making; increasing development risk.
EMS703
Model-Based Systems Engineering 42
What does MBSE mean to NASA?
EMS703
Model-Based Systems Engineering 43
What does MBSE mean to Ansys?
EMS703
Model-Based Systems Engineering 44
What does MBSE mean to Siemens?
EMS703
Model-Based Systems Engineering 45
What is a ‘System model’?
Stakeholder needs Functions / Behaviours Structure / Form
(purpose) (what it does) (what it is)
Requirements modelling Behavioural modelling Structural modelling
EMS703
Model-Based Systems Engineering 46
What is a ‘System model’?
• A system model is an interconnected set of
model elements that represent key system
aspects including:
• Structure form
• Behaviour function
• Requirements purpose
• Parametrics equations
• A system model represent logical
relationships among requirements, design,
analysis, and verification elements
EMS703
Model-Based Systems Engineering 47
Example of System model
EMS703
Model-Based Systems Engineering 48
What is SysML?
• SysML = Systems Modelling Language
• SysML is a general-purpose modelling language that supports the
specification, design, analysis, and verification of systems that
may include hardware, software, data, personnel, procedure, and
facilities.
• SysML is a visual modelling language that is both human- and
computer understandable, and extensible.
• SysML is the new industry standard language designed
specifically to support modern systems engineering.
EMS703
Model-Based Systems Engineering 49
Agenda
• What is a model?
- Why need models? What are benefits? What are different types?
- Quality of good models, model curation
- Model Fidelity vs. Model Credibility
- Joining models together
• What is MBSE?
- Moving from document centric to model-centric SE
- Philosophy, scope, purpose, users, and use in lifecycle
- What is a System Model?
• Introduction to SysML
- Requirements, user-case, behaviour, structure diagrams)
EMS703
Model-Based Systems Engineering 50
System Modelling Languages
Unified Modeling Language (UML) Offers unified representation of:
[Link] • Functions
Mainly applied to software • Objects
• SysML • Relationships
[Link] • Attributes related to functions, objects,
relationships
Generalisation to cyber-physical
systems
• OPM
- Object Process Methodology
- ISO standard
EMS703
Model-Based Systems Engineering 51
Unified Modelling Language (UML)
EMS703
Model-Based Systems Engineering 52
Systems Modelling Language (SysML)
Source: [Hart 2015]
EMS703
Model-Based Systems Engineering 53
Systems Modelling Language (SysML)
Source: [Hart 2015]
EMS703
Model-Based Systems Engineering 54
What is SysML?
• SysML is a subset of UML with extensions to support requirements for systems
engineering.
• UML = Unified Modelling Language
• Use of SysML facilitates system-software communication within projects, since UML is the
de facto standard software modelling language.
EMS703
Model-Based Systems Engineering 55
4 Pillars of SysML
• Structure
Specification of hierarchies, interconnection,
model organization
• Behaviour
Specification of sequences of actions, life cycle
of a block, message based behaviour
• Requirements
Specification of requirements and relationships
among model elements
• Parametrics
Expresses constraints, enables integration of
engineering analysis and design models
EMS703
Model-Based Systems Engineering 56
4 Pillars of SysML
EMS703
Model-Based Systems Engineering 57
Key takeaways
• Traditional Systems Engineering produces documents
- e.g., Requirements Document, Interface Control Document etc...
- Written in natural language
- Many downsides: changes do not propagate easily, ambiguous interpretations
• Model-based Systems Engineering (MBSE)
- Replace Documents with (executable) models
- Need rigorous System Modelling Languages (Ontology, Semantics, Syntax)
- Object-Process Methodology (OPM) – 1 diagram type
- SysML – Widely used in some industries, 9 diagram types
EMS703
Model-Based Systems Engineering 58
Post-session reading
• INCOSE Handbook v5, Section 3.1
• OMG System Modeling Language
• Madni, Azad M., and Michael Sievers. "Model‐based systems engineering: Motivation, current status,
and research opportunities." Systems Engineering 21.3 (2018): 172-190.
• Estefan, J. A. (2007). Survey of model-based systems engineering (MBSE) methodologies. Incose
MBSE Focus Group, 25(8), 1-12.
• Finance, Guillaume. "SysML Modelling Language explained(2010)." (2010): 1-12.
[Link]
• Dov Dori, Object-Process Methodology for Structure-Behavior Co-Design. In Handbook of Research
on Conceptual Modeling for Complex Systems. D. Embley and B. Thalheim (Eds.), Springer, 2010.
EMS703
Model-Based Systems Engineering 59
References
• Fosse, Elyse. "Model-based systems engineering (MBSE) 101." (2016).
[Link]
• Hart, Laura E. "Introduction to model-based system engineering (MBSE) and SysML." Delaware Valley
INCOSE Chapter Meeting. Vol. 30. Mount Laurel, New Jersey: Ramblewood Country Club, 2015.
• Reymondet, Lucie, Adam M. Ross, and Donna H. Rhodes. "Considerations for model curation in
model-centric systems engineering." 2016 Annual IEEE Systems Conference (SysCon). IEEE, 2016.
• Flanagan, Genevieve Genevieve Elise Cregar. Key challenges to model-based design: distinguishing
model confidence from model validation. Diss. Massachusetts Institute of Technology, 2012.
• De Weck, Olivier L. "Fundamentals of systems engineering." Massachusetts Institute of Technology:
MIT Open Courseware 16 (2015).
• Finance, Guillaume. "SysML Modelling Language explained(2010)." (2010): 1-12.
[Link]
EMS703
Model-Based Systems Engineering 60
