《CMM五级(英文,cYerQ咨询公司).ppt》由会员分享，可在线阅读，更多相关《CMM五级(英文,cYerQ咨询公司).ppt（37页珍藏版）》请在三一办公上搜索。
1、Introduction to CMMVer 1.1OPTIMIZING LEVEL,TYPICAL CHARACTERISTICS OF A OPTIMIZING LEVEL ORGANISATION,At level 4,the process is quantitatively understoodAt level 5,continuous process improvement is a way of life.The focus is on preventing the occurrence of defects and innovations.,Typical Characteri
2、stics of a Optimizing Level Organisation,In immature organizations,no one may be responsible for process improvementMature organizations usually have 70-80%participation in improvement activities at any given point in time-everyone is involved.Continuous process improvement means controlled change a
3、nd measurably improving process capability,KEY PROCESS AREAS,Process change measurementTechnology change managementDefect prevention,DEFECT PREVENTION,Purpose is to identify the cause of defects and prevent them from recurringInvolvesAnalyzing defects that were encountered in the past.Taking specifi
4、c actions to prevent the occurrence of these types of defects in the future.Trends are analyzed to track the types of defects that have been encountered and to identify defects that are likely to recur.,Defect Prevention-Common Features,CommitmentWritten organizational policy/and policy for the proj
5、ect for defect prevention activities.AbilityTeam that is responsible for coordinating the defect prevention activities should exist at the organization level and project level.Adequate resources and fundingTraining on defect prevention for personnel performing these activities,Defect Prevention-Comm
6、on Features(contd),MeasurementTo determine the status of the defect prevention activities.,Defect Prevention-Activities,Defect prevention activities are planned.The software project develops and maintains a plan for its defect prevention activities.At the beginning of a software task,the members of
7、the team performing the task meet to prepare for the activities of that task and the related defect prevention activities.,Defect Prevention-Activities,Common Causes of Defects Are Sought Out and Identified.Causal analysis meetings are conducted according to a documented procedure.Defect prevention
8、data are documented and tracked across the teams coordinating defect prevention activities.,Defect Prevention-Activities,Common causes of defects are prioritized and systematically eliminated.The teams assigned to coordinate defect prevention activities meets on a periodic basis to review and coordi
9、nate implementation of action proposals from the causal analysis meetings.Revisions to the organizations OSSP resulting from defect prevention actions are incorporated adocprocRevisions to the projects DSP resulting from defect prevention actions are incorporated adocprocMembers of the software engi
10、neering group and software-related groups receive feedback on the status and results of the organizations and projects defect prevention activities on a periodic basis.,Defect Prevention-Summary,Why did defects occur?Causal analysisSpecial causesCommon causesRemove common causes,thus preventing defe
11、cts from recurring,Defect Prevention-Summary,Teams exist at org.level and project level to coordinate defect prevention activitiesProject has a defect prevention planCausal analysis meetings heldAction points are implemented Defect prevention data tracked,Defect Prevention-Summary,Changes made to OS
12、SP.Changes made to defined SW processMeasurements include defect age,cost of quality,defect density etc.,TECHNOLOGY CHANGE MANAGEMENT,Purpose is to identify new technologies(i.e.,Tools,methods,and processes)and transfer them in an organization in an orderly manner.InvolvesIdentifying,selecting,and e
13、valuating new technologies(tools,methods and processes).Pilot efforts are performed to assess new technologies.Incorporating effective technologies into the organization.,Technology Change Management-Common Features,COMMITMENTWritten organizational policy for managing software quality.Senior Managem
14、ent sponsors and oversees the technology change management activities.ABILITYGroup that is responsible for technology change management activities exists.Adequate resources and funding Support for collecting and analyzing data needed to evaluate technology changesMEASUREMENTTo determine the status o
15、f Technology change management activities.,Technology Change Management-Activities,Incorporation of technology changes are planned.The organization develops and maintains a plan for technology change management.,Technology Change Management-Activities,New technologies are evaluated to determine thei
16、r effect on quality and productivity.The group responsible for the organizations TCM activities works with the software projects in identifying areas of technology change.The group responsible for the organizations TCM analyzes the OSSP to identify areas that need or could benefit from new technolog
17、y.Technologies are selected and acquired for the organization and software projects adocprocPilot efforts for improving technology are conducted,where appropriate,before a new technology is introduced into normal practice.,Technology Change Management-Activities,Appropriate New Technologies Are Tran
18、sferred Into Normal Practice Across the Organization.Software managers and technical staff are kept informed of new technologies.Appropriate new technologies are incorporated into the organizations standard software process according to a documented procedure.Appropriate new technologies are incorpo
19、rated into the projects defined software processes according to a documented procedure.,Technology Change Management,Identify new technologies and track them into organization in an orderly mannerTechnology support groupPilots done first;then incorporated into normal practice,Technology Change Manag
20、ement,Analysis of processes to identify areas that could benefit from new technology-based on dataTechnologies selected&acquiredPilots carried outIncorporated into standard process,PROCESS CHANGE MNGT.,Purpose Is to Continuously Improve the Software Process Used in the Organization With the Intent o
21、f Improving Software Quality,Increasing Productivity,and Decreasing the Cycle Time for Product DevelopmentInvolvesDefining process improvement goalsSystematically identifying,evaluating,and implementing improvements to the organizations standard software process and the projects defined software pro
22、cesses,Process Change Management-Common Features,COMMITMENTWritten organizational policy for implementing software process improvements.Senior Management sponsorship for software process improvement.ABILITYAdequate resources and fundingTraining for software managers in software process improvement.S
23、enior Management receives required training in software process improvement.MEASUREMENTTo determine the status of the software process improvement activities.,Process Change Management-Activities,Continuous Process Improvement Is Planned.The group responsible for the organizations software process a
24、ctivities(e.g.,software engineering process group)coordinates the software process improvement activities.The organization develops and maintains a plan for software process improvement according to a documented procedure.The software process improvement activities are performed in accordance with t
25、he software process improvement plan.,Process Change Management-Activities,Participation in the organizations software process improvement activities is organisation wide.A software process improvement program is established which empowers the members of the organization to improve the processes of
26、the organization.Members of the organization actively participate in teams to develop software process improvements for assigned process areas.,Process Change Management-Activities,Participation in the organizations software process improvement activities is organisation wide.Software managers and t
27、echnical staff receive feedback on the status and results of the software process improvement activities on an event-driven basis.,Process Change Management-Activities,The organisations standard software process and the projects defined software process are improved continuously.The software process
28、 improvement activities are performed in accordance with the software process improvement plan.Software process improvement proposals are handled according to a documented procedure.Where appropriate,the software process improvements are installed on a pilot basis to determine their benefits and eff
29、ectiveness before they are introduced into normal practice.,Process Change Management-Activities,The organisations standard software process and the projects defined software process are improved continuously.When the decision is made to transfer a software process improvement into normal practice,t
30、he improvement is implemented according to a documented procedure.Records of software process improvement activities are maintained.,Challenges in implementing Level 5 requirements,DISCUSSIONS,SUMMARY-LEVEL 2,Requirements ManagementControl system requirements allocated to software to establish the b
31、aselineKeep software plans,products,and activities consistent with the system requirements allocated to software.Change to requirements are reviewed and incorporated into the software projectSoftware Project Planning Document estimatesDevelop and document plansEstablish commitments and negotiateInvo
32、lve all affected groups,SUMMARY-LEVEL 2,Software project tracking and oversightManage the project according to the documented plans.Take corrective action when required.Renegotiate commitments and and adjust the plan based on the actual results.Software subcontract managementDefine the work to be su
33、bcontracted.Establish commitment between prime and subcontractorSelect and monitor the subcontractorMaintain ongoing communication,SUMMARY-LEVEL 2,Software Quality AssuranceSQA group is formed and their activities are planned.Review and/or audit software product and processesReport resultsEscalate n
34、oncompliance issues that cannot be resolved.Involve in making plans for the project.Software Configuration ManagementPlan SCM activitiesIdentify and maintain configuration itemsSystematically control changesMaintain integrity and traceability of baseline throughout the software life cycle,SUMMARY-LE
35、VEL 3,Organization Process FocusForm a group to coordinate software process improvement activitiesIdentify strengths and weaknesses of processesPlan organizations software process improvement effortsCoordinate training activities on defined processes.Organization Process DefinitionDevelop and mainta
36、in an organizations standard software process and description of life cycles approved for use.Develop and maintain tailoring guidelines.Collect,review,and distribute data and documents related to the standard software process.,SUMMARY-LEVEL 3,Training ProgramPlan organizational training activitiesPr
37、ovide training for developing skills and knowledge for the organizationEnsure that individuals are trainedDevelop standards for developing and delivering training programs.Integrated Software ManagementDevelop the projects defined software processManage the project according to a plan which includes
38、 the projects defined software processTake corrective action as appropriate.,SUMMARY-LEVEL 3,Software Product EngineeringPerform software activities in a defined,integrated,and consistent mannerEnsure consistency between productsCollect measures to determine process efficiency and defects.Intergroup
39、 CoordinationInvolve all affected groupsEnsure commitments are agreed to by all affected partiesIdentify,track,and resolve intergroup issuesPeer ReviewsPlan peer review activitiesIdentify and remove defects,SUMMARY-LEVEL 4,Quantitative Process ManagementDefine plan for quantitative process Managemen
40、t.Define strategy for data collection and analysisReport the results of quantitative process Management.Establish process capability baseline for the organizations standard software process.Software Quality Management Develop quality plan for the project.Set quality goals for project and work produc
41、tsMonitor and revise product goals throughout the software life cycle.,SUMMARY-LEVEL 5,Defect Preventiondevelop and maintain a plan for defect prevention.conduct causal analysis meetings.prioritize and plan for removal of defectstrack the progress made on defect preventionTechnology Change Managemen
42、tdevelop and maintain a plan for technology changes.identify processes/areas that would benefit from new technology.evaluate and acquire new technologies.conduct pilot efforts for improving technology.,SUMMARY-LEVEL 5,Process Change ManagementEstablish process improvement program and develop a plan for process improvementImprovements are transferred across the organization.,
