1
Q
5.5.2. (K2) Distinguish between project and product risks____PRODUCT risks
A
- Software might not perform its intended functions according to the specification
- Software might not perform its intended functions according to user, customer, and/or stakeholder needs
- A system architecture may not adequately support some non-functional requirement(s)
- A particular computation may be performed incorrectly in some circumstances
- A loop control structure may be coded incorrectly
- Response-times may be inadequate for a high-performance transaction processing system
- User experience (UX) feedback might not meet product expectations
1
Q
5.5.1. (K1) Define risk level by using likelihood and impact
A
Risk involves the possibility of an event in the future which has negative consequences. The level of risk is determined by the likelihood of the event and the impact (the harm) from that event.
2
Q
5.5.2. (K2) Distinguish between project and product risks____PROJECT risks
A
- Project issues:
- Organizational issues:
- Political issues:
- Technical issues:
- Supplier issues:
3
Q
5.5.3. (K2) Describe, by using examples, how product risk analysis may influence the thoroughness and scope of testing
A
- Determine the test techniques to be employed
- Determine the particular levels and types of testing to be performed (e.g., security testing, accessibility testing)
- Determine the extent of testing to be carried out
- Prioritize testing in an attempt to find the critical defects as early as possible
- Determine whether any activities in addition to testing could be employed to reduce risk (e.g., providing training to inexperienced designers)
4
Q
risk management activities provide a disciplined approach to:
A
- Analyze (and re-evaluate on a regular basis) what can go wrong (risks)
- Determine which risks are important to deal with
- Implement actions to mitigate those risks
- Make contingency plans to deal with the risks should they become actual events
