Вы находитесь на странице: 1из 8

QUALITY ASSURANCE WORK THROUGHAND INSPECTIONS

QUALITY ASSURANCE
refers to the planned and systematic activities implemented in a quality system so that quality requirements for a product or service will be fulfilled. Two principles included in QA are: "Fit for purpose", the product should be suitable for the intended purpose; and "Right first time", mistakes should be eliminated. Part of Quality Assurance Program: 1. 2. 3. 4. Design Development Production Distribution 5. Installation 6. Servicing 7. Documentation

QA includes management of the quality of raw materials, assemblies, products and components, services related to production, and management, production and inspection processes. Suitable Quality is determined by product users, clients or customers, not by society in general. It is not related to cost and adjectives or descriptors such "High" and "Poor" are not applicable. For example, a low priced product may be viewed as having high quality because it is disposable where another may be viewed as having poor quality because it is disposable.

What is a walkthrough?

A walkthrough is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required. The Purpose of walkthrough is to: Find problems Discuss alternative solutions Focusing on demonstrating how requirements.

work product meets all

IEEE 1028 recommends three specialist roles in a walkthrough:

Leader: who conducts the walkthrough, handles administrative tasks, and ensures orderly conduct (and who is often the Author) Recorder: who notes all anomalies (potential defects), decisions, and action items identified during the walkthrough meeting, normally generate minutes of meeting at the end of walkthrough session. Author: who presents the software product in step-by-step manner at the walk-through meeting, and is probably responsible for completing most action items.

Walkthrough Process Author describes the artefact to be reviewed to reviewers during the meeting. Reviewers present comments, possible defects, and improvement suggestions to the author. Recorder records all defect, suggestion during walkthrough meeting. Based on reviewer comments, author performs any necessary rework of the work product if required. Recorder prepares minutes of meeting and sends the relevant stakeholders and leader is normally to monitor overall walkthrough meeting activities as per the defined company process or responsibilities for conducting the reviews, generally performs monitoring activities, commitment against action items etc.

What is an inspection?

An inspection is more formalized than a walkthrough. The subject of the inspection is typically a document such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, not to fix anything. Attendees should prepare for this type of meeting by reading thru the document; most problems will be found during this preparation. The result of the inspection meeting should be a written report. Thorough preparation for inspections is difficult, painstaking work, but is one of the most cost effective methods of ensuring quality. of the

The objectives inspection process are to

Find problems at the earliest possible point in the software development process Verify that the work product meets its requirement Ensure that work product has been presented according to predefined standards Provide data on product quality and process effectiveness Inspection advantages are to build technical knowledge and skill among team members by reviewing the output of other people Increase the effectiveness of software testing.

IEEE 1028 recommends following roles in an Inspection:

Inspector Leader: The inspection leader shall be responsible for administrative tasks pertaining to the inspection, shall be responsible for planning and preparation, shall ensure that the inspection is conducted in an orderly manner and meets its objectives, should be responsible for collecting inspection data. Recorder: The recorder should record inspection data required for process analysis. Reader: The reader shall lead the inspection team through the software product in a comprehensive and logical fashion, interpreting sections of the work product and highlighting important aspects. Author: The author shall be responsible for the software product meeting its inspection entry criteria, for contributing to the inspection based on special understanding of the software product, and for performing any rework required to make the software product meet its inspection exit criteria. Inspector: Inspectors shall identify and describe anomalies in the software product.

Inspection Process:

Following are review phases

Planning: Inspection Leader perform following task in planning phase. Determine which work products need to be inspected. Determine if a work product that needs to be inspected is ready to be inspected. Identify the inspection tea. Determine if an overview meeting is needed. Overview: Purpose of the overview meeting is to educate inspectors; meeting is lead by Inspector lead and is presented by author, overview is presented for the inspection, this meeting normally acts as optional meeting, purpose to sync the entire participant and the area to be inspected. Preparation: Objective of the preparation phase is to prepare for the inspection meeting by critically reviewing the review materials and the work product, participant drill down on the document distributed by the lead inspector and identify the defect before the meeting. Examination meeting: The objective of the inspection meeting is to identify final defect list in the work product being inspected, based on the initial list of defects prepared by the inspectors [identified at preparation phase and the new one found during the inspection meeting. Rework and Follow-up: Objective is to ensure that corrective action has been taken to correct problems found during an inspection.