Architecture and Function of Complex Systems System architecture is the study of early decision making in complex systems. This text teaches how to capture experience and analysis about early system decisions, and how to choose architectures that meet stakeholder needs, integrate easily, and evol
System architecture strategy and product development for complex systems
β Scribed by Crawley, Edward;Cameron, Bruce;Selva, Daniel
- Publisher
- Pearson
- Year
- 2015;2016
- Tongue
- English
- Leaves
- 482
- Category
- Library
No coin nor oath required. For personal study only.
β¦ Synopsis
Architecture and Function of Complex SystemsSystem architecture is the study of early decision making in complex systems. This text teaches how to capture experience and analysis about early system decisions, and how to choose architectures that meet stakeholder needs, integrate easily, and evolve flexibly. With case studies written by leading practitioners, from hybrid cars to communications networks to aircraft, this text showcases the science and art of system architecture.
οΏ½KEY TOPICS:SYSTEM THINKING: Introduction to System Architecture, System Thinking, Thinking about Complex Systems, ANALYSIS OF SYSTEM ARCHITECTURE: Form, Function, System Architecture, Solution-Neutral Function and Concepts, From Concept to Architecture, CREATING SYSTEM ARCHITECTURE: The Role of the Architect, Upstream and Downstream Influences on System Architecture, Translating Needs into Goals, Applying Creativity to Generating a Concept, Decomposition as a Tool for Managing Complexity, ARCHITECTURE AS DECISIONS: System Architecture as a Decision-Making Process, Reasoning about Architectural Tradespaces, Formulating and Solving System Architecture Optimization Problems
MARKET:This text is beneficial for engineers and programmers studying systems architecture.
β¦ Table of Contents
Cover......Page 1
Title Page......Page 2
Copyright Page......Page 3
Contents......Page 4
Foreword......Page 8
Preface......Page 10
Part 1 System Thinking......Page 16
The Advantages of Good Architecture......Page 17
Learning Objectives......Page 20
Organization of the Text......Page 21
References......Page 22
2.2 Systems and Emergence......Page 23
2.3 Task 1: Identify the System, Its Form, and Its Function......Page 28
2.4 Task 2: Identify Entities of a System, Their Form, and Their Function......Page 32
2.5 Task 3: Identify the Relationships among the Entities......Page 41
2.6 Task 4 Emergence......Page 43
2.7 Summary......Page 48
References......Page 49
3.2 Complexity in Systems......Page 50
3.3 Decomposition of Systems......Page 54
3.4 Special Logical Relationships......Page 58
3.5 Reasoning through Complex Systems......Page 59
3.6 Architecture Representation Tools: SysML and OPM......Page 60
3.7 Summary......Page 63
References......Page 65
Part 2 Analysis of System Architecture......Page 66
4.2 Form in Architecture......Page 68
4.3 Analysis of Form in Architecture......Page 73
4.4 Analysis of Formal Relationships in Architecture......Page 78
4.5 Formal Context......Page 90
4.6 Form in Software Systems......Page 92
References......Page 97
5.2 Function in Architecture......Page 98
5.3 Analysis of External Function and Value......Page 104
5.4 Analysis of Internal Function......Page 109
5.5 Analysis of Functional Interactions and Functional Architecture......Page 113
5.6 Secondary Value-Related External and Internal Functions......Page 123
References......Page 124
6.1 Introduction......Page 125
6.2 System Architecture: Form and Function......Page 126
6.3 Non-idealities, Supporting Layers, and Interfaces in System Architecture......Page 136
6.4 Operational Behavior......Page 140
6.5 Reasoning about Architecture Using Representations......Page 144
References......Page 151
7.1 Introduction......Page 152
7.2 Identifying the Solution-Neutral Function......Page 155
7.3 Concept......Page 157
7.4 Integrated Concepts......Page 167
7.5 Concepts of Operations and Services......Page 172
7.6 Summary......Page 173
References......Page 174
8.1 Introduction......Page 175
8.2 Developing the Level 1 Architecture......Page 177
8.3 Developing the Level 2 Architecture......Page 181
8.4 Home Data Network Architecture at Level 2......Page 185
8.5 Modularizing the System at Level 1......Page 188
8.6 Summary......Page 190
References......Page 191
Part 3 Creating System Architecture......Page 192
9.2 Ambiguity and the Role of the Architect......Page 193
9.3 The Product Development Process......Page 199
9.4 Summary......Page 207
References......Page 211
10.1 Introduction......Page 212
10.2 Upstream Influence: Corporate Strategy......Page 213
10.3 Upstream Influence: Marketing......Page 216
10.4 Upstream Influence: Regulation and Pseudo-Regulatory Influences......Page 219
10.5 Upstream Influence: Technology Infusion......Page 221
10.6 Downstream Influence: ImplementationβCoding, Manufacturing, and Supply Chain Management......Page 222
10.7 Downstream Influence: Operations......Page 225
10.8 Downstream Influence: Design for X......Page 227
10.9 Downstream Influence: Product and System Evolution, and Product Families......Page 229
10.10 The Product Case: Architecture Business Case Decision (ABCD)......Page 232
10.11 Summary......Page 236
References......Page 239
11.1 Introduction......Page 241
11.2 Identifying Beneficiaries and Stakeholders......Page 242
11.3 Characterizing Needs......Page 251
11.4 Interpreting Needs as Goals......Page 259
11.5 Prioritizing Goals......Page 265
11.6 Summary......Page 268
References......Page 274
12.1 Introduction......Page 277
12.2 Applying Creativity to Concept......Page 278
12.3 Develop the Concepts......Page 283
12.4 Expand the Concepts and Develop the Concept Fragments......Page 284
12.5 Evolve and Refine the Integrated Concepts......Page 289
12.6 Select a Few Integrated Concepts for Further Development......Page 292
12.7 Summary......Page 294
References......Page 299
13.2 Understanding Complexity......Page 301
13.3 Managing Complexity......Page 310
13.4 Summary......Page 318
References......Page 323
Part 4 Architecture as Decisions......Page 324
14.1 Introduction......Page 326
14.2 Formulating the Apollo Architecture Decision Problem......Page 327
14.3 Decisions and Decision Support......Page 332
14.4 Four Main Tasks of Decision Support Systems......Page 334
14.5 Basic Decision Support Tools......Page 335
14.6 Decision Support for System Architecture......Page 341
References......Page 343
15.1 Introduction......Page 346
15.2 Tradespace Basics......Page 347
15.3 The Pareto Frontier......Page 349
15.4 Structure of the Tradespace......Page 356
15.5 Sensitivity Analysis......Page 360
15.6 Organizing Architectural Decisions......Page 365
15.7 Summary......Page 371
References......Page 372
16.1 Introduction......Page 374
16.2 Formulating a System Architecture Optimization Problem......Page 376
16.3 NEOSS Example: An Earth Observing Satellite System for NASA......Page 378
16.4 Patterns in System Architecting Decisions......Page 380
16.5 Formulating a Large-scale System Architecture Problem......Page 404
16.6 Solving System Architecture Optimization Problems......Page 409
References......Page 417
Appendices......Page 421
Chapter Problems......Page 436
Index......Page 463
Principles of System Architecture......Page 481
π SIMILAR VOLUMES
<p>Systems Engineering Guidebook: A Process for Developing Systems and Products is intended to provide readers with a guide to understanding and becoming familiar with the systems engineering process, its application, and its value to the successful implementation of systems development projects. Th
This groundbreaking resource offers you new insights for building and evolving open systems using the best mix of standards for your software development projects. Numerous books have been published that describe individual computer standards, but only Open Systems and Standards for Software Product
<p>Health Information Systems: Architectures and Strategies is a definitive introductory resource that tackles the pivotal role of information systems in health care. Illustrating the importance of information systems in delivering high-quality health care at the lowest possible cost, this book prov
Industry, government, and academic efforts to create a generalized systems engineering process have repeatedly fallen short. The outcome? Systems engineering failures that produce losses like the September 1999 destruction of the Mars Climate Orbiter. A simple information transfer error between team