1. Procedures for CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Jerzy.Nawrocki@put.poznan.pl www.cs.put.poznan.pl/jnawrocki/mse/require/ Quality Management Lecture 7 Quality Management Lecture 7

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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)

8. 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

9. 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.

10. 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.

11. 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.

12. 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

13. 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.

14. 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.

15. 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:....................................

16. 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.):

17. 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.

18. 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, 1994. R. Pressman, Software Engineering. A practitioner’s Approach, McGraw Hill, New York, 1997. 

19. 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.

20. 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?