Lecture 2 software metrics and estimation.
Download as PPTX, PDF0 likes6 views
Lecture 2 software metrics and estimation by Snr Assoc prof Faiz ul haque Zeya
![Subjective measure
For subjective metrics, even qualified observers may measure
different values for a given metric, since their subjective judgment is
involved in arriving at the measured value.
An example of a subjective product metric is the classification of
the software as “organic,” “semi-detached,” or “embedded,” as
required in the COCOMO cost estimation model [Boehm81].
Although most programs might be easy to classify, those on the
borderline between categories might reasonably be classified in
different ways by different knowledgeable observers.
level of programmer experience is likely to be a subjective measure.](https://image.slidesharecdn.com/metric2-250413063200-ed38487b/85/Lecture-2-software-metrics-and-estimation-11-320.jpg)
Lecture 2 software metrics and estimation.
- 1. Software metrics lecture 2 ENGR. FAIZ UL HAQUE ZEYA
- 2. Software metrics categories. 1. Product metrics. 2. Process metrics. 3. Project metrics.
- 3. Another way to categorize Objective metrics. Subjective metrics.
- 4. . ProcessMetrics: It can be used to improve the process efficiency of the SDLC(Software Development Life Cycle). These are metrics that pertain to Process Quality. They are used to measure the efficiency and effectiveness of various processes. –Efforts required –Time to produce the product –Numbers of defect found –Tools and technology –Efficiency
- 6. Product Metrics: It deals with the quality of the software product. These are metrics that pertain to Product Quality. They describe the characteristics of the product such as size, complexity, design features, performance, and quality level. –Size –Complexity –Design features –Performance –Reliability
- 8. Project Metrics: It can be used to measure the efficiency of a project team. These are metrics that relate to Project Quality. They describe the project characteristics and execution –Number of software developers –Staffing pattern over the life cycle of the software –Cost –Schedule –Productivity. –Progress of on going project
- 10. Objective measure Objective metrics should always result in identical values for a given metric, as measured by two or more qualified observers. For product metrics, the size of the product measured in lines of code (LOC) is an objective measure, for which any informed observer, working from the same definition of LOC, should obtain the same measured value for a given program Development time is an example of an objective measure
- 11. Subjective measure For subjective metrics, even qualified observers may measure different values for a given metric, since their subjective judgment is involved in arriving at the measured value. An example of a subjective product metric is the classification of the software as “organic,” “semi-detached,” or “embedded,” as required in the COCOMO cost estimation model [Boehm81]. Although most programs might be easy to classify, those on the borderline between categories might reasonably be classified in different ways by different knowledgeable observers. level of programmer experience is likely to be a subjective measure.