CMM二級(jí)英文cYerQ咨詢公司學(xué)習(xí)教案

1、Key Practices at theRepeatable Level (Level 2)第1頁/共82頁第一頁，共83頁。RECAPITULATIONPROJECT APROJECT BPROJECT C LEVEL 2Reqmts. Mgt. Project PlanningProject trackingSQAConfig mgt.Subcontract mgt.Reqmts. Mgt. Project PlanningProject trackingSQAConfig mgt.Subcontract mgt.Reqmts. Mgt. Project PlanningProject t

2、rackingSQAConfig mgt.Subcontract mgt.第2頁/共82頁第二頁，共83頁。Level 2 - Recap. Project focus Basic software management controls Realistic planning based on past Project tracking on schedules, costs and functionality第3頁/共82頁第三頁，共83頁。Level 2 KPAs Requirements management Software project planning SW project tr

3、acking and oversight SW sub contractor management SW quality assurance SW configuration management第4頁/共82頁第四頁，共83頁。Requirements Management Activities performed: SEG reviews allocated reqmts. Plans, products and activities are based on the allocated reqmts. Changes to reqmts. are reviewed and incorpo

4、rated第5頁/共82頁第五頁，共83頁。Requirements Management - Common Features COMMITMENT Written Organizational Policy for managing System requirements ABILITY Allocated requirements are documented MEASUREMENTS to determine status of activities pertaining to Requirements Management第6頁/共82頁第六頁，共83頁。Requirements Ma

5、nagement - Activities System requirements allocated to software are controlled to establish a baseline for software engineering and management use. Software Engineering Group Reviews the allocated requirements before they are incorporated into the project.第7頁/共82頁第七頁，共83頁。Requirements Management - A

6、ctivities Software plans, products, activities are kept consistent with the system requirements allocated to software. The Software Engineering Group uses the allocated requirements as the basis for software plans, work products and activities.第8頁/共82頁第八頁，共83頁。Requirements Management - Activities So

7、ftware plans, products, activities are kept consistent with the system requirements allocated to software. Changes to the allocated requirements are reviewed and incorporated into the software project.第9頁/共82頁第九頁，共83頁。Software Project Planning Abilities: Apart from standard Statement of work exists

8、Activities: SEG participates in project proposal (system level) SW life cycle defined Project plan prepared第10頁/共82頁第十頁，共83頁。Software Project Planning Activities .contd.: Work products identified Estimates prepared Important from metrics point of view Size, effort and cost Schedule prepared Risks id

9、entified第11頁/共82頁第十一頁，共83頁。 Software Project Planning - Common Features Commitments A project software manager is designated to be responsible for project activities Written organizational policy for planning a software project Ability Approved Statement of Work Responsibilities for developing Softw

10、are development plan Resources and Funding Training on Software Estimation and Planning第12頁/共82頁第十二頁，共83頁。 Software Project Planning - Common Features Measurements to determine status of activities pertaining to Software Planning第13頁/共82頁第十三頁，共83頁。 Software Project Planning -Activities Software esti

11、mates are documented for use in planning and tracking of software projects. Estimates for size (or changes to size), effort and cost, critical computer resources, software schedule are derived according to a documented procedure. Software planning data are recorded.第14頁/共82頁第十四頁，共83頁。 Software Proje

12、ct Planning -Activities Software project activities and commitments are planned and documented. Project planning is initiated in the early stages A software life cycle with predefined stages of manageable size is defined Software development plan is defined according to a documented procedure and do

13、cumented Software work products are identified第15頁/共82頁第十五頁，共83頁。 Software Project Planning -Activities Software project activities and commitments are planned and documented. Risks associated with cost, resource, schedule and technical aspects of the software project are identified, assessed and do

14、cumented. Plan for software engineering facilities and support tools are prepared第16頁/共82頁第十六頁，共83頁。 Software Project Planning -Activities Affected groups and individuals agree to their commitments related to the software project. Software Engineering group participates in the project proposal team

15、and with other groups in the overall project planning. Project commitments made to individuals and groups external / internal to the organization are reviewed with Senior Management according to a documented procedure第17頁/共82頁第十七頁，共83頁。Project tracking and oversight Activities: Monitoring done via t

