lecture03基于GQM范型的度量框架課件

SoftwareMetricsLecture3:Part2

AGoal-basedFrameworkforSoftwareMeasurement(1)清華大學軟件學院2004年3月9日1SoftwareMetricsLecture3:ParContentsSoftwareMetricsClassificationGoal-BasedFrameworkMeasurementValidation2ContentsSoftwareMetricsClassGoal-BasedMeasurement(GBM)Theprimaryquestioningoal-basedmeasurement

“Whatdowewanttoknoworlearn?”

insteadof

“Whatmetricsshouldweuse?”

Becausetheanswersdependonyourgoals,nofixedsetofmetricsisuniversallyappropriate

Insteadofattemptingtodevelopgeneral-purposemetrics,onehastodescribeanadaptableprocessthatuserscanusetoidentifyanddefinemetricsthatprovideinsightsintotheirowndevelopmentproblem3Goal-BasedMeasurement(GBM)ThGBMProcessDeterminingwhattomeasureDetermininghowtomeasureIdentifyingentitiesClassifyingentitiestobeexaminedDeterminingrelevantgoalsInquireaboutmetricsAssignmetrics4GBMProcessDeterminingwhattoSection1

SoftwareMetricsClassification

TypesofEntitiesTypesofAttributes5Section1

SoftwareMetricsClTypesofEntitiesProcess

Product

Resource

AcollectionofsoftwarerelatedactivitiesusuallyassociatedwithsometimescaleDifferentSEprocesses:development,maintenance,testing,reuse,configurationandmanagementprocess,etc

Anyartifacts,deliverablesordocumentsthatresultfromaprocessactivity

Entitiesrequiredbyaprocessactivity6TypesofEntitiesProcessProduTypesofAttributesInternalattributesAttributesthatcanbemeasuredentirelyintermsoftheprocess,productorresourceitselfseparate

fromitsbehaviour

Externalattributes

Attributesthatcanbemeasuredwithrespecttohowtheprocess,productorresourcerelatestoitsenvironmentthroughitsbehaviour7TypesofAttributesInternalatSampleProcessMetrics/1ProcessEntitiesAttributesPossiblemetricsdevelopmentprocesselapsedtimeCalendardays,workingdaysmilestonesCalendardatesdevelopmenteffortStaff-hours,days,ormonthstestprocessvolumeNumberoftestsscheduledprogressNumberoftestsexecutedNumberoftestspassed8SampleProcessMetrics/1ProceSampleProcessMetrics/2ProcessEntitiesAttributesPossiblemetricsdetaileddesignelapsedtimecalendardays,workingdaysdesignqualityDefectdensity:numberofdesigndefectsfoundindown-streamactivitiesdividedbyametricofproductsize,suchasfunctionpointsorphysicalsourcelinesofcode.maintenancecostdollarsperyearstaff-hoursperchangerequest9SampleProcessMetrics/2ProceSampleProductMetrics/1ProductentitiesAttributesPossiblemetricsSystemSizeNumberofmodulesNumberoffunctionpointsNumberofphysicalsourcelineofcodedefectdensityDefectsperKLOCDefectsperfunctionpointModuleLengthPhysicalsourcelinesofcodeLogicalsourcestatementsPercentreusedRatioofunchangedphysicallinestototalphysicallines,commentsandblanksexcluded10SampleProductMetrics/1ProduSampleProductMetrics/2ProductentitiesAttributesPossiblemetricsUnitNumberoflinearlyindependentflowpathsMcCabe’scomplexityDocumentLengthNumberofpagesLineofcodeStatementtypeTypenamesProgramminglanguageLanguagename11SampleProductMetrics/2ProduSampleResourceMetricsResourceEntitiesAttributesPossiblemetricsAssignedstaffTeamsizeNumberofpeopleassignedExperienceYearsofdomainexperienceYearsofprogrammingexperienceCASEtoolsTypeNameoftypeIsused?Yes/no(abinaryclassification)TimeStartdate,duedateCalendardatesExecutiontimeCPUclocks12SampleResourceMetricsResourcProcessesInternalattributesExternalattributesConstructSpecificationsTime,effort,numberofrequirementschanges,…Quality,cost,stability,…DetailedDesignsTime,effort,numberofspecificationfaultsfound…Cost-effectiveness,cost,…TestingTime,effort,numberofbugsfound,…Cost-effectiveness,stability,cost,…………SampleAttributes(Process)13ProcessesInternalattributesExProductsInternalattributesExternalattributesSpecificationsSize,reuse,modularity,functionality,syntacticcorrectness…Comprehensibility,maintainability,…DesignsSize,reuse,modularity,coupling,cohesiveness,functionality…Quality,complexity,maintainability,…CodeSize,reuse,modularity,coupling,functionality,algorithmcomplexity,control-flowstructurednessReliability,usability,maintainability,…TestDataSize,coveragelevel,…Quality,…SampleAttributes(Product)14ProductsInternalattributesExtResourcesInternalattributesExternalattributesPersonnelAge,price,…Productivity,experience,intelligence,…TeamsSize,communicationlevel,structuredness,Productivity,qualitySoftwarePrice,size,….Usability,reliabilityHardwarePrice,speed,memorysize,…Reliability,…OfficesSize,temperature,lightComfort,qualitySampleAttributes(Resources)15ResourcesInternalattributesExSection2

