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

The statements regarding the design principle ‘information hiding’ that are true and false are as follows:

• True:
• False:

The principle of ‘information hiding’ is a fundamental concept in software engineering that promotes encapsulation and abstraction. Here’s an explanation of each statement:

• True Statements:
• False Statements:

Information hiding is crucial for maintaining a clean and modular architecture, where components can be developed, maintained, and replaced independently.

References:

• Stack Overflow discussion on Abstraction vs Information Hiding vs Encapsulation1.
• Wikipedia article on Information Hiding2.
• Kansas State University textbook excerpt on Information Hiding3.
• Techopedia definition of Information Hiding4.

The layered architectural pattern, also known as n-tier architecture, is a common framework in software development that organizes a system into distinct layers with specific roles and responsibilities. The primary advantage of this pattern is its Separation of Concerns (SoC), which means each layer is independent and can be understood without the others2. This separation enhances flexibility because changes in one layer can be made with minimal impact on others, allowing for easier maintenance and scalability12.

While creating high-performance systems (B) and being able to use application servers © are also considerations in system architecture, they are not the main benefits attributed to the layered pattern. The layered architecture is more about managing complexity and promoting modularity rather than directly enhancing performance or dictating the use of specific technologies like application servers34.

References:

• Baeldung on Computer Science article on Layered Architecture1.
• O’Reilly’s Software Architect’s Handbook on Advantages of Layered Architectures2.
• Bitloops documentation on Layered Architecture3.
• Developn article on Software Architecture Patterns

When designing external interfaces, several considerations must be taken into account:A. Volatility of neighbouring systems - Changes in neighboring systems can affect the stability and compatibility of interfaces, requiring interfaces to be adaptable to changes.C. Protocols enforced by neighbouring systems - It's crucial to align with the protocols used by neighboring systems to ensure seamless communication and interoperability.D. Expected amount of parallel calls - This affects the scalability and performance requirements of the interface, as it must be designed to handle the expected load efficiently.

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) FalseB) TrueC) TrueD) False

A) Architectural objectives and project objectives need to be identical.

• This is false. Architectural objectives are concerned with the technical goals and quality attributes of the system, while project objectives are broader and include timelines, budgets, and overall project deliverables12.

B) Most of the time, architectural objectives are of a more long-term nature than project objectives.

• This is true. Architectural objectives often focus on the sustainability and maintainability of the system, which are long-term considerations, whereas project objectives may be more immediate and focused on the project’s completion12.

C) Architectural objectives and project objectives need to be negotiated between the concerned parties.

• True. Both sets of objectives should align with the stakeholders’ needs and the project’s overall goals, and thus require negotiation to ensure that all parties’ interests are addressed3.

D) Architectural objectives are a subset of project objectives.

• This is false. Architectural objectives are not necessarily a subset but are related and should support the project objectives. They deal specifically with the architecture of the system, which is one aspect of the project

A) TrueB) FalseC) TrueD) True

A) The project plan from management is influenced by architectural decisions.

• True. Architectural decisions often have significant implications on the project plan, including timelines, resource allocation, and technical approaches1.

B) Cost estimates are primarily the responsibility of the architect.

• False. While architects may contribute to cost estimates, especially regarding design-related expenses, it is typically the management’s responsibility to oversee and finalize cost estimates for the entire project2.

C) Architects advise project management on the definition of work packages.

• True. Architects play a crucial role in defining work packages, particularly in ensuring that the technical aspects of the project are accurately captured and planned for1.

D) Management and architects cooperate on handling of technical risks.

• True. Both management and architects need to work closely to identify, assess, and manage technical risks throughout the project2.

The purpose of defining the system context includes:

• To illustrate the system’s interfaces with external systems (B) - True
• To clarify the area of responsibility of the software architect C - True
• To represent the external systems (D) - True
• To distinguish between infrastructure and application (E) - True
• To distinguish between the hardware and software of a solution (F) - True

Defining the system context is a crucial step in software architecture as it helps to establish the boundaries and interactions of a system within its environment. Here’s a detailed explanation of the purposes:

• To Illustrate the System’s Interfaces with External Systems (B): It is essential to understand how the system interacts with other systems, which can influence requirements and design1.
• To Clarify the Area of Responsibility of the Software Architect ©: By defining the system context, the architect’s responsibilities regarding the system’s interactions and boundaries are made clear1.
• To Represent the External Systems (D): The system context helps identify and represent all external entities that interact with the system, which is important for comprehensive design and analysis1.
• To Distinguish Between Infrastructure and Application (E): Understanding the system context allows for a clear distinction between the infrastructure (the environment in which the application operates) and the application itself1.
• To Distinguish Between the Hardware and Software of a Solution (F): The system context helps to differentiate between the hardware components and the software components of a system, which is vital for system integration and deployment1.

These aspects of the system context are fundamental for ensuring that the system is designed and developed to meet its intended goals and operate effectively within its designated environment.

References:

• Smartpedia article on System Context1.
• Visual Paradigm Blog on System Context Diagrams2.
• microTOOL article on System Context3.

The Architecture Tradeoff Analysis Method (ATAM) helps evaluate architecture decisions with respect to quality attributes by producing several key artifacts:

• B: The concrete quality tree illustrates and organizes the quality attributes specific to the architecture being evaluated, showing how generic quality attributes are refined into measurable scenarios.
• C: Description of quality scenarios specifies and documents the scenarios under which the architecture's responses are tested against the desired quality attributes.
• G: List of the architectural risks identifies potential risks in the architecture that may threaten the system’s ability to meet its quality goals, aiding in proactive risk management.

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.