16、he Plan Plan updated as and when reqd. Scope of work, effort, schedule, risks tracked and data recorded Progress review meetings; both project team and senior mgt.第18頁/共82頁第十八頁，共83頁。Software Project Tracking and Oversight - Common Features Commitment Project software Manager is designated to be resp

17、onsible for the projects activities and results. Written organizational policy for managing software projects Ability Software development plan is documented and approved Responsibility for every work product is assigned explicitly第19頁/共82頁第十九頁，共83頁。Software Project Tracking and Oversight - Common F

18、eatures (contd.) Resources and funding for tracking Training on technical and personnel aspects of the software project Orientation on Technical aspects of the project for Software Managers. Measurements to determine the status of Project tracking activities第20頁/共82頁第二十頁，共83頁。Software Project Tracki

19、ng and Oversight - Activities Actual results and performances are tracked against the software plans. A documented Software Development Plan is used The size of the work product, effort and cost, critical computer resources, software schedule, software engineering and technical activities are tracke

20、d and corrective action taken when necessary.第21頁/共82頁第二十一頁，共83頁。Software Project Tracking and Oversight - Activities (contd) Risks associated with cost, resource, schedule and technical aspects are tracked Actual measurement data and replanning data are recorded Software engineering group conducts

21、periodic internal reviews and track technical progress, plan, performance, and issues against the software development plan. Formal reviews to address the accomplishments and results of the project are conducted at selected project milestones 第22頁/共82頁第二十二頁，共83頁。Software Project Tracking and Oversig

22、ht - Activities Corrective actions are taken and managed to closure when actual results and performance deviate significantly from the software plans. The projects software development plan is revised according to a documented procedure. 第23頁/共82頁第二十三頁，共83頁。Software Project Tracking and Oversight -

23、Activities (contd) The size of the work products, changes to size, effort and costs, critical computer resources,k software schedule and engineering technical activities are tracked and corrective actions are taken as necessary. Actual measurement data and replanning data for the software project ar

24、e recorded.第24頁/共82頁第二十四頁，共83頁。Software Project Tracking and Oversight - Activities Changes to software commitments are agreed to by the affected groups and individuals. Software project commitments and changes to commitments made to individuals and groups external to the organization are reviewed w

25、ith senior management according to a documented procedure. Approved changes to commitments that affect the software project are communicated to the members of the software engineering group and other software related groups.第25頁/共82頁第二十五頁，共83頁。Software Project Tracking and Oversight - Activities Cha

26、nges to software commitments are agreed to by the affected groups and individuals. Software project commitments and changes to commitments made to individuals and groups external to the organization are reviewed with senior management according to a documented procedure. Approved changes to commitme

27、nts that affect the software project are communicated to the members of the software engineering group and other software related groups.第26頁/共82頁第二十六頁，共83頁。Software Subcontract Management Subcontracting a defined portion of work which is an integral part of work done by prime contractor Activities:

28、 Acquisition practices Project planning and tracking Quality assurance & config. Mgt.第27頁/共82頁第二十七頁，共83頁。Software Sub contract Management - Common Features Commitment Written organizational policy for Managing the software sub contract. A sub contract manager is designated to be responsible for

29、establishing and managing the software sub contract. Ability Adequate resources and funding Training for those who manage sub contract activity on performing sub contract related activities and technical aspects. Measurements To determine the status of the activities for managing the software sub co

30、ntract.第28頁/共82頁第二十八頁，共83頁。Software Sub contract Management - Activities The prime contractor selects qualified software sub contractors. The work to be sub contracted is defined and planned according to a documented procedure. The software subcontractor is selected, based on an evaluation of the su

31、bcontract bidders ability to perform the work, according to a documented procedure.第29頁/共82頁第二十九頁，共83頁。Software Sub contract Management - Activities (contd) The prime contractor and the software subcontractor agree to their commitments to each other. The contractual agreement between the prime contr

32、actor and the software subcontractor is used as the basis for managing the subcontract. A documented subcontractors software development plan is reviewed and approved by the prime contractor.第30頁/共82頁第三十頁，共83頁。Software Sub contract Management - Activities Prime contractor and the software subcontrac

