Creating software architecture

Designing good-quality software architecture has always been important, but in today's dynamic, rapidly changing and complex development environment, the programs are essential. A solid, well-thought-out project facilitates the management of software complexity, finding a compromise between often conflicting requirements and, finally, the timely launch of a good product on the market.
This book is a source of practical tips and methods for creating good software projects. In general, the basics of software architecture are discussed, and in detail - tasks related to its creation, while focusing on four architectural perspectives: conceptual, modular, executive and code. Analyzing four real cases, the observations and the best solutions of the most professional software architects were presented. It shows how the concepts and methods described in the book are applied in the most modern architectural projects. It was given how
- create projects that are flexible enough to include the latest achievements in them;
- use architecture as the basis for meeting performance requirements, modifiability, reliability and security;
- identify priorities in conflicting requirements and come to successful solutions;
- use the software architecture as a means of facilitating the integration of system components.
The Scientific and Technical Publishers recommend this book to computer science students and employees of software companies. We hope that it will enable them to thoroughly learn about the role of architecture in the process of creating quality software.

Table of Contents

List of drawings
List of tables
Preface
Preface

Part I Software architecture

Chapter 1. Introduction

1.1. The context of software architecture
1.1.1. Software architecture as a design plan
1.1.2. Software architecture as an abstraction
1.1.3. Terminology regarding software architecture
1.2. Where are the four perspectives from?
1.2.1. A loose connection of perspectives
1.2.2. Various engineering issues to which different perspectives relate
1.3. Using four perspectives
1.4. Notation
Additional literature

Part II. Designing, describing and using software architecture

Chapter 2. IS2000: advanced image processing system

2.1. System overview
2.2. Product properties
2.3. System interactions
2.4. The future of the IS2000 system

Chapter 3. Global analysis

3.1. Overview of global analysis activities
3.1.1. Analysis of factors
3.1.2. Strategy development
3.2. Analysis of company-dependent factors
3.3. Start strategy development
3.4. Analysis of technical factors
3.5. Continuation of strategy development
3.6. Analysis of factors related to the product
3.7. Continuation of strategy development
3.8. Summary of global analysis
Additional literature

Chapter 4. Conceptual architectural perspective

4.1. Design tasks in a conceptual architectural perspective
4.1.1. Global analysis
4.1.2. The main design tasks
4.1.3. Final project task: allocation of resources
4.2. Designing a conceptual architectural perspective for the IS200 system
4.2.1. Global analysis
4.2.2. Main design tasks: components, connectors and configuration
4.2.3. Final project task: allocation of resources
4.2.4. Summary of conceptual perspective design for IS2000
4.3. Summary of the conceptual architectural perspective
4.3.1. Traceability
4.3.2. Application of a conceptual architectural perspective
Additional literature

Chapter 5. Modular architectural perspective

5.1. Design tasks in a modular architectural perspective
5.1.1. Global analysis
5.1.2. The main design tasks
5.1.3. Final project task: interface design
5.2. Designing a modular architectural perspective for the IS2000 system
5.2.1. Global analysis
5.2.2. Main project tasks: defining modules and layers
5.2.3. Final project task: interface design
5.2.4. Summary of modular perspective design for IS2000
5.3. Summary of the modular architectural perspective
5.3.1. Traceability
5.3.2. The use of a modular architectural perspective
Additional literature

Chapter 6. Executive architectural perspective

6.1. Design tasks in an executive architectural perspective
6.1.1. Global analysis
6.1.2. The main design tasks
6.1.3. Final project task: allocation of resources
6.2. Designing an executive architectural perspective for the IS2000 system
6.2.1. Global analysis
6.2.2. Main project tasks: executive units, communication paths
and configuration
6.2.3. Final project task: allocation of resources
6.2.4. Summary of executive perspective design for IS2000
6.3. Summary of the executive architectural perspective
6.3.1. Traceability
6.3.2. The use of an executive architectural perspective
Additional literature

Chapter 7. Code architectural perspective

7.1. Design tasks in a code architectural perspective
7.1.1. Global analysis
7.1.2. The main design tasks
7.1.3. Final project tasks
7.2. Designing a code architectural perspective for the IS2000 system
7.2.1. Global analysis
7.2.2. Main project tasks: source, intermediate and implementation components
7.2.3. Final project tasks: building procedure and configuration management
7.2.4. A summary of the code design of the architectural perspective for IS2000
7.3. Summary of the code architectural perspective
7.3.1. Traceability
7.3.2. Application of a code architectural perspective
Additional literature

