L5 - CS 514 Software Product & Process Evaluation...

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

View Full Document Right Arrow Icon
CS 514 Software Product & Process Evaluation Fall 2008 James M. Bieman Copyright © 2000 - 2008 James M. Bieman 5-1 CS 514 Copyright © 2000 -2008 James M. Bieman 5-1 Chapter 5 Chapter 5 Internal and External Internal and External Software Quality Software Quality Source [Fenton & Pfleeger 97], 97], James M. Bieman Computer Science Dept Colorado State University CS 514 Copyright © 2000 - 2008 James M. Bieman 5-2 Outline Outline Internal software quality Functionality. Structure. External software quality Overview. Faults and failures. Usability and maintainability. CS 514 Copyright © 2000 - 2008 James M. Bieman 5-3 Internal Software Quality Internal Software Quality - Size Size Size is not “complexity”. The key concern should be the size of the software entity, not its complexity. Focus on counts of “things” in the implementation, design, requirements, test plans, etc. Adjustments aimed to match a notion of complexity lead to problems. What can KLOC tell us?
Background image of page 1

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

View Full DocumentRight Arrow Icon
CS 514 Software Product & Process Evaluation Fall 2008 James M. Bieman Copyright © 2000 - 2008 James M. Bieman 5-2 CS 514 Copyright © 2000 - 2008 James M. Bieman 5-4 Lines of Code (LOC, KLOC) Lines of Code (LOC, KLOC) What should we count? Use consistent counting rules. LOC based measures: Comment density. Reuse: % of reused code. LOC is the most commonly used software measure; it’s very useful. CS 514 Copyright © 2000 - 2008 James M. Bieman 5-5 Halstead Halstead ’s Software Science s Software Science Based on counts: n1: number of unique operators. n2: number of unique operands. N1: total occurrences of operators. N2: total occurrences of operands. Derived measures: Vocabulary: n = n1 + n2. Length: N = N1 + N2. Volume: V = N x log2(n) Minimum binary encoding of a program. CS 514 Copyright © 2000 - 2008 James M. Bieman 5-6 Other Halstead Software Science Other Halstead Software Science Measures Measures Halstead defined other measures: program level, difficulty, language level These other measures have been largely discredited by the research community. Don’t satisfy representation condition. Problems with empirical studies “demonstrating” prediction systems.
Background image of page 2
CS 514 Software Product & Process Evaluation Fall 2008 James M. Bieman Copyright © 2000 - 2008 James M. Bieman 5-3 CS 514 Copyright © 2000 - 2008 James M. Bieman 5-7 Functionality Functionality – Function Points Function Points Quantifies “functionality” based on a requirements spec. Unadjusted FP (UFP):
Background image of page 3

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

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

This note was uploaded on 05/29/2010 for the course CS 514 taught by Professor Prof.j.bieman during the Fall '09 term at Colorado State.

Page1 / 14

L5 - CS 514 Software Product & Process Evaluation...

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

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