Procedures for CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Quality Management.

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.
Formal Technical Reviews
 Every stage from phase DESIGN in Software Development Process will have “design document” especially in analysis and design phases.  “Design document”
Quality Assurance Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxiliary.
OHT 8.1 Galin, SQA from theory to implementation © Pearson Education Limited Review objectives Formal design reviews (FDRs) Participants Preparations.
OHT 8.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review objectives Formal design reviews (FDRs) Participants Preparations.
SE 555 Software Requirements & Specification Requirements Validation.
Software Configuration Management (SCM)
Introduction to ISO 9001:2000 Copyright, 2002 © Jerzy R. Nawrocki Quality Management.
Configuration Management
Software Configuration Management
Software Engineering Institute Capability Maturity Model (CMM)
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
Project Planning Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxilliary.
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Rational Suite and CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
N By: Md Rezaul Huda Reza n
Configuration Management Copyright, 2002 © Jerzy R. Nawrocki Quality Management.
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
Software Quality Assurance Activities
Software Quality Assurance
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
CMM Level 2 KPA’s CS 4320 Fall Requirements Management 1 Goals: – System requirements allocated to software are controlled using a baseline for.
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
Quality Model for Requirements Eng. Copyright, 2002 © Jerzy R. Nawrocki Quality.
1 Software Development Configuration management. \ 2 Software Configuration  Items that comprise all information produced as part of the software development.
Requirements Verification & Validation Requirements Engineering & Project Management.
Copyright, 2006 © L. Ouyang Introduction to PSP Liubo Ouyang Personal Software Process Lecture 1.
Good Practices of Requirements Eng. Copyright, 2000 © Jerzy R. Nawrocki Requirements.
By Ritesh Reddy Nagaram.  Organizations which are developing software processes are facing many problems regarding the need for change of already existing.
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.
Georgia Institute of Technology CS 4320 Fall 2003.
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.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.1.
ReviewsReviews Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxiliary.
Introduction to Requirements Eng. Copyright, 2001 © Jerzy R. Nawrocki Requirements.
Configuration Management at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Quality Model for RE Process Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Change Management Requirements Engineering & Project Management Lecture 10.
© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.
Introduction to Quality Management Copyright, 2000 © Jerzy R. Nawrocki Quality.
Configuration Management (II) Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Timesheet training Version: Introduction Duration: 1.5 hours Purpose: Guide on how to use Timesheet.
Software Engineering Lecture 8: Quality Assurance.
Quality Assurance at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
Introduction to SoDA Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
Requirements Management and Changes Copyright, 2003 © Jerzy R. Nawrocki Requirements.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.
Requirements Engineering Lecture 7
Review Techniques SEII-Lecture 16
Software Configuration Management
Software Project Configuration Management
Requirements Engineering Lecture 13
Software Configuration Management (SCM)
Requirements Engineering Lecture 2
Introduction to PRINCE 2
QA Reviews Lecture # 6.
Software Reviews.
3. Software Quality Management
Presentation transcript:

Procedures for CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Quality Management Lecture 7 Quality Management Lecture 7

J. Nawrocki, Quality Management, Lecture 7 Plan of the lecture Introduction Documents for CMM level 2 Reviews in CMM level 2 Generic FTR procedure FTR meeting Preparation form

J. Nawrocki, Quality Management, Lecture 7 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 Management, Lecture 7 Documents for CMM level 2 Policies for.. software requirements management planning (software life cycle) managing a software project managing a software subcontract software quality assurance software configuration management

J. Nawrocki, Quality Management, Lecture 7 Documents for CMM level 2 Documented procedures for.. reviewing external commitments developing an SDP estimating size, effort, cost, critical computer resources, and schedule making revisions to the SDP reviewing a project at milestones planning SQA activities dealing with deviations in activities & products

J. Nawrocki, Quality Management, Lecture 7 Documents for CMM level 2 Documented procedures for.. planning SCM dealing with change requests & problem reports controlling changes to baseline releasing products from baseline library documenting the status of configuration items auditing the software baseline

J. Nawrocki, Quality Management, Lecture 7 Statement of work Reviews in CMM Level 2 Statement of work External commitments Project at selected milestones The software baseline (audit)

J. Nawrocki, Quality Management, Lecture 7 Generic FTR procedure Parameters to be specified in SDP Name of the product URL of the standard doc-struct Due date for approved product Producer Review leader (SQA group) Recorder (SQA group) Reviewers (including recorder) Expected preparation time Expected meeting duration  SDSD P

J. Nawrocki, Quality Management, Lecture 7 Generic FTR procedure Steps (I) Producer informs the project leaders + review leader + area manager (B.W.) that the product is ready and sends them a copy of it. The review leader contacts all the participants of the review meeting to establish the date of the meeting (preferably in 3 days). He also distributes copies of the product to the reviewers.

J. Nawrocki, Quality Management, Lecture 7 Generic FTR procedure Steps (II) The review leader is responsible for establishing an agenda for the review meeting. The meeting takes place The recorder prepares a review report and sends it to the participants of the meeting. A copy of it must also go to the project managers, the area manager and the SDS supervisor.

J. Nawrocki, Quality Management, Lecture 7 FTR meeting A proposed agenda (I) Review leader: Introduction of the agenda. Participants can propose some changes. Recorder: Collecting the preparation forms Producer: Presentation of the material. The producer “walks through” the material and explains, while reviewers raise issues. The recorder takes notes of valid defects and problems.

J. Nawrocki, Quality Management, Lecture 7 FTR meeting A proposed agenda (II) Recorder: Summary of defects and problems. All attendees except producer: Anonymous (in written) presentation of early decision. Recorder: Collecting of early decisions and their presentation. Producer: “Last word” All attendees except producer: Making final decision

J. Nawrocki, Quality Management, Lecture 7 FTR meeting The decision Accept. No modifications are necessary Accept provisionally. There are some minor defects that must be corrected but no additional review is required (the project manager is responsible for checking the follow-up). Reject. There are severe defects and another review is necessary.

J. Nawrocki, Quality Management, Lecture 7 FTR meeting The decision If the decision made by the reviewers is not clear (e.g. some are for Accept, some for Reject), the final decision belongs to the area manager.

J. Nawrocki, Quality Management, Lecture 7 Preparation form for FTR Heading Name of the product & its version:... Producer: Reviewer: The product received on: Expected preparation time: Actual preparation time: Meeting scheduled on: Early decision:

J. Nawrocki, Quality Management, Lecture 7 Preparation form for FTR Body Severe defects & problems (e.g. hidden problems, ambiguity, lack of understanding, etc.): Minor problems (e.g. spelling, grammar, format etc.):

J. Nawrocki, Quality Management, Lecture 7 SummarySummary Documented procedures are necessary for CMM level 2. Review procedures can be stated in a generic form. The main difference between a Fagan inspection and walk- through is: lack of checklists for walkthroughs and lack of presentation for Fagan inspections.

J. Nawrocki, Quality Management, Lecture 7 Further readings M.C. Paulk et. al.,The Capability Maturity Model: Guidelines for Improving the Software Process, Addison-Wesley, Reading, R. Pressman, Software Engineering. A practitioner’s Approach, McGraw Hill, New York, 

J. Nawrocki, Quality Management, Lecture 7 HomeworkHomework Organise and perform a review of the Initial Project Description. Organise and perform a review of the usage scenarios for your project.

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