Professional Documents
Culture Documents
Full Chapter Sysml For Systems Engineering A Model Based Approach Jon Holt PDF
Full Chapter Sysml For Systems Engineering A Model Based Approach Jon Holt PDF
https://textbookfull.com/product/sysml-for-systems-engineering-a-
model-based-approach-3rd-edition-jon-holt/
https://textbookfull.com/product/cyber-physical-systems-a-model-
based-approach-1st-edition-walid-m-taha/
https://textbookfull.com/product/virtual-equivalent-system-
approach-for-stability-analysis-of-model-based-control-systems-
weicun-zhang/
https://textbookfull.com/product/embedded-systems-architecture-
for-agile-development-a-layers-based-model-mirtalebi/
Estimation and Inference in Discrete Event Systems A
Model Based Approach with Finite Automata Christoforos
N. Hadjicostis
https://textbookfull.com/product/estimation-and-inference-in-
discrete-event-systems-a-model-based-approach-with-finite-
automata-christoforos-n-hadjicostis/
https://textbookfull.com/product/advanced-model-based-
engineering-of-embedded-systems-extensions-of-the-
spes-2020-methodology-1st-edition-klaus-pohl/
https://textbookfull.com/product/zebrafish-a-model-for-marine-
peptide-based-drug-screening-saravanan-ramachandran/
https://textbookfull.com/product/energy-based-control-of-
electromechanical-systems-a-novel-passivity-based-approach-
victor-manuel-hernandez-guzman/
https://textbookfull.com/product/security-aware-design-for-cyber-
physical-systems-a-platform-based-approach-1st-edition-chung-wei-
lin/
Professional Applications of Computing Series 10
Engineering
SysML is a tailored version of the unified modelling language (UML) that meets the needs of
today’s systems engineering professional. SysML for Systems Engineering, 2nd Edition: A model-
Professor Jon Holt is an
internationally-recognised expert in
2nd Edition: A model-based approach
based approach provides a thorough introduction to the language and considers how best to model-based systems engineering
apply it to projects and businesses using model-based systems engineering (MBSE). and this is his ninth book in the field.
This new edition of this popular text has been fully updated to reflect SysML 1.3, the latest version Jon is also a fellow of both the IET
of the standard, and the discussion has been extended to show the power of SysML as a tool for and the BCS and is an international
systems engineering in an MBSE context. Beginning with a thorough introduction to the concepts award-winning public speaker.
behind MBSE, and the theoretical aspects and syntax of SysML, the book then describes how to Simon Perry has over 25 years’
implement SysML and MBSE in an organisation, and how to model real projects effectively and experience working as a systems and
efficiently, illustrated using an extensive case study . software engineer, and is an expert
SysML for Systems Engineering, 2nd Edition: A model-based approach is an essential introduction in model-based systems engineering.
to the implementation of MBSE using SysML for research-based and practising systems engineers, He is a Member of the IET and
managers and students, systems architects, project managers, software engineers, process INCOSE and a public speaker. This is
engineers, and enterprise architects. his fifth book in the field.
This publication is copyright under the Berne Convention and the Universal Copyright
Convention. All rights reserved. Apart from any fair dealing for the purposes of research
or private study, or criticism or review, as permitted under the Copyright, Designs and
Patents Act 1988, this publication may be reproduced, stored or transmitted, in any
form or by any means, only with the prior permission in writing of the publishers, or in
the case of reprographic reproduction in accordance with the terms of licences
issued by the Copyright Licensing Agency. Enquiries concerning reproduction outside
those terms should be sent to the publisher at the undermentioned address:
The Institution of Engineering and Technology
Michael Faraday House
Six Hills Way, Stevenage
Herts, SG1 2AY, United Kingdom
www.theiet.org
While the authors and publisher believe that the information and guidance given in this
work are correct, all parties must rely upon their own skill and judgement when making
use of them. Neither the authors nor publisher assume any liability to anyone for any
loss or damage caused by any error or omission in the work, whether such an error or
omission is the result of negligence or any other cause. Any and all such liability is
disclaimed.
The moral rights of the authors to be identified as authors of this work have been
asserted by them in accordance with the Copyright, Designs and Patents Act 1988.
Acknowledgements xvii
Part 1 Introduction 1
1 Introduction to model-based systems engineering 3
1.1 Introduction 3
1.2 Understand the concepts and terms that will be used
throughout the book 4
1.2.1 Systems engineering 4
1.2.2 Model-based systems engineering 6
1.3 Understand why we do what we do and define an approach 7
1.4 Understand the common notation that we will be adopting
throughout the book 9
1.5 Understand how to apply the approach for specific areas of
systems engineering 9
1.6 Understand how to implement such an approach in real
organisations 9
1.7 Using this book 10
References 11
2 Approach 13
2.1 Introduction 13
2.1.1 The fundamental approach – I know an old lady 13
2.1.2 Writing conventions adopted in the book 15
2.2 The approach 16
2.2.1 The ‘MBSE Ontology’ 17
2.2.2 The ‘MBSE Framework’ 20
2.2.3 The ‘View’ 20
2.3 Summary 22
References 23
3 MBSE concepts 25
3.1 Introduction 25
3.1.1 Provenance of the MBSE Ontology 25
3.1.2 The Systems Engineering Body of Knowledge (SEBoK) 27
3.1.3 Disagreements with the MBSE Ontology 28
viii SysML for systems engineering
Part 2 Modelling 71
4 Introduction to SysML and systems modelling 73
4.1 Introduction 73
4.2 Why we model? 73
4.2.1 The kennel (doghouse) 73
4.2.2 The house 75
4.2.3 The office block 77
4.2.4 The point 78
4.3 The three evils 79
4.3.1 Complexity 79
4.3.2 Lack of understanding 81
4.3.3 Communication 82
4.3.4 The vicious triangle 83
4.4 What is SysML? 83
4.4.1 SysML’s relationship with UML 83
4.4.2 A brief history of SysML 85
4.5 Modelling 86
4.5.1 Defining modelling 86
4.5.2 The choice of model 87
4.5.3 The level of abstraction 87
4.5.4 Connection to reality 87
4.5.5 Independent views of the same system 88
4.6 The SysML diagrams 88
4.7 Structural modelling 91
4.7.1 Adding more detail to relationships 95
4.8 Behavioural modelling 98
4.8.1 Behavioural modelling – a simple example 100
4.9 The relationships between behavioural diagrams and
structural level 107
4.10 Identifying complexity through levels of abstraction 112
4.10.1 The systems 114
4.10.2 Structural view 114
4.10.3 Behavioural views 115
4.11 Summary 120
References 120
Contents ix
This book represents much of what I learned about MBSE in this and the previous
millennium. The book started off as an update to our previous SysML book and has
since evolved into the monster that you now hold in your hands.
It would be impossible to thank everybody, so I shan’t, but there are a few
notable people who should be mentioned. Simon who needs no thanks but will get
them anyway, Mikey B who will return hopefully in future books, Mike and Sue
(without whom, etc, etc.), the staff at the IET who never learn and keep inviting us
back, and all of my co-workers, clients and many others.
Finally, to my beautiful wife Rebecca, my children: Jude, Eliza, Roo, and, of
course, to Betty and Olive.
Jon Holt, September 2013
This book is the culmination of over a decade of working on the various topics
covered with Jon, first as a client of his, then as a colleague and now as a friend.
Thanks Jon for helping me to see the light all those years ago.
Thanks also to all those clients and colleagues, past and present, whose ques-
tions, ideas and comments have made me a better engineer. While far too many to
name, you know who you are. This book wouldn’t exist without you.
Since my last book was written Motley the Cat, our feline alarm clock, is sadly
no longer with us; old age finally caught up with her. She is not forgotten but the
cat-shaped hole she left behind has, for now, been filled by Walter and Dolly who
daily prove that people don’t own cats.
Finally, I must, as ever, thank my wife Sally for her patience, love, friendship
and wisdom. Without her I would be a lesser person.
S. A. Perry, August 2013
Part 1
Introduction
Chapter 1
Introduction to model-based systems engineering
You will never find a more wretched hive of scum and villainy. We must
be cautious.
Obi Wan Kenobi
1.1 Introduction
The world of systems engineering is changing. In recent years, the whole field of
systems engineering has been seen as no longer an emerging discipline but as a
valid approach to realising successful systems. Systems engineering is a broad field
that encompasses many disciplines, can be utilised in many industries and can be
applied across many and varied life cycles.
If you have read this far into this book (the first two sentences) and find
yourself agreeing with the basic, common-sense statements in the previous para-
graph, then consider the following:
● What do we mean by systems? For example: technical systems, social systems
and economic systems.
● What disciplines do we include when we refer to ‘many disciplines’? For
example: engineering, management, acquisition and quality assurance.
● What life cycles do we refer to? For example: the product life cycle, the project
life cycle and the programme life cycle.
There are only three questions here, but they are certainly significant ones. Before
progressing any further and trying to define some of these terms more fully consider that
even with the simple statements in the first paragraph and subsequent three questions,
there are three properties that can be applied to everything stated so far, which are:
● Complexity. There is clearly much complexity here with regard to the number
of questions that may be asked.
● A need for understanding. What exactly do we mean by these terms?
● A need for effective communication. Can we convey this information to
interested parties?
The main aim of this book is to address these three properties of systems
engineering by the application of effective modelling. In fact, this will be
4 SysML for systems engineering
just the starting point as we will then use the same modelling techniques
to drive every aspect of systems engineering that falls within the scope of
this book.
We will be using modelling to:
● Understand the concepts and terms that will be used throughout the book
● Understand why we do what we do and define an approach
● Understand the common notation that we will be adopting throughout the book
● Understand how to apply the approach for specific areas of systems
engineering
● Understand how to implement such an approach in real organisations
When we use the model to drive the whole approach of systems engineering, we
will term this Model-based Systems Engineering, or MBSE. The aim of this book is
therefore to help people implement MBSE effectively and efficiently.
looked at across its whole life cycle and not just at one small part. Also notice here
that non-technical facets of the system are mentioned as having an influence on the
system.
The next definition comes from Howard Eisner:
The definition that will be used for the purposes of this book is:
‘Systems engineering is a multi-disciplinary, common-sense approach that
enables the realisation of successful systems.’
Having established this definition, let us see how modelling fits in with systems
engineering.
things can be greatly improved by the introduction of ‘diagrams, photos and other
models’. Diagrams do not equate to a true model. One of the main points that will
be made throughout this book is that using diagrams, even with a standard notation
such as SysML, does not necessarily result in a model.
For the next definition, we return to INCOSE, but this time to their long-term
vision for the future of systems engineering:
‘MBSE is part of a long-term trend toward model-centric approaches
adopted by other engineering disciplines, including mechanical, electrical
and software.
In particular, MBSE is expected to replace the document-centric
approach that has been practiced by systems engineers in the past and
influence the future practice of systems engineering by being fully
integrated into the definition of systems engineering processes.’ [5]
This statement, although not strictly speaking a definition for MBSE, makes a very
important point in much stronger terms – mainly, the use of the terms ‘model-centric’
and ‘fully integrated’. This really goes to reinforce the importance of MBSE and is far
closer to what we propose in this book, rather than that in the original INCOSE definition.
The definition of model-based systems engineering that will be used for the
purposes of this book is:
‘Model-based systems engineering is an approach to realising successful
systems that is driven by a model that comprises a coherent and consistent
set of views that reflect multiple viewpoints of the system.’
These definitions will be used throughout the book and will provide the drive
behind everything that is presented and discussed.
It has been established that it is difficult to pin down an exact definition for systems
engineering. However, it is not so difficult to pin down why we need systems
engineering. To put it as simply as possible, many systems end in failure or disaster.
The term failure here refers to a system where the project never reached delivery
and where time and money were wasted because time or cost overran. The term
disaster here refers to a system where people were hurt or the environment was
damaged as a result of the system failure.
‘The fundamental reason, therefore, why we need systems engineering is
that it is very easy for things to go wrong, resulting in disasters or failures.’
We need to understand how likely it is that something will go wrong and the
severity of the consequences of it going wrong. To put this into other words – we
need to understand the risk.
In order to understand how likely it is that something will go wrong, we need to
understand why things go wrong. Luckily for us, this has been done many times before,
8 SysML for systems engineering
and almost all disasters and failures can be attributed to the three evils of engineering,
which are complexity, lack of understanding and poor communications.
Traditional systems engineering provides an approach that can be applied to
minimise the risk, such as understanding requirements, analysis, design, testing,
etc., but this approach itself is complex and requires understanding and good
communications.
The main aim of modelling, as will be discussed in more detail throughout this
book, is to address these three evils. We can apply modelling to the projects and
systems, of course, but we can also apply the modelling to the fundamental
approach itself, and this forms the heart of the philosophy of this book and of
model-based systems engineering.
The approach described in this book forms part of an overall model-based
systems engineering (MBSE) approach. There are many benefits associated with
the application of effective MBSE (note the use of the word ‘effective’ here),
which are:
● Automatic generation and maintenance of system documents. All system
documents may be generated automatically from the model, resulting in sim-
pler document maintenance, more consistent document content and drastically
reduced documentation effort and time.
● Complexity control and management. Models may be measured and, therefore,
controlled. This measurement may be automated and the results may be used to
control and manage the complexity of the model, hence the project or system.
● Consistency of information. A true model results in consistent and coherent
views across the whole system architecture.
● Inherent traceability. When the model is correct, then traceability between all
the system artefacts, across all life cycle stages, is contained within the model.
● Simpler access to information. The model represents the knowledge of the
project or system and, as the previous point mentioned, traceability exists to all
project or system information. Without a coherent model knowledge of the
system is potentially spread across multiple sources, such as heterogeneous
models, spread sheets and documents.
● Improved communication – language. When a model is in place and it has been
defined using an established modelling notation, then it is possible to use this
notation as a common language.
● Improved communication – concepts and terminology. A consistent and
coherent model will have an underlying definition of all the relevant concepts
and terms, referred to later in this book as an ontology, which is used as basis
for the views that make up the model.
● Increased understanding. The very act of modelling, particularly with small
teams of people, provides an excellent way to achieve a common understanding
and obtain consensus.
When trying to sell the idea of MBSE to other people in an organisation, it is
essential that the above benefits are related directly back to saving cost, time or
Introduction to model-based systems engineering 9
resources. Each of these points should be tailored to reflect the way that you work
in your organisation to achieve the full impact of the benefits.
«block»
Book
6
«block»
Part
Minä kumarsin.
»No, sanokaa pois!» käski hän terävästi. »Kyllä vai eikö, herra de
Berault?»
»Kyllä, monseigneur.»
II luku
»Vihreässä pilarissa»
»Mutta teillä ei ole tilaa tai ruokaa tai on vaimonne sairaana taikka
jotakin muuta on vialla», keskeytin ärtyisesti. »Aion joka tapauksessa
maata täällä. Siihen teidän täytyy tyytyä, sekä itsenne että vaimonne
— jos teillä on sellainen.»
»Se saa rehua», vakuutti mies lyhyeen. Sitten hän odotti, että
menisin sisälle. »Vaimoni on sisällä», jatkoi hän ja katsoi minuun
itsepintaisesti.
»Ei.»
»Ei.»
»Enkö osaa?» sanoi hän räpyttäen silmiään. »Vai niin, vai en?»
Mutta minä ymmärsin. Minä tiesin, että hän oli ollut vähällä
ilmaista kaikki ja lavertaa, että hevonen oli de Cocheforêtin,
comprenez bien! Minä käännyin pimeään, jottei hän olisi nähnyt
hymyäni, enkä sitten laisinkaan kummeksunut, että mies oli
silmänräpäyksessä kerrassaan muuttunut. Oven suljettuaan hän oli
yhtä selvä ja epäluuloinen kuin ennenkin; hän häpesi ja oli
raivoissaan minulle. Hän oli sellaisessa mielentilassa, että olisi
voinut katkaista kurkkuni pienimmästäkin aiheesta.
Juuri sitä olin toivonut, sillä nyt saatoin pitää silmällä ja ainakin
saada selville, poistuiko Cocheforêt ennen aamua. Jollei hän lähtisi
pois, niin aioin hankkia tilaisuuden nähdä hänen kasvonsa ja kenties
saada tietooni muita seikkoja, joista minulle saattoi vastedes olla
hyötyä.
»Vai niin, vai ette», vastasi hän verkalleen. »Ja ettekö halua
mitään?»
Ennen kuin hän oli päässyt ihan alas, olin taas ikkunaluukulla.
Nainen, jonka olin nähnyt, viipyi vielä samassa paikassa, ja hänen
vieressään seisoi mies, joka oli puettu talonpojan asuun ja piteli
lyhtyä. Mutta se mies, jonka olisin mieluimmin nähnyt, ei ollut siellä.
Hän oli mennyt, ja selvää oli, etteivät toiset enää pelänneet minua,
sillä tähystellessäni alas tuli isäntä heidän luokseen, hänkin lyhty
kädessään ja sanoi jotakin naiselle, jolloin tämä katsoi ylös ikkunaani
ja nauroi.