33、tor agree to their commitments to each other. Changes to the software subcontractors statement of work, subcontract terms and conditions and other commitments are resolved according to a documented procedure第31頁/共82頁第三十一頁，共83頁。Software Sub contract Management - Activities The prime contractor and th

34、e software subcontractor maintain ongoing communications. The prime contractors management conducts periodic status/ coordination reviews with the software subcontractors management Periodic technical reviews and interchanges are held with the software subcontractor.第32頁/共82頁第三十二頁，共83頁。SW Quality As

35、surance Elements of QA and QC both Independent SQA group for each project team Implementation needs to be done carefully, especially in an ISO organization第33頁/共82頁第三十三頁，共83頁。SW Quality Assurance Activities: Quality plan Consultancy to project team on plans, standards and procedures Review of activi

36、ties (Process audits?) Work product audits /ITG/reviews 第34頁/共82頁第三十四頁，共83頁。Software Quality Assurance - Common Features Commitment Written organizational policy for implementing software quality assurance Ability A group that is responsible for coordinating and implementing SQA for the project exis

37、ts Adequate resources and funding Members of SQA group are trained to perform their SQA activities. Orientation to members of the projects on SQA activities and roles and responsibilities第35頁/共82頁第三十五頁，共83頁。Software Quality Assurance - Common Features Measurement To determine the status, cost and sc

38、hedule of SQA activities. VERIFICATION Experts independent of the SQA group periodically review the activities of SQA group第36頁/共82頁第三十六頁，共83頁。Software Quality Assurance - Activities Software Quality Assurance activities are planned A SQA plan is prepared for the software project according to a docu

39、mented procedure. The SQA groups activities are performed in accordance with the SQA plan.第37頁/共82頁第三十七頁，共83頁。Software Quality Assurance - Activities Adherence of software products and activities to be applicable standards, procedures, and requirements is verified objectively. The SQA groups activit

40、ies are performed in accordance with the SQA plan The SQA group participates in the preparation and review of the projects software development plan, standards and procedures. The SQA group reviews the software engineering activities to verify compliance The SQA group audits designated software work

41、 products to verify compliance.第38頁/共82頁第三十八頁，共83頁。Software Quality Assurance - Activities Affected groups and individuals are informed of software quality assurance activities and results. The SQA group periodically reports the results of its activities to the software engineering group. Deviations

42、 identified in the software activities and software work products are documented and handled according to a documented procedure. The SQA group conducts periodic reviews of its activities and findings with customers SQA personnel, as appropriate.第39頁/共82頁第三十九頁，共83頁。SW Configuration ManagementImpleme

43、ntation similar to that in most ISO organizations Ability: Configuration Control Board exists CM group exists第40頁/共82頁第四十頁，共83頁。Configuration management Unique identification of each component Assemble from components Disassemble product Ensure obsolete items are not used by mistakeImportant for con

44、trolling changes第41頁/共82頁第四十一頁，共83頁。Basic CM tasks Identification of items to configure Version control Change control Configuration auditing Configuration status reporting第42頁/共82頁第四十二頁，共83頁。Baselining A known point of integrity A CI that has been agreed upon that serves as the basis for further de

45、velopment and changed through formal change procedures - IEEE Stds Baselined CIs kept in Project library Check in / Check out第43頁/共82頁第四十三頁，共83頁。Configuration Status Reporting Also called status accounting Document master list CI Index Either soft or hard copy Always kept current第44頁/共82頁第四十四頁，共83頁。

46、Software Configuration Management - Common Features Commitment A written organizational policy for implementing SCM. Ability A software configuration control board exists. SCM group for a project exist Adequate resources and funding Training to SCM group on objectives, procedures and methods of perf

47、orming SCM activities. Training to Software engineering group to perform SCM activities MEASUREMENTS To determine the status of the SCM activities第45頁/共82頁第四十五頁，共83頁。Software Configuration Management - Activities Software Configuration Management activities are planned. A SCM plan is prepared for ea

48、ch software project according to a documented procedure. A documented and approved SCM plan is used as the basis for performing the SCM activities.第46頁/共82頁第四十六頁，共83頁。Software Configuration Management - Activities Selected software work products are identified, controlled, and available. A documente

