Bài giảng Software Measurement

Nội dung text: Bài giảng Software Measurement

1. Software Measurement l Measuring software indicators: metrics and methods l Jalote-2002, Ali Arya, 2003 Software Project Management, Measurement Slide 1
2. Models Empirical Numerical Model Measurement Model Understanding/ Statistical/Math Refinement Analysis Results Results (Empirical) (Numerical) Interpretation Ali Arya, 2003 Software Project Management, Measurement Slide 2
3. Basic Concepts l Project planning and tracking need measurement l Purpose = control and visibility l Metrics (Measures), quantified process attributes • e.g. size in LOC l Plan based on organizational model and goals • e.g. using GQM method l Continuous and including phase information • e.g. defect tracking Ali Arya, 2003 Software Project Management, Measurement Slide 3
4. Core Metrics l Management • Work and progress • Budget and cost • Staffing and team dynamics l Quality • Change and stability • Modularity • Rework • MTBF Ali Arya, 2003 Software Project Management, Measurement Slide 4
5. Metrics Characteristics l Meaningful to all people involved l Quantifiable correlation between process and business l Objective and clear l Displaying trends (extrapolation) l Natural by-product of process l Automation supported l Correlated Ali Arya, 2003 Software Project Management, Measurement Slide 5
6. Frequently-Used Metrics l Size • SLOC, FP, • Consider re-use and modification • Separate definitions for different languages/system • Compared to estimation (trend) l Personnel • Number of staff • Specify experienced, support, • Lower in “total” estimates results in increase in “experienced” Ali Arya, 2003 Software Project Management, Measurement Slide 6
7. Frequently-Used Metrics l Volatility • Number of changes in requirements and defects • Includes developers’ understanding of requirements • Change in requirements has to decrease and eventually freeze l Computer Resource Utilization • CPU, memory, IO, l Schedule • Months/weeks of work • Usual to fall behind initially • Relate to actual cost Ali Arya, 2003 Software Project Management, Measurement Slide 7
8. GQM Method l Goal-Question-Metric l Goal-oriented measurement l Based on Business and process model • Business model provides the goals • Process model provides the details and sub-goals Goals Q1, Q2 Q3, Q4 M1, M2, M3 M4, M5, M6 Ali Arya, 2003 Software Project Management, Measurement Slide 8
9. GQM Steps l 1- Define business goals • High quality product • Customer satisfaction • Service improvement l 2- Provide the process model (made of entities) • Inputs (resources, policies, ) • Outputs (software, documents, ) • Activities (analysis, design, ) • Artefacts (knowledge, experience, meeting notes, ) Ali Arya, 2003 Software Project Management, Measurement Slide 9
10. GQM Steps l 3- Prepare general questions about entities (for each high-level goal) • People: Trained? (related to “quality” goal) • Reports: Signed off? • Code: Size? l 4- Group the related questions into “groups” (based on entity) and then “sub-goals” (based on objective) • Group: Documents • Sub-goal: Improved requirement analysis • Question: Requirement document ready and clear for design? Ali Arya, 2003 Software Project Management, Measurement Slide 10
11. GQM Steps l 5- Find the entities under question and all the related attributes • Entity: review meetings • Attributes: # defects found l 6- Formalized measurement goals l 7- Quantifiable questions • Metrics l 8- Data elements Ali Arya, 2003 Software Project Management, Measurement Slide 11
12. Measurement Plan Report Metrics Collect Procedures Goal Data Media Validate Ali Arya, 2003 Software Project Management, Measurement Slide 12
13. Measurement Plan l a name and definition for each unique metric; l the classification for each metric; l an association point in product development that identifies when and how data is to be collected; l definitions of the data collection forms; l the procedures for data reporting, collection,and validation; Ali Arya, 2003 Software Project Management, Measurement Slide 13
14. Analysis Plan l The last deliverable of MP is “analysis plan” l AP describes how to analyze measured data into presentation formats like charts. fault density for the reuse categories. bars are faults/KSLOC Ali Arya, 2003 Software Project Management, Measurement Slide 14