Chapter 5: risks and testing Flashcards

1
Q

What is a product risk?

A

Product risk involves the possibility that a work product (e.g., a specification, component, system, or test) may fail to satisfy the legitimate needs of its users and/or stakeholders

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is the level of risk?

A

The level of risk is that likelihood and impact of the event

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is a risk?

A

Risk involves the possibility of an event in the future which has negative consequences

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

When do quality risks arise?

A

When the project risks are associated with specific quality characteristics of a product (e.g., functional suitability, reliability, performance efficiency, usability, security, compatibility, maintainability, and portability), product risks are also called quality risks

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Give examples of 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What kind of project risk issue is this?
Delays may occur in delivery, task completion, or satisfaction of exit criteria or definition
of done

A

Project risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What kind of project risk issue is this?
Inaccurate estimates, reallocation of funds to higher priority projects, or general costcutting across the organization may result in inadequate funding

A

Project risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What kind of project risk issue is this?
Late changes may result in substantial re-work

A

Project risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What kind of project risk issue is this?
Skills, training, and staff may not be sufficient

A

Organisational risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What kind of project risk issue is this?
Personnel issues may cause conflict and problems

A

Organisational risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What kind of project risk issue is this?
Users, business staff, or subject matter experts may not be available due to conflicting
business priorities

A

Political risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What kind of project risk issue is this?
Testers may not communicate their needs and/or the test results adequately

A

Political risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What kind of project risk issue is this?
Developers and/or testers may fail to follow up on information found in testing and
reviews (e.g., not improving development and testing practices)

A

Political risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What kind of project risk issue is this?
There may be an improper attitude toward, or expectations of, testing (e.g., not
appreciating the value of finding defects during testing)

A

Political risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What kind of project risk issue is this?
Requirements may not be defined well enough

A

Technical issue

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What kind of project risk issue is this?
The requirements may not be met, given existing constraints

A

Technical issue

17
Q

What kind of project risk issue is this?
The test environment may not be ready on time

A

Technical issue

18
Q

What kind of project risk issue is this?
Data conversion, migration planning, and their tool support may be late

A

Technical issue

19
Q

What kind of project risk issue is this?
Weaknesses in the development process may impact the consistency or quality of project
work products such as design, code, configuration, test data, and test cases

A

Technical issue

20
Q

What kind of project risk issue is this?
Poor defect management and similar problems may result in accumulated defects and
other technical debt

A

Technical issue

21
Q

What kind of project risk issue is this?
A third party may fail to deliver a necessary product or service, or go bankrupt

A

Supplier issue

22
Q

What kind of project risk issue is this?
Contractual issues may cause problems to the project

A

Supplier issue

23
Q

Who is responsible for project risks?

A

Project risks may affect both development activities and test activities. In some cases, project managers
are responsible for handling all project risks, but it is not unusual for test managers to have responsibility
for test-related project risks

24
Q

What might project risks effect?

A

Project risks may affect both development activities and test activities

25
Q

How is risk used in testing?

A
  • To find where to focus effort durring testing
  • where and when to start testing
  • find the areas that need more attention
26
Q

Explain a risk based approach to testing

A
  • proactive opportunities to reduce the levels of product risk
  • It involves product risk analysis, which includes the identification of product risks and the assessment of each risk’s likelihood and impact.
    -The resulting product risk information is used to guide test planning, the specification, preparation and execution of test cases, and test monitoring and control.
    -Analysing product risks early contributes to the success of a project.
  • In addition, testing may identify new risks, help to determine what risks should be mitigated, and lower uncertainty about risks.
    Summary:
    find product risks, their likelihood & impact -> let this guide you in planning, executing and testing monitoring & control -> contribute to success

In addition, testing may identify new risks, help to determine what risks should be mitigated, and lower uncertainty about risks.

27
Q

What are the advantages of testing when it comes to risk?

A
  • A risk based approach to testing means risks can be analysed early which contributes to success
  • testing may identify new risks, help to determine what risks should be mitigated, and lower uncertainty about risks.
  • Testing is used to reduce the probability of an adverse even occurring or reducing it’s impact
  • It is a risk mitigation activity, to provide information about identified risks, as well as providing information on residual (unresolved) risks
28
Q

In risk based testing, what are the results of product risk analysis?

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)
29
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