Quality Assurance Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxiliary.

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

Planning at CMM level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements Engineering.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
How ISO9001 Compares with CMM Mark C. Paulk JAN,1995 CMM version 1.1 ISO9001 July 1994 presented by Zhilan Zhou.
Procedures for CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
OHT 6.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Development plan and quality plan objectives The elements of the development.
University of Sunderland CIFM03Lecture 1 1 Quality Management of IT CIFM03 Introduction.
Chapter 3 The Structure of the CMM
Introduction to ISO 9001:2000 Copyright, 2002 © Jerzy R. Nawrocki Quality Management.
Chapter 16 Software Quality Assurance
Chapter 16 Software Quality Assurance
Project Planning Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxilliary.
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Chapter 4 Interpreting the CMM. Group (3) Fahmi Alkhalifi Pam Page Pardha Mugunda.
Introduction to Software Quality Assurance (SQA)
Rational Suite and CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Comparison of CMM Level 2 and eXtreme Programming Copyright, 2002 © Bartosz Walter Quality Connection 2002, Helsinki Poznan University of Technology Poznan,
Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
Configuration Management Copyright, 2002 © Jerzy R. Nawrocki Quality Management.
Software Quality Assurance Activities
Michael Dermody September 2010  Capability Maturity Model Integration ◦ Is a Trademark owned by the Software Engineering Institute (SEI) of Carnegie.
CMM Level 2 KPA’s CS 4320 Fall Requirements Management 1 Goals: – System requirements allocated to software are controlled using a baseline for.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
Software Quality Assurance Lecture #2 By: Faraz Ahmed.
S Q A.
Copyright, 2006 © L. Ouyang Introduction to PSP Liubo Ouyang Personal Software Process Lecture 1.
PRINCE 2 for Managers Copyright, 2003 © Jerzy R. Nawrocki
Project Planning Copyright, 2002 © Jerzy R. Nawrocki Requirements Engineering.
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Q & QA1 Quality & Quality Assurance Advanced Software Engineering COM360 University Of Sunderland © 1999.
Georgia Institute of Technology CS 4320 Fall 2003.
Software Process Improvement: SEI Capability Maturity Model
Quality of Usage Scenarios Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Implementing XP at PUT Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Introduction to SoDA Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Introduction to Requirements Engineering Copyright, 2000 © Jerzy R. Nawrocki Requirements.
ReviewsReviews Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxiliary.
RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 29 Slide 1 Configuration management.
Configuration Management at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Introduction to Quality Management Copyright, 2000 © Jerzy R. Nawrocki Quality.
Configuration Management (II) Copyright, 2000 © Jerzy R. Nawrocki Requirements.
1 Lecture 12: Chapter 16 Software Quality Assurance Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides.
Pittsburgh, PA CMMI Acquisition Module - Page M5-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This.
Quality Assurance at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Introduction to SoDA Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Requirements Management and Changes Copyright, 2003 © Jerzy R. Nawrocki Requirements.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
Requirements Engineering Lecture 7
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Configuration Management
Software Configuration Management
Software Project Configuration Management
Software Quality Control and Quality Assurance: Introduction
Requirements Engineering Lecture 13
Requirements Engineering Lecture 2
Software Quality Assurance
Software Configuration Management
H. Overview of Capability Maturity Model (CMM)
Configuration Management
Chapter 21 Software Quality Assurance
CMMI – Staged Representation
Chapter 21 Software Quality Assurance
CMM Overview A Focus on Level 2
Quality Measurable characteristic Cyclomatic complexity Cohesion
QA Reviews Lecture # 6.
Presentation transcript:

Quality Assurance Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxiliary material Quality Management Auxiliary material

J. Nawrocki, Quality Assurance IntroductionIntroduction CMM 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 AbilitiesAbilities 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 AbilitiesAbilities Ab2. Adequate resources and funding are provided. Is it enough?

J. Nawrocki, Quality Assurance AbilitiesAbilities 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 ActivitiesActivities Ac1. A SQA plan is prepared for each project according to a documented procedure. I’m afraid, I need a documented procedure!

J. Nawrocki, Quality Assurance ActivitiesActivities 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 ActivitiesActivities 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 ActivitiesActivities Ac2. A documented and approved SQA plan is used as the basis for performing the SQA activities

J. Nawrocki, Quality Assurance ActivitiesActivities Responsibilities and authority of the SQA group Resource requirements for the SQA group The SQA group’s participation in planning Evaluations, audits and reviews to be performed by the SQA group Review and audit procedures Documenting and tracking non-compliance issues SQA documentation and reports Schedule of the SQA activities SQA Plan Items

J. Nawrocki, Quality Assurance ActivitiesActivities Ac3. The SQA group participates in the preparation and review of the project’s software development plan, standards, and procedures. 

J. Nawrocki, Quality Assurance ActivitiesActivities Ac4. The SQA group reviews the software engineering activities to verify compliance.

J. Nawrocki, Quality Assurance ActivitiesActivities 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; ActivitiesActivities Ac5. The SQA group audits designated software work products to verify compliance.

J. Nawrocki, Quality Assurance ActivitiesActivities 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 ActivitiesActivities Ac6. The SQA group periodically reports the results of its activities to the software engineering group. It’s getting better!

J. Nawrocki, Quality Assurance ActivitiesActivities 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 ActivitiesActivities Ac7. Deviations identified in the activities and work products are documented and handled according to a documented procedure. Err

J. Nawrocki, Quality Assurance ActivitiesActivities 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 ActivitiesActivities 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 ActivitiesActivities 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 SummarySummary 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 readings [CMM] M.C. Paulk et. al.,The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, Reading, 

J. Nawrocki, Quality Assurance Quality 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?