ec12b--QMv1

ec12b--QMv1 - USC C SE University of Southern California...

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

View Full Document Right Arrow Icon
577a Quality Management A Winsor Brown AWBrown@CSE.USC.edu CS577a September 22, 2008 © 2005 USC Center for Software Engineering 1 of 24 11/4/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
577a Quality Management Outline CS577 Quality Management Overview © 2005 USC Center for Software Engineering 2 of 24 11/4/2009 USC C S E University of Southern California Center for Software Engineering
Background image of page 2
577a Quality Management CS577 Software Engineering of Real Systems Not enough time to do a "large" system, but - Real client - Real deliverables Teach and Use "best practices": techniques, tools and . .. - IICM-Sw; COCOMO II - OO Analysis and Design - Quality Management (QM) - Peer Reviews and other QM early assessment techniques - Configuration Management (CM) - Integrated Independent Verification and Validation (IIV&V) - Evolving: © 2005 USC Center for Software Engineering 3 of 24 11/4/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
577a Quality Management MBASE/RUP/ ICM Activity/Process Model © 2005 USC Center for Software Engineering 4 of 24 11/4/2009 USC C S E University of Southern California Center for Software Engineering
Background image of page 4
577a Quality Management Quality Management The Quality tasks in QM Quality Assessment (and Reporting) - Peer (team) Reviews: Internal/Informal Artifact Reviews - Agile Artifact Reviews (Single-peer [often IIV&Ver] review) - Testing Quality Tracking (Follow up on the "Reports") Quality Improvement With pre-requisites Configuration Management Early Defect Finding (Identification) mechanisms Defect and Effort Data submittal © 2005 USC Center for Software Engineering 5 of 24 11/4/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
577a Quality Management Defect In/Out Model Framework © 2005 USC Center for Software Engineering 6 of 24 11/4/2009 USC C S E University of Southern California Center for Software Engineering
Background image of page 6
577a Quality Management Quality: Defects vs. Issues What's a defect? Orthogonal Defect Categorization specialists forced to conclude the ONLY objective way to know there is/was a defect is because of [compound] change in the artifact or code! ONLY exception is Fagan's Inspections Defects are determined ONLY by the responsible Author of an artifact Typically start out as concerns in informal or agile reviews What's an "issue" Concerns that can NOT be fixed by the author of the artifact under review In developments with large numbers of people or cycles,
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 / 24

ec12b--QMv1 - USC C SE University of Southern California...

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