References
by Edward Crawley, Bruce Cameron, Daniel Selva
System Architecture: Strategy and Product Development for Complex Systems, First Edition
- System Architecture Strategy and Product Development for Complex Systems
- Contents
- Foreword
- Preface
- Part 1 System Thinking
- Chapter 1 Introduction to System Architecture
- Chapter 2 System Thinking
- 2.1 Introduction
- 2.2 Systems and Emergence
- 2.3 Task1: Identify the System, Its Form, and Its Function
- 2.4 Task 2: Identify Entities of a System, Their Form, and Their Function
- Entities with Form and Function
- Define the Initial Decomposition into Entities
- Identify the Potential Entities of the System—Holistic Thinking
- Include the Important Entities of the System—Focus
- Create or Recognize Abstractions for the Entities
- Define the Boundary of the System, and Separate It from Context
- 2.5 Task 3: Identify the Relationships among the Entities
- 2.6 Task4 Emergence
- 2.7 Summary
- References
- Chapter 3 Thinking about Complex Systems
- Part 2 Analysis of System Architecture
- References
- Chapter 4 Form
- 4.1 Introduction
- 4.2 Form in Architecture
- 4.3 Analysis of Form in Architecture
- 4.4 Analysis of Formal Relationships in Architecture
- 4.5 Formal Context
- 4.6 Form in Software Systems
- 4.7 Summary
- References
- Chapter 5 Function
- Chapter 6 System Architecture
- 6.1 Introduction
- 6.2 System Architecture: Form and Function
- 6.3 Non-idealities, Supporting Layers, and Interfaces in System Architecture
- 6.4 Operational Behavior
- 6.5 Reasoning about Architecture Using Representations
- 6.6 Summary
- References
- Chapter 7 Solution-Neutral Function and Concepts
- Chapter 8 From Concept to Architecture
- Part 3 Creating System Architecture
- Chapter 9 The Role of the Architect
- Chapter 10 Upstream and Downstream Influences on System Architecture
- 10.1 Introduction
- 10.2 Upstream Influence: Corporate Strategy
- 10.3 Upstream Influence: Marketing
- 10.4 Upstream Influence: Regulation and Pseudo-Regulatory Influences
- 10.5 Upstream Influence: Technology Infusion
- 10.6 Downstream Influence: Implementation—Coding, Manufacturing, and Supply Chain ManagementDownstream Influence: Implementation—Coding, Manufacturing, and Supply Chain Management
- 10.7 Downstream Influence: Operations
- 10.8 Downstream Influence: Design for X
- 10.9 Downstream Influence: Product and System Evolution, and Product Families
- 10.10 The Product Case: Architecture Business Case Decision (ABCD)
- 10.11 Summary
- References
- Chapter 11 Translating Needs into Goals
- Chapter 12 Applying Creativity to Generating a Concept
- 12.1 Introduction
- 12.2 Applying Creativity to Concept
- 12.3 Develop the Concepts
- 12.4 Expand the Concepts and Develop the Concept Fragments
- 12.5 Evolve and Refine the Integrated Concepts
- 12.6 Select a Few Integrated Concepts for Further Development
- 12.7 Summary
- References
- Chapter 13 Decomposition as a Tool for Managing Complexity
- Part 4 Architecture as Decisions
- Chapter 14 System Architecture as a Decision-Making Process
- Chapter 15 Reasoning about Architectural Tradespaces
- Chapter 16 Formulating and Solving System Architecture Optimization Problems
- 16.1 Introduction
- 16.2 Formulating a System Architecture Optimization Problem
- 16.3 NEOSS Example: An Earth Observing Satellite System for NASA
- 16.4 Patterns in System Architecting Decisions
- 16.5 Formulating a Large-scale System Architecture Problem
- 16.6 Solving System Architecture Optimization Problems
- Introduction
- Full-Factorial Enumeration
- Heuristics for Architecture Optimization
- A Generic Population-Based Heuristic Optimization
- Generating the Initial Population
- Completing an Initial Population with Deterministic Architectures
- General Heuristics and Meta-Heuristics for Efficient Search
- Heuristics in Genetic Algorithms
- Augmenting the Genetic Algorithm with More Heuristics
- 16.7 Summary
- References
- Appendices
- Chapter Problems
- System Architecture–Chapter 3
- System Architecture–Chapter 4
- System Architecture–Chapter 5
- System Architecture–Chapter 6
- System Architecture–Chapter 7
- System Architecture–Chapter 8
- System Architecture–Chapter 9
- System Architecture–Chapter 10
- System Architecture–Chapter 11
- System Architecture–Chapter 12
- System Architecture–Chapter 13
- System Architecture–Chapter 14
- System Architecture–Chapter 15
- System Architecture–Chapter 16
- Index
- Principles of System Architecture
References
[1] “Economies of Scale Made Steel,” Economist, 2011. http://ww3.economist.com/node/21538156
[2] http://www.maersk.com/innovation/leadingthroughinnovation/pages/buildingtheworldsbiggestship.aspx
[3] “Comparison of Event-Triggered and Time-Triggered Concepts with Regard to Distributed Control Systems,” A. Albert, Robert Bosch GmbH Embedded World, 2004, Nürnberg.
[4] J.E. Bailey and C.W. Sullivan. 2009–2012, Offshore Drilling Monthly, (Houston, TX: Jefferies and Company).
[5] “US Gulf Oil Profits Lure $16 Billion More Rigs by 2015,” Bloomberg, 2013. http://www.bloomberg.com/news/2013-07-16/u-s-gulf-oil-profits-lure-16-billion-more-rigs-by-2015.html)
[6] E. Fricke and A.P. Schulz, “Design for Changeability (DfC): Principles to Enable Changes in Systems throughout Their Entire Lifecycle,” Systems Engineering 8, no. 4 (2005).
[7] Norman R. Augustine, Augustine’s Laws, AIAA, 1997.
[8] “The Cost of Weapons—Defense Spending in a Time of Austerity,” Economist, 2010. http://www.economist.com/node/16886851
[9] D.A. Powner, “Polar-Orbiting Environmental Satellites: Agencies Must Act Quickly to Address Risks That Jeopardize the Continuity of Weather and Climate,” Washington, D.C.: United States Government Accountability Office, 2010. Report No.: GAO-10-558.
[10] D.A. Powner, “Environmental Satellites: Polar-Orbiting Satellite Acquisition Faces Delays; Decisions Needed on Whether and How to Ensure Climate Data Continuity,” Washington, D.C.: United States Government Accountability Office, 2008. Report No.: GAO-08-518.
-
No Comment