reviews checklists

12
SOFTWARE QUALITY ASSURANCE REVIEWS & CHECKLISTS Seminar: Oana FEIDI Quality Manager – Continental Automotive

Upload: oana-feidi

Post on 16-Nov-2014

2.394 views

Category:

Documents


0 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Reviews Checklists

SOFTWARE QUALITY ASSURANCEREVIEWS & CHECKLISTS

Seminar: Oana FEIDIQuality Manager – Continental Automotive

Page 2: Reviews Checklists

Prerequisites

rework cost in average is responsible for ~40% of the total software development cost

engineers spend up to 1/3 of their compiling & testing, relying on these activities to detect defects

reviews – an inexpensive& effective approach for reducing rework NASA – by introducing software reviews

activities in its projects 29% of total improvement in its process 10% in the reliability on its products

Page 3: Reviews Checklists

Software Quality activities

software reviews – objective: finding analysis and design defects in SW artifacts produced in the initial phases of SW development

testing patterns & formal procedures change control SW metrics – used to trace SW QA and to

evaluate the impact of various methodologies and procedures

Documented & stored records

Page 4: Reviews Checklists

Review

A software review is "A process or meeting during

which a software product is [examined by] project personnel, managers, users, customers, user representatives, or other interested parties for comment or approval” [IEEE 1028:1997 – “IEEE Standard for software reviews”]

The earlier errors are found, the lower the costs of correcting

the errors and the higher the probability of

correcting the errors correctly

Categories Walkthrough Code Inspection

Source: http://cronos.cos.ufrj.br/publicacoes/reltec/es55601.pdf

Page 5: Reviews Checklists

Reviews targets

to have a more comprehensible project, that facilitates comprehension by other developers, by describing in a condensed way what is described in the code

saving implementation time, by removing problems with faulty logic and missing functionality before implementation

improving the efficiency of the reviews, since fewer artifacts need to be reviewed together and defects are removed incrementally, rather than at one time

Page 6: Reviews Checklists

Code Inspections

A set of procedures and error-detection techniques Concentrates on discovering errors, not correcting them

Objective: to find errors in the program, thus improving the quality of work

Benefits The programmer receives feedback concerning

programming style, choice of algorithms and programming techniques

The other members of the team: share experience

Optimal amount of time: 90-120 min Rate: average 150 program statements/hour Comments should be directed toward the program,

rather than the programmer

Page 7: Reviews Checklists

The team

An inspection team usually consists of four people Moderator Programmer Test specialist Program’s designer

Moderator Distributes materials and schedules the inspection

session Leads the session

ensures that the discussions proceed along productive lines ensures that the participants focus their attention on finding

errors, not correcting them Records all errors found Ensures that the errors are subsequently corrected

Page 8: Reviews Checklists

Walkthroughs

“ a designer or programmer leads members of the development team and other interested parties through a software product, and the participants ask questions and make comments about possible errors, violation of development standards, and other problems" [IEEE 1028:1997 – “IEEE Standard for software reviews”]

Objectives to gain feedback about the technical quality or content of the document to familiarize the audience with the content

IEEE 1028 recommends three specialist roles in a walkthrough: 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 leader, who conducts the walkthrough, handles administrative tasks, and ensures orderly conduct (and who is often the Author); and

The recorder, who notes all potential defects, decisions, and action items identified during the walkthrough meeting.

Page 9: Reviews Checklists

Review flow

Planning: - verify materials meet entry criteria - schedule meeting - distribute documents

Meeting: - materials presented by authors / materials reviewed as a group - defects recorded - metrics collected (if necessary)

Rework: - author fixes defects alone

DONE

Additional defects found - inspection repeats

Page 10: Reviews Checklists

Review template structure

Location of error chapter, function, …

Severity major, minor

Type error or remark algorithm,

documentation, data usage

Time spent per review

Review template

Metrics:• effort per review• findings per review• number of lines reviewed

Page 11: Reviews Checklists

Checklist

An important part of the inspection is the use of checklist to examine the program for common errors

As general as possible Based on lessons learned

Examples “Are comments accurate and meaningful?” “Are all variables declared?”

Java: http://www.processimpact.com/reviews_book/java_checklist.doc

Requirements:

http://www.processimpact.com/reviews_book/requirements_review_checklist.doc

Page 12: Reviews Checklists

THANK YOU!