Atnaujinkite slapukų nuostatas

SysML for Systems Engineering: A model-based approach 3rd edition [Kietas viršelis]

5.00/5 (2 ratings by Goodreads)
(Scarecrow Consultants, UK), (Scarecrow Consultants, UK)
  • Formatas: Hardback, 880 pages, aukštis x plotis: 254x203 mm
  • Serija: Computing and Networks
  • Išleidimo metai: 11-Jan-2019
  • Leidėjas: Institution of Engineering and Technology
  • ISBN-10: 1785615548
  • ISBN-13: 9781785615542
Kitos knygos pagal šią temą:
SysML for Systems Engineering: A model-based approach 3rd editionDidesnis paveikslėlis
  • Formatas: Hardback, 880 pages, aukštis x plotis: 254x203 mm
  • Serija: Computing and Networks
  • Išleidimo metai: 11-Jan-2019
  • Leidėjas: Institution of Engineering and Technology
  • ISBN-10: 1785615548
  • ISBN-13: 9781785615542
Kitos knygos pagal šią temą:
Pastovi nuoroda: https://www.kriso.lt/db/9781785615542.html
Raktažodžiai:

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.

A comprehensive overview for systems and IT engineers, managers, and architects, process modellers and managers and program managers, and students and lecturers in systems and IT engineering.



Now with several new chapters, this third edition of the popular guide to SysML for systems engineering has been fully aligned with latest version (SysML 1.4) of the standard, and includes updates of the core modelling notation, standards models, benefits of MBSE, model management, model maturity and value chain modelling.

