No priority or severity assigned

Incident numbering is manual rather than automated

No mentioning of reproduceability

No classification on type of incident

To verify the success of corrective actions.

To prevent a task from being incorrectly considered completed.

To ensure that defects have not been introduced by a modification.

To motivate better unit testing by the programmers.

To adapt the models to the context of project and product characteristics.

To choose the waterfall model because it is the first and best proven model.

To start with the V-model and then move to either iterative or incremental models.

To only change the organization to fit the model and not vice versa.

A requirements review meeting

A business analyst eliciting requirements

Performing acceptance tests against requirements

A test report showing requirements coverage

They ensure a common understanding of the product.

They find defects early.

They enhance project communication.

They can be performed without exercising the code.

All supported credit cards

Language localization

Valid and invalid advances

Usability

Response time

Align technical concepts during the design phase

Establish a common understanding of requirements

Provide independent evaluation of compliance to processes, regulations, standards etc.

To monitor progress, assess the status of a project, and make decisions about future actions

(i) and (ii)

(i) and (iv)

(ii) and (iii)

(ii) and (iv)

In the delivered application, one of the countries, as specified in the requirements, has not been correctly implemented.

The application takes too long to process a request for additional cover.

The test cases do not cover the key requirements.

The successful bidder may not deliver all the required functionality on time.

It will extend the development team’s abilities and enhance future delivery capabilities.

It will allow the marketing, clerical and testing staff to validate and verify the early screen prototypes.

Time-box constraints will guarantee code releases are delivered on schedule.

More time can be spent on test execution as less formal documentation is required.

Create an estimate based on the function point analysis technique and test point analysis

Create an estimate based on the complexity of the code

Create an estimate based on the credentials of the successful bidder

Create an estimate based on a percentage of the development effort

Test planning, test case preparation and test execution for each of the four iterations

Work should be explicitly allocated to test completion, test management, installation and to training on using the system

Activities to deploy the system in the user environment

Regression testing in the second, third and fourth iterations

Development activities for unit and integration testing

Reviews on requirements documentation

Defining test environment requirements for system testing

The quality of the development estimate may be poor.

In general bottom-up estimation is always better than top-down estimation.

The percentage based technique only applies to the V life cycle model.

Using the same percentage every time does not address the level of risk of the application to be tested.

The maturity of the organization, e.g. the quality of the test basis, quality of development testing, configuration management, availability of test tools, also influence the effort needed for testing.

It builds on large set of historical data

The result is almost always a too low estimate for the required test effort

Test planning

Test execution

Test management

Test design

The skills and experience of developers to correct the failures.

The standards used for the requirements specification.

The metrics recorded from testing the capture-replay tool.

The number of testers in the company and their grade.

Analysis and design of tests begins as soon as development is completed.

Some, but not all, development activities have corresponding test activities.

Each test level has test objectives specific to that level.

All document reviews involve the development team.

Acceptance testing to verify the business process

Acceptance testing to verify operational requirements

Requirements testing as part of testing regulatory compliance

Another system test cycle to verify defect resolution

Criteria A = OK, criteria B = OK, criteria C = OK

Criteria A = NOT OK, criteria B = NOT OK, criteria C = OK

Criteria A = OK, criteria B = NOT OK, criteria C = NOT OK

Criteria A = NOT OK, criteria B = NOT OK, criteria C = NOT OK

700

720

784

570

5 maturity levels

Focussed on higher level testing

20 key areas

Highly related to CMMI

Continuous model

Staged model

Focussed on component and integration testing

Integration with other tools

Learning time required to use the new tool

Tool portability

Evaluation of suitable tools

Has there been sufficient comparison of tools?

What are the problems we are trying to address?

Do we have a set of tool requirements to validate the tool against?

How will the implementation be organized?

Which project will be selected to perform the tool pilot?

Is customized training available?

How will the change process be managed?

The entry and exit criteria for each test phase

Test training needs for the project resources

The test design techniques to be used

Test performance indicators

The test schedule

Component testing: decision testing; System testing: exploratory testing

Component testing: decision testing; System testing: decision table testing

Component testing: statement testing; System testing: equivalence partitioning

Component testing: statement testing; System testing: decision table partitioning

Easier to quickly adapt testing to changing requirements compared to experienced-based testing

Targets certain types of faults

Will guide experienced testers to find defects

Provides a way to differentiate depth of testing based on product risks by using different techniques

More enhanced documentation and therefore higher repeatability and reproducibility

Will make non-systematic testing redundant

Will reduce the need for early reviews

A person with the ability to complete tasks

A quality assurance officer

A person with in-depth technical skills

A person who brings new ideas to the team

i, ii, iv, vi

ii, i, v, vi

ii, v, i, iii

i, iv, v, vi