Team Assignment 15 Team 04 Class K15T2

Agenda 1. Introduction 2. Measurement process 3. GQM 4. Strength Weakness of metrics

Introduction The primary purpose of measurement is to provide insight into software process and products so that Viking team is better able to make decisions and manage the achievement of goals. This report proposes some plan that can help team integrate a measurement process with their overall software process.

Purpose Purpose Measurement is often equated with collecting and reporting data and focuses on presenting the numbers. The primary purpose of this report is to focus measurement more on setting goals, analyzing data with respect to software issues and manage project, and using the data to make decisions.

Scope This plan addresses all the activities for software development projects including planning, requirement analysis, project tracking, quality assurance, configuration management, design, and coding related procedures. The result of these measurements will be reported to ABC Systems Project Manager

Overview Measurement Goals: The goals of te measurement program relative to the projet in term of achievement, improvement and quality. Metrics: the metrics that are to be synthesized at regulated intervals on the project to support the goals Measurement process: provide the step by step to team to act for exactly and easy to implement collect and validate history data as well as improve process Time and role: this is table provide role to each members responsible for the metric to collect weekly, monthly or each release.

Agenda 1. Introduction 2. Measurement process 3. GQM 4. Strength Weakness of metrics

Measurement process Define procedures -Measures -Collection -Analysis -Feedback Identify scope -Objectives -Issues -Measures Collect data -Record and store data -Review and revise procedures Analyze data -Prepare reports -Present reports -Review and revise procedures - Evolve process -Evaluate progress -Evaluate process Planning Implementing Improving

Measurement process Activity in software measurement process Purpose Identify scope/ define procedure(plan) Estimate a purpose, plan and procedure for measurement tied to organization goals ImplementExecute the plan to collect data Analyze Analyze data to determine progress toward measurement goals. Evaluate and improve process Make decision based on the progress towards goals and recommend improvements on measurement process being used.

Agenda 1. Introduction 2. Measurement process 3. GQM 4. Strength Weakness of metrics

GQM Finish project on time Improve quality 20% How is current progres s of project? How many issues are there in project? How many percent defect decrease when release? Is the end user satisfied ? What is the status of defects ?

GQM GOALFinish project on time Question How is current progress of project Criteria Metric 1 The completed task*100 /total of task <10%: very bad 10% -> 50%: bad 50%->80%: normal 80%->90%: good 100%: very good Question How many issues are there in project? Metric 2Total number of issues - Number of issues is resolved >10 issues: bad 5 ->10 issues: normal 2 -> 5: Acceptable <2: good

GQM GOALImprove quality 20% QuestionWhat is the status of defects?Criteria Metric 1 Number of defect found/ 1KLOC/ release 10 defects: acceptable 10-> 20: normal >20: bad <10: good Question How many percent defect decrease when release? Metric 2 (Average number of defects in release n) – (Average number of defects in release n-1) <0: good >0: bad QuestionIs the end user satisfied? Metric 3Based on the survey<50% agree: bad 50% -> 80%: normal >80%: good

Agenda 1. Introduction 2. Measurement process 3. GQM 4. Strength Weakness of metrics

Strength Weakness of metrics 1/ The completed task*100 /total of task Strength: We can track a progress of project Weakness: We can’t identify level important of completed task

Strength Weakness of metrics 2/ Total number of issues - Number of issues is resolved Strength: We can track a progress of project Weakness: We can’t identify level important of resolved issues

Strength Weakness of metrics 3/ Number of defect found/ 1KLOC/ release Strength: The number of defect found metric is easy to count and the physical KLOC metric has been extensively automated for counting. The metric is easily to execute. Weakness: The physical KLOC metric may include substantial “dead code”. The physical KLOC metric may include blanks and comments.

Strength Weakness of metrics 4/ (Average number of defects in release n) – (Average number of defects in release n-1) Strength: It helps we know if project haves a poor quality. We can know that defects have released so that we know that the project have finished on time Weakness: We can’t identify how important defect is => the project can be failed because defect, which doesn’t release, is very important.

Strength Weakness of metrics 5/ Based on the survey Strength: Surveys are almost infinitely adaptable and can be constructed to gather information on virtually any topic. It focuses on expectative customer. It is easily to do and to use. Surveys are one of the best ways to examine customer’ expectative and attitudes. Weakness: The primary disadvantage of using surveys to assess customer’ expectative is that they provide only indirect evidence. Typically they measure satisfaction and impressions but do not generate information about deeper product.

Thanks For Your Listening! !!