软件度量十二步详解.ppt

12 Steps to Useful Software Metrics Linda Westfall What are Software Metrics? Measurement Defined Two Historic Schools of Thought Collect data on everything -- then find meaning Implement a random selection of metrics Step 1 - Identify Metrics Customers Who needs the information? Who’s going to use the metrics? Step 2 - Target Goals Organizational goals Be the low cost provider Meet projected revenue targets Frustrations Goals Project manager: our estimated project schedules always end up being way off. Functional manager: if we have another late delivery... Engineer: too much overtime -- not enough time to do things right Test manager: no time left to test product before it is scheduled to ship Step 3 - Ask Questions Goal: Maintain a high level of customer satisfaction What is our current level of customer satisfaction? What attributes of our products and services are most important to our customers? How do we compare with our competition? Turning Questions into Lower Level Goals High level goal: Ship only defect free software Questions: Is software adequately tested? How many defects are still undetected? Are all known defects corrected? Lower level goal: Ensure all known defects are corrected before shipment Step 4 - Select Metrics Select metrics that provide information to help answer the questions Be practical, realistic, pragmatic Consider current engineering environment Start with the possible Selecting Metrics Goal: Ensure all known defects are corrected before shipment Role of Measurement Metrics Objective Statement Template Example - Metric: % defects corrected Benefits Clearly defined metric objectives: Ensures a well defined metric based on customer goals Eliminates misunderstandings Communicates need Provides requirements statement Step 5 - Standardize Definitions Standardize Definitions Select definitions from the literature that match your organizational goals Use them as a basis for creating your