A) True B) True C) True D) True E) True F) True G) 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 simultaneously 1 .

B) Support of UML 2.x and SysML ensures that the tool can handle widely-used modeling languages for software and systems engineering 1 .

C) Document generation is a key feature that allows for the automatic creation of documentation from the model 1 .

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 code 1 .

E) Support of code generation can significantly speed up the development process by generating code from the models 1 .

F) Compliance with standards ensures that the tool adheres to industry standards, which can be crucial for interoperability and future-proofing 1 .

G) Purchase and licensing costs are practical considerations that affect the total cost of ownership of the tool 1 .

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 tool 1 .

A) Beneficial B) Beneficial C) Not Beneficial D) Not Beneficial E) 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 documentation 1 .

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 documentation 1 .

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 documentation 1 .

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 code 1 .

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-date 1 .

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 architecture 1 .