CPSA-FL Practice Exam Questions and Answers

A) TrueB) TrueC) TrueD) TrueE) TrueF) TrueG) True

When choosing a software-architecture modeling tool, several factors can play a role:

A) Multi-user capability is important for collaborative environments where multiple architects work on the same model simultaneously1.

B) Support of UML 2.x and SysML ensures that the tool can handle widely-used modeling languages for software and systems engineering1.

C) Document generation is a key feature that allows for the automatic creation of documentation from the model1.

D) Support of model transformations in preparation of the code generation indicates the tool’s ability to convert models into other forms or even into executable code1.

E) Support of code generation can significantly speed up the development process by generating code from the models1.

F) Compliance with standards ensures that the tool adheres to industry standards, which can be crucial for interoperability and future-proofing1.

G) Purchase and licensing costs are practical considerations that affect the total cost of ownership of the tool1.

These criteria are aligned with the iSAQB® SOFTWARE ARCHITECTURE – FOUNDATION LEVEL documents, which emphasize the importance of these factors in the selection of a software-architecture modeling tool1.

The correct statements about data structures, specifically stacks, are:

A.  

D.  

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) FalseC) TrueD) TrueE) TrueF) 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 stakeholders1.

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

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

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

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

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

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 techniques best suited to illustrate the interaction of runtime building blocks are:

A.  

B.  

C.  

G.  

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.

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.

References:

Known patterns for the adaptation of interfaces include:

A.  

D.