Home » Guide to Selecting Software Measures and Metrics
Product Image

Guide to Selecting Software Measures and Metrics

Capers Jones
€59.99
Quantity:
In stock with our UK publisher. 14-28 days
Delivery/Collection within 10-20 working days
14 days return policy Shipping & Delivery
A01=Capers Jones
advanced software metrics comparison
Agile Methods
Author_Capers Jones
Bug Repairs
Burden Rate
Category=KJMP
Category=UMZ
Category=UTF
Certified Test Personnel
CMMI Level
code
Defect Removal
Defect Removal Cost
development methodology analysis
DRE
eq_bestseller
eq_business-finance-law
eq_computing
eq_isMigrated=1
eq_isMigrated=2
eq_nobargain
eq_non-fiction
ERP Package
function
Function Point
Function Point Counter
Function Point Metrics
Function Point Size Range
IFPUG
IFPUG Function Point
industry
ISBSG
logical
measurement
measurement error correction
Mis Project
months
nonfunctional
Nonfunctional Requirements
point
programming language metrics
Software Cost Estimates
Software Defect Potentials
software effort estimation
software project benchmarking
Software Quality
Software Quality Control
Software Quality Measurements
SRM
staff
statements
team experience evaluation
Unpaid Overtime

Product details

  • ISBN 9781032476919
  • Weight: 740g
  • Dimensions: 156 x 234mm
  • Publication Date: 21 Jan 2023
  • Publisher: Taylor & Francis Ltd
  • Publication City/Country: GB
  • Product Form: Paperback
Secure checkout Fast Shipping Easy returns
Description

Going where no book on software measurement and metrics has previously gone, this critique thoroughly examines a number of bad measurement practices, hazardous metrics, and huge gaps and omissions in the software literature that neglect important topics in measurement. The book covers the major gaps and omissions that need to be filled if data about software development is to be useful for comparisons or estimating future projects.

Among the more serious gaps are leaks in reporting about software development efforts that, if not corrected, can distort data and make benchmarks almost useless and possibly even harmful. One of the most common leaks is that of unpaid overtime. Software is a very labor-intensive occupation, and many practitioners work very long hours. However, few companies actually record unpaid overtime. This means that software effort is underreported by around 15%, which is too large a value to ignore. Other sources of leaks include the work of part-time specialists who come and go as needed. There are dozens of these specialists, and their combined effort can top 45% of total software effort on large projects.

The book helps software project managers and developers uncover errors in measurements so they can develop meaningful benchmarks to estimate software development efforts. It examines variations in a number of areas that include:



  • Programming languages


  • Development methodology


  • Software reuse


  • Functional and nonfunctional requirements


  • Industry type


  • Team size and experience

Filled with tables and charts, this book is a starting point for making measurements that reflect current software development practices and realities to arrive at meaningful benchmarks to guide successful software projects.

More from this author