Home Page Icon
Home Page
Table of Contents for
Cover
Close
Cover
by Raghvinder S. Sangwan
Software and Systems Architecture in Action
Preface
About the Author
Chapter 1 - Architecture and Its Significance
1.1 Introduction
1.2 Rising Complexity
1.3 Constant Change
1.4 Distributed Development
1.5 Practice for Architecture-Centric Engineering
1.6 Summary
1.7 Questions
References
Chapter 2 - Stakeholders and Their Business Goals
2.1 Introduction
2.2 Influence of Business Goals on the Architecture
2.3 Representing Business Goals
2.4 Refining Business Goals
2.5 Translating Engineering Objectives into Architectural Requirements
2.6 Prioritizing Architectural Requirements
2.7 Summary
2.8 Questions
References
Chapter 3 - Establishing Broad Functional Understanding
3.1 Introduction
3.2 System Context
3.3 System Use Cases
3.4 Domain Model
3.5 An End-to-End Operational View
3.6 Constraints
3.7 Summary
3.8 Questions
References
Chapter 4 - Getting Ready for Designing the Architecture
4.1 Introduction
4.2 Architectural Drivers
4.3 Patterns
4.3.1 Layered View
4.3.2 Data Flow View
4.3.3 Data-Centered View
4.3.4 Adaptation View
4.3.5 Language Extension View
4.3.6 User Interaction View
4.3.7 Component Interaction View
4.3.8 Distribution View
4.4 What Is a Tactic?
4.4.1 Tactics for Availability
4.4.2 Tactics for Interoperability
4.4.3 Tactics for Modifiability
4.4.4 Tactics for Performance
4.4.5 Tactics for Security
4.4.6 Tactics for Testability
4.4.7 Tactics for Usability
4.5 Summary
4.6 Questions
References
Chapter 5 - Creating the Architecture
5.1 Introduction
5.2 Architecture of the Building Automation System
5.2.1 Support for Adding New Field Devices
5.2.2 Addressing Latency and Load Conditions
5.2.3 Addressing International Language Support
5.3 Architecture Trade-Offs
5.3.1 Revisiting Modifiability Drivers
5.3.2 Revisiting Performance Drivers
5.4 The Final Architecture
5.5 Summary
5.6 Questions
References
Chapter 6 -
6.1 Introduction
6.2 Views as a Basis for Documentation
6.3 Documenting a View
6.4 Building an Architecture Description Document
6.5 Architecture Description for the Building Automation System
6.5.1 Section 1: Document Road Map
6.5.1.1 Section 1.1: Description of the Architecture Documentation
6.5.1.2 Section 1.2: How Stakeholders Can Use the Documentation
6.5.2 Section 2: System Overview
6.5.2.1 Section 2.1: Business Goals
6.5.2.2 Section 2.2: System Context
6.5.2.3 Section 2.3: Functions
6.5.2.4 Section 2.4: Quality Attribute Requirements
6.5.2.5 Section 2.5: Constraints
6.5.2.6 Section 2.6: Architectural Drivers
6.5.3 Section 3: View Template
6.5.4 Section 4: Views
6.5.4.1 Section 4.1: Module View
6.5.4.2 Section 4.2: Component-and-Connector View
6.5.4.3 Section 4.3: Deployment View
6.5.5 Section 5: Mapping between Views
6.5.6 Section 6: Rationale
6.6 Conclusions
6.7 Questions
References
Chapter 7 - Architecture and Detailed Design
7.1 Introduction
7.2 Defining Interfaces
7.3 Creating the Domain Object Model
7.3 The Rule Manager
7.3.1 Addressing Architectural Responsibilities
7.3.2 Addressing Functional Responsibilities
7.4 Summary
7.5 Question
References
Chapter 8 - Role of Architecture in Managing Structural Complexity
8.1 Introduction
8.2 Analyzing System Complexity
8.2.1 Partitioning a DSM
8.2.2 Partitioning Algorithms
8.2.3 Tearing a DSM
8.3 Managing Structural Complexity
8.3.1 Testing the Hypothesis
8.4 Discussion and Conclusions
8.5 Discussion Questions
References
Search in book...
Toggle Font Controls
Playlists
Add To
Create new playlist
Name your new playlist
Playlist description (optional)
Cancel
Create playlist
Sign In
Email address
Password
Forgot Password?
Create account
Login
or
Continue with Facebook
Continue with Google
Sign Up
Full Name
Email address
Confirm Email Address
Password
Login
Create account
or
Continue with Facebook
Continue with Google
Next
Next Chapter
Preliminaries
Add Highlight
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click
here
login for view all page.
Day Mode
Cloud Mode
Night Mode
Reset