SysML for Systems Engineering: A model-based approach

This document was uploaded by one of our users. The uploader already confirmed that they had the permission to publish it. If you are author/publisher or own the copyright of this documents, please report to us by using this DMCA report form.

Simply click on the Download Book button.

Yes, Book downloads on Ebookily are 100% Free.

Sometimes the book is free on Amazon As well, so go ahead and hit "Search on Amazon"

Systems Modelling Language (SysML) is a tailored version of the unified modelling language (UML) that meets the needs of today's systems engineering professionals and engineers. It supports the specification, analysis, design, verification and validation of a broad range of systems and systems-of-systems, including hardware, software, information, personnel, procedures, and facilities in a graphical notation.

SysML for Systems Engineering: A model-based approach provides a comprehensive overview on how to implement SysML and Model-based Systems Engineering (MBSE) in an organisation in order to model real projects effectively and efficiently. Topics covered include approach and concepts; SysML notation; diagramming guidelines; process and requirements modelling with MBSE; architectures and architectural frameworks with MBSE; value chain modelling; deploying MBSE; the benefits of MBSE; the 'people', the 'process' and the 'tool'; model structure and management; and model maturity. A detailed case study is included to illustrate the key concepts.

Fully updated and revised to reflect the latest version of the standard (SysML 1.5, released in May 2017), this new edition also includes new chapters on the benefits of MBSE, model management, model maturity and value chain modelling.

Author(s): Jon Holt, Simon Perry
Series: IET Professional Applications of Computing Series, 20
Edition: 3
Publisher: The Institution of Engineering and Technology
Year: 2019

Language: English
Pages: 881
City: London

