Model-based Systems Architecting

Daniel Krob is one of the leading world experts in systems architecting and engineering. He was Institute Professor at Ecole Polytechnique, Palaiseau, France, and founder and Director of its Industrial Chair dedicated to complex systems engineering for more than 15 years. He is currently President of the Center of Excellence on Systems Architecture, Management, Economy & Strategy (CESAMES) and has been an INCOSE Fellow since 2014.

• Preface ixAcknowledgments xvIntroduction xviiChapter 1 Introduction to CESAM 11.1 CESAM: a mathematically sound system modeling framework 11.2 CESAM: a framework focused on complex integrated systems 81.3 CESAM: a collaboration-oriented architecting framework 121.4 CESAM: a business-oriented framework 16Chapter 2 Why Architecting Systems? 192.1 Product and project systems 192.2 The complexity threshold 222.3 Addressing systems architecting becomes key 252.4 The value of systems architecting 312.5 The key role of systems architects 342.6 How to analyze a systems architect profile? 36Chapter 3 CESAM Framework 393.1 Elements of systemics 393.1.1 Interface 393.1.2 Environment of a system 413.2 The three architectural visions 423.2.1 Architectural visions definition 423.2.2 Architectural visions overview 463.2.3 Relationships between the three architectural visions 523.2.4 Organization of a system model 553.3 CESAM systems architecture pyramid 573.3.1 The three key questions to ask 573.3.2 The last question that shall not be forgotten 593.4 More systems architecture dimensions 603.4.1 Descriptions versus expected properties 603.4.2 Descriptions 623.4.3 Expected properties 733.5 CESAM systems architecture matrix 78Chapter 4 Identifying Stakeholders: Environment Architecture 834.1 Why identify stakeholders? 834.2 The key deliverables of environment architecture 854.2.1 Stakeholder hierarchy diagram 854.2.2 Environment diagram 87Chapter 5 Understanding Interactions with Stakeholders: Operational Architecture 915.1 Why understand interactions with stakeholders? 915.2 The key deliverables of operational architecture 945.2.1 Need architecture diagram 945.2.2 Lifecycle diagram 955.2.3 Use case diagrams 975.2.4 Operational scenario diagrams 995.2.5 Operational flow diagram 101Chapter 6 Defining What the System Shall Do: Functional Architecture 1036.1 Why understand what the system does? 1036.2 The key deliverables of functional architecture 1056.2.1 Functional requirement architecture diagram 1066.2.2 Functional mode diagram 1086.2.3 Functional breakdown and interaction diagrams 1096.2.4 Functional scenario diagrams 1116.2.5 Functional flow diagram 112Chapter 7 Deciding How the System Shall be Formed: Constructional Architecture 1157.1 Understanding how the system is formed? 1157.2 The key deliverables of constructional architecture 1177.2.1 Constructional requirement architecture diagram 1187.2.2 Configuration diagram 1207.2.3 Constructional breakdown and interaction diagram 1217.2.4 Constructional scenario diagram 1237.2.5 Constructional flow diagram 124Chapter 8 Taking into Account Failures: Dysfunctional Analysis 1278.1 Systems do not always behave as they should 1278.2 The key deliverables of dysfunctional analysis 1348.2.1 Dysfunctional analysis from an operational perspective 1358.2.2 Dysfunctional analysis from a functional perspective 1368.2.3 Dysfunctional analysis from a constructional perspective 138Chapter 9 Choosing the Best Architecture: Trade-off Techniques 1419.1 Systems architecting does not usually lead to a unique solution 1419.2 Trade-off techniques 1439.2.1 General structure of a trade-off process 1439.2.2 Managing trade-offs in practice 145Conclusion 149Appendices 157Appendix 1 System Temporal Logic 159Appendix 2 Classical Engineering Issues 163Appendix 3 Example of System Model Managed with CESAM 177Appendix 4 Implementing CESAM through a SysML Modeling Tool 199Appendix 5 Some Good Practices in Systems Modeling 209References 211Index 219