Book Image

Software Architecture with C++

By : Adrian Ostrowski, Piotr Gaczkowski
Book Image

Software Architecture with C++

By: Adrian Ostrowski, Piotr Gaczkowski

Overview of this book

Software architecture refers to the high-level design of complex applications. It is evolving just like the languages we use, but there are architectural concepts and patterns that you can learn to write high-performance apps in a high-level language without sacrificing readability and maintainability. If you're working with modern C++, this practical guide will help you put your knowledge to work and design distributed, large-scale apps. You'll start by getting up to speed with architectural concepts, including established patterns and rising trends, then move on to understanding what software architecture actually is and start exploring its components. Next, you'll discover the design concepts involved in application architecture and the patterns in software development, before going on to learn how to build, package, integrate, and deploy your components. In the concluding chapters, you'll explore different architectural qualities, such as maintainability, reusability, testability, performance, scalability, and security. Finally, you will get an overview of distributed systems, such as service-oriented architecture, microservices, and cloud-native, and understand how to apply them in application development. By the end of this book, you'll be able to build distributed services using modern C++ and associated tools to deliver solutions as per your clients' requirements.
Table of Contents (24 chapters)
1
Section 1: Concepts and Components of Software Architecture
5
Section 2: The Design and Development of C++ Software
6
Architectural and System Design
10
Section 3: Architectural Quality Attributes
15
Section 4: Cloud-Native Design Principles
21
About Packt
Functional and Nonfunctional Requirements

As an architect, it is important for you to recognize which requirements are significant for the architecture and why. This chapter will teach you about the various requirements of a solution—functional and nonfunctional. Functional requirements are those that tell you what your solution should do. On the other hand, nonfunctional ones are those that tell you how your solution should be.

In this chapter, we'll cover the following topics:

  • Understanding the types of requirements
  • Recognizing architecturally significant requirements
  • Gathering requirements from various sources
  • Documenting requirements
  • Documenting architecture
  • Choosing the right views to document
  • Generating documentation

By the end of this chapter, you will have learned how to recognize and categorize both types of requirements and how...