Correct Answer: A,B,C  🗳️

Explanation: Only visible for PassTorrent members. You can sign-up / login (it's free).

Correct Answer: B,C,D  🗳️

Explanation: Only visible for PassTorrent members. You can sign-up / login (it's free).

Correct Answer:

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.

Correct Answer: B,D  🗳️

Explanation: Only visible for PassTorrent members. You can sign-up / login (it's free).

Correct Answer:

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.