Software architecture in practice

The book is devoted to the practical use of the previously developed software architecture. Its authors are recognized in the world specialists in this field.
It consists of four parts. The first presents the basic issues related to software architecture, the second discusses the process of creating architecture, the third discusses the transition from architecture to ready software, and the fourth discusses the topic of multiple use of architecture. All the considerations were supported by numerous, aptly chosen examples.
There is no such item on the Polish market. The Scientific and Technical Publishers have decided to fill this gap, wanting to make it easier for Polish IT specialists to produce software products of the best quality, which is usually impossible without prior development of the proper architecture.

Table of Contents

Preface
thanks
Guide for the reader

PART ONE. CREATING A VISION OF ARCHITECTURE

Chapter 1. Business cycle of creating architecture

1.1. Where does architecture come from?
l.2. Software development processes and the business cycle of creating architecture
1.3. What makes architecture "good"?
1.4. Summary
1.5. Questions for discussion

Chapter 2. What is software architecture?

2.1. What is and what software architecture is not
2.2. Other points of view
2.3. Architectural patterns, reference models and reference architectures
2.4. Why is software architecture important?
2.5. Architectural structures and perspectives
2.6. Summary
2.7. Additional literature
2.8. Questions for discussion

Chapter 3. A-7E avionics system: case study of use

architectural structures

3.1. Connection to the business cycle of creating architecture
3.2. Requirements and quality features
3.3. Architecture of the A-7E avionics system
3.4. Summary
3.5. Additional literature
3.6. Questions for discussion

PART TWO. CREATING ARCHITECTURE

Chapter 4. Understanding of quality attributes

4.1. Functionality and architecture
4.2. Architecture and quality attributes
4.3 Quality attributes of the system
4.4. Scenarios of qualitative attributes in practice
4.5. Other system quality attributes
4.6. Business quality features
4.7. Quality features of architecture
4.8. Summary
4.9. Additional literature
4.10. Questions for discussion

Chapter 5. Achieving qualitative features

5.1. Presentation of tactics
5.2. Availability tactics
5.3. Modality tactics
5.4. Tactics of efficiency
5.5. Security tactics
5.6. Tests tactics
5.7. Usability tactics
5.8. Relationship tactics with architectural patterns
5.9. Patterns and architectural styles
5.10. Summary
5.11. Questions for discussion
5.12. Additional literature

Chapter 6. Air traffic control: design case study

in terms of high availability

6.1. Connection to the business cycle of creating architecture
6.2. Requirements and quality features
6.3. Architectural solution
6.4. Summary
6.5. Additional literature
6.6. Questions for discussion

Chapter 7. Architecture design

7.1. Architecture in the system life cycle
7.2. Architecture design
7.3. Shaping the division into teams
7.4. Creating a backbone system
7.5. Summary
7.6. Additional literature
7.7. Questions for discussion

Chapter 8. Flight simulation: case study of the architecture being created

for the possibility of merging

8.1. Links to the business cycle of architecture creation
8.2. Requirements and quality features
8.3. Architectural solution
8.4. Summary
8.5. Additional literature
8.6. Questions for discussion

Chapter 9. Documenting software architecture

9.1. Application of architectural documentation
9.2. outlook
9.3. Choosing the right perspectives
9.4. Documenting the perspective
9.5. Cross-sectional documentation
9.6. Unified Modeling Language
9.7. Summary
9.8. Additional literature
9.9. Questions for discussion

Chapter 10. Reconstruction of software architecture

10.1. Introduction
10.2. Extracting information
10.3. Building a database
10.4. Synthesis of perspective
10.5. Reconstruction
10.6. Example
10.7. Summary
10.8. Additional literature
10.9. Questions for discussion

PART THREE. ANALYZING ARCHITECTURE

Chapter 11. ATAM: full method of assessing architecture

11.1. ATAM participants
11.2. ATAM results
11.3. ATAM stages
11.4. Nightingale system: case study of ATAM application
11.5. Summary
11.6. Additional literature
11.7. Questions for discussion

Chapter 12. CBAM: a quantitative approach to architectural making

design decisions

12.1. Determinants of decision making
12.2. The basis of CBAM
12.3. Implementing CBAM
12.4. Case study: ECS NASA project
12.5. Results of the CBAM evaluation
12.6. Summary
12.7. Additional literature
12.8. Questions for discussion

Chapter 13. Web: a case study of interoperability

13.1. Links to the business cycle of architecture creation
13.2. Requirements and quality features
13.3. Architectural solution
13.4. The next stage of the ABC cycle: the evolution of e-commerce architecture based on the WWW
13.5. Achieving quality goals
13.6. The business cycle of creating architecture today
13.7. Summary
13.8. Additional literature
13.9. Questions for discussion

PART FOUR. FROM ONE SYSTEM TO MANY

Chapter 14. Assortments of software products: re-use

architectural assets

14.1. Advantages of the assortment of software products
14.2. What makes the assortment of software products a success?
14.3. Determining the scope
14.4. Architectural solutions for the product range
14.5. What makes implementing a range of software products difficult?
14.6. Summary
14.7. Additional literature
14.8. Questions for discussion

Chapter 15. CelsiusTech: case study of creating a range of products

15.1. Links to the business cycle of architecture creation
15.2. Requirements and quality features
15.3. Architectural solution
15.4. Summary
15.5. Additional literature
15.6. Questions for discussion

Chapter 16. J2EE / EJB: case study

processing infrastructure

16.1. Links to the business cycle of architecture creation
16.2. Requirements and quality features
16.3. Architectural solution
16.4. Decisions on the implementation of the system
16.5. Summary
16.6. Additional literature
16.7. Questions for discussion

Chapter 17. Luther Architecture: a case study of a mobile application

based on J2EE

17.1. Links to the business cycle of architecture creation
17.2. Requirements and quality features
17.3. Architectural solution
17.4. How Luther's architecture has ensured the achievement of quality objectives
17.5. Summary
17.6. Additional literature
17.7. Questions for discussion

Chapter 18. Building systems from commercial components

18.1. The influence of components on architecture
18.2. Architectural divergence
18.3. Component design as a search
18.4. The ASEILM example
18.5. Summary
18.6. Additional literature

Chapter 19. Software architecture in the future

19.1. We are going back to the business cycle of creating architecture
19.2. Creating architecture
19.3. Place of architecture in the system life cycle
19.4. The impact of commercial components
19.5. Summary

acronyms
Literature
Index