ec17a=QM&PRv0

ec17a=QM&PRv0 - USC C SE University of Southern...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
CM & QM and Peer Reviews A Winsor Brown AWBrown@CSE.USC.edu CS577a October 2, 2009 © 2005-2009 USC Center for Software Engineering 1 of 32 11/13/2009 USC C S E University of Southern California Center for Software Engineering
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CM & QM and Peer Reviews Outline CS577a Quality Management (QM) The three legs CS577a Configuration Management (CM) CM System Approaches Change Control Peer Reviews (AKA wrongly as "Inspections") ROI by Type of Review Peer Reviews as practiced in 577a Peer Review Workshop © 2005-2009 USC Center for Software Engineering 2 of 32 11/13/2009 USC C S E University of Southern California Center for Software Engineering
Background image of page 2
CM & QM and Peer Reviews Quality Management The Quality tasks in QM Quality Assessment (and Reporting) - Peer (team) Reviews - Agile (IIV&V) Artifact Reviews - Testing Quality Tracking (Follow up on the "Reports") until closure Quality Improvement With pre-requisites Configuration Management Early Defect Finding (Identification) mechanisms Defect and Effort Data submittal © 2005-2009 USC Center for Software Engineering 3 of 32 11/13/2009 USC C S E University of Southern California Center for Software Engineering
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CM & QM and Peer Reviews CS577a Quality Management Pre-requisites Configuration Management: Your's described in your LCP Early Defect Finding (Identification) mechanisms: PBR & AAR Defect & Effort Data submittal: QR (needed for 1 sem. Prj.) The Quality tasks in QM Quality Assessment (and Reporting) - Artifact/Package Reviews withExit Criteria: IIV&V - Peer (team) Reviews: Agile Role Based Internal Reviews (AIR) - Testing? (needed for one semester development projects) - Problem Reports (via Bugzilla) Quality Assessments Tracking (Follow up on the "Reports") - Available mechanisms: Bugzilla © 2005-2009 USC Center for Software Engineering 4 of 32 11/13/2009 USC C S E University of Southern California Center for Software Engineering
Background image of page 4
CM & QM and Peer Reviews Quality Improvement - © 2005-2009 USC Center for Software Engineering 5 of 32 11/13/2009 USC C S E University of Southern California Center for Software Engineering
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CM & QM and Peer Reviews Cost Schedule Quality Tradeoff Q, $, Time: non-ICM projects: Pick two of the three: the other is the "independent" variable IICM-SWprojects: Pick all three: Reduce the "size" of the project to satisfice stakeholders - features/capabilities - documentation/project-requirements - LOS - Interfaces - Evolution © 2005-2009 USC Center for Software Engineering 6 of 32 11/13/2009 USC C S E University of Southern California Center for Software Engineering
Background image of page 6
CM & QM and Peer Reviews CS577a CM CM System Approaches ( possible /recommended) For Documents: - File naming conventions on Team Website - ClearCase Light - Subversion For Prototype Code (especially if more than one prototyper; definitely for executable prototype). -
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 32

ec17a=QM&PRv0 - USC C SE University of Southern...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online