Cover
Contents
Author biographies
Preface to the Third Edition
Part I Introduction
P1.1 Overview
1 Introduction to Model-Based Systems Engineering
1.1 Introduction
1.2 Understand the concepts and terms that will be used throughout the book
1.2.1 Systems engineering
1.2.2 Model-Based Systems Engineering
1.3 Understand why we do what we do and define an approach
1.4 Understand the concept of the common language
1.4.1 The spoken language
1.4.2 The domain-specific language
1.5 Understand how to apply the approach for specific areas of Systems Engineering
1.6 Understand how to implement such an approach in real organisations
1.7 Using this book
References
2 Approach
2.1 Introduction
2.1.1 Writing conventions adopted in the book
2.2 The MBSE Mantra
2.3 The MBSE fundamentals
2.4 The MBSE approach
2.4.1 The 'MBSE Ontology'
2.4.2 The 'MBSE Framework'
2.4.3 The 'View'
2.4.3.1 Defining Viewpoints and creating Views
2.5 Chapter summary
References
3 MBSE Concepts
3.1 Introduction
3.1.1 Provenance of the MBSE Ontology
3.1.2 The Systems Engineering Body of Knowledge
3.1.3 Disagreements with the MBSE Ontology
3.2 The MBSE Ontology
3.2.1 The System concept
3.2.1.1 System-related concepts as described by the International Standards Organisation (ISO)
3.2.1.2 System-related concepts as described by the International Council on Systems Engineering (INCOSE)
3.2.1.3 System-related concepts as described by the US Department of Defense
3.2.1.4 The MBSE Ontology definition for System-related concepts
3.2.2 The Need concept
3.2.2.1 Need-related concepts as described by the Oxford English Dictionary
3.2.2.2 Need-related concepts as described by the International Council on Systems Engineering (INCOSE)
3.2.2.3 Need-related concepts as described by the Modelling Community
3.2.2.4 Need-related concepts as described by the International Standards Organisation (ISO)
3.2.2.5 The MBSE Ontology definition for Need-related concepts
3.2.3 The Architecture concept
3.2.3.1 Architecture-related concepts as described by the International Standards Organisation (ISO)
3.2.3.2 Architecture-related concepts as described by the International Council on Systems Engineering (INCOSE)
3.2.3.3 Architecture-related concepts as described by the Architecture Framework community
3.2.3.4 The Zachman Framework
3.2.3.5 Defence-based Architecture Frameworks
3.2.3.6 Non-defence Architecture Frameworks
3.2.3.7 The MBSE Ontology definition for Architecture
3.2.4 The 'Life Cycle' concept
3.2.4.1 Life Cycle related concepts as described by the International Standards Organisation (ISO)
3.2.4.2 Life Cycle-related concepts as described by the Capability Maturity Model Integration (CMMI)
3.2.4.3 The MBSE Ontology definition
3.2.5 The Process concept
3.2.5.1 Process-based concepts as described by the International Standards Organisation (ISO)
3.2.5.2 Process-based concepts as described by the Capability Maturity Model Integration (CMMI)
3.2.5.3 The MBSE Ontology definition for Process-related concepts
3.2.6 The Competence concept
3.2.6.1 The competence-related concepts as described by the International Standards Organisation (ISO)
3.2.6.2 The Competence-related concepts as described by the Capability Maturity Model Integration (CMMI)
3.2.6.3 The Competence-related concepts as described by Competency Framework Community
3.2.6.4 UKSPEC
3.2.6.5 INCOSE competencies Framework
3.2.6.6 The Competence-related concepts as described by the US Office of Personnel Management
3.2.6.7 The MBSE Ontology for Competence-related concepts
3.2.7 The Project concept
3.2.7.1 The Project-related concepts as described by the International Standards Organisation (ISO)
3.2.7.2 The Project-related concepts as described by the Capability Maturity Model Integration (CMMI)
3.2.7.3 The Project-related concepts as described by the US Project Management Institute (PMI)
3.2.7.4 The Project-related concepts as described by the Association for Project Management (APM) Institute
3.2.7.5 MBSE Ontology definition for Project-related concepts
3.3 Summary
References
Part II Modelling
P2.1 Overview
4 Introduction to SysML and Systems Modelling
4.1 Introduction
4.2 Why we model?
4.2.1 The kennel (doghouse)
4.2.2 The house
4.2.3 The office block
4.2.4 The point
4.3 The three evils
4.3.1 Complexity
4.3.2 Lack of understanding
4.3.3 Communication
4.3.4 The vicious triangle
4.4 What is SysML?
4.4.1 SysML's relationship with UML
4.4.2 A brief history of SysML
4.5 Modelling
4.5.1 Defining modelling
4.5.2 The choice of model
4.5.3 The level of abstraction
4.5.4 Connection to reality
4.5.5 Independent views of the same system
4.6 The SysML diagrams
4.7 Structural modelling
4.7.1 Adding more detail to relationships
4.8 Behavioural modelling
4.8.1 Behavioural modelling – a simple example
4.8.1.1 Simple behaviour
4.8.1.2 Adding more detail
4.8.1.3 Ensuring consistency
4.8.1.4 Solving the inconsistency
4.9 The relationships between behavioural diagrams and structural level
4.10 Identifying complexity through levels of abstraction
4.10.1 The systems
4.10.2 Structural view
4.10.3 Behavioural views
4.11 Chapter summary
References
5 The SysML Notation
5.1 Introduction
5.1.1 Diagram ordering
5.1.2 The worked example
5.2 The structure of SysML diagrams
5.2.1 Frames
5.3 Stereotypes
5.4 The SysML meta-model
5.5 The SysML diagrams
5.5.1 Block definition diagrams
5.5.1.1 Diagram elements
5.5.1.2 Examples
5.5.1.3 Summary
5.5.2 Internal block diagrams
5.5.2.1 Diagram elements
5.5.2.2 Examples
5.5.2.3 Summary
5.5.3 Package diagrams
5.5.3.1 Diagram elements
5.5.3.2 Examples
5.5.3.3 Summary
5.5.4 Parametric diagrams
5.5.4.1 Diagram elements
5.5.4.2 Examples
5.5.4.3 Summary
5.5.5 Requirement diagrams
5.5.5.1 Diagram elements
5.5.5.2 Examples
5.5.5.3 Summary
5.5.6 State machine diagrams
5.5.6.1 Diagram elements
5.5.6.2 Examples
5.5.6.3 Summary
5.5.7 Sequence diagrams
5.5.7.1 Diagram elements
5.5.7.2 Examples
5.5.7.3 Summary
5.5.8 Activity diagrams
5.5.8.1 Diagram elements
5.5.8.2 Examples
5.5.8.3 Summary
5.5.9 Use case diagrams
5.5.9.1 Diagram elements
5.5.9.2 Examples
5.5.9.3 Summary
5.6 Auxiliary constructs
5.7 Chapter summary
References
6 Diagramming Guidelines
6.1 Introduction
6.2 Naming conventions
6.2.1 Structural diagrams
6.2.2 Behavioural diagrams
6.2.3 Stereotypes
6.3 Diagram frame labels
6.4 Additional guidelines
6.4.1 Block and internal block diagrams – showing interfaces
6.4.2 Block and internal block diagrams – showing item flows
6.4.3 Activity diagrams
6.4.4 Default tool settings
6.4.4.1 The use of colour
6.4.4.2 Navigability
6.4.4.3 Other common settings
6.5 Chapter summary
Reference
Part III Applications
P3.1 Overview
7 Process Modelling with MBSE
7.1 Introduction
7.1.1 Background
7.2 Approach
7.2.1 The MBSE Ontology (revisited)
7.2.2 The Framework
7.2.3 The Viewpoints
7.2.3.1 The Requirement Context Viewpoint
7.2.3.2 The Stakeholder Viewpoint
7.2.3.3 The Process Structure Viewpoint
7.2.3.4 The Process Content Viewpoint
7.2.3.5 The Process Behaviour Viewpoint
7.2.3.6 The Information Viewpoint
7.2.3.7 The Process Instance Viewpoint
7.3 The process modelling framework
7.4 Using the process modelling framework
7.4.1 Analysing existing Processes
7.4.2 Creating a new process document from scratch
7.4.3 Abstracting tacit process knowledge for a new System
7.4.4 Abstracting tacit process knowledge for an existing System
7.4.5 Process improvement for existing Processes
7.4.6 Summary
7.5 Summary
References
8 Expanded Process Modelling
8.1 Introduction
8.1.1 Background
8.2 Expanded Process modelling – standards modelling
8.2.1 Views
8.2.1.1 ISO 15288 – Requirement Context View
8.2.1.2 ISO 15288 – Stakeholder View
8.2.1.3 ISO 15288 – Process Content View
8.2.2 Summary
8.3 Expanded Process modelling – compliance mapping
8.3.1 Process Mapping Process (PoMP)
8.3.1.1 PoMP – Process Structure View
8.3.1.2 PoMP – Requirement Context View
8.3.1.3 PoMP – Stakeholder View
8.3.1.4 PoMP – Process Content View
8.3.2 Using PoMP
8.3.2.1 The 'Process Identification' Process
8.3.2.2 The 'Process Model set-up' Process
8.3.2.3 The 'Process analysis' Process
8.3.3 Summary
8.4 Expanded Process modelling – competence
8.4.1 The expanded MBSE Ontology
8.4.2 The Framework
8.4.3 Views
8.4.3.1 The Framework View
8.4.3.2 The Applicable Competency View
8.4.3.3 The Competency Scope View
8.4.3.4 The Competency Profile View
8.5 Expanded Process modelling – Life Cycle modelling
8.5.1 The expanded MBSE Ontology
8.5.1.1 The Framework
8.5.1.2 The Life Cycle View
8.5.1.3 The Life Cycle Model View
8.5.1.4 The Interaction Identification View
8.5.1.5 The Interaction Behaviour View
8.5.2 Summary
8.6 Expanded Process modelling – project management
8.6.1 The expanded MBSE Ontology
8.6.2 The Framework
8.6.3 Views
8.6.3.1 The Project Schedule Viewpoint
8.6.3.2 The Programme Structure Viewpoint
8.7 Summary
References
9 Requirements Modelling with MBSE
9.1 Introduction
9.1.1 Background
9.2 Approach
9.2.1 The MBSE Ontology (revisited)
9.2.1.1 The 'Need' concept
9.2.1.2 The 'Need Description' concept
9.2.1.3 The 'Source Element' concept
9.2.1.4 The 'Rule' concept
9.2.1.5 The 'Scenario' concept
9.2.1.6 The 'Context' concept
9.2.1.7 Stakeholder Context
9.2.1.8 System Contexts
9.2.1.9 The 'Use Case' concept
9.2.2 The Framework
9.2.3 Viewpoints
9.2.3.1 The Source Element Viewpoint
9.2.3.2 Requirement Description Viewpoint
9.2.3.3 Definition Rule Set Viewpoint
9.2.3.4 Requirement Context Viewpoint
9.2.3.5 Context Definition Viewpoint
9.2.3.6 Validation Viewpoint
9.2.3.7 The traceability Viewpoints
9.3 The Requirements modelling Framework
9.4 Using the Requirements modelling Framework
9.4.1 The ACRE Process – Process Content View
9.5 Summary
References
10 Expanded Requirements Modelling – Systems of Systems
10.1 Introduction
10.1.1 Background
10.1.2 Defining a System of Systems
10.1.3 Types of Systems of Systems
10.2 Approach
10.2.1 The MBSE Ontology (revisited)
10.2.2 The Framework
10.2.2.1 Changes to the Framework
10.2.3 The Viewpoints
10.2.3.1 The Context Interaction Viewpoint
10.2.3.2 The Validation Interaction View
10.3 Summary
References
11 Architectures and Architectural Frameworks with MBSE
11.1 Introduction
11.1.1 Background
11.2 Approach
11.2.1 The MBSE Ontology (revisited)
11.2.2 The Framework
11.2.3 The Viewpoints
11.2.3.1 The AF Context Viewpoint
11.2.3.2 The Ontology Definition Viewpoint
11.2.3.3 The Viewpoint Relationships Viewpoint
11.2.3.4 The Viewpoint Context Viewpoint
11.2.3.5 The Viewpoint Definition Viewpoint
11.2.3.6 The Rules Definition Viewpoint
11.3 The Framework for Architectural Frameworks
11.4 Using the FAF
11.5 Chapter Summary
References
12 Value Chain Modelling
12.1 Introduction
12.2 Aims of the Value Chain Framework
12.3 Main Concepts – the Value Chain Framework's Ontology
12.4 Viewpoints
12.4.1 Engagement Relationship Viewpoint
12.4.1.1 Aims
12.4.1.2 Definition
12.4.1.3 Example
12.4.2 Engagement Definition Viewpoint
12.4.2.1 Aims
12.4.2.2 Definition
12.4.2.3 Example
12.4.3 Business Value Viewpoint
12.4.3.1 Aims
12.4.3.2 Definition
12.4.3.3 Example
12.4.4 Contact Information Viewpoint
12.4.4.1 Aims
12.4.4.2 Definition
12.4.4.3 Example
12.4.5 Overview of Ontology Elements Covered by the Viewpoints
12.5 Rules Governing the use of the Value Chain Framework
12.6 Implementation of the Value Chain Framework
12.7 Summary
Reference
Part IV Case Study
P4.1 Overview
13 Case Study Introduction and Architectural Framework
13.1 Introduction
13.1.1 Background
13.2 The MBSE Architectural Framework
13.2.1 The AF Context View
13.2.2 The Ontology Definition View
13.2.3 The Viewpoint Relationships View
13.2.4 The Rules Definition View
13.2.5 Viewpoint Definitions
13.2.5.1 The Post Structure Viewpoint
13.2.5.2 The System Structure Viewpoint
13.3 Defining Viewpoints using SysML Auxiliary Constructs
13.4 Chapter Summary
Reference
14 The Case Study
14.1 Introduction
14.2 The Need Perspective
14.2.1 The Source Element View
14.2.2 The Definition Rule Set View
14.2.3 The Requirement Description View
14.2.4 The Context Definition View
14.2.5 The Requirement Context View
14.2.6 The Validation View
14.2.7 The Traceability View
14.3 The System of Systems Perspective
14.3.1 The Context Interaction View
14.3.2 The Validation Interaction View
14.4 The Life Cycle Perspective
14.4.1 Life Cycle View
14.4.2 The Life Cycle Model View
14.4.3 Interaction Identification View
14.4.4 Interaction Behaviour View
14.5 The Process Perspective
14.5.1 Process Structure View
14.5.2 Requirement Context View
14.5.3 Process Content View
14.5.4 Stakeholder View
14.5.5 Information View
14.5.6 Process Behaviour View
14.5.7 Process Instance View
14.6 The Project Perspective
14.6.1 The Programme Structure View
14.6.2 The Project Schedule View
14.7 The Organisational Perspective
14.7.1 The Organisation Unit Structure View
14.7.2 The Organisation Unit Instance View
14.7.3 The Rank Hierarchy View
14.7.4 The Post Structure View
14.7.5 The Post Instance View
14.7.6 The Post to Role View
14.7.7 The Martian Instance View
14.8 The Competency Perspective
14.8.1 Framework View
14.8.2 Applicable Competency View
14.8.3 Competency Scope View
14.9 The System Perspective
14.9.1 System Identification View
14.9.2 System Structure View
14.9.3 Interface Definition View
14.9.4 System Configuration View
14.9.5 System State View
14.9.6 System Behaviour View
14.9.7 System Interaction View
14.9.8 System Parametric View
14.10 Chapter Summary
References
Part V Deploying MBSE
P5.1 Overview
15 Benefits of MBSE
15.1 Introduction
15.2 ''I know an Old Lady who swallowed a fly''
15.3 ''I know an Old Lady who swallowed a spider''
15.4 ''I know an old lady who swallowed a bird/cat/dog''.
15.5 ''I know an old lady who swallowed a goat/cow''
15.6 ''I know an old lady who swallowed a horse''
16 The 'People'
16.1 Introduction
16.2 The MBSE Ontology (revisited)
16.3 Teaching guide
16.3.1 Different types of teaching
16.3.2 Professional training
16.3.2.1 Teaching Context – Stakeholder Roles
16.4 Teaching as part of an undergraduate or postgraduate course
16.4.1 Teaching Context – Stakeholder Roles and Use Cases
16.4.2 A generic course structure
16.4.2.1 The 'Introduction' section
16.4.2.2 The 'Modelling Notation' section
16.4.2.3 The 'Concepts' section
16.4.2.4 The 'Example' section
16.4.2.5 The 'Application' section
16.4.2.6 Developing 'Course Work'
16.4.2.7 Marking schedules
16.4.3 Summary
16.5 Competence
16.6 The MBSE Stakeholder Roles
16.7 Generic Competencies
16.7.1 Example Competency Scope
16.7.2 Generic Competency Scope – Evidence Types
16.8 Bespoke Competencies
16.8.1 Example Competency Scope
16.8.2 Bespoke Competency Scope – Evidence Types
16.9 Generic vs. specific Competencies
16.10 Defining a bespoke Competency Framework
16.10.1 The 'Bespoke Competency Definition' Process
16.10.1.1 The 'identify ontology' Activity
16.10.1.2 The 'identify source framework' Activity
16.10.1.3 The 'identify competencies' Activity
16.10.1.4 The 'define concept-related competencies' Activity
16.10.1.5 The 'define process-related competencies' Activity
16.10.1.6 The 'define skill-related competencies' Activity
16.10.1.7 The 'review' Activity
16.10.2 The 'Bespoke Framework Definition' Process
16.10.2.1 The 'analyse bespoke framework' Activity
16.10.2.2 The 'define levels' Activity
16.10.2.3 The 'define evidence types' Activity
16.10.2.4 The 'review' Activity
16.10.3 Competency assessment
16.11 Summary
References
17 The 'Process'
17.1 Introduction
17.2 Defining the Process
17.2.1 The ACRE Process
17.2.2 The ACRE Process – the Process Content View (PCV)
17.3 Using the Process
17.3.1 Example use – quick and dirty Process
17.3.2 Example use – semi-formal Process
17.3.3 Example use – formal Process
17.3.4 Summary of process implementation
17.4 Deploying the Process
17.4.1 'Make process available'
17.4.2 'Make process accessible'
17.4.3 'Ensure awareness of process'
17.4.4 'Ensure appropriate presentation'
17.4.5 'Ensure value of process'
17.4.6 'Provide feedback mechanism'
17.4.7 'Ensure consistency'
17.4.8 'Contribute to wider initiative'
17.5 Compliance mapping with best practice
17.5.1 Automated compliance
17.6 Summary
References
18 The 'Tool'
18.1 Introduction
18.2 Considering the types of Tools available
18.2.1 The 'Individual Tool'
18.2.1.1 The 'PAPS' Tool
18.2.1.2 The 'Automated Tool'
18.2.2 The 'Tool Chain'
18.2.2.1 The 'Closed' Tool Chain
18.2.2.2 The 'Open' Tool Chain
18.2.2.3 The 'Heterogeneous' Tool Chains
18.2.2.4 The 'Integrated' Tool Chains
18.2.3 'Tool Capability'
18.2.3.1 'Office Capability'
18.2.3.2 'Support Capability'
18.2.3.3 'Modelling Capability'
18.2.4 Summary
18.3 Understanding the Need for the Tool
18.3.1 Pemberton's cooking analogy
18.4 Using Tools with existing Processes
18.4.1 Example Tool realisation – quick and dirty Process
18.4.2 Example Tool realisation – semi-formal process
18.4.3 Example Tool realisation – formal Process
18.4.4 Guidance for using Tools
18.5 Considering Tool selection
18.5.1 'Provide modelling capability'
18.5.2 'Ensure compatibility with modelling language'
18.5.3 'Understand operational environment'
18.5.4 'Provide interoperability'
18.5.5 'Ensure vendor's quality of service'
18.5.6 'Ensure compatibility with the process model'
18.5.7 'Provide capability'
18.5.8 'Provide application functionality'
18.5.9 'Decide on tool'
18.6 Tool evaluation
18.6.1 The MonTE Processes
18.6.2 MonTE – the Process Content View
18.6.3 Information View
18.6.4 Process Instance View
18.7 Summary
19 Model Structure and Management
19.1 Introduction
19.2 Model structure
19.3 Model management
19.3.1 Version management
19.3.2 Model access
19.3.3 Sandboxing
19.3.4 Correctness through scripting
19.4 Chapter summary
Reference
20 Model Maturity
20.1 Introduction
20.2 Maturity
20.2.1 Technology maturity
20.2.2 Process maturity
20.2.3 Individual maturity
20.3 Modelling for TRLs
20.4 Readiness levels for models
20.5 Assessment approach
20.6 Applying Model Maturity
20.7 Conclusions
References
Part VI Annex
P6.1 Overview
Appendix A Ontology and Glossary
A.1 Introduction
A.2 Ontology
A.3 Glossary
Appendix B Summary of SysML Notation
B.1 Introduction
B.2 Structural Diagrams
B.2.1 Block Definition Diagrams
B.2.2 Internal block Diagrams
B.2.3 Package Diagrams
B.2.4 Parametric Diagram
B.2.5 Requirement Diagrams
B.3
Behavioural Diagrams
B.3.1 State machine diagrams
B.3.2 Sequence diagrams
B.3.3 Activity diagrams
B.3.4 Use case diagrams
B.4 Auxiliary Concepts
B.4.1 Allocations
B.5 Relationships between diagrams
Appendix C Process Model for ISO15288:2015
C.1 Introduction
C.2 Requirement Context View
C.3 Stakeholder View
C.4 Process Structure View
C.5 Process Content View
C.5.1 Process Content View – Agreement Process Group
C.5.2 Process Content View – Organisational Project-Enabling Process Group
C.5.3 Process Content View – Technical Management Process Group
C.5.4 Process Content View – Technical Process Group
References
Appendix D Competency Framework
D.1 Introduction
D.2 MBSE Competency Framework – Levels
D.2.1 Level 1 – Awareness
D.2.2 Level 2 – Support
D.2.3 Level 3 – Lead
D.2.4 Level 4 – Expert
D.3 Evidence Types
D.3.1 Level 1 – Awareness
D.3.2 Level 2 – Support
D.3.3 Level 3 – Lead
D.3.4 Level 4 – Expert
D.4 MBSE Competency Framework – Competency Areas
D.5 MBSE Competency area – MBSE concepts
D.6 MBSE Competency area – Life Cycle Process
D.7 MBSE Competency area – Technical Skill
D.8 MBSE Competency area – Soft Skill
D.9 Competency Scopes
D.10 Generic scopes
D.11 Competency Scope – 'Configuration Manager'
D.12 Competency Scope – 'Assessment Manager'
D.13 Competency Scope – 'Requirement Manager'
D.14 Competency Scope – 'Process Manager'
D.15 Competency Scope – 'Project Manager'
D.16 Competency Scope – 'Primary Assessor'
D.17 Competency Scope – 'Secondary Assessor'
D.18 Competency Scope – 'Requirement Engineer'
D.19 Competency Scope – 'Systems Modeller'
D.20 Competency scope – 'Tester'
D.21 Competency scope – 'Reviewer'
D.22 Competency scope – 'Author'
D.23 Competency scope – 'Process Modeller'
D.24 Competency scope – 'Builder'
D.25 Competency scope – 'SoS Engineer'
D.26 Competency scope – 'MBSE Champion'
D.27 Competency scope – 'MBSE Mentor'
D.28 Competency scope – 'MBSE Trainer'
Appendix E The MBSE Memory Palace
E.1 Introduction to the memory palace
E.2 Strange days
E.3 Strange days revisited
E.4 Summary
References
Index
Back Cover