Author biographies xv
Preface to the Third Edition xvii
Part I: Introduction 1(78)
1 Introduction to model-based Systems Engineering
3(12)
1.1 Introduction
1.2 Understand the concepts and terms that will be used throughout the book
4(4)
1.2.1 Systems engineering
4(2)
1.2.2 Model-based Systems Engineering
6(2)
1.3 Understand why we do what we do and define an approach
8(1)
1.4 Understand the concept of the common language
9(2)
1.4.1 The spoken language
9(1)
1.4.2 The domain-specific language
10(1)
1.5 Understand how to apply the approach for specific areas of Systems Engineering
11(1)
1.6 Understand how to implement such an approach in real organisations
11(1)
1.7 Using this book
11(2)
References
13(2)
2 Approach
15(16)
2.1 Introduction
15(2)
2.1.1 Writing conventions adopted in the book
15(2)
2.2 The MBSE Mantra
17(1)
2.3 The MBSE fundamentals
18(4)
2.4 The MBSE approach
22(7)
2.4.1 The 'MBSE Ontology'
22(3)
2.4.2 The 'MBSE Framework'
25(2)
2.4.3 The 'View'
27(2)
2.5
Chapter Summary
29(1)
References
30(1)
3 MBSE Concepts
31(48)
3.1 Introduction
31(3)
3.1.1 Provenance of the MBSE Ontology
31(2)
3.1.2 The Systems Engineering Body of Knowledge
33(1)
3.1.3 Disagreements with the MBSE Ontology
34(1)
3.2 The MBSE Ontology
34(40)
3.2.1 The System concept
36(6)
3.2.2 The Need concept
42(4)
3.2.3 The Architecture concept
46(10)
3.2.4 The 'Life Cycle' concept
56(3)
3.2.5 The Process concept
59(4)
3.2.6 The Competence concept
63(6)
3.2.7 The Project concept
69(5)
3.3 Summary
74(2)
References
76(3)
Part II: Modelling 79(174)
4 Introduction to SysML and Systems Modelling
81(48)
4.1 Introduction
81(1)
4.2 Why we model?
81(6)
4.2.1 The kennel (doghouse)
81(2)
4.2.2 The house
83(1)
4.2.3 The office block
84(2)
4.2.4 The point
86(1)
4.3 The three evils
87(4)
4.3.1 Complexity
87(2)
4.3.2 Lack of understanding
89(1)
4.3.3 Communication
90(1)
4.3.4 The vicious triangle
91(1)
4.4 What is SysML?
91(2)
4.4.1 SysML's relationship with UML
91(1)
4.4.2 A brief history of SysML
92(1)
4.5 Modelling
93(3)
4.5.1 Defining modelling
94(1)
4.5.2 The choice of model
94(1)
4.5.3 The level of abstraction
95(1)
4.5.4 Connection to reality
95(1)
4.5.5 Independent views of the same system
96(1)
4.6 The SysML diagrams
96(2)
4.7 Structural modelling
98(8)
4.7.1 Adding more detail to relationships
103(3)
4.8 Behavioural modelling
106(10)
4.8.1 Behavioural modelling-a simple example
108(8)
4.9 The relationships between behavioural diagrams and structural level
116(5)
4.10 Identifying complexity through levels of abstraction
121(6)
4.10.1 The systems
121(1)
4.10.2 Structural view
121(1)
4.10.3 Behavioural views
122(5)
4.11
Chapter Summary
127(1)
References
127(2)
5 The SysML Notation
129(108)
5.1 Introduction
129(1)
5.1.1 Diagram ordering
129(1)
5.1.2 The worked example
129(1)
5.2 The structure of SysML diagrams
130(1)
5.2.1 Frames
131(1)
5.3 Stereotypes
131(4)
5.4 The SysML meta-model
135(1)
5.5 The SysML diagrams
135(97)
5.5.1 Block definition diagrams
135(15)
5.5.2 Internal block diagrams
150(14)
5.5.3 Package diagrams
164(5)
5.5.4 Parametric diagrams
169(11)
5.5.5 Requirement diagrams
180(8)
5.5.6 State machine diagrams
188(9)
5.5.7 Sequence diagrams
197(12)
5.5.8 Activity diagrams
209(11)
5.5.9 Use case diagrams
220(12)
5.6 Auxiliary constructs
232(3)
5.7
Chapter Summary
235(1)
References
236(1)
6 Diagramming Guidelines
237(16)
6.1 Introduction
237(1)
6.2 Naming conventions
237(4)
6.2.1 Structural diagrams
237(3)
6.2.2 Behavioural diagrams
240(1)
6.2.3 Stereotypes
241(1)
6.3 Diagram frame labels
241(4)
6.4 Additional guidelines
245(6)
6.4.1 Block and internal block diagrams-showing interfaces
245(1)
6.4.2 Block and internal block diagrams-showing item flows
245(2)
6.4.3 Activity diagrams
247(1)
6.4.4 Default tool settings
247(4)
6.5
Chapter Summary
251(1)
Reference
251 (2)
Part III: Applications 253(228)
7 Process Modelling with MBSE
255(40)
7.1 Introduction
255(3)
7.1.1 Background
255(3)
7.2 Approach
258(28)
7.2.1 The MBSE Ontology (revisited)
258(1)
7.2.2 The Framework
258(2)
7.2.3 The Viewpoints
260(26)
7.3 The Process Modelling Framework
286(1)
7.4 Using the process modelling framework
286(7)
7.4.1 Analysing existing Processes
287(1)
7.4.2 Creating a new process document from scratch
288(1)
7.4.3 Abstracting tacit process knowledge for a new System
289(2)
7.4.4 Abstracting tacit process knowledge for an existing System
291(1)
7.4.5 Process improvement for existing Processes
292(1)
7.4.6 Summary
293(1)
7.5
Chapter Summary
293(1)
References
293(2)
8 Expanded Process Modelling
295(58)
8.1 Introduction
295(1)
8.1.1 Background
295(1)
8.2 Expanded Process modelling-standards modelling
296(7)
8.2.1 Views
297(6)
8.2.2 Summary
303(1)
8.3 Expanded Process modelling-compliance mapping
303(13)
8.3.1 Process Mapping Process (PoMP)
305(4)
8.3.2 Using PoMP
309(5)
8.3.3 Summary
314(2)
8.4 Expanded Process modelling-competence
316(12)
8.4.1 The expanded MBSE Ontology
316(1)
8.4.2 The Framework
317(1)
8.4.3 Views
317(11)
8.5 Expanded Process modelling-Life Cycle modelling
328(15)
8.5.1 The expanded MBSE Ontology
329(13)
8.5.2 Summary
342(1)
8.6 Expanded Process modelling-project management
343(8)
8.6.1 The expanded MBSE Ontology
343(2)
8.6.2 The Framework
345(1)
8.6.3 Views
346(5)
8.7 Summary
351(1)
References
352(1)
9 Requirements Modelling with MBSE
353(50)
9.1 Introduction
353(1)
9.1.1 Background
353(1)
9.2 Approach
354(45)
9.2.1 The MBSE Ontology (revisited)
354(9)
9.2.2 The Framework
363(2)
9.2.3 Viewpoints
365(34)
9.3 The Requirements modelling Framework
399(1)
9.4 Using the Requirements modelling Framework
400(2)
9.4.1 The ACRE Process-Process Content View
400(2)
9.5 Summary
402(1)
References
402(1)
10 Expanded Requirements Modelling-Systems of Systems
403(22)
10.1 Introduction
403(5)
10.1.1 Background
403(3)
10.1.2 Defining a System of Systems
406(1)
10.1.3 Types of Systems of Systems
406(2)
10.2 Approach
408(15)
10.2.1 The MBSE Ontology (revisited)
408(4)
10.2.2 The Framework
412(1)
10.2.3 The Viewpoints
413(10)
10.3 Summary
423(1)
References
423(2)
11 Architectures and Architectural Frameworks with MBSE
425(34)
11.1 Introduction
425(3)
11.1.1 Background
425(3)
11.2 Approach
428(27)
11.2.1 The MBSE Ontology (revisited)
428(1)
11.2.2 The Framework
428(2)
11.2.3 The Viewpoints
430(25)
11.3 The Framework for Architectural Frameworks
455(1)
11.4 Using the FAF
456(1)
11.5
Chapter Summary
457(1)
References
458(1)
12 Value Chain Modelling
459(22)
12.1 Introduction
459(1)
12.2 Aims of the Value Chain Framework
460(1)
12.3 Main Concepts-the Value Chain Framework's Ontology
461(2)
12.4 Viewpoints
463(13)
12.4.1 Engagement Relationship Viewpoint
464(2)
12.4.2 Engagement Definition Viewpoint
466(3)
12.4.3 Business Value Viewpoint
469(2)
12.4.4 Contact Information Viewpoint
471(2)
12.4.5 Overview of Ontology Elements Covered by the Viewpoints
473(3)
12.5 Rules Governing the use of the Value Chain Framework
476(1)
12.6 Implementation of the Value Chain Framework
477(2)
12.7 Summary
479(1)
Reference
480 (1)
Part IV: Case Study 481(96)
13 Case Study Introduction and Architectural Framework
483(20)
13.1 Introduction
483(1)
13.1.1 Background
483(1)
13.2 The MBSE Architectural Framework
484(15)
13.2.1 The AF Context View
484(2)
13.2.2 The Ontology Definition View
486(1)
13.2.3 The Viewpoint Relationships View
486(4)
13.2.4 The Rules Definition View
490(1)
13.2.5 Viewpoint Definitions
490(9)
13.3 Defining Viewpoints using SysML Auxiliary Constructs
499(2)
13.4
Chapter Summary
501(1)
Reference
501(2)
14 The Case Study
503(74)
14.1 Introduction
503(1)
14.2 The Need Perspective
503(16)
14.2.1 The Source Element View
504(1)
14.2.2 The Definition Rule Set View
504(2)
14.2.3 The Requirement Description View
506(1)
14.2.4 The Context Definition View
506(1)
14.2.5 The Requirement Context View
506(4)
14.2.6 The Validation View
510(5)
14.2.7 The Traceability View
515(4)
14.3 The System of Systems Perspective
519(5)
14.3.1 The Context Interaction View
521(1)
14.3.2 The Validation Interaction View
522(2)
14.4 The Life Cycle Perspective
524(7)
14.4.1 Life Cycle View
524(3)
14.4.2 The Life Cycle Model View
527(2)
14.4.3 Interaction Identification View
529(1)
14.4.4 Interaction Behaviour View
530(1)
14.5 The Process Perspective
531(7)
14.5.1 Process Structure View
531(1)
14.5.2 Requirement Context View
531(1)
14.5.3 Process Content View
532(1)
14.5.4 Stakeholder View
533(1)
14.5.5 Information View
533(2)
14.5.6 Process Behaviour View
535(1)
14.5.7 Process Instance View
536(2)
14.6 The Project Perspective
538(4)
14.6.1 The Programme Structure View
538(3)
14.6.2 The Project Schedule View
541(1)
14.7 The Organisational Perspective
542(9)
14.7.1 The Organisation Unit Structure View
542(1)
14.7.2 The Organisation Unit Instance View
543(2)
14.7.3 The Rank Hierarchy View
545(1)
14.7.4 The Post Structure View
546(3)
14.7.5 The Post Instance View
549(1)
14.7.6 The Post to Role View
549(1)
14.7.7 The Martian Instance View
550(1)
14.8 The Competency Perspective
551(3)
14.8.1 Framework View
551(1)
14.8.2 Applicable Competency View
552(1)
14.8.3 Competency Scope View
553(1)
14.9 The System Perspective
554(22)
14.9.1 System Identification View
555(3)
14.9.2 System Structure View
558(3)
14.9.3 Interface Definition View
561(1)
14.9.4 System Configuration View
562(2)
14.9.5 System State View
564(2)
14.9.6 System Behaviour View
566(3)
14.9.7 System Interaction View
569(5)
14.9.8 System Parametric View
574(2)
14.10
Chapter Summary
576(1)
References
576 (1)
Part V: Deploying MBSE 577(128)
15 Benefits of MBSE
579(14)
15.1 Introduction
579(1)
15.2 'I know an Old Lady who swallowed a fly'
579(7)
15.3 'I know an Old Lady who swallowed a spider'
586(2)
15.4 'I know an old lady who swallowed a bird/cat/dog'.
588(1)
15.5 'I know an old lady who swallowed a goat/cow'
589(1)
15.6 'I know an old lady who swallowed a horse'
590(3)
16 The 'People'
593(38)
16.1 Introduction
593(2)
16.2 The MBSE Ontology (revisited)
595(1)
16.3 Teaching guide
596(4)
16.3.1 Different types of teaching
597(1)
16.3.2 Professional training
598(2)
16.4 Teaching as part of an undergraduate or postgraduate course
600(5)
16.4.1 Teaching Context-Stakeholder Roles and Use Cases
600(1)
16.4.2 A generic course structure
601(4)
16.4.3 Summary
605(1)
16.5 Competence
605(2)
16.6 The MBSE Stakeholder Roles
607(6)
16.7 Generic Competencies
613(4)
16.7.1 Example Competency Scope
615(1)
16.7.2 Generic Competency Scope-Evidence Types
616(1)
16.8 Bespoke Competencies
617(2)
16.8.1 Example Competency Scope
618(1)
16.8.2 Bespoke Competency Scope-Evidence Types
619(1)
16.9 Generic vs. specific Competencies
619(1)
16.10 Defining a bespoke Competency Framework
620(9)
16.10.1 The 'Bespoke Competency Definition' Process
622(5)
16.10.2 The 'Bespoke Framework Definition' Process
627(2)
16.10.3 Competency assessment
629(1)
16.11 Summary
629(1)
References
629(2)
17 The 'Process'
631(24)
17.1 Introduction
631(3)
17.2 Defining the Process
634(3)
17.2.1 The ACRE Process
634(1)
17.2.2 The ACRE Process-the Process Content View (PCV)
634(3)
17.3 Using the Process
637(7)
17.3.1 Example use-quick and dirty Process
639(1)
17.3.2 Example use-semi-formal Process
640(2)
17.3.3 Example use-formal Process
642(2)
17.3.4 Summary of process implementation
644(1)
17.4 Deploying the Process
644(4)
17.4.1 'Make process available'
644(2)
17.4.2 'Make process accessible'
646(1)
17.4.3 'Ensure awareness of process'
646(1)
17.4.4 'Ensure appropriate presentation'
646(1)
17.4.5 'Ensure value of process'
647(1)
17.4.6 'Provide feedback mechanism'
647(1)
17.4.7 'Ensure consistency'
648(1)
17.4.8 'Contribute to wider initiative'
648(1)
17.5 Compliance mapping with best practice
648(5)
17.5.1 Automated compliance
653(1)
17.6 Summary
653(1)
References
654(1)
18 The 'Tool'
655(30)
18.1 Introduction
655(2)
18.2 Considering the types of Tools available
657(6)
18.2.1 The 'Individual Tool'
658(1)
18.2.2 The 'Tool Chain'
658(2)
18.2.3 'Tool Capability'
660(2)
18.2.4 Summary
662(1)
18.3 Understanding the Need for the Tool
663(1)
18.3.1 Pemberton's cooking analogy
663(1)
18.4 Using Tools with existing Processes
664(11)
18.4.1 Example Tool realisation-quick and dirty Process
665(2)
18.4.2 Example Tool realisation-semi-formal process
667(3)
18.4.3 Example Tool realisation-formal Process
670(4)
18.4.4 Guidance for using Tools
674(1)
18.5 Considering Tool selection
675(4)
18.5.1 'Provide modelling capability'
676(1)
18.5.2 'Ensure compatibility with modelling language'
676(1)
18.5.3 'Understand operational environment'
676(1)
18.5.4 'Provide interoperability'
677(1)
18.5.5 'Ensure vendor's quality of service'
677(1)
18.5.6 'Ensure compatibility with the process model'
678(1)
18.5.7 'Provide capability'
678(1)
18.5.8 'Provide application functionality'
679(1)
18.5.9 'Decide on tool'
679(1)
18.6 Tool evaluation
679(5)
18.6.1 The MonTE Processes
679(1)
18.6.2 MonTE-the Process Content View
680(1)
18.6.3 Information View
681(1)
18.6.4 Process Instance View
682(2)
18.7 Summary
684(1)
19 Model Structure and Management
685(10)
19.1 Introduction
685(1)
19.2 Model structure
685(3)
19.3 Model management
688(5)
19.3.1 Version management
688(2)
19.3.2 Model access
690(1)
19.3.3 Sandboxing
691(1)
19.3.4 Correctness through scripting
691(2)
19.4
Chapter Summary
693(1)
Reference
694(1)
20 Model Maturity
695(10)
20.1 Introduction
695(1)
20.2 Maturity
695(2)
20.2.1 Technology maturity
695(1)
20.2.2 Process maturity
696(1)
20.2.3 Individual maturity
697(1)
20.3 Modelling for TRLs
697(2)
20.4 Readiness levels for models
699(3)
20.5 Assessment approach
702(1)
20.6 Applying Model Maturity
703(1)
20.7 Conclusions
704(1)
References
704(1)
Part VI: Annex 705(138)
Appendix A Ontology and Glossary
707(8)
Appendix B Summary of SysML Notation
715(32)
Appendix C Process Model for ISO15288:2015
747(40)
Appendix D Competency Framework
787(52)
Appendix E The MBSE Memory Palace
839(4)
Index 843
Jon Holt is an internationally-recognised expert in the field of Model-based Systems Engineering (MBSE). He is an award-winning author and public speaker and has authored 12 books on MBSE and its applications. Since 2014 he has been a director and consultant for Scarecrow Consultants, who are experts in the field of MBSE. He is also a Professor of Systems Engineering at Cranfield University, UK. He is a Fellow of both the IET and the BCS and a Chartered Engineer and Chartered IT Professional. He is currently the Technical Director of INCOSE UK. He is also actively involved in the promotion of Science Technology Engineering and Mathematics (STEM) where he uses magic, mind-reading and occasional escapology to promote Systems Engineering at science festivals. He has authored the children's STEM book 'Think Engineer'.



Simon Perry is an expert in the field of Model-Based Systems Engineering. He regularly speaks at systems engineering conferences and is the author of eight books on systems engineering and related topics. Since 2014 he has been a director and consultant for Scarecrow Consultants, who are experts in the field of MBSE. He delivers systems engineering training and consultancy to customers and carries out research in many aspects of systems engineering. He works for industry, government and academia, and he has applied his work across many disciplines in a wide range of industries including the defence, nuclear, timber engineering, finance, train manufacturing and automotive industries. Speaking at events, writing books and teaching training courses and workshops have given Simon a great experience in communicating technical concepts to non-domain experts and to non-technical audiences.