Transcription of Vol. 13, No. 1 …
{{id}} {{{paragraph}}}
2006 Vol. 13, No. 1 IMPLEMENTING PRODUCTAND process QUALITY ASSURANCEWith permission from a client of The process GroupOne of the process Areas (PA's) in the CMMI* is process andProduct Quality Assurance (PPQA). This process area supportsthe delivery of high-quality products and services by providingthe project staff and managers with appropriate visibility into, andfeedback on, processes and associated work products throughoutthe life of the this article we share an example process definition for PPQA from one of our clients. The company uses seven part-time Software Quality Assurance(SQA) staff, each person working eight hours per month onaverage performing audits. Each auditor is either a developer ortester as his or her primary job. To ensure objectivity, each personis assigned to a project other than the one they work on. All auditactivities are managed by the leader of the Engineering ProcessGroup (EPG), a part-time position of seven hours per month for apopulation of 80 software benefits of implementing a lightweight audit process are to: Maintain the gains made in process improvement over theprevious five years Detect process refinements needed to simplify process imple-mentation Share engineering and management practices across the devel-opment groupsProcess
IMPLEMENTING PRODUCT AND PROCESS QUALITYASSURANCE(Continued from page 1) 5.0 AUDIT REPORTING The completed checklist acts as the audit report. 5.1 Naming Conventions A standard naming convention for audit report files is
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}
CONTROL NUMBER AND FILE NAMING, CONTROL NUMBER AND FILE NAMING CONVENTIONS, DOCUMENT TYPES AND NAMING CONVENTIONS, NAMING CONVENTIONS, INTERIM ADVICE NOTE 184/16 conventions, File, Interim Advice Note 184/16, NonStop Pathway/iTS SCUP Reference Manual, Control, Number, Informatics, Informatics Practices