A process to produce zero defects

A defect identification strategy

Another way of expressing statistical process control

A strategy built around control charts

A management philosophy

helps an organization to decide how the Quality function is deployed

is testing of previously verified program of application

is another approach to implementing balance score card method

is a systematic method to translate customer wants or needs into product or service

Frequency * Occurrence

Occurrence * Risk Factor

Risk Factor * Risk Response Number

Probability * Influence

Defect Prevention

Defect discovery/defect naming

Defect resolution

All of the above

None

An attribute to be possessed by the product/function to be performed by the product

The performance standard for the attribute or a function

The measuring process to be used in verifying that the standard has been met

All the above

None

All the below

a way of empowering people in the organization

the analysis performed by executing the program code

a powerful way of expressing yourself to make your presence felt

All of the following

Activities involved

Users/Customer served

Deficiencies noted

Procedure used to perform work

Eliminating risks

Avoiding risks

Risk analysis

Developing strategies to address risk

It can help identify error-prone parts of the process

It cannot be applied; there is no normal variation in software

It cannot be used to identify similar types of failures

It cannot be applied; software failure expose the root cause directly

Meeting requirements

Customer satisfaction

Zero defects

All of the above

Option 1 and option 2

Prevent defect from occurring

Assign quality responsibilities

Conducting testing

Find and correct defects

Writing work processes

Total Quality Management

Problem Analysis

Regression Testing

Continuous Process Improvement

Tracing requirements

Developers are not as careful as testers

Developers are generally not willing to put in the effort required to find faults in their

No-one can adequately test their own work

An independent person may find faults more quickly.

We cannot run the test

It may be difficult to repeat the test

It may be difficult to determine if the test has passed or failed

We cannot automate the user inputs

2 is a valid reason; 1,3,4 & 5 are not

1,2,3,4 are valid reasons; 5 is not

1,2,3 are valid reasons; 4 & 5 are not

All of them are valid reasons for failure

Execution

Design

Planning

Check Exit criteria completion

Preventive

Appraisal

Failure

Corrective

Is unlikely to be completed on schedule

Is likely to be fault-free

Is unlikely to cause a failure

Is likely to be liked by the users

Monitoring progress of tests runs

Identifying test activities

Planning for rework and retest cycle

Estimating total effort to report faults

Report on deviations form the project plan

Sign the system off for the release

Raise incidents on faults that they have found

Provide information for risk analysis and quality improvement