Model-based Systems Architecting is a key tool for designing complex industrial systems. It is dedicated to the working systems architects, engineers and modelers, in order to help them master the complex integrated systems that they are dealing with in their day-to-day professional lives.
It presents the CESAMES Systems Architecting Method (CESAM), a systems architecting and modeling framework which has been developed since 2003 in close interaction with many leading industrial companies, providing rigorous and unambiguous semantics for all classical systems architecture concepts. This approach is practically robust and easy-to-use: during the last decade, it was deployed in more than 2,000 real system development projects within the industry, and distributed to around 10,000 engineers around the globe.
Author(s): Daniel Krob
Series: Systems and Industrial Engineering Series: Systems of Systems Complexity Set, 3
Publisher: Wiley-ISTE
Year: 2022
Language: English
Pages: 274
City: London
Cover
Half-Title Page
Title Page
Copyright Page
Contents
Preface
Acknowledgments
Introduction
Chapter 1. Introduction to CESAM
1.1. CESAM: a mathematically sound system modeling framework
1.2. CESAM: a framework focused on complex integrated systems
1.3. CESAM: a collaboration-oriented architecting framework
1.4. CESAM: a business-oriented framework
Chapter 2. Why Architecting Systems?
2.1. Product and project systems
2.2. The complexity threshold
2.3. Addressing systems architecting becomes key
2.4. The value of systems architecting
2.5. The key role of systems architects
2.6. How to analyze a systems architect profile?
Chapter 3. CESAM Framework
3.1. Elements of systemics
3.1.1. Interface
3.1.2. Environment of a system
3.2. The three architectural visions
3.2.1. Architectural visions definition
3.2.2. Architectural visions overview
3.2.3. Relationships between the three architectural visions
3.2.4. Organization of a system model
3.3. CESAM systems architecture pyramid
3.3.1. The three key questions to ask
3.3.2. The last question that shall not be forgotten
3.4. More systems architecture dimensions
3.4.1. Descriptions versus expected properties
3.4.2. Descriptions
3.4.3. Expected properties
3.5. CESAM systems architecture matrix
Chapter 4. Identifying Stakeholders: Environment Architecture
4.1. Why identify stakeholders?
4.2. The key deliverables of environment architecture
4.2.1. Stakeholder hierarchy diagram
4.2.2. Environment diagram
Chapter 5. Understanding Interactions with Stakeholders: Operational Architecture
5.1. Why understand interactions with stakeholders?
5.2. The key deliverables of operational architecture
5.2.1. Need architecture diagram
5.2.2. Lifecycle diagram
5.2.3. Use case diagrams
5.2.4. Operational scenario diagrams
5.2.5. Operational flow diagram
Chapter 6. Defining What the System Shall Do: Functional Architecture
6.1. Why understand what the system does?
6.2. The key deliverables of functional architecture
6.2.1. Functional requirement architecture diagram
6.2.2. Functional mode diagram
6.2.3. Functional breakdown and interaction diagrams
6.2.4. Functional scenario diagrams
6.2.5. Functional flow diagram
Chapter 7. Deciding How the System Shall be Formed: Constructional Architecture
7.1. Understanding how the system is formed?
7.2. The key deliverables of constructional architecture
7.2.1. Constructional requirement architecture diagram
7.2.2. Configuration diagram
7.2.3. Constructional breakdown and interaction diagram
7.2.4. Constructional scenario diagram
7.2.5. Constructional flow diagram
Chapter 8. Taking into Account Failures: Dysfunctional Analysis
8.1. Systems do not always behave as they should
8.2. The key deliverables of dysfunctional analysis
8.2.1. Dysfunctional analysis from an operational perspective
8.2.2. Dysfunctional analysis from a functional perspective
8.2.3. Dysfunctional analysis from a constructional perspective
Chapter 9. Choosing the Best Architecture: Trade-off Techniques
9.1. Systems architecting does not usually lead to a unique solution
9.2. Trade-off techniques
9.2.1. General structure of a trade-off process
9.2.2. Managing trade-offs in practice
Conclusion
Appendices
Appendix 1. System Temporal Logic
Appendix 2. Classical Engineering Issues
Appendix 3. Example of System Model Managed with CESAM
Appendix 4. Implementing CESAM through a SysML Modeling Tool
Appendix 5. Some Good Practices in Systems Modeling
References
Index
Other titles from iSTE in Systems and Industrial Engineering - Robotics
EULA
