CPSA-FL試験無料問題集「ISQI ISAQB Certified Professional for Software Architecture - Foundation Level 認定」

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

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

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

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.