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

Explanation:
A) Not AppropriateB) AppropriateC) Not Appropriate
For a project involving multiple architects and developers, achieving consistent and adequate documentation is crucial. Here's how the methods listed would fare:
A) The chief architect creates the documentation: This method is not appropriate because it places the entire burden of documentation on a single individual, which can lead to bottlenecks and may not accurately reflect the contributions and insights of the entire team1.
B) Identical templates are used for the documentation: This is an appropriate method as it ensures consistency across the documentation produced by different team members. Using identical templates helps maintain a uniform structure and style, which is beneficial for readability and maintenance1.
C) All parts of the architecture documentation are automatically extracted from the source code: Relying solely on automatic extraction is not appropriate because it may not capture all the necessary details and decisions made during the architectural design process. Manual documentation is also important to provide context and rationale that cannot be automatically generated1.
These methods are in line with the iSAQB SOFTWARE ARCHITECTURE - FOUNDATION LEVEL, which emphasizes the importance of clear, consistent, and comprehensive documentation practices1.

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

Explanation:
A) TrueB) FalseC) TrueD) True
A) The project plan from management is influenced by architectural decisions.
* True. Architectural decisions often have significant implications on the project plan, including timelines, resource allocation, and technical approaches1.
B) Cost estimates are primarily the responsibility of the architect.
* False. While architects may contribute to cost estimates, especially regarding design-related expenses, it is typically the management's responsibility to oversee and finalize cost estimates for the entire project2.
C) Architects advise project management on the definition of work packages.
* True. Architects play a crucial role in defining work packages, particularly in ensuring that the technical aspects of the project are accurately captured and planned for1.
D) Management and architects cooperate on handling of technical risks.
* True. Both management and architects need to work closely to identify, assess, and manage technical risks throughout the project2.

Explanation:
For a building block, the characteristics visible only in the whitebox view are:
* Code structure of the building block (D)
* Algorithms used in the building block (E)
* Implementation details for the security requirements of the building blocks (G) The blackbox view suffices for:
* Public interfaces of the building block (A)
* Test coverage based on unit tests for sub building blocks contained in the building block (B)
* Test coverage based on integration tests
* Security requirements of the building blocks (F)
In software architecture, the whitebox view reveals the internal workings of a building block, including its code structure, algorithms, and specific implementation details1. This view is essential when the internal structure and behavior of the component need to be understood or modified.
On the other hand, the blackbox view treats the building block as an opaque entity, focusing on its exposed interfaces and observable behaviors without revealing its internal structure2. This view is sufficient for understanding what the building block does from an external perspective, such as its public interfaces and how well it performs its functions as determined by testing.
Here's a breakdown of the characteristics:
* Whitebox View:
* Code Structure (D): This includes the organization of code within the building block, such as classes, interfaces, and other components.
* Algorithms (E): The specific algorithms used within the building block to perform its functions.
* Implementation Details for Security (G): The actual code and strategies used to fulfill the security requirements.
* Blackbox View:
* Public Interfaces (A): The interfaces that are exposed to other building blocks or systems.
* Test Coverage for Sub Building Blocks (B): The extent to which the unit tests cover the sub-components within the building block.
* Test Coverage for Integration Tests : The coverage of tests that verify the interactions between building blocks.
* Security Requirements (F): The security objectives and criteria that the building block must meet.
References:
* arc42 Documentation on Building Block View1.
* Stack Overflow discussion on the difference between black box and white box in component diagrams2.
* Flylib Section on Black-Box and White-Box Component Views3.