49、d and approved SCM plan is used as the basis for performing the SCM activities. A configuration management library system is established as a repository for the software baselines. The software work products to be placed under configuration management are identified. Products from the software basel

50、ine library are created and their release is controlled according to a documented procedure第47頁/共82頁第四十七頁，共83頁。Software Configuration Management - Activities Changes to identified software work products are controlled. Change requests and problem reports for all configuration items/units are initiat

51、ed, recorded, reviewed, approved, and tracked according to a documented procedure. Changes to baselines are controlled according to a documented procedure.第48頁/共82頁第四十八頁，共83頁。Software Configuration Management - Activities Affected groups and individuals are informed of the status and content of soft

52、ware baselines. The status of configuration items/units is recorded according to a documented procedure. Standard reports documenting the SCM activities and the contents of the software baseline are developed and made available to affected groups and individuals. Software baseline audits are conduct

53、ed according to a documented procedure.第49頁/共82頁第四十九頁，共83頁。You may refer to TR 25 now. How would you fulfil the requirements of SQA? How are you placed vis a vis Requirements Management KPA?Time - 5 mins. + 5 mins.EXERCISE第50頁/共82頁第五十頁，共83頁。EXERCISE What are the measures you may need for Project Tra

54、cking and oversight? What are the measures you may need for Project Planning?Time - 5 mins. + 5 mins.第51頁/共82頁第五十一頁，共83頁。Key Practices at the Defined Level (Level 3)第52頁/共82頁第五十二頁，共83頁。Miscellany Mil standards / IEEE standards CMM vs. ISO Why CMM - Discussion Potential benefits of CMM - Discussion C

55、hallenges / next steps第53頁/共82頁第五十三頁，共83頁。PROCESS QUALITY MODELS ISO 9000 FAMILY OF STANDARDS SEI CMM Military (MiL) STANDARDS IEEE STANDARDS MALCOLM BALDRIDGE AWARD SPICE第54頁/共82頁第五十四頁，共83頁。MILITARY STANDARDS Often called MiL standards Deptt of Defense, USA Focussed on systems development for Defen

56、se applications Detailed process descriptions - how tos are also defined第55頁/共82頁第五十五頁，共83頁。MILITARY STANDARDScontd. For SW development: MiL 2167A - Life Cycle activities MiL 1521B - Verification and Validation MiL 498 Independent audit第56頁/共82頁第五十六頁，共83頁。IEEE STANDARDS IEEE SW Engineering Standards

57、 Collection (1994 edition) A set of 27 recommended guidelines Hence, detailed process descriptions are given for all aspects of SW Engineering第57頁/共82頁第五十七頁，共83頁。IEEE STANDARDScontd. Important standards are: IEEE 730 - Quality Assurance Plans IEEE 828 - Configuration Management Plans IEEE 829 - SW T

58、est Documentation IEEE 830 - Requirement Specifications IEEE 1016 - Design Descriptions IEEE 1028 - Reviews and Audits第58頁/共82頁第五十八頁，共83頁。IEEE STANDARDScontd. IEEE 1058 - Project Management Plans IEEE 1045 - Productivity Metrics IEEE 1061 - Quality Metrics IEEE 1219 - SW Maintenance IEEE 1074 - Deve

59、loping SW Life Cycle processes IEEE 1298 - SW Quality Management Systems第59頁/共82頁第五十九頁，共83頁。Comparison of CMM with ISO ISO 9000 - A quick recap: Standards are ISO 9001, 9002 and 9003 Guidelines for SW industry - 9000-3 Thus, applicable standard for SW industry is ISO 9001 as interpreted by ISO 9000-

60、3第60頁/共82頁第六十頁，共83頁。ISO 8402Other GuidelinesISO 9000ISO 9001ISO9000-3ISO 9003ISO 9002ISO9004-2ISO 9000 FAMILY OF STANDARDS第61頁/共82頁第六十一頁，共83頁。Scope of ISO 9001- Product Design, development and serviceIn-goods DesignProduceInspect & TestInstallService第62頁/共82頁第六十二頁，共83頁。Scope of ISO 9002 - Production and Installat