华为cmm基础知识培训面向学生

,SoftwareQualityManagement,QuantitativeProcessManagement,ManagedLevel-CMMLevel4,TYPICALCHARACTERISTICSOFAMANAGEDLEVELORGANISATION,Atlevel3,measurementshavebeendefinedandcollectedsystematicallyAtlevel4,decisionsaremadebasedondatacollectedTheorganisationsetsquantitativegoalsforbothsoftwareproductsandprocesses.Theprocessperformanceofaprojectiscontrolledquantitatively.CommonmeasurementDataanalysis,Standards,Activity,Results,toproduce,Level4,Planning,Evaluation,inputto,toimprove,inputto,inputto,toforecast,Predicttheresultsyouneedandexpectandthencreateopportunitiestogetthoseresults,QUANTITATIVEPROCESSMANAGEMENT,PurposeistocontroltheprocessperformanceofthesoftwareprojectquantitativelyInvolvesEstablishinggoalsforprocessperformanceMeasuringtheperformanceoftheprojectAnalyzingthesemeasurementsmakingadjustmentstomaintainprocessperformancewithinacceptablelimitsIdentifyingvariationsinperformancethatarenotwithinthenormalrangeofprocessperformanceIdentifying“Extraordinary”eventsoutsidetheboundsofprocesscapability,QuantitativeProcessManagement-CommonFeatures,CommitmentWrittenorganizationalpolicyformeasuringandquantitativelycontrollingtheperformanceoftheprojectsDSPAbilityGroupthatisresponsibleforcoordinatingthequantitativeprocessmanagementactivitiesshouldexist.AdequateresourcesandfundingSupportforcollecting,recordingandanalyzingdata,QuantitativeProcessManagement-CommonFeatures(contd.),TrainingonQuantitativeprocessmanagementforpersonnelperformingtheseactivitiesOrientationtoSoftwareengineeringgroupMeasurementTodeterminethestatusofQPMactivities.,QuantitativeProcessManagement-Activities,Thequantitativeprocessmanagementactivitiesareplanned.ThesoftwareprojectsplanforquantitativeprocessmanagementisdevelopedadocprocThesoftwareprojectsquantitativeprocessmanagementactivitiesareperformedinaccordancewiththeprojectsquantitativeprocessmanagementplan.Thestrategyforthedatacollectionandthequantitativeanalysestobeperformedaredeterminedbasedontheprojectsdefinedsoftwareprocess.,QuantitativeProcessManagement,GroupresponsibleforQPMactivitiesexists-MetricsCouncilisgoodtodoAmetricationplanfortheorganizationexists,QuantitativeProcessManagement-Moreinsights,ProcessperformanceResultsobtainedfromfollowingasoftwareprocessMeasuredattheprojectlevelProcesscapabilityProcessperformanceanewprojectmayattain,QuantitativeProcessManagement-Moreinsights,Processstability-fordefinedsoftwareprocessSetupcontrollimitsBaselinesestablishedProcessperformancethencontrolledquantitatively,QuantitativeProcessManagement-Activities,TheProcessPerformanceoftheProjectsDefinedSoftwareProcessIsControlledQuantitatively.Thesoftwareprojectsquantitativeprocessmanagementactivitiesareperformedinaccordancewiththeprojectsquantitativeprocessmanagementplan.,QuantitativeProcessManagement-Activities,Theprocessperformanceoftheprojectsdefinedsoftwareprocessiscontrolledquantitatively.Themeasurementdatausedtocontroltheprojectsdefinedsoftwareprocessquantitativelyarecollectedaccordingtoadocumentedprocedure.Theprojectsdefinedsoftwareprocessisanalyzedandbroughtunderquantitativecontrolaccordingtoadocumentedprocedure.Reportsdocumentingtheresultsofthesoftwareprojectsquantitativeprocessmanagementactivitiesarepreparedanddistributed.,QuantitativeProcessManagement-Moreinsights,ProjecthasaplanforQPMHowtocollectdataWhatanalysesistobedone?DatacollectedDefinedSWprocessanalyzedandbroughtunderquantitativecontrolcontd.,QuantitativeProcessManagement-Moreinsights,Contd.Dataanalysis:scatterdiagrams,controlcharts,ParetodiagramsControllimitssetupProcessperformancebaselineknownandpublishedCapabilitybaselineforOSSP,SoftwareQualityManagement,Understandquantitativelythequalityofproductwhiletheproductisbeingdeveloped,andcomparewithquantitativequalitygoalsfortheproduct,SoftwareQualityManagement,PURPOSEIstodevelopaquantitativeunderstandingofthequalityoftheprojectssoftwareproductsandachievespecificqualitygoalsINVOLVESDefiningqualitygoalsforthesoftwareproductsEstablishingplanstoachievethesegoalsMonitoringandadjustingsoftwareplans,softwareworkproducts,activitiesandqualitygoalstosatisfytheneedsanddesiresofcustomerandend-user,SoftwareQualityManagement-CommonFeatures,COMMITMENTWrittenorganizationalpolicyformanagingsoftwarequality.ABILITYAdequateresourcesandfundingTrainingtoindividualstoperformqualitymanagementactivitiesMEASUREMENTTodeterminethestatusofSoftwarequalitymanagementactivities.,SoftwareQualityManagement-Activities,TheProjectsSoftwareQualityManagementActivitiesArePlanned.Theprojectssoftwarequalityplanisdevelopedandmaintainedaccordingtoadocumentedprocedure.Theprojectssoftwarequalityplanisthebasisfortheprojectsactivitiesforsoftwarequalitymanagement.,SoftwareQualityManagement-Activities,Measurablegoalsforsoftwareproductqualityandtheirprioritiesaredefined.Theprojectsquantitativequalitygoalsforthesoftwareproductsaredefined,monitored,andrevisedthroughoutthesoftwarelifecycle.Thesoftwareprojectsquantitativequalitygoalsfortheproductsareallocatedappropriatelytothesubcontractorsdeliveringsoftwareproductstotheproject.,SoftwareQualityManagement-Activities,ActualProgressTowardAchievingtheQualityGoalsfortheSoftwareProductsIsQuantifiedandManaged.TheprojectssoftwarequalityplanisthebasisfortheprojectsactivitiesforsoftwarequalitymanagementThequalityoftheprojectssoftwareproductsismeasured,analyzed,andcomparedtotheproductsquantitativequalitygoalsonanevent-drivenbasis.,SoftwareQualityManagement,QualityplanforprojecthasmeasurablequalitygoalsProductsaremeasuredforqualityandcomparedwithgoalsSimilarpracticeforsubcontractors,ChallengesinImplementingLevel4Requirements,DISCUSSIONS,DefectPrevention,OptimizingLevel-CMMLevel5,ProcessChangeManagement,TechnologyChangeManagement,TYPICALCHARACTERISTICSOFAOPTIMIZINGLEVELORGANISATION,Atlevel4,theprocessisquantitativelyunderstoodAtlevel5,continuousprocessimprovementisawayoflife.Thefocusisonpreventingtheoccurrenceofdefectsandinnovations.,TypicalCharacteristicsofaOptimizingLevelOrganisation,Inimmatureorganizations,noonemayberesponsibleforprocessimprovementMatureorganizationsusuallyhave70-80%participationinimprovementactivitiesatanygivenpointintime-everyoneisinvolved.Continuousprocessimprovementmeanscontrolledchangeandmeasurablyimprovingprocesscapability,Standards,Activity,Results,toproduce,Level5,Planning,Evaluation,inputto,toimprove,inputto,inputto,toforecast,toimprove,Createlessonslearned,anduselessonslearnedtocreatemorelessonslearned,andusemorelessonslearnedtocreateevenmorelessonslearned,anduseevenmorelessonslearnedtocreate.etc.,DEFECTPREVENTION,PurposeistoidentifythecauseofdefectsandpreventthemfromrecurringInvolvesAnalyzingdefectsthatwereencounteredinthepast.Takingspecificactionstopreventtheoccurrenceofthesetypesofdefectsinthefuture.Trendsareanalyzedtotrackthetypesofdefectsthathavebeenencounteredandtoidentifydefectsthatarelikelytorecur.,DefectPrevention-CommonFeatures,CommitmentWrittenorganizationalpolicy/andpolicyfortheprojectfordefectpreventionactivities.AbilityTeamthatisresponsibleforcoordinatingthedefectpreventionactivitiesshouldexistattheorganizationlevelandprojectlevel.AdequateresourcesandfundingTrainingondefectpreventionforpersonnelperformingtheseactivities,DefectPrevention-CommonFeatures(contd),MeasurementTodeterminethestatusofthedefectpreventionactivities.,DefectPrevention-Activities,Defectpreventionactivitiesareplanned.Thesoftwareprojectdevelopsandmaintainsaplanforitsdefectpreventionactivities.Atthebeginningofasoftwaretask,themembersoftheteamperformingthetaskmeettopreparefortheactivitiesofthattaskandtherelateddefectpreventionactivities.,DefectPrevention-Activities,CommonCausesofDefectsAreSoughtOutandIdentified.Causalanalysismeetingsareconductedaccordingtoadocumentedprocedure.Defectpreventiondataaredocumentedandtrackedacrosstheteamscoordinatingdefectpreventionactivities.,DefectPrevention-Activities,Commoncausesofdefectsareprioritizedandsystematicallyeliminated.Theteamsassignedtocoordinatedefectpreventionactivitiesmeetsonaperiodicbasistoreviewandcoordinateimplementationofactionproposalsfromthecausalanalysismeetings.RevisionstotheorganizationsOSSPresultingfromdefectpreventionactionsareincorporatedadocprocRevisionstotheprojectsDSPresultingfromdefectpreventionactionsareincorporatedadocprocMembersofthesoftwareengineeringgroupandsoftware-relatedgroupsreceivefeedbackonthestatusandresultsoftheorganizationsandprojectsdefectpreventionactivitiesonaperiodicbasis.,DefectPrevention-Summary,Whydiddefectsoccur?CausalanalysisSpecialcausesCommoncausesRemovecommoncauses,thuspreventingdefectsfromrecurring,DefectPrevention-Summary,Teamsexistatorg.levelandprojectleveltocoordinatedefectpreventionactivitiesProjecthasadefectpreventionplanCausalanalysismeetingsheldActionpointsareimplementedDefectpreventiondatatracked,DefectPrevention-Summary,ChangesmadetoOSSP.ChangesmadetodefinedSWprocessMeasurementsincludedefectage,costofquality,defectdensityetc.,TECHNOLOGYCHANGEMANAGEMENT,Purposeistoidentifynewtechnologies(i.e.,Tools,methods,andprocesses)andtransfertheminanorganizationinanorderlymanner.InvolvesIdentifying,selecting,andevaluatingnewtechnologies(tools,methodsandprocesses).Piloteffortsareperformedtoassessnewtechnologies.Incorporatingeffectivetechnologiesintotheorganization.,TechnologyChangeManagement-CommonFeatures,COMMITMENTWrittenorganizationalpolicyformanagingsoftwarequality.SeniorManagementsponsorsandoverseesthetechnologychangemanagementactivities.ABILITYGroupthatisresponsiblefortechnologychangemanagementactivitiesexists.AdequateresourcesandfundingSupportforcollectingandanalyzingdataneededtoevaluatetechnologychangesMEASUREMENTTodeterminethestatusofTechnologychangemanagementactivities.,TechnologyChangeManagement-Activities,Incorporationoftechnologychangesareplanned.Theorganizationdevelopsandmaintainsaplanfortechnologychangemanagement.,TechnologyChangeManagement-Activities,Newtechnologiesareevaluatedtodeterminetheireffectonqualityandproductivity.ThegroupresponsiblefortheorganizationsTCMactivitiesworkswiththesoftwareprojectsinidentifyingareasoftechnologychange.ThegroupresponsiblefortheorganizationsTCManalyzestheOSSPtoidentifyareasthatneedorcouldbenefitfromnewtechnology.TechnologiesareselectedandacquiredfortheorganizationandsoftwareprojectsadocprocPiloteffortsforimprovingtechnologyareconducted,whereappropriate,beforeanewtechnologyisintroducedintonormalpractice.,TechnologyChangeManagement-Activities,AppropriateNewTechnologiesAreTransferredIntoNormalPracticeAcrosstheOrganization.Softwaremanagersandtechnicalstaffarekeptinformedofnewtechnologies.Appropriatenewtechnologiesareincorporatedintotheorganizationsstandardsoftwareprocessaccordingtoadocumentedprocedure.Appropriatenewtechnologiesareincorporatedintotheprojectsdefinedsoftwareprocessesaccordingtoadocumentedprocedure.,TechnologyChangeManagement,IdentifynewtechnologiesandtrackthemintoorganizationinanorderlymannerTechnologysupportgroupPilotsdonefirst;thenincorporatedintonormalpractice,TechnologyChangeManagement,Analysisofprocessestoidentifyareasthatcouldbenefitfromnewtechnology-basedondataTechnologiesselected&acquiredPilotscarriedoutIncorporatedintostandardprocess,PROCESSCHANGEMNGT.,PurposeIstoContinuouslyImprovetheSoftwareProcessUsedintheOrganizationWiththeIntentofImprovingSoftwareQuality,IncreasingProductivity,andDecreasingtheCycleTimeforProductDevelopmentInvolvesDefiningprocessimprovementgoalsSystematicallyidentifying,evaluating,andimplementingimprovementstotheorganizationsstandardsoftwareprocessandtheprojectsdefinedsoftwareprocesses,ProcessChangeManagement-CommonFeatures,COMMITMENTWrittenorganizationalpolicyforimplementingsoftwareprocessimprovements.SeniorManagementsponsorshipforsoftwareprocessimprovement.ABILITYAdequateresourcesandfundingTrainingforsoftwaremanagersinsoftwareprocessimprovement.SeniorManagementreceivesrequiredtraininginsoftwareprocessimprovement.MEASUREMENTTodeterminethestatusofthesoftwareprocessimprovementactivities.,ProcessChangeManagement-Activities,ContinuousProcessImprovementIsPlanned.Thegroupresponsiblefortheorganizationssoftwareprocessactivities(e.g.,softwareengineeringprocessgroup)coordinatesthesoftwareprocessimprovementactivities.Theorganizationdevelopsandmaintainsaplanforsoftwareprocessimprovementaccordingtoadocumentedprocedure.Thesoftwareprocessimprovementactivitiesareperformedinaccordancewiththesoftwareprocessimprovementplan.,ProcessChangeManagement-Activities,Participationintheorganizationssoftwareprocessimprovementactivitiesisorganisationwide.Asoftwareprocessimprovementprogramisestablishedwhichempowersthemembersoftheorganizationtoimprovetheprocessesoftheorganization.Membersoftheorganizationactivelyparticipateinteamstodevelopsoftwareprocessimprovementsforassignedprocessareas.,ProcessChangeManagement-Activities,Participationintheorganizationssoftwareprocessimprovementactivitiesisorganisationwide.Softwaremanagersandtechnicalstaffreceivefeedbackonthestatusandresultsofthesoftwareprocessimprovementactivitiesonanevent-drivenbasis.,ProcessChangeManagement-Activities,Theorganisationsstandardsoftwareprocessandtheprojectsdefinedsoftwareprocessareimprovedcontinuously.Thesoftwareprocessimprovementactivitiesareperformedinaccordancewiththesoftwareprocessimprovementplan.Softwareprocessimprovementproposalsarehandledaccordingtoadocumentedprocedure.Whereappropriate,thesoftwareprocessimprovementsareinstalledonapilotbasistodeterminetheirbenefitsandeffectivenessbeforetheyareintroducedintonormalpractice.,ProcessChangeManagement-Activities,Theorganisationsstandardsoftwareprocessandtheprojectsdefinedsoftwareprocessareimprovedcontinuously.Whenthedecisionismadetotransferasoftwareprocessimprovementintonormalpractice,theimprovementisimplementedaccordingtoadocumentedprocedure.Recordsofsoftwareprocessimprovementactivitiesaremaintained.,ChallengesinimplementingLevel5requirements,DISCUSSIONS,SUMMARY-LEVEL2,RequirementsManagementControlsystemrequirementsallocatedtosoftwaretoestablishthebaselineKeepsoftwareplans,products,andactivitiesconsistentwiththesystemrequirementsallocatedtosoftware.ChangetorequirementsarereviewedandincorporatedintothesoftwareprojectSoftwareProjectPlanningDocumentestimatesDevelopanddocumentplansEstablishcommitmentsandnegotiateInvolveallaffectedgroups,SUMMARY-LEVEL2,SoftwareprojecttrackingandoversightManagetheprojectaccordingtothedocumentedplans.Takecorrectiveactionwhenrequired.Renegotiatecommitmentsandandadjusttheplanbasedontheactualresults.SoftwaresubcontractmanagementDefinetheworktobesubcontracted.EstablishcommitmentbetweenprimeandsubcontractorSelectandmonitorthesubcontractorMaintainongoingcommunication,SUMMARY-LEVEL2,SoftwareQualityAssuranceSQAgroupisformedandtheiractivitiesareplanned.Reviewand/orauditsoftwareproductandprocessesReportresultsEscalatenoncomplianceissuesthatcannotberesolved.Involveinmakingplansfortheproject.SoftwareConfigurationManagementPlanSCMactivitiesIdentifyandmaintainconfigurationitemsSystematicallycontrolchangesMaintainintegrityandtraceabilityofbaselinethroughoutthesoftwarelifecycle,SUMMARY-LEVEL3,OrganizationProcessFocusFormagrouptocoordinatesoftwareprocessimprovementactivitiesIdentifystrengthsandweaknessesofprocessesPlanorganizationssoftwareprocessimprovementeffortsCoordinatetrainingactivitiesondefinedprocesses.OrganizationProcessDefinitionDevelopandmaintainanorganizationsstandardsoftwareprocessanddescriptionoflifecyclesapprovedforuse.Developandmaintaintailoringguidelines.Collect,review,anddistributedataanddocumentsrelatedtothestandardsoftwareprocess.,SUMMARY-LEVEL3,TrainingProgramPlan