codecamp iasi 10 march 2012 - qa-plan-key-to-a-project-succes

16

Upload: codecampiasi

Post on 23-Dec-2014

1.036 views

Category:

Technology


2 download

DESCRIPTION

 

TRANSCRIPT

Page 1: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes
Page 2: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

QA Plan – key to a project successOana FeidiContinental Automotive

10.03.2012

Page 3: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

What is SQA?

Quality has much in common with …

Philip Crosby

Page 4: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

So … what is SQA?

ReviewsTestingPatterns and formal proceduresChange controlSoftware metricsDocumentationAssessments

Page 5: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

Now … really … what is SQA?SQA processes provide assurance that the software products and processes

in the project life cycle conform to their specified requirements

by planning, enacting, and performing a set of activities to provide adequate confidence

that quality is being built into

the software.

Page 6: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

A defect caught by testing costs

14.5

times as much to correct as did one found by formal inspection,

while a defect discovered by customer costs

68

times as much to fix.

Page 7: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

ReviewsWHAT

Documents, releases/sprintsWHEN

Correlate with the release content Include the reviews in the project planning

HOW Choose the correct review method Use automatic tools (static code analysis) Use checklists (“hunt for anticipated types of

errors”)WHO

Nominate reviewers based on experience and role

Page 8: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

"Walking on water and developing software from a specification are easy if both are frozen.” (Edward V Berard)

Page 9: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

TestingWHAT

Establish what you test against Module/integration/validation testing Define coverage targets

WHEN Correlate the need with the release content Start early enough

HOW Choose the correct testing methods to derive the

tests Traceability towards requirements workflow Quality, NOT QUANTITY

WHO Nominate which person tests what

Page 10: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

Patterns and formal procedures

pattern and procedures imposed by the client or rules that direct how the project must be developed

Page 11: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

Change controlFormalize the order of changes by evaluating the nature of the change and controlling its impact

Input for root cause analysis & improvements (criteria)

Page 12: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

Software metrics

“You can’t control what you can’t measure” (Tom DeMarco)

Page 13: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

Documentation

quality of the documentdocument’s technical completeness future availability of documents (maintenance, further development of the software system or customer’s complaints)

support investigation of software failure causes and develop corrective/improvement actions.

Page 14: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

Assessment

Assessment : process improvement (project specific or organisation

wide process), by evaluating how a project/organisation performs against an approved process reference model

process conformance, by checking how a project performs against the process it has to follow

Page 15: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

What about QA Plan?

Documentation for project’s specific → QA Plan

Page 16: CodeCamp Iasi 10 march 2012 - QA-Plan-key-to-a-project-succes

Please fill in the evaluation forms!

Thank you!