iSQI CPSA-FL ISAQB Certified Professional for Software Architecture -Foundation Level Exam Practice Test

In the context of software architecture, certain elements serve as building blocks to structure and organize software systems effectively.

• A: An algorithm is a sequence of steps designed to perform a specific task and can be a critical part of system logic and functionality.
• B: A component is a modular part of a system that encapsulates its contents and whose deployment and versioning can be managed independently.
• D: A class in object-oriented programming encapsulates data for the object and operations that manipulate that data, serving as a blueprint within the architecture.
• H: A package helps organize classes and interfaces that are related functionally, promoting a cleaner and more manageable architecture structure.

A) FalseB) TrueC) True

In a system with a multitude of class dependencies, the following measures can be considered:

A) The dependencies between classes are the responsibility of the developers. No measures are required within the architecture: This is false. While developers do manage day-to-day class dependencies, architectural measures are necessary to address systemic issues in a mature system1.

B) Loosening of direct dependencies between classes through the introduction of interfaces: This is true. Introducing interfaces can decouple classes and allow for more flexible and maintainable code1.

C) Loosening of direct dependencies between classes through the introduction of factories: This is also true. Factories can provide a way to create instances of classes without specifying the exact class, thus reducing dependencies1.

These measures align with the iSAQB® SOFTWARE ARCHITECTURE – FOUNDATION LEVEL guidelines, which suggest that managing dependencies is crucial for maintaining and extending systems effectively1.

To evaluate the reliability of a software system effectively, two methods stand out:B. Measurement of ‘Mean-Time-between-Failure’ (MTBF) - This is a standard measure of system reliability and is crucial for determining the average time between failures, helping to predict system reliability over time.E. Conducting an ATAM evaluation - Architecture Tradeoff Analysis Method (ATAM) provides a structured approach for evaluating decisions involving high-stake tradeoffs in software architectures, particularly affecting reliability among other quality attributes.

Considering that the requirements are still being determined, designing components with specific attributes can ensure adaptability and maintainability of the architecture.

• B: Weak coupling makes individual components less dependent on each other, enhancing the flexibility and scalability of the system.
• C: Strong cohesion ensures that components are designed with a clear purpose and functionality, improving the system's integrity and ease of maintenance.
• D: Making components open for extension but closed for modification supports the adaptability of the system to changing requirements without disrupting existing functionality.

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 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.

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.

A) CorrectB) IncorrectC) CorrectD) CorrectE) IncorrectF) Incorrect

The concept of coupling between building blocks is crucial in software architecture, and the iSAQB® SOFTWARE ARCHITECTURE – FOUNDATION LEVEL provides guidance on this topic. Here’s an analysis of the statements based on the curriculum:

A) A high degree of coupling of a building block reduces its reusability: This is correct. High coupling means that a building block is heavily dependent on other components, which can limit its ability to be reused in different contexts1.

B) Low coupling of a building block improves the ability to meet functional requirements: This statement is incorrect. While low coupling can contribute to a more maintainable and flexible architecture, it does not directly improve the ability to meet functional requirements1.

C) Low cohesion often leads to high coupling: This is correct. Cohesion refers to how closely related the responsibilities of a module are. Low cohesion can result in modules that perform a wide range of actions, which often leads to higher coupling with many other modules1.

D) Loose coupling often leads to less effort for making changes: This is correct. Loose coupling allows for easier modification of a system with minimal impact on other components, thus reducing the effort required for changes1.

E) For call dependencies, the degree of coupling is independent of the direction of the call: This statement is incorrect. The degree of coupling can be affected by the direction of the call, as it determines which module controls the interaction1.

F) In object-oriented programming languages, inheritance reduces coupling: This statement is incorrect. Inheritance can actually increase coupling because it creates a direct dependency between the superclass and the subclass1.

These insights are aligned with the principles outlined in the iSAQB® SOFTWARE ARCHITECTURE – FOUNDATION LEVEL curriculum, which emphasizes the importance of understanding and managing coupling for effective software architecture design1.

The term 'coupling' in software architecture refers to the degree of direct knowledge that one component has about another. This can be reflected in:A. A building block uses an interface of another building block. - This represents a form of coupling where components interact through well-defined interfaces, influencing the level of dependency between them.D. A building block uses internal data structures of another building block. - This indicates a higher degree of coupling, as it involves direct knowledge of another component’s internal workings, which is generally discouraged to maintain modularity and ease of maintenance.

These answers are based on fundamental software architecture and design principles widely recognized in the field.

A) TrueB) FalseC) TrueD) FalseE) True

The building-block view, as per the iSAQB® SOFTWARE ARCHITECTURE – FOUNDATION LEVEL, typically includes the following information:

A) Which building blocks the software is composed of: This is true. The building-block view shows the composition of software building blocks1.

B) How the building blocks interact during run time: This is false. The interaction during runtime is typically shown in the runtime view, not the building-block view1.

C) How the building blocks are hierarchically decomposed: This is true. The building-block view includes hierarchical decomposition of the software building blocks1.

D) How the building blocks are distributed in a distributed system: This is false. The distribution of building blocks in a distributed system is part of the deployment view1.

E) The dependencies between the building blocks: This is true. The building-block view should show the dependencies between the different building blocks1.

These aspects are essential for understanding the structure and organization of the software architecture and are aligned with the iSAQB® SOFTWARE ARCHITECTURE – FOUNDATION LEVEL documents1.

References:

Known patterns for the adaptation of interfaces include:A. Bridge - This design pattern is used to separate abstraction from its implementation so that both can be modified independently without affecting each other.D. Façade - This pattern provides a simplified interface to a more complex subsystem, serving as a point of entry to a larger body of code, making it easier to use.

A) TrueB) TrueC) FalseD) TrueE) TrueF) True

A) Top-down and bottom-up design may be employed in the same project.

• Top-down and bottom-up are two approaches to the design of software architecture. In top-down, the high-level design is created first, focusing on general functionalities and structure. In contrast, bottom-up starts with detailed designs focusing on a component or module level.