ISQI CPSA-FL 問題集

質問 1：
You are the software architect on a large development project and are entrusted with the task of building a tool chain for continuous architecture evaluation and analysis.
Which of the following statements regarding this tool selection are correct/incorrect? (Assign all answers.)

正解：

Explanation:
A) IncorrectB) CorrectC) IncorrectD) IncorrectE) Incorrect
In the context of building a tool chain for continuous architecture evaluation and analysis, the following statements can be assessed:
A) Tools for static code analysis do not find all dependencies in the source code. They can find many, but not necessarily all, especially if dynamic programming techniques are used1.
B) Several tools for static code analysis can be used to verify compliance with architectural rules. This is one of the primary uses of static code analysis tools1.
C) Tools for static code analysis cannot reliably measure cohesion because cohesion is a qualitative aspect of modules that depends on the context and design intent, which static analysis alone cannot fully capture1.
D) Tools for static code analysis are not typically used to optimize runtime efficiency. They are more focused on code quality, security, and compliance with coding standards1.
E) Tools for dynamic analysis, such as profilers, can be used to optimize static structures. They provide runtime information that can inform decisions about the static structure of the code1.
These assessments are based on the iSAQB SOFTWARE ARCHITECTURE - FOUNDATION LEVEL documents, which provide guidelines on the selection and use of tools for software architecture evaluation and analysis1.

質問 2：
Which of the following statements regarding the design principle 'information hiding' are true and which are false? (Assign all answers.)

正解：

Explanation:
The statements regarding the design principle 'information hiding' that are true and false are as follows:
* True:
* Adhering to the 'information hiding' principle increases flexibility for modifications (A).
* Information hiding involves deliberately hiding information from callers or consumers of the building block (B).
* In object-oriented development, information hiding is primarily relevant at class level (E).
* False:
* Information hiding makes it harder to distinguish between interface and implementation C.
* Information hiding is a derivative of the approach of incremental refinement along the control flow (D).
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:
* (A): Information hiding allows for changes in the implementation without affecting other parts of the system, thus increasing flexibility1.
* (B): The core idea of information hiding is to keep the implementation details away from the users of the component, revealing only what is necessary2.
* (E): In object-oriented programming, information hiding is typically applied at the class level, where internal data and methods are hidden from other classes3.
* False Statements:
* C: Information hiding does not make it harder to distinguish between interface and implementation; rather, it helps to clearly define the interface by hiding the implementation details1.
* (D): Information hiding is not a derivative of incremental refinement along the control flow; it is a separate principle that focuses on hiding the internal complexities of a component4.
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.

質問 3：
Choose the most desirable characteristics of interfaces. (Choose three.)
A. Easy to extend
B. Scalable to many consumers
C. Geared towards the capabilities of the provider
D. As few parameters as possible
E. Hard to misuse
F. Clear descriptions of assertions and prerequisites
G. Remotely callable
正解：A,E,F
解説: (Topexam メンバーにのみ表示されます)

質問 4：
Which characteristics of a black-box building block are you able to specify as an architect? (Assign all answers.)

正解：

Explanation:
As an architect, you can specify the following characteristics of a black-box building block:
* Compliance with functional requirements (A)
* Compliance with non-functional requirements (B)
* Purpose and/or responsibility (D)
* Method signature of public interfaces (E)
* Data formats of public interfaces (F)
In software architecture, a black-box building block is a component whose internal structure is not exposed to or understood by other components. It is defined only by its provided functionality and the services it offers.
Here's a detailed explanation of each characteristic:
* Compliance with Functional Requirements (A): This refers to the ability of the building block to perform the functions it was designed to do, which are often captured in a functional specification document.
* Compliance with Non-functional Requirements (B): These are criteria that can be used to judge the operation of a system, rather than specific behaviors. This includes requirements related to scalability, performance, security, and reliability.
* Purpose and/or Responsibility (D): This defines the role the building block plays in the overall system architecture, including its responsibilities and the services it provides.
* Method Signature of Public Interfaces (E): The method signature defines the interface that other components can use to interact with the building block. It includes the method name, parameters, and return type.
* Data Formats of Public Interfaces (F): This specifies the format and structure of the data that is accepted or returned by the building block's public interfaces.
These characteristics are essential for ensuring that the building block can be effectively integrated into a larger system and interact with other components as expected.
References:
* Bass, L., Clements, P., & Kazman, R. (2012). Software Architecture in Practice (3rd ed.).
Addison-Wesley Professional.
* Martin, R. C. (2003). Agile Software Development: Principles, Patterns, and Practices. Prentice Hall.
* Fowler, M. (2002). Patterns of Enterprise Application Architecture. Addison-Wesley.

質問 5：
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.