Goal-BasedFrameworkGQMApproachSEICMMGQMandCMM16Section2

Goal-BasedFrameworGQMApproach/1Goal-Question-Metric(GQM)approachprovidesaframeworkforderivingmetricsfromorganizationorbusinessgoalsReferencesV.R.BasiliandD.Weiss(1984),AMethodologyforCollectingValidSoftwareEngineeringData,IEEETrans.SoftwareEngineering,vol.10,pp.728-738.V.R.BasiliandH.D.Rombach(1988),TheTameProject:TowardsImprovement-OrientedSoftwareEnvironments,IEEETrans.SoftwareEngineering,vol.14,pp.758-773.17GQMApproach/1Goal-Question-GQMApproach/2GQMProcessG1MeetPlannedProjectScheduleG2DevelopZeroDefectSoftwareG3ProvideDataforBetterEstimatesQ1.1Q1.2Q2.1Q3.1Q3.2M1M2M3M4M5M618GQMApproach/2GQMProcessG1GGQMApproach/3Goal:Listmajorgoalsofdevelopmentormaintenanceproject.Question:Derivefromeachgoalthequestionsthatmustbeansweredtodetermineifthegoalsarebeingmet.Metrics:Decidewhatmustbemeasuredinordertobeabletoanswerthequestionsadequately.19GQMApproach/3Goal:ListmajTemplateforGoalDefinition(1)Purpose:To(characterize,evaluate,predict,motivate,etc.)the(process,product,model,metric,etc.)inorderto(understand,assess,manage,engineer,learn,improve,etc.)it.

