ISQI CPSA-FL 問題集

質問 1：
You are responsible for the documentation of the software architecture of a large development project. The project consists of three teams, each with its own architect, but with you as the person having overall responsibility of the entire project's software architecture.
Which of the following measures are beneficial? (Assign all answers.)

正解：

Explanation:
A) BeneficialB) BeneficialC) Not BeneficialD) Not BeneficialE) Beneficial In the context of documenting the software architecture for a large development project with multiple teams, the following measures can be considered beneficial:
A) Dividing the whole architecture documentation into sub-documents for each of the three sub-projects can be beneficial as it allows each team to focus on their specific area while maintaining a modular approach to documentation1.
B) Predefining the structure of the entire architecture documentation ensures consistency and coherence across all sub-projects. It helps in maintaining a uniform standard and facilitates easier integration of the sub-documents into the overall project documentation1.
C) Leaving the decision regarding the documentation structure to the team that first begins the documentation of its sub-project is not beneficial. This approach can lead to inconsistencies and may result in a lack of uniformity across the project's documentation1.
D) Rejecting word processing for the documentation because it is not connected with the source code is not beneficial. While it is important to link documentation with the source code, word processing tools can still be used effectively for creating comprehensive documentation. Tools like version control can be used to maintain a connection between the documentation and the source code1.
E) Having developers document their parts of the architecture documentation using source code can be beneficial. This approach ensures that the documentation is close to the implementation and can be more easily kept up-to-date1.
These measures align with the best practices for software architecture documentation as per the iSAQB SOFTWARE ARCHITECTURE - FOUNDATION LEVEL documents, which emphasize the importance of clear, consistent, and coherent documentation in software architecture1.

質問 2：
How are written documentation and verbal communication of software architectures related? Please mark the following statements as true or false. (Assign all answers.)

正解：

Explanation:
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

質問 3：
Which of the following statements are covered by the term 'coupling'? (Choose two.)
A. A building block uses internal data structures of another building block.
B. Two building blocks offer operations with the same name.
C. A building block uses an interface of another building block.
D. A building block only contains operations that belong together logically.
正解：A,C
解説: (Topexam メンバーにのみ表示されます)

質問 4：
Which of the following statements about the coupling between building blocks are correct? (Assign all answers.)

正解：

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