Book news: Architecture Practice-Software Architecture Design Process

Architecture Practice-Software Architecture Design Process

Basic Information

Author: (English) Peter eelespeter Cripps
Translator: Cai huanghui; MA Wentao
Press: Machinery Industry Press
ISBN: 9787111301158
Mounting time:
Published on: February 1, April 2010
Start: 16
For more details, see: http://www.china-pub.com/196666

Introduction

Starting from the basic principles, this book introduces some concepts, processes, methods, work products used and reusable resources involved in the software architecture design process, starting from Chapter 1, describe a specific case to illustrate how to define requirements, create logical architecture, and create physical architecture. In Chapter 2 "advanced", the author adds the relationships between architects and other aspects of software development projects, and explains the possible difficulties and Corresponding Solutions of various software development projects.
This book combines theory with practice to introduce some of the best methods that can be applied to the entire or part of the architectural design process. Whether you are a senior architect or a beginner user who is interested in becoming an architect, you can benefit from reading this book.

Directory

Translator's preface
Collation
Preface
Thank you
Author Profile
Chapter 1 Introduction
1.1 process application
1.2 Process Overview
Range: 1.3
1.4 conclusion
Chapter 4 architecture, architect and Architecture Design
2.1 Architecture
2.1.1 Architecture Definition Structure
2.1.2 Architecture Definition Behavior
2.1.3 important elements of Architecture
2.1.4 architecture balancing the needs of stakeholders
2.1.5 concrete decision-making based on rational evidence
2.1.6 the architecture follows an architectural style
2.1.7 architecture affected by its Environment
2.1.8 architecture affects the development team structure

. 2.1.9 architecture exists for all systems
2.1.10 the architecture has a specific scope
2.2 architect
2.2.1 The architect is a technical leader
2.2.2 An architect's role may be played by a team
2.2.3 the architect understands the software development process
2.2.4 architects have knowledge in the business field
2.2.5 architects master technical knowledge
2.2.6 architects master design skills
2.2.7 architects have programming skills
2.2.8 the architect is an excellent communication Engineer
2.2.9 architects make decisions
2.2.10 architects understand organizational policies
2.2.11 the architect is a negotiating expert
2.3 Architecture Design
2.3.1 architecture design is a science
2.3.2 architecture design is an art
2.3.3 architecture design across many aspects
2.3.4 architecture design is a gradual Activity
2.3.5 architecture design is driven by many stakeholders
2.3.6 architecture design often includes compromise
2.3.7 experience in Architecture Design
2.3.8 Architecture Design from top to bottom
2.4 advantages of Architecture Design
2.4.1 architecture design solves System Quality Problems
2.4.2 consensus on Architecture Design
2.4.3 architecture design support plan preparation process
2.4.4 Architecture Design Promotes architecture integrity
2.4.5 architecture design facilitates management complexity
2.4.6 architecture design provides the foundation for Reuse
2.4.7 architecture design reduces maintenance costs
2.4.8 Architecture Design Support impact analysis
2.5 Conclusion
Chapter 1 Basic Principles of methods
3.1 Key Concepts
3.2 Method Content
3.2.1 role
3.2.2 work products
3.2.3 activities
3.2.4 task
3.3 Process
3.3.1 waterfall Process
3.3.2 Iterative Process
3.3.3 agile process
3.4 Conclusion
Chapter 4 compiling software architecture documents
4.1 final conclusion
4.2 Key Concepts
4.3 viewpoint and view
4.3.1 basic viewpoint
4.3.2 cross Viewpoint
4.3.3 views and charts
4.3.4 advantages of viewpoint and view
4.4 Model
4.4.1 implementation level
4.4.2 advantages of the Model
4.5 architecture description framework features
4.5.1 4 + 1 view model of software architecture
4.5.2zachman framework
4.5.3rozanski and Woods frameworks
4.6 architecture description Framework
4.6.1 Viewpoint
4.6.2 work products
4.6.3 implementation level
4.6.4 consistent views
4.7 Software Architecture document
4.8 conclusion
Chapter 2 Reusable Architecture Resources
5.1 source of Architecture
5.2 architecture resource Meta Model
5.2.1 development resources
5.2.2 resources during runtime
5.3 type of resources
5.3.1 reference architecture
5.3.2 Development Method
5.3.3 view directory
5.3.4 architecture style
5.3.5 Architecture
5.3.6 Mode
5.3.7 Reference Model
5.3.8 architecture Decision-Making
5.3.9 existing applications
5.3.10 encapsulated applications
5.3.11 Application Framework
5.3.12 Component Library/component
5.4 architecture resource attributes
5.5 other reuse considerations
5.6 conclusion
Chapter 2 case studies
6.1 process application
6.2 scope of case studies
6.2.1 Project Team
6.2.2 external factors
6.3 application Overview
6.4yourtour vision
6.4.1 statement
6.4.2 stakeholders
6.4.3 system functions
6.4.4 System Quality
6.4.5 Constraints
6.5 conclusion
Chapter 1 definition requirements
7.1 associated requirements and architecture
7.2 functional and non-functional requirements
7.3 techniques for compiling Requirement documents
7.4 process application
7.5 understand task description
7.6 define requirements: Activity Overview
7.7 conclusion
Chapter 4 logical architecture creation
8.1 from demand to Solution
8.2 value of logical architecture
8.2.1 minimize the logical architecture
8.2.2 logical architecture as an investment
8.2.3 importance of traceability
8.3 process application
8.4 create a logical architecture: Activity Overview
8.5 conclusion
Chapter 4 create a physical architecture
9.1 from logical architecture to physical architecture
9.2 process application
9.3 create a physical architecture: Activity Overview
9.4 task: Investigate architecture Resources
9.5 task: Define Architecture Overview
9.6 task: Compile the architecture decision document
9.7 task: Overview of functional elements
9.7.1 map logical function elements to physical function Elements
9.7.2 confirm physical function Elements
9.7.3 purchase products
9.7.4 model for adapting to specific technologies
9.8 task: Overview of deployment Elements
9.8.1 map logical deployment elements to physical deployment Elements
9.8.2 confirm physical deployment Elements
9.8.3 hardware procurement
9.9 task: test the architecture
9.10 task: proof of architecture construction
9.11 task: refine functional elements
9.12 task: refine deployment Elements
9.13 task: confirm the architecture
9.14 task: update the software architecture document
9.15 task: Review the architecture with stakeholders
9.16 conclusion
Chapter 2 advanced
10.1 architects and project teams
10.1.1 architects and requirements
10.1.2 architect and development
10.1.3 architect and Test
10.1.4 architect and Project Management
10.1.5 architect and configuration management
10.1.6 architect and change management
10.1.7 architect and development environment
10.1.8 architect and business analysis
10.2 architects and external influences
10.2.1 Enterprise Architecture
10.2.2 Design Authority
10.2.3 infrastructure provider
10.2.4 system maintainer
10.3 Architecture Design of Complex Systems
10.3.1 many unique features are under development
10.3.2 many people participate in development
10.3.3 The system is highly distributed.
10.3.4 the development team is distributed
10.3.5 extremely challenging operation quality
10.3.6 System
10.4 conclusion
Appendix A Software Architecture Meta-Model
Appendix B viewpoint directory
Appendix C method Overview
Appendix D architecture requirement check list
Glossary
References

This book Douban address: http://book.douban.com/subject/4818685/