lecture14_2up

lecture14_2up - Object-Oriented Software Engineering Extra...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Object-Oriented Software Engineering Extra Chapter: Software Metrics Lecture 14 Why Measure Software? Projects often • Go over budget • Miss deadlines • Exhibit poor quality Measurements can be used to improve the process and quality • Both short term (current) and long term (future) Systematic improvement is not possible without measurement 700 Software Metrics Defnition • The measurement of the software development process and its resulting product The soFtware product includes the source code, executable code, and related documentation Used to • Estimate cost • Estimate schedule • Measure productivity • Measure quality 701 Characteristics of Good Metrics • Can be used to predict, not just describe • Simple; precisely deFnable • Objective • Easily obtained; low cost • Valid; relevant to intended measurement • Robust; relatively insensitive to insigniFcant changes 702 Metrics Classification Process • Measurements of the development process • Examples —Development time —Methodology (Waterfall, Spiral, etc.) —Average years of experience for development staff Product • Measurements of software at any point in development • Examples —Design complexity —Program size (source or executable) in lines of code (LOC) —Pages of documentation 703 More Classifications Objective versus subjective • Do different observers measure the same values? • Examples —Objective: LOC, development time —Subjective: developer experience Primitive versus computed • Examples —Primitive: LOC, development time —Computed: LOC/Person-month, Defects/KLOC 704 Data Examples Nominal • Program type: database, network, application Ordinal • Programmer experience: low, medium, high Interval • Program complexity: 5, 4, 3, 2, 1 Ratio • LOC: 2000 is twice as large as 1000 705 Process Metrics For individuals...
View Full Document

This note was uploaded on 02/23/2012 for the course CS 307 taught by Professor Staff during the Summer '08 term at Purdue.

Page1 / 14

lecture14_2up - Object-Oriented Software Engineering Extra...

This preview shows document pages 1 - 5. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online