Architecture Fundamentals and Roles Flashcards

According to iSAQB CPSA-F, which of the following is a key characteristic of a 'good' software architecture?

Answer: It achieves required quality attributes while meeting functional requirements

A good architecture fulfills functional requirements while achieving the required quality attributes such as performance, security, and maintainability appropriate to the system's context.

A software architect must balance multiple conflicting quality goals. Which approach best represents the architect's role in this situation?

Answer: Negotiate trade-offs with stakeholders based on business priorities

Architects facilitate stakeholder discussions to prioritize and trade off competing quality attributes based on real business needs and constraints.

What is the role of 'fitness functions' in evolutionary architecture?

Answer: Automated checks that verify the architecture meets defined quality and structural criteria

Fitness functions are automated mechanisms (tests, metrics, monitors) that continuously verify that the architecture conforms to defined quality and structural properties.

Which of the following best describes 'technical debt' from an architectural perspective?

Answer: The future rework cost incurred by choosing an expedient solution over a better approach

Technical debt is the implied future cost of rework resulting from choosing a faster or easier solution now instead of a better long-term approach.

In the context of CPSA, what does 'architecture communication' primarily involve?

Answer: Conveying architectural decisions, rationale, and structures to relevant stakeholders appropriately

Architecture communication means conveying architectural structures, decisions, and their rationale to different stakeholder groups using appropriate notations and levels of detail.

Which scenario best illustrates a violation of the 'stable dependencies' principle?

Answer: A frequently changing UI module that is depended upon by a stable core domain module

Stable dependencies requires that stable (less frequently changed) modules should not depend on volatile (frequently changed) modules; a stable domain depending on a volatile UI violates this.

What is the significance of the 'view' concept in software architecture documentation?

Answer: A view represents the system from a particular stakeholder perspective, addressing specific concerns

An architectural view presents the system from the perspective of a specific set of concerns relevant to particular stakeholders, such as runtime behavior, deployment, or module structure.