CPSA-FL Deutsch 無料問題集「ISQI ISAQB Certified Professional for Software Architecture - Foundation Level (CPSA-FL Deutsch Version)」

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

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

解説: (JPNTest メンバーにのみ表示されます)

Explanation:
The aspects that are more of a domain-related nature and those that are more of a technical nature are as follows:
* More technical:
* Choosing a database (A)
* Choosing a layout manager in a GUI (D)
* The average number of methods per class (E)
* More domain-related:
* Modelling a banking account (B)
* Legal constraints for the execution of a money transfer
* Specification of a calculation formula (F)
In software architecture, aspects can be categorized based on their relevance to the domain (the problem space) or the technology (the solution space). Here's an explanation of each:
* More Technical:
* Choosing a database (A): This is a technical decision based on factors like data volume, concurrency, performance, and technology stack.
* Choosing a layout manager in a GUI (D): This involves technical considerations about how user interface elements are arranged and managed on the screen.
* The average number of methods per class (E): This is a technical metric used in object-oriented design to assess complexity and maintainability.
* More Domain-Related:
* Modelling a banking account (B): This involves understanding the business rules and operations of banking accounts, which is domain-specific knowledge.
* Legal constraints for the execution of a money transfer : These are domain-related as they pertain to the legal and regulatory requirements of financial transactions.
* Specification of a calculation formula (F): This is typically domain-related because it involves the business logic and rules for performing calculations within the domain.
These distinctions are important for architects to consider when making design decisions, ensuring that both technical and domain-related aspects are adequately addressed.
References:
* Rozanski, N., & Woods, E. (2011). Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives. Addison-Wesley Professional.
* Fowler, M. (2002). Patterns of Enterprise Application Architecture. Addison-Wesley.