Example:Evaluatingmaintenanceprocessinordertoimproveit.20TemplateforGoalDefinition(TemplateforGoalDefinition(2)Perspective:Examinethe(cost,effectiveness,correctness,defects,changes,productmetrics,etc.)fromtheviewpointofthe(developer,manager,customer,etc.)

Example:Examinethecostfromtheviewpointofthemanager.21TemplateforGoalDefinition(TemplateforGoalDefinition(3)Environment:Theenvironmentconsistsofthefollowing:processfactors,peoplefactors,problemfactors,methods,tools,constraints,etc.Example:Themaintenancestaffarepoorlymotivatedprogrammerswhohavelimitedaccesstotools.22TemplateforGoalDefinition(3Examples(1)Purpose:EvaluateworkingenvironmentinordertoidentifyopportunitiestoimprovetheproductivityofourdevelopmentteamPerspective:Examinetheratioofworktimetobreaktimeofouremployees,theaccommodations,incentives,extra-curricularactivitiesoffered,workspace(roomanddesksize,ventilation)whereouremployeesworkfromthepointofviewoftheemployeesthemselvesEnvironmentandconstraints:PayrollapplicationsprogramminginC++100softwaredeveloperswith5ormoreyearsexperienceinC++CustomersarebusinessesDonotmaintainareusablemoduledatabaseExaminenewprojectscompletedandsoldfrom1/1/1998to31/12/200223Examples(1)Purpose:23Examples(2)Purpose:EvaluatetheimpactofvariousCASEtoolsontheproductivityofthedevelopmentteamPerspective:ExaminetheeffectivenessofusingvariousCASEtoolstohelpinthedevelopmentofourproductfromthepointofviewofthedevelopersandtestersEnvironmentandconstraints:PayrollapplicationsprogramminginC++100softwaredeveloperswith5ormoreyearsexperienceinC++CustomersarebusinessesDonotmaintainareusablemoduledatabaseExaminenewprojectscompletedandsoldfrom1/1/1998to31/12/200224Examples(2)Purpose:24GQM,EntitiesandAttributesWecanrelatetheGQMtemplatetotheEntity&Attributeframework.AGoalorquestioncanbeassociatedwithatleastonepairofEntitiesandAttributes.Onceameasureisobtained,itcanberelatedbacktoquestionsandgoals.25GQM,EntitiesandAttributesWeExample:AT&T’sGQMGoal:Bettercodeinspection

Subgoals:BetterinspectionplanningBettermonitorandcontrolofthecodeImprovingcodeinspection26Example:AT&T’sGQMGoal:BettAT&T’sGQM/1GA:Codeinspection:Plan

Q1:

Howmuchdoestheinspectionprocesscost?

Q2:

Howmuchcalendartimedoestheinspectionprocesstake?

M1.1:AverageeffortperKLOCM1.2:Percentageofre-inspection

M2.1:AverageeffortperKLOCM2.2:TotalKLOCinspected27AT&T’sGQM/1GA:CodeinspecAT&T’sGQM/2GB:Codeinspection:Monitor&controlQ1:

Whatisthequalityoftheinspectedsoftware?

Q2:

Whatdegreedidthestaffconformtoprocedure?

Q3:

Whatisthestatusoftheinspectionprocess?

M1.1:AveragefaultdetectedperKLOCM1.2:AverageinspectionrateM1.3:AveragepreparationrateM2.1:AverageinspectionrateM2.2:AveragepreparationrateM2.3:AveragelinesofcodeinspectedM2.4:Percentageofre-inspectionM3.1:TotalKLOCinspected28AT&T’sGQM/2GB:CodeinspecAT&T’sGQM/3GC:Codeinspection:Improve

Q1:

Howeffectiveistheinspectionprocess?

Q2:

Whatistheproductivityoftheinspectionprocess?

M1.1:

Defectremovalefficiency

M1.2:

AveragefaultdetectedperKLOC

M1.3:

Averageinspectionrate

M1.4:

Averagepreparationrate

M1.5:

Averagelinesofcodeinspected

M2.1:

Averageeffortperfaultdetected

M2.2:

Averageinspectionrate

M2.3:

Averagepreparationrate

M2.4:

Averagelinesofcodeinspected29AT&T’sGQM/3GC:CodeinspecAT&T’sNineMetrics(1)30AT&T’sNineMetrics(1)30AT&T’sNineMetrics(2)31AT&T’sNineMetrics(2)31Example:HP’sGQMThreegoals

A:

Maximizecustomersatisfaction

B:

Minimizeengineeringeffortandschedule

C:

Minimizedefects32Example:HP’sGQMThreegoals3Example:HP’sGQM-A/1GA:Maximizecustomersatisfaction

QA1:

Whataretheattributesofcustomersatisfaction?

MA1:

Functionality,usability,reliability,performance,supportability.

QA2:

Whatarethekeyindicatorsofcustomersatisfaction?

MA2:

Survey,qualityfunctiondeployment(QFD).

QA3:

Whataspectsresultincustomersatisfaction?

MA3:

Survey,QFD.QA4:

Howsatisfiedarecustomers?

MA4:

Survey,interviewrecord,numberofcustomersseverelyaffectedbydefects.

QA5:

Howmanycustomersareaffectedbyaproblem?

MA5:

Numberofduplicatedefectsbyseverity33Example:HP’sGQM-A/1GA:MaExample:HP’sGQM-A/2GA:Maximizecustomersatisfaction

QA6:

Howmanyproblemsareaffectingthecustomer?

MA6-1:

IncomingdefectrateMA6-2:

Opencriticalandseriousdefects

MA6-3:

Defectreport/fixratio

MA6-4:

Post-releasedefectdensity

QA7:

Howlongdoesittaketofixaproblem?

MA7-1:

Meantimetoacknowledgeproblem

MA7-2:

Meantimetodeliversolution

MA7-3:

Scheduledvs.actualdelivery

MA7-4:

Customerexpectationoftimetofix

34Example:HP’sGQM-A/2GA:MaExample:HP’sGQM-A/2

GA:Maximizecustomersatisfaction

QA8:

Howdoesinstallingafixaffectthecustomer?

MA8-1:

TimecustomersoperationisdownMA8-2:

Customerseffortrequiredduringinstallation

QA9:

Wherearethebottlenecks?

MA9:

Backlogstatus,timespentdoingdifferentactivities

35Example:HP’sGQM-A/2GA:MExample:HP’sGQM-B/1GB:Minimizeengineeringeffort&schedule

QB1:

Wherearetheworstreworkloopsintheprocess?

MB1:Person-monthsbyproduct-component-activity.QB2:

Whatarethetotallife-cyclemaintenanceandsupportcostsfortheproduct?

MB2.1:Person-monthsbyproduct-component-activity.MB2.2:Person-monthsbycorrective,adaptive,perfectivemaintenance.QB3:

Whatdevelopmentmethodsaffectmaintenancecosts?MB3:Pre-releaserecordsofmethodsandpost-releasecosts.36Example:HP’sGQM-B/1GB:MiExample:HP’sGQM-B/2GB:Minimizeengineeringeffort&scheduleQB4:

Howmaintainableistheproductaschangesoccur?MB4.1:IncomingproblemrateMB4.2:detectdensityMB4.3:CodestabilityMB4.4:ComplexityMB4.5:NumberofmoduleschangedtofixonedetectQB5:

Whatwillprocessmonitoringcostandwherearethecostsdistributed?

MB5:Person-monthsandcostsQB6:

Whatwillmaintenancerequirementsbe?

MB6.1:Codestability,complexity,sizeMB6.2:Pre-releasedefectdensity

37Example:HP’sGQM-B/2GB:MiExample:HP’sGQM-B/3GB:Minimizeengineeringeffort&schedule

QB7:

Howcanwepredictcycletime,reliability,andeffort?

MB7.1:CalendartimeMB7.2:Person-monthMB7.3:DefectdensityMB7.4:NumberofdetectstofixMB7.5:Defectreport/fixratioMB7.6:CodestabilityMB7.7:ComplexityMB7.8:Numberoflinestochange38Example:HP’sGQM-B/3GB:MiExample:HP’sGQM-B/4GB:Minimizeengineeringeffort&schedule

QB8:

Whatpracticesyieldbestresults?

MB8:Correlationsbetweenpre-releasepracticesandcustomersatisfactiondata

QB9:

Howmuchdothemaintenancephaseactivitiescost?

MB9:Personal-monthsandcost

QB10:

Whataremajorcostcomponents?

MB10:Person-monthsbyproduct-component-activity

QB11:

Howdocostschangeovertime?MB11:Trackcostcomponentsoverentitymaintenancelife-cycle.

39Example:HP’sGQM-B/4GB:MiExample:HP’sGQM-C/1GC:MinimizedefectsQC1:

WhatarekeyIndicatorsofprocesshealthandhowarewedoing?

MC1:Releaseschedulemet,trendsofdefectdensity,seriousandcriticaldetects.QC2:

Whatarehigh-leverageopportunitiesforpreventivemaintenance?

MC2.1:DefectcategorizationMC2.2:CodestabilityQC3:

Arefixeseffectivewithlesssideeffects?

MC3:Defectreport/fixratio40Example:HP’sGQM-C/1GC:MiExample:HP’sGQM-C/2GC:MinimizedefectsQC4:

Whatisthepost-releasequalityofeachmodule?

MC4:Defectdensity,criticalandseriousdetects.

QC5:

Whatarewedoingright?

MC5.1:DefectremovalefficiencyMC5.2:Defectreport/fixratioQC6:

Howdoweknowwhentorelease?

MC6.1:Predicteddefectdetectionandremainingdefects.MC6.2:Testcoverage.41Example:HP’sGQM-C/2GC:MiExample:HP’sGQM-C/3GC:MinimizedefectsQC7:

Howeffectiveisthedevelopmentprocessinpreventingdefects?

MC7:Post-releasedetectdensityQC8:

Whatcanwepredictwillhappenpost-releasebasedonpre-releasedata?

MC8:Correctionsbetweenpre-releasecomplexity,defectdensity,stability,andcustomersurveydata.

QC9:

Whatdefectsaregettingthroughandtherecauses?

MC9:Detectcategorization42Example:HP’sGQM-C/3GC:MiSummaryMeaningful?Operationsonmetrics?Directorindirectmetrics?Objectiveandsubjectivemetrics?Softwaremetricclassification?Goal-basedframework?43SummaryMeaningful?OperationsoFurtherreading1.R.E.Park,W.B.Goethert,W.A.Florac.Goal-DrivenSoftwareMeasurement-AGuidebook.CMU/SEI-96-HB-002,(189pages)2.J.Barnard,A.Price.ManagingCodeInspectionInformation.IEEESoftware,1994.(11pages)Homework44FurtherreadingHomework44Thanksforyourtimeandattention!45ThanksforyourtimeandattenSoftwareMetricsLecture3:Part2

AGoal-basedFrameworkforSoftwareMeasurement(1)清華大學軟件學院2004年3月9日46SoftwareMetricsLecture3:ParContentsSoftwareMetricsClassificationGoal-BasedFrameworkMeasurementValidation47ContentsSoftwareMetricsClassGoal-BasedMeasurement(GBM)Theprimaryquestioningoal-basedmeasurement

“Whatdowewanttoknoworlearn?”

insteadof

“Whatmetricsshouldweuse?”

Becausetheanswersdependonyourgoals,nofixedsetofmetricsisuniversallyappropriate

Insteadofattemptingtodevelopgeneral-purposemetrics,onehastodescribeanadaptableprocessthatuserscanusetoidentifyanddefinemetricsthatprovideinsightsintotheirowndevelopmentproblem48Goal-BasedMeasurement(GBM)ThGBMProcessDeterminingwhattomeasureDetermininghowtomeasureIdentifyingentitiesClassifyingentitiestobeexaminedDeterminingrelevantgoalsInquireaboutmetricsAssignmetrics49GBMProcessDeterminingwhattoSection1

SoftwareMetricsClassification

TypesofEntitiesTypesofAttributes50Section1

SoftwareMetricsClTypesofEntitiesProcess

Product

Resource

AcollectionofsoftwarerelatedactivitiesusuallyassociatedwithsometimescaleDifferentSEprocesses:development,maintenance,testing,reuse,configurationandmanagementprocess,etc

Anyartifacts,deliverablesordocumentsthatresultfromaprocessactivity

Entitiesrequiredbyaprocessactivity51TypesofEntitiesProcessProduTypesofAttributesInternalattributesAttributesthatcanbemeasuredentirelyintermsoftheprocess,productorresourceitselfseparate

fromitsbehaviour

Externalattributes

Attributesthatcanbemeasuredwithrespecttohowtheprocess,productorresourcerelatestoitsenvironmentthroughitsbehaviour52TypesofAttributesInternalatSampleProcessMetrics/1ProcessEntitiesAttributesPossiblemetricsdevelopmentprocesselapsedtimeCalendardays,workingdaysmilestonesCalendardatesdevelopmenteffortStaff-hours,days,ormonthstestprocessvolumeNumberoftestsscheduledprogressNumberoftestsexecutedNumberoftestspassed53SampleProcessMetrics/1ProceSampleProcessMetrics/2ProcessEntitiesAttributesPossiblemetricsdetaileddesignelapsedtimecalendardays,workingdaysdesignqualityDefectdensity:numberofdesigndefectsfoundindown-streamactivitiesdividedbyametricofproductsize,suchasfunctionpointsorphysicalsourcelinesofcode.maintenancecostdollarsperyearstaff-hoursperchangerequest54SampleProcessMetrics/2ProceSampleProductMetrics/1ProductentitiesAttributesPossiblemetricsSystemSizeNumberofmodulesNumberoffunctionpointsNumberofphysicalsourcelineofcodedefectdensityDefectsperKLOCDefectsperfunctionpointModuleLengthPhysicalsourcelinesofcodeLogicalsourcestatementsPercentreusedRatioofunchangedphysicallinestototalphysicallines,commentsandblanksexcluded55SampleProductMetrics/1ProduSampleProductMetrics/2ProductentitiesAttributesPossiblemetricsUnitNumberoflinearlyindependentflowpathsMcCabe’scomplexityDocumentLengthNumberofpagesLineofcodeStatementtypeTypenamesProgramminglanguageLanguagename56SampleProductMetrics/2ProduSampleResourceMetricsResourceEntitiesAttributesPossiblemetricsAssignedstaffTeamsizeNumberofpeopleassignedExperienceYearsofdomainexperienceYearsofprogrammingexperienceCASEtoolsTypeNameoftypeIsused?Yes/no(abinaryclassification)TimeStartdate,duedateCalendardatesExecutiontimeCPUclocks57SampleResourceMetricsResourcProcessesInternalattributesExternalattributesConstructSpecificationsTime,effort,numberofrequirementschanges,…Quality,cost,stability,…DetailedDesignsTime,effort,numberofspecificationfaultsfound…Cost-effectiveness,cost,…TestingTime,effort,numberofbugsfound,…Cost-effectiveness,stability,cost,…………SampleAttributes(Process)58ProcessesInternalattributesExProductsInternalattributesExternalattributesSpecificationsSize,reuse,modularity,functionality,syntacticcorrectness…Comprehensibility,maintainability,…DesignsSize,reuse,modularity,coupling,cohesiveness,functionality…Quality,complexity,maintainability,…CodeSize,reuse,modularity,coupling,functionality,algorithmcomplexity,control-flowstructurednessReliability,usability,maintainability,…TestDataSize,coveragelevel,…Quality,…SampleAttributes(Product)59ProductsInternalattributesExtResourcesInternalattributesExternalattributesPersonnelAge,price,…Productivity,experience,intelligence,…TeamsSize,communicationlevel,structuredness,Productivity,qualitySoftwarePrice,size,….Usability,reliabilityHardwarePrice,speed,memorysize,…Reliability,…OfficesSize,temperature,lightComfort,qualitySampleAttributes(Resources)60ResourcesInternalattributesExSection2

Goal-BasedFrameworkGQMApproachSEICMMGQMandCMM61Section2

Goal-BasedFrameworGQMApproach/1Goal-Question-Metric(GQM)approachprovidesaframeworkforderivingmetricsfromorganizationorbusinessgoalsReferencesV.R.BasiliandD.Weiss(1984),AMethodologyforCollectingValidSoftwareEngineeringData,IEEETrans.SoftwareEngineering,vol.10,pp.728-738.V.R.BasiliandH.D.Rombach(1988),TheTameProject:TowardsImprovement-OrientedSoftwareEnvironments,IEEETrans.SoftwareEngineering,vol.14,pp.758-773.62GQMApproach/1Goal-Question-GQMApproach/2GQMProcessG1MeetPlannedProjectScheduleG2DevelopZeroDefectSoftwareG3ProvideDataforBetterEstimatesQ1.1Q1.2Q2.1Q3.1Q3.2M1M2M3M4M5M663GQMApproach/2GQMProcessG1GGQMApproach/3Goal:Listmajorgoalsofdevelopmentormaintenanceproject.Question:Derivefromeachgoalthequestionsthatmustbeansweredtodetermineifthegoalsarebeingmet.Metrics:Decidewhatmustbemeasuredinordertobeabletoanswerthequestionsadequately.64GQMApproach/3Goal:ListmajTemplateforGoalDefinition(1)Purpose:To(characterize,evaluate,predict,motivate,etc.)the(process,product,model,metric,etc.)inorderto(understand,assess,manage,engineer,learn,improve,etc.)it.

Example:Evaluatingmaintenanceprocessinordertoimproveit.65TemplateforGoalDefinition(TemplateforGoalDefinition(2)Perspective:Examinethe(cost,effectiveness,correctness,defects,changes,productmetrics,etc.)fromtheviewpointofthe(developer,manager,customer,etc.)

Example:Examinethecostfromtheviewpointofthemanager.66TemplateforGoalDefinition(TemplateforGoalDefinition(3)Environment:Theenvironmentconsistsofthefollowing:processfactors,peoplefactors,problemfactors,methods,tools,constraints,etc.Example:Themaintenancestaffarepoorlymotivatedprogrammerswhohavelimitedaccesstotools.67TemplateforGoalDefinition(3Examples(1)Purpose:EvaluateworkingenvironmentinordertoidentifyopportunitiestoimprovetheproductivityofourdevelopmentteamPerspective:Examinetheratioofworktimetobreaktimeofouremployees,theaccommodations,incentives,extra-curricularactivitiesoffered,workspace(roomanddesksize,ventilation)whereouremployeesworkfromthepointofviewoftheemployeesthemselvesEnvironmentandconstraints:PayrollapplicationsprogramminginC++100softwaredeveloperswith5ormoreyearsexperienceinC++CustomersarebusinessesDonotmaintainareusablemoduledatabaseExaminenewprojectscompletedandsoldfrom1/1/1998to31/12/200268Examples(1)Purpose:23Examples(2)Purpose:EvaluatetheimpactofvariousCASEtoolsontheproductivityofthedevelopmentteamPerspective:ExaminetheeffectivenessofusingvariousCASEtoolstohelpinthedevelopmentofourproductfromthepointofviewofthedevelopersandtestersEnvironmentandconstraints:PayrollapplicationsprogramminginC++100softwaredeveloperswith5ormoreyearsexperienceinC++CustomersarebusinessesDonotmaintainareusablemoduledatabaseExaminenewprojectscompletedandsoldfrom1/1/1998to31/12/200269Examples(2)Purpose:24GQM,EntitiesandAttributesWecanrelatetheGQMtemplatetotheEntity&Attributeframework.AGoalorquestioncanbeassociatedwithatleastonepairofEntitiesandAttributes.Onceameasureisobtained,itcanberelatedbacktoquestionsandgoals.70GQM,EntitiesandAttributesWeExample:AT&T’sGQMGoal:Bettercodeinspection

Subgoals:BetterinspectionplanningBettermonitorandcontrolofthecodeImprovingcodeinspection71Example:AT&T’sGQMGoal:BettAT&T’sGQM/1GA:Codeinspection:Plan

Q1:

Howmuchdoestheinspectionprocesscost?

Q2:

Howmuchcalendartimedoestheinspectionprocesstake?

M1.1:AverageeffortperKLOCM1.2:Percentageofre-inspection

M2.1:AverageeffortperKLOCM2.2:TotalKLOCinspected72AT&T’sGQM/1GA:CodeinspecAT&T’sGQM/2GB:Codeinspection:Monitor&controlQ1:

Whatisthequalityoftheinspectedsoftware?

Q2:

Whatdegreedidthestaffconformtoprocedure?

Q3:

Whatisthestatusoftheinspectionprocess?

M1.1:AveragefaultdetectedperKLOCM1.2:AverageinspectionrateM1.3:AveragepreparationrateM2.1:AverageinspectionrateM2.2:AveragepreparationrateM2.3:AveragelinesofcodeinspectedM2.4:Percentageofre-inspectionM3.1:TotalKLOCinspected73AT&T’sGQM/2GB:CodeinspecAT&T’sGQM/3GC:Codeinspection:Improve

Q1:

Howeffectiveistheinspectionprocess?

Q2:

Whatistheproductivityoftheinspectionprocess?

M1.1:

Defectremovalefficiency

M1.2:

AveragefaultdetectedperKLOC

M1.3:

Averageinspectionrate

M1.4:

Averagepreparationrate

M1.5:

Averagelinesofcodeinspected

M2.1:

Averageeffortperfaultdetected

M2.2:

Averageinspectionrate

M2.3:

Averagepreparationrate

M2.4:

Averagelinesofcodeinspected74AT&T’sGQM/3GC:CodeinspecAT&T’sNineMetrics(1)75AT&T’sNineMetrics(1)30AT&T’sNineMetrics(2)76AT&T’sNineMetrics(2)31Example:HP’sGQMThreegoals

A:

Maximizecustomersatisfaction

B:

Minimizeengineeringeffortandschedule

C:

Minimizedefects77Example:HP’sGQMThreegoals3Example:HP’sGQM-A/1GA:Maximizecustomersatisfaction

QA1:

Whataretheattributesofcustomersatisfaction?

MA1:

Functionality,usability,reliability,performance,supportability.

QA2:

Whatarethekeyindicatorsofcustomersatisfaction?

MA2:

Survey,qualityfunctiondeployment(QFD).

QA3:

Whataspectsresultincustomersatisfaction?

MA3:

Survey,QFD.QA4:

Howsatisfiedarecustomers?

MA4:

Survey,interviewrecord,numberofcustomerssever