Quality AssuranceQuality Assurance

Copyright, 2002 © Jerzy R. Nawrocki

Jerzy.Nawrocki@put.poznan.pl

www.cs.put.poznan.pl/jnawrocki/mse/quality/

Quality ManagementQuality Management

Auxiliary materialAuxiliary material

Quality ManagementQuality Management

Auxiliary materialAuxiliary material

J. Nawrocki, Quality Assurance

IntroductionIntroductionIntroductionIntroduction

CMMCMM

• Requirements management• Software project planning• Software project tracking and

oversight• Software subcontract

management• Software quality assurance• Software configuration

management

CMM Level 2 - Repeatable

J. Nawrocki, Quality Assurance

AbilitiesAbilitiesAbilitiesAbilities

Ab1. A group that is responsible for co-ordinating and implementing SQA for the project (i.e. the SQA group) exists.

SQA at PUT:

Two 5-year students per project.

J. Nawrocki, Quality Assurance

AbilitiesAbilitiesAbilitiesAbilities

Ab2. Adequate resources and funding are provided.

Is it enough?

J. Nawrocki, Quality Assurance

AbilitiesAbilitiesAbilitiesAbilities

Ab3. Members of the SQA group are trained to perform their SQA activities.

Ab4. Members of the software project receive orientation on

• the role,

• responsibilities,

• authority, and

• value

of the SQA group.

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac1. A SQA plan is prepared for each project according to a documented procedure.

I’m afraid, I needa documented

procedure!

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

• The SQA plan can be baselined, i.e. it can be placed under SCM.

• The SQA plan is reviewed by all the team members including Project Managers (4th year), and Developers (3rd year).

SQA Planning Procedure (I)

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

• The SQA plan is approved by the Project Area Manager (Bartek or Adam).

• The SQA plan is available through the project’s web page along with all the previous versions of it. That web page is referenced in the Initial Project Description (IPD).

SQA Planning Procedure (II)

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac2. A documented and approved SQA plan is used as the basis for performing the SQA activities

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Responsibilities and authority of the SQA groupResource requirements for the SQA groupThe SQA group’s participation in planningEvaluations, audits and reviews to be performed by

the SQA groupReview and audit proceduresDocumenting and tracking non-compliance issuesSQA documentation and reportsSchedule of the SQA activities

SQA Plan Items

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac3. The SQA group participates in the preparation and review of the project’s

• software development plan,

• standards, and • procedures.

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac4. The SQA group reviews the software engineering activities to verify compliance.

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac4. The SQA group reviews the software engineering activities to verify compliance.

• The activities are evaluated against the SDP, and the designated standards and procedures.

• Deviations are identified, documented and tracked to closure.

• Corrections are verified.

J. Nawrocki, Quality Assurance

if (a < b) a+= b;

ActivitiesActivitiesActivitiesActivities

Ac5. The SQA group audits designated software work products to verify compliance.

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac5. The SQA group audits designated software work products to verify compliance.

• The products are evaluated against the chosen standards and contractual requirements.

• Deviations are identified, documented and tracked to closure.

• Corrections are verified.

• The deliverable products are evaluated before they are delivered to the customer.

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac6. The SQA group periodically reports the results of its activities to the software engineering group.

It’s getting better!

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac6. The SQA group periodically reports the results of its activities to the software engineering group.

every 2 weeks

Reports at PUT

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac7. Deviations identified in the activities and work products are documented and handled according to a documented procedure.

Err

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac7. Deviations identified in the activities and work products are documented and handled according to a documented procedure.

• Deviations from the SDP, designated standards, and procedures are documented and resolved with the project managers or the project area manager (BW or AW).

• Deviations not resolvable with the project area manager are presented to the SDS supervisor (JN).

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac7. Deviations identified in the activities and work products are documented and handled according to a documented procedure.

• Non-compliance items presented to the SDS supervisor are periodically reviewed (e.g. every 2 weeks) until they are resolved.

• The documentation of non-compliance items is managed and controlled.

J. Nawrocki, Quality Assurance

ActivitiesActivitiesActivitiesActivities

Ac8. The SQA group conducts periodic reviews of its activities and findings with the customer’s SQA personnel, as appropriate.

Reviews at PUT

• April

• June

J. Nawrocki, Quality Assurance

SummarySummarySummarySummary

• SQA Planning procedure & SQA plan elements

• The SQA group reviews activities and audits work products.

• Deviations are handled at the lowest possible level of management.

J. Nawrocki, Quality Assurance

Further readingsFurther readingsFurther readingsFurther readings

[CMM] M.C. Paulk et. al.,The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, Reading, 1994.

J. Nawrocki, Quality Assurance

Quality assessmentQuality assessmentQuality assessmentQuality assessment

1. What is your general impression? (1 - 6)

2. Was it too slow or too fast?

3. What important did you learn during the lecture?

4. What to improve and how?