CMM二级(英文,cYerQ咨询公司).ppt

Key Practices at the Repeatable Level (Level 2),RECAPITULATION,PROJECT A,PROJECT B,PROJECT C,LEVEL 2,Reqmts. Mgt. Project Planning Project tracking SQA Config mgt. Subcontract mgt.,Reqmts. Mgt. Project Planning Project tracking SQA Config mgt. Subcontract mgt.,Reqmts. Mgt. Project Planning Project tracking SQA Config mgt. Subcontract mgt.,Level 2 - Recap.,Project focus Basic software management controls Realistic planning based on past Project tracking on schedules, costs and functionality,Level 2 KPAs,Requirements management Software project planning SW project tracking and oversight SW sub contractor management SW quality assurance SW configuration management,Requirements Management,Activities performed: SEG reviews allocated reqmts. Plans, products and activities are based on the allocated reqmts. Changes to reqmts. are reviewed and incorporated,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,Requirements Management - 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.,Requirements Management - Activities,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.,Requirements Management - Activities,Software 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.,Software Project Planning,Abilities: Apart from standard Statement of work exists Activities: SEG participates in project proposal (system level) SW life cycle defined Project plan prepared,Software Project Planning,Activities contd.: Work products identified Estimates prepared Important from metrics point of view Size, effort and cost Schedule prepared Risks identified,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 Software development plan Resources and Funding Training on Software Estimation and Planning,Software Project Planning - Common Features,Measurements to determine status of activities pertaining to Software Planning,Software Project Planning -Activities,Software estimates 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.,Software Project 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 documented Software work products are identified,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 documented. Plan for software engineering facilities and support tools are prepared,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 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,Project tracking and oversight,Activities: Monitoring done via the 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.,Software Project Tracking and Oversight - Common Features,Commitment Project software Manager is designated to be responsible 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,Software Project Tracking and Oversight - Common Features (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,Software Project Tracking 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 tracked and corrective action taken when necessary.,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 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 according to a c,Software Project Tracking and Oversight - 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.,Software Project Tracking and Oversight - 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 are recorded.,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 with 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.,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 with 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.,Software Subcontract Management,Subcontracting a defined portion of work which is an integral part of work done by prime contractor Activities: Acquisition practices Project planning and tracking Quality assurance & config. Mgt.,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 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 contract.,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 subcontract bidders ability to perform the work, according to a documented procedure.,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 contractor 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.,Software Sub contract Management - Activities,Prime contractor and the software subcontractor 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,Software Sub contract Management - Activities,The prime contractor and the 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.,SW Quality Assurance,Elements of QA and QC both Independent SQA group for each project team Implementation needs to be done carefully, especially in an ISO organization,SW Quality Assurance,Activities: Quality plan Consultancy to project team on plans, standards and procedures Review of activities (Process audits?) Work product audits /ITG/reviews,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 exists 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,Software Quality Assurance - Common Features,Measurement To determine the status, cost and schedule of SQA activities. VERIFICATION Experts independent of the SQA group periodically review the activities of SQA group,Software Quality Assurance - Activities,Software Quality Assurance activities are planned A SQA plan is prepared for the software project according to a documented procedure. The SQA groups activities are performed in accordance with the SQA plan.,Software Quality Assurance - Activities,Adherence of software products and activities to be applicable standards, procedures, and requirements is verified objectively. The SQA groups activities 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 products to verify compliance.,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 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.,SW Configuration Management,Implementation similar to that in most ISO organizations Ability: Configuration Control Board exists CM group exists,Configuration management,Unique identification of each component Assemble from components Disassemble product Ensure obsolete items are not used by mistake Important for controlling changes,Basic CM tasks,Identification of items to configure Version control Change control Configuration auditing Configuration status reporting,Baselining,A known point of integrity A CI that has been agreed upon that serves as the basis for further development and changed through formal change procedures - IEEE Stds Baselined CIs kept in Project library Check in / Check out,Configuration Status Reporting,Also called status accounting Document master list CI Index Either soft or hard copy Always kept current,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 performing SCM activities. Training to Software engineering group to perform SCM activities MEASUREMENTS To determine the status of the SCM activities,Software Configuration Management - Activities,Software Configuration Management activities are planned. A SCM plan is prepared for each software project according to a documented procedure. A documented and approved SCM plan is used as the basis for performing the SCM activities.,Software Configuration Management - Activities,Selected software work products are identified, controlled, and available. A documented 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 baseline library are created and their release is controlled according to a documented procedure,Software Configuration Management - Activities,Changes to identified software work products are controlled. Change requests and problem reports for all configuration items/units are initiated, recorded, reviewed, approved, and tracked according to a documented procedure. Changes to baselines are controlled according to a documented procedure.,Software Configuration Management - Activities,Affected groups and individuals are informed of the status and content of software 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 conducted according to a documented procedure.,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,EXERCISE,What are the measures you may need for Project Tracking and oversight? What are the measures you may need for Project Planning? Time - 5 mins. + 5 mins.,Key Practices at the Defined Level (Level 3),Miscellany,Mil standards / IEEE standards CMM vs. ISO Why CMM - Discussion Potential benefits of CMM - Discussion Challenges / next steps,PROCESS QUALITY MODELS,ISO 9000 FAMILY OF STANDARDS SEI CMM Military (MiL) STANDARDS IEEE STANDARDS MALCOLM BALDRIDGE AWARD SPICE,MILITARY STANDARDS,Often called MiL standards Deptt of Defense, USA Focussed on systems development for Defense applications Detailed process descriptions - how tos are also defined,MILITARY STANDARDScontd.,For SW development: MiL 2167A - Life Cycle activities MiL 1521B - Verification and Validation MiL 498 Independent audit,IEEE STANDARDS,IEEE SW Engineering Standards Collection (1994 edition) A set of 27 recommended guidelines Hence, detailed process descriptions are given for all aspects of SW Engineering,IEEE STANDARDScontd.,Important standards are: IEEE 730 - Quality Assurance Plans IEEE 828 - Configuration Management Plans IEEE 829 - SW Test Documentation IEEE 830 - Requirement Specifications IEEE 1016 - Design Descriptions IEEE 1028 - Reviews and Audits,IEEE STANDARDScontd.,IEEE 1058 - Project Management Plans IEEE 1045 - Productivity Metrics IEEE 1061 - Quality Metrics IEEE 1219 - SW Maintenance IEEE 1074 - Developing SW Life Cycle processes IEEE 1298 - SW Quality Management Systems,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-3,ISO 8402,Other Guidelines,ISO 9000,ISO 9001,ISO 9000-3,ISO 9003,ISO 9002,ISO 9004-2,ISO 9000 FAMILY OF STANDARDS,Scope of ISO 9001 - Product Design, development and service,In-goods,Design,Produce,Inspect & Test,Install,Service,Scope of ISO 9002 - Production and Installation,In-goods,Produce,Inspect & Test,Install,Service,Scope of ISO 9003 - Inspection and Testing,Inspect & Test,Install,Comparison of CMM with ISO,ISO is a “pass - fail” standard CMM has various levels - you will always be at one level or the other CMM explicitly provides for continuous improvement Strong emphasis on metrics,CMM vs. ISO,Equivalence of ISO to CMM = 2.7, according to a paper by Mark Paulk However, ISO has many attributes of Level 3, 4 and 5 as well Hence, this number can be misleading,CMM vs. ISO,ISO A quick way to bring about process discipline across the organization May lead to dissimilar implementations Not developed with software industry in mind May not lead to institutionalization and, thus, lasting benefits may not be there,CMM vs. ISO,CMM Helps to institutionalize Quantitative focus at higher levels Developed for software industry Explicit a