CPSA-FL ISAQB Certified Professional for Software Architecture -Foundation Level Questions and Answers

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.

A) False B) False C) True D) True E) True F) True

A)  Agile approaches make written documentation unnecessary. In such cases, verbal communication can substitute for documentation.

False.  Even in agile approaches, written documentation is important for maintaining a clear and consistent understanding of the architecture among team members and stakeholders 1 .

B)  Written documentation makes verbal reiteration unnecessary.

False.  Verbal communication is essential for clarifying and reinforcing the content of written documentation, especially when addressing complex or nuanced architectural issues 2 .

C)  Despite written documentation, verbal communication of architectural interrelationships is important.

True.  Verbal communication plays a crucial role in explaining the rationale behind architectural decisions and interrelationships that may not be fully captured in documentation 2 .

D)  Documentation and communication should use identical terms and rationale.

True.  Consistency in terminology and rationale between documentation and verbal communication helps prevent misunderstandings and ensures that all parties have a common understanding of the architecture 2 .

E)  Documentation should be created primarily for project participants who either cannot or do not want to read the system’s source code.

True.  Documentation serves as a guide for those who may not be directly involved in coding but need to understand the architecture, such as managers, new team members, or external stakeholders 2 .

F)  Communication and documentation complement each other: verbal communication helps architects determine what must be recorded in writing.

True.  Verbal communication often reveals what aspects of the architecture are most important or confusing to team members, guiding what should be emphasized in written documentation

A) Not Appropriate B) Appropriate C) Not Appropriate

For a project involving multiple architects and developers, achieving consistent and adequate documentation is crucial. Here’s how the methods listed would fare:

A) The chief architect creates the documentation : This method is not appropriate because it places the entire burden of documentation on a single individual, which can lead to bottlenecks and may not accurately reflect the contributions and insights of the entire team 1 .

B) Identical templates are used for the documentation : This is an appropriate method as it ensures consistency across the documentation produced by different team members. Using identical templates helps maintain a uniform structure and style, which is beneficial for readability and maintenance 1 .

C) All parts of the architecture documentation are automatically extracted from the source code : Relying solely on automatic extraction is not appropriate because it may not capture all the necessary details and decisions made during the architectural design process. Manual documentation is also important to provide context and rationale that cannot be automatically generated 1 .

These methods are in line with the iSAQB® SOFTWARE ARCHITECTURE – FOUNDATION LEVEL, which emphasizes the importance of clear, consistent, and comprehensive documentation practices 1 .

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.

Understandability in architecture documentation is crucial as it directly impacts the ease with which the architecture can be reviewed, maintained, and extended. Here’s why the chosen answers are relevant:

It is an important quality characteristic (C) : Understandability ensures that the architecture is accessible not only to the creators but also to other stakeholders like new team members, management, and maintenance personnel. This aids in the effective communication of the architecture’s intent, usage, and functionalities.

It is a quality characteristic together with simplicity and brevity (E) : Simplicity and brevity contribute to making complex systems easier to understand. Concise and straightforward documentation helps in quicker comprehension and reduces ambiguities.

It is a quality characteristic together with scope and completeness (F) : While it is important for the documentation to be comprehensive, it should also clearly define the scope of the system. This helps in setting the right expectations and ensures that the documentation covers all necessary aspects thoroughly, thus enhancing understandability.

References:

“Documenting Software Architectures: Views and Beyond” by Paul Clements et al. emphasizes the importance of these aspects in effective architecture documentation.

ISO/IEC 42010 also highlights understandability as a fundamental quality characteristic of architectural descriptions.

A) False B) False C) False D) True E) True F) False

Postel’s law, also known as the robustness principle, is a guideline in software engineering that advises to " be conservative in what you do, be liberal in what you accept from others " 1 . This principle has implications for system design and interaction with external interfaces:

A) Response time of the system is reduced : This is false. Postel’s law does not directly relate to the response time of a system 1 .

B) Implementation effort increases : This is false. Being liberal in what is accepted can actually simplify implementation because the system is designed to handle a wider range of inputs without failure 1 .

C) Usability of the system is reduced : This is false. Postel’s law aims to increase robustness and interoperability, which can enhance usability by making the system more resilient and accommodating 1 .

D) Robustness of the system is increased : This is true. By being conservative in outputs and liberal in inputs, the system becomes more robust, handling a variety of inputs without error 1 .

E) The integrity of the data transferred via interfaces is increased : This is true. Accepting a wide range of inputs and adhering strictly to output specifications helps maintain data integrity across different systems 1 .

F) Availability of the system is reduced due to potentially bad quality of input data : This is false. Postel’s law suggests that the system should be designed to handle poor quality input data gracefully, thus maintaining availability 1 .

Applying Postel’s law helps create systems that are more tolerant of input variations and strict in their outputs, contributing to overall system robustness and reliability 1 .

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.

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.