Quality Attributes and Scenarios Flashcards
7 cards from real CPSA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Quality Attributes and Scenarios flashcards as text
In iSAQB, which component of a quality scenario describes what triggers the quality-relevant event?
Answer: Stimulus source
The stimulus source identifies the actor or entity that initiates the stimulus in a quality scenario.
A system must handle 500 concurrent users with response time under 2 seconds at peak load. Which quality attribute does this PRIMARILY address?
Answer: Performance efficiency
Performance efficiency covers response time and resource usage under specified load conditions.
Which quality attribute is MOST concerned with how easily a system can be moved from one environment to another?
Answer: Portability
Portability (ISO 25010) addresses the ease of transferring a system to different hardware, software, or operational environments.
When two quality attributes conflict, what is the RECOMMENDED approach for an architect?
Answer: Make the conflict explicit and let stakeholders decide based on business priorities
Architects must surface trade-offs transparently so stakeholders can make informed prioritization decisions.
The 'response measure' part of a quality scenario defines:
Answer: The quantifiable criterion used to evaluate whether the system met the quality goal
The response measure provides a testable, quantitative or qualitative criterion for assessing the system's quality response.
Which quality attribute is PRIMARILY concerned with the ability of a system to prevent unauthorized access to data?
Answer: Security — confidentiality sub-characteristic
Confidentiality, a sub-characteristic of Security in ISO 25010, ensures data is accessible only to those authorized.
In a quality scenario for 'modifiability', a realistic stimulus would be:
Answer: A developer needs to add a new payment method to the checkout module
Modifiability scenarios are triggered by change requests, typically from developers, to alter system functionality.