A Small Truth

533 views
462 views

Published on

Published in: Spiritual, Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
533
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

A Small Truth

  1. 1. CAPABILITY MATURITY MODEL for Software (CMM) Version 1.1 Maturity Level – 4 (Managed Level)
  2. 2. Characteristics of a Level 4 Organization <ul><li>At level 3, measurements have been defined and collected systematically </li></ul><ul><li>At level 4, decisions are made based on data collected </li></ul><ul><li>The ORGANISATION sets quantitative goals for both software products and processes. </li></ul><ul><li>The process performance of a project is controlled quantitatively. </li></ul>
  3. 3. Key Process Areas <ul><li>Quantitative process management </li></ul><ul><li>Software quality management </li></ul>
  4. 4. Quantitative Process Management <ul><li>Purpose is to control the process performance of the software project quantitatively </li></ul><ul><li>Involves </li></ul><ul><ul><li>Establishing goals for process performance </li></ul></ul><ul><ul><li>Measuring the performance of the project </li></ul></ul><ul><ul><li>Analyzing these measurements making adjustments to maintain process performance within acceptable limits </li></ul></ul>
  5. 5. QPM - Common Features <ul><li>Commitment </li></ul><ul><ul><li>Written organizational policy for measuring and quantitatively controlling the performance of the project’s defined software process </li></ul></ul>
  6. 6. QPM - Common Features <ul><li>Ability </li></ul><ul><ul><li>Group that is responsible for coordinating the quantitative process management activities should exist. </li></ul></ul><ul><ul><li>Adequate resources and funding </li></ul></ul><ul><ul><li>Support for collecting, recording and analyzing data </li></ul></ul><ul><ul><li>Training on quantitative process management for personnel performing these activities </li></ul></ul><ul><ul><li>Orientation to software engineering group on the goals and value of quantitative process management </li></ul></ul><ul><li>Measurement </li></ul><ul><ul><li>To determine the status of the quantitative process management activities. </li></ul></ul>
  7. 7. QPM - Activities <ul><li>The quantitative process management activities are planned. </li></ul><ul><ul><li>The software project's plan for quantitative process management is developed according to a documented procedure. </li></ul></ul><ul><ul><li>The software project's quantitative process management activities are performed in accordance with the project's quantitative process management plan. </li></ul></ul><ul><ul><li>The strategy for the data collection and the quantitative analyses to be performed are determined based on the project's defined software process. </li></ul></ul>
  8. 8. QPM - Activities <ul><li>The process performance of the project’s defined software process is controlled quantitatively. </li></ul><ul><ul><li>The software project's quantitative process management activities are performed in accordance with the project's quantitative process management plan. </li></ul></ul>
  9. 9. QPM - Activities <ul><li>The process performance of the project’s defined software process is controlled quantitatively. </li></ul><ul><ul><li>The measurement data used to control the project's defined software process quantitatively are collected according to a documented procedure. </li></ul></ul><ul><ul><li>The project's defined software process is analyzed and brought under quantitative control according to a documented procedure. </li></ul></ul><ul><ul><li>Reports documenting the results of the software project's quantitative process management activities are prepared and distributed. </li></ul></ul>
  10. 10. Software Quality Management <ul><li>Purpose </li></ul><ul><ul><li>Is to develop a quantitative understanding of the quality of the project’s software products and achieve specific quality goals </li></ul></ul><ul><li>Involves </li></ul><ul><ul><li>Defining quality goals for the software products </li></ul></ul><ul><ul><li>Establishing plans to achieve these goals </li></ul></ul><ul><ul><li>Monitoring and adjusting software plans, software work products, activities and quality goals to satisfy the needs and desires of customer and end-user </li></ul></ul>
  11. 11. SQM - Common Features <ul><li>Commitment </li></ul><ul><ul><li>Written organizational policy for managing software quality. </li></ul></ul><ul><li>Ability </li></ul><ul><ul><li>Adequate resources and funding </li></ul></ul><ul><ul><li>Training to individuals to perform quality management activities </li></ul></ul><ul><li>Measurement </li></ul><ul><ul><li>To determine the status of software quality management activities. </li></ul></ul>
  12. 12. SQM - Activities <ul><li>The project’s software quality management activities are planned. </li></ul><ul><ul><li>The project's software quality plan is developed and maintained according to a documented procedure. </li></ul></ul><ul><ul><li>The project's software quality plan is the basis for the project's activities for software quality management. </li></ul></ul><ul><li>Measurable goals for software product quality and their priorities are defined. </li></ul><ul><ul><li>The project's quantitative quality goals for the software products are defined, monitored, and revised throughout the software life cycle. </li></ul></ul><ul><ul><li>The software project's quantitative quality goals for the products are allocated appropriately to the subcontractors delivering software products to the project. </li></ul></ul>
  13. 13. SQM - Activities <ul><li>Actual progress toward achieving the quality goals for the software products is quantified and managed. </li></ul><ul><ul><li>The project's software quality plan is the basis for the project's activities for software quality management </li></ul></ul><ul><ul><li>The quality of the project's software products is measured, analyzed, and compared to the products' quantitative quality goals on an event-driven basis. </li></ul></ul>
  14. 14. End of Managed Level (L4) KPAs

×