Model based

Analytical

Methodical

Heuristic

Underestimating the effort needed to maintain the test assets

Losing access to important testing information when needed

Relying too much on qualitative and quantitative assessments

Lowering the morale of the test team because of repetition

Operational

Customer

Contractual

Regulatory

System testing

Operational testing

Structural testing

Integration testing

Project Managers

Operators of the product

Developers

Technical Experts

Test Implementation and execution

Test Analysis and Design

Evaluating the Exit Criteria and reporting

Test Closure Activities

I, ii, iii are true and iv is false

I , iii, iv are true and ii is false

ii, iii are true and i and iv are false

I , ii are false and iii, iv are true

17

19

24

21

22, 23, 26

21, 39, 40

29, 30, 31

0, 15, 22

static testing includes desk checking

Static testing requires the running of tests through the code

static testing includes techniques such as reviews and inspections

static testing can give measurements such as cyclomatic complexity

Component Integration Testing

Component System Testing

Component Sub System Testing

Maintenance Testing

Provide support for statistical analysis

Store and manage bug reports

Enable the traceability between test ware and software work products and product variants

The analysis of structures and dependencies (e.g. linked web pages)

Development team

Testing team

Both

None of the Above

Consultative Approach

Regression Approach

Preventive Approach

Reactive Approach

Consultative Approach

Preventive Approach

Dynamic Approach

Model Based Approach

Live data

Change Control

Reports

Problem reporting

Customer risk

Project risk

Product risk

Organizational risk

Where to test more

Adverse effect occurring

Impact of an effect

Is the coverage done

Status of incident

Solution to the Incident

References to Incident

Expected and actual results

Actual results

Program specification

User requirements

System specification