SE513 Software Quality AssuranceSE513 Software Quality Assurance

Lecture10: Lecture10: Documentation and Quality Records Control Documentation and Quality Records Control

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

• Controlled documents and quality records • Definitions and objectives • Documentation control procedures

• The controlled documents list • Controlled document preparation • Issues of controlled document approval • Issues of controlled document storage and

retrieval

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

• Controlled document A document that is currently vital or may become vital for the development and maintenance of software systems as well as for the management of current and future relationships with the customer. Hence, its preparation, storage, retrieval and disposal are controlled by documentation procedures.

• Quality recordA quality record is a special type of controlled document. It is a customer-targeted document that may be required to demonstrate full compliance with customer requirements and effective operation of the software quality assurance system throughout the development and maintenance processes.

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

• * To assure the quality of the document.• * To assure its technical completeness and

compliance with document structure procedures and instructions

• * To assure the future availability of documents that may be required for software system maintenance, or responses to the customer’s future complaints.

• * To support investigation of software failure causes as part of corrective and other actions.

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

* Definition of the list of the document typesand updates to be controlled (some classified asquality records).

* Document preparation requirements. * Document approval requirements. * Document storage and retrieval requirements,

including controlled storage of document versions,revisions and disposal, document security.

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

Deciding which document type be categorized as a controlled document and which controlled document types be classified as quality record.

Deciding about the adequate level of control for each controlled document type.

Following up of compliance with the controlled document types list.

Analyzing follow-up findings and initiating the required updates, changes, removals and additions to the controlled documents types list.

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

• The components of project progress control• Progress control of internal projects and external

participants• Implementation of project progress control

regimes• Computerized tools for software progress control

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

· Control of risk management activities· Project schedule control· Project resource control· Project budget control

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

· Human resources · Development and testing facilities · Purchase of COTS software · Purchase of hardware · Payments to subcontractors.

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

* Lists of software risk items by category and their planned solution dates

* Lists of exceptions of software risk items – overrun solution dates

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

* Classified lists of delayed activities.* Classified lists of delays of critical activities – delays that can

affect the project’s completion date. * Updated activity schedules, according to progress reports

and correction measures. * Classified lists of delayed milestones.* Updated milestones schedules, according to progress reports

and applied correction measures.

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

* Project resources allocation plan - for activities and software modules - for teams and development units - for designated time periods, etc.

* Project resources utilization – as specified above* Project resources utilization exceptions – as specified above* Updated resource allocation plans generated according to

progress reports and reaction measures applied

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004

* Project budget plans- for activity and software module- for teams and development units- for designated time periods, etc.

* Project budget utilization reports — as specified above * Project budget utilization deviations – by period or

accumulated – as specified above* Updated budget plans generated according to progress

reports ports and correction measures

Galin, SQA from Theory to Implementation@Pearson Education Limited 2004