ISQI ISAQB Certified Professional for Software Architecture - Foundation Level - CPSA-FL Exam Practice Test

Explanation:
The performance of a system often competes with its:
* Flexibility (A) - True1
* Memory usage (B) - True1
* On-time completion of the project C - False
* Adaptability (D) - True1
* Usability (E) - True1
* Security (F) - True1
* Testability (G) - True
In system design, performance trade-offs are a critical consideration. Here's an explanation of how each listed aspect competes with system performance:
* Flexibility (A): Systems designed for high performance may be less flexible because they are optimized for specific tasks or conditions1.
* Memory Usage (B): High-performance systems may require more memory to store data and instructions for rapid access, which can be at odds with limited memory resources1.
* On-time Completion of the Project : While performance considerations can impact project timelines, they do not inherently compete with the on-time completion of a project.
* Adaptability (D): Systems that need to perform well under varying conditions may sacrifice adaptability, as they are tightly coupled with their performance optimizations1.
* Usability (E): Sometimes, the pursuit of performance can lead to complex user interfaces or workflows, affecting usability negatively1.
* Security (F): Security measures can introduce additional processing and checks, potentially slowing down system performance1.
* Testability (G): High-performance systems may be harder to test due to their complexity and the need for specialized testing environments or tools1.
These trade-offs highlight the importance of balancing different system attributes to meet the overall goals and constraints of a project.
References:
* CodingDrills article on Trade-Offs in System Design1

Explanation:
A) FalseB) FalseC) TrueD) TrueE) TrueF) True
A) Agile approaches make written documentation unnecessary. In such cases, verbal communication can substitute for documentation.
* False. Even in agile approaches, written documentation is important for maintaining a clear and
* consistent understanding of the architecture among team members and stakeholders1.
B) Written documentation makes verbal reiteration unnecessary.
* False. Verbal communication is essential for clarifying and reinforcing the content of written documentation, especially when addressing complex or nuanced architectural issues2.
C) Despite written documentation, verbal communication of architectural interrelationships is important.
* True. Verbal communication plays a crucial role in explaining the rationale behind architectural decisions and interrelationships that may not be fully captured in documentation2.
D) Documentation and communication should use identical terms and rationale.
* True. Consistency in terminology and rationale between documentation and verbal communication helps prevent misunderstandings and ensures that all parties have a common understanding of the architecture2.
E) Documentation should be created primarily for project participants who either cannot or do not want to read the system's source code.
* True. Documentation serves as a guide for those who may not be directly involved in coding but need to understand the architecture, such as managers, new team members, or external stakeholders2.
F) Communication and documentation complement each other: verbal communication helps architects determine what must be recorded in writing.
* True. Verbal communication often reveals what aspects of the architecture are most important or confusing to team members, guiding what should be emphasized in written documentation

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

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) TrueB) TrueC) FalseD) TrueE) TrueF) True
A) Top-down and bottom-up design may be employed in the same project.
* Top-down and bottom-up are two approaches to the design of software architecture. In top-down, the high-level design is created first, focusing on general functionalities and structure. In contrast, bottom-up starts with detailed designs focusing on a component or module level.