Part III. Examples of proper architecture design

software

Chapter 8. SafetyVision

8.1. Global analysis
8.1.1. Analysis of factors related to the product
8.1.2. Analysis of technical factors
8.1.3. Analysis of company-dependent factors
8.1.4. Developing a strategy
8.2. A conceptual architectural perspective
8.2.1. Components in the software specification
8.2.2. Connectors appearing in the software specification
8.2.3. Conceptual configuration
8.2.4. Allocation of system resources
8.3. Modular architectural perspective
8.3.1. Layer Software Applications
8.3.2. Layer Platform Software
8.4. Executive architectural perspective
8.4.1. processes
8.4.2. Communication paths
8.4.3. Executive configuration
8.5. Code architectural perspective
8.6. Application of software architecture
8.6.1. The process of creating software for enterprises
8.6.2. Testing ventures
8.7. Summary

Chapter 9. Healthy Vision

9.1. Global analysis
9.1.1. Analysis of factors related to the product
9.1.2. Analysis of technical factors
9.1.3. Analysis of company-dependent factors
9.1.4. Developing a strategy
9.2. A conceptual architectural perspective
9.3. Modular architectural perspective
9.3.1. Decomposition of application software
9.3.2. Decomposition of platform software
9.3.3. Layer structure
9.3.4. Recording of errors
9.4. Executive architectural perspective
9.4.1. Defining executive units
9.4.2. Communication paths
9.4.3. Return to conceptual and modular perspectives
9.4.4. Executive configuration
9.5. Code architectural perspective
9.5.1. Programming environment
9.5.2. Configuration management and building strategies
9.6. Application of software architecture
9.6.1. Rating
9.6.2. Creating a schedule
9.6.3. implementation of
9.6.4. Tracking requirements
9.7. Summary
9.7.1. Software architecture concepts
9.7.2. Experience

Chapter 10. Central Vision

10.1. Global analysis
10.1.1. Analysis of factors related to the product
10.1.2. Analysis of technical factors
10.1.3. Analysis of company-dependent factors
10.1.4. Developing a strategy
10.2. A conceptual architectural perspective
10.3. Modular architectural perspective
10.3.1. Decomposition and layer formation
10.3.2. Decomposition
10.4. Executive architectural perspective
10.4.1. Defining executive units
10.4.2. Defining communication paths
10.4.3. Defining the execution configuration
10.4.4. Allocation of resources
10.5. Code architectural perspective
10.5.1. The main design tasks
10.5.2. Building procedure and configuration management
10.6. Application of software architecture
10.7. Summary
10.7.1. Software architecture concepts
10.7.2. Experience

Chapter 11. Comm Vision

11.1. Global analysis
11.1.1. Analysis of factors related to the product
11.1.2. Analysis of technical factors
11.1.3. Analysis of company-dependent factors
11.1.4. Developing a strategy
11.2. A conceptual architectural perspective
11.3. Modular architectural perspective
11.3.1. Decomposition
11.3.2. SPU interfaces and dependencies between SPU
11.3.3. A layered structure and a coating model
11.4. Executive architectural perspective
11.4.1. Defining executable units and configurations
11.4.2. Communication
11.4.3. Restoration and communication packets resistant to restoring
11.4.4. Allocation of resources
11.5. Code architectural perspective
11.5.1. Source components
11.5.2. Intermediate components
11.5.3. Configuration management
11.6. Application of software architecture
11.6.1. Simulating and generating code
11.6.2. Greater efficiency in software development
11.6.3. Stage testing of coatings during manufacture
11.6.4. The process of controlling architecture
11.7. Summary
11.7.1. Software architecture concepts
11.7.2. Experience

Part IV Software architecture and your future

Chapter 12. The role of software architect

12.1. Creating a vision
12.2. Architect as a key technical consultant
12.3. The architect makes decisions
12.4. The architect gives guidance and supervises
12.5. The architect coordinates
12.6. The architect implements
12.7. The architect advocates
12.8. Software architecture as a career field

Dictionary
Four perspectives in a nutshell
Literature
Index