In the context of software architecture, the common definitions often focus on the structural aspects of system design. Here’s how the chosen answers align with the iSAQB® guidelines on software architecture:

Building Blocks (B): A fundamental concept in software architecture, building blocks refer to the modular units from which the system is constructed. These can include modules, classes, or components, all of which are vital for defining the structure and behavior of the system.

Relationships (D): Relationships in software architecture define how different components or building blocks interact with each other. These interactions are essential for understanding data flow, dependencies, and communication patterns within the system.

Components (E): Components are larger than building blocks and encompass them, representing significant units of functionality within the system. Each component usually encapsulates a portion of the system ' s overall functionality and interacts with other components via interfaces.

Interfaces (G): Interfaces define the points of interaction between components or building blocks. They are critical for ensuring that components can function independently yet interact seamlessly when required.

The correct statements about design patterns are: A. Design patterns are not invented but discovered. - Design patterns represent solutions to common design problems and are derived from repeated experiences and observations in software development rather than being invented. B. Design patterns should always be described alongside the problem they are supposed to solve. - A fundamental aspect of using design patterns is understanding the specific problem a pattern addresses, which helps in applying the pattern effectively in relevant scenarios.

The most accurate statements about quality characteristics are: B. Increased flexibility improves robustness - Flexibility in

design allows the system to handle and recover from errors and unexpected inputs more robustly. C.

Simplicity increases comprehensibility - A simpler design is easier to understand, maintain, and less prone to errors, directly

impacting the comprehensibility of the software.

Quality requirements specify the conditions under which a system must operate to meet the needs of its users and stakeholders, focusing on performance, usability, reliability, etc.

C : Automatic spelling correction is a feature related to the system ' s usability and accuracy, improving the overall quality of user interaction.

D : Stating a failure rate of less than 0.1% specifies a reliability target that the system must achieve, making it a quantifiable and critical quality requirement.

In template-based architecture documentation, the most important fields are: A. To describe module structures (white boxes) - This involves detailing the internal structure of modules, which is crucial for understanding how software components are implemented and how they interact internally. B. To describe individual architectural modules and their external interfaces (black boxes) - This focuses on the interfaces and interactions of modules with external components, essential for understanding system integrations and dependencies. D. To use a standardized document structure - Standardization in documentation facilitates consistency, readability, and maintainability of documents, which is critical for long-term project management and new team member onboarding.