Tag Archives: capers jones

#14 – SOURCES OF SOFTWARE BENCHMARKS – CAPERS JONES

Posted on by
Reply

Capers Jones pix
Version 22.1 February 3, 2013
Capers Jones VP and CTO
Namcook Analytics LLC
Web: www.Namcook.com
Email: Capers.Jones3@gmail.com

INTRODUCTION

Number of benchmark sources currently:                     23

Number of projects in all benchmarks sources:            91,000 (approximately)

Quantitative software benchmark data is valuable for measuring process improvement programs, for calibrating software estimating tools, and for improving software quality levels.  It is also useful for studies of industry and company progress over time.  This catalog of software benchmark data sources is produced as a public service by Namcook Analytics LLC for the software community.  It is not copyrighted and can be freely distributed. 

There are many different kinds of benchmarks including productivity and quality levels for specific projects; portfolio benchmarks for large numbers of projects, operational benchmarks for data center performance; security benchmarks, compensation and staffing benchmarks for human resource purposes; and software customer satisfaction benchmarks.  SEI software assessment data is also included. Continue reading →

#13 – DO SOFTWARE – READ ABOUT THE UNIVERSAL SOFTWARE METRIC – (C) Capers Jones

Posted on by
Reply

Capers Jones pix

Function point metrics are the most accurate and effective metrics yet developed for software sizing and also for studying software productivity, quality, costs, risks, and economic value.

Unlike the older “lines of code” metric function points can be used to study requirements, design, and in fact all software activities from development through maintenance. Continue reading →

#12 – EARLY SIZING AND EARLY RISK ANALYSIS FOR SOFTWARE PROJECTS – (C) CAPERS JONES

Posted on by
Reply

Capers Jones pixMost methods of software sizing are based on software requirements and design documents, or on the source code itself.  For both new applications and enhancements this means that substantial funds will have been expended before sizing takes place. 

Many risks are proportional to software size.  As a result of delayed sizing, software project risk analysis usually occurs after development methods are locked in place.   When problems or risks are identified, it is often too late to introduce improved methods so the only options are staffing increases, unpaid overtime, or deferred functionality. Continue reading →

#11 – SOFTWARE PATTERN MATCHING – (C) CAPERS JONES

Posted on by
Reply

Capers Jones pixPattern matching is a predictive methodology that uses a formal taxonomy to compare results of historical software projects against the possible outcomes of new software projects that are about to start development.

Pattern matching for software starts with a questionnaire that uses multiple-choice questions.  These questions elicit information about a new project, such as its nature, scope, class, type, and complexity. Continue reading →

#11 – WEARABLE COMPUTERS – (C) Capers Jones

Posted on by
Reply

Capers Jones pix

Excerpt from The Technical and Social History of Software Engineering

(To be published by Addison Wesley in the autumn of 2013)

Copyright © 2013 by Capers Jones.  All rights reserved.

As many readers know Google has already been working on a prototype of a wearable computer called “Google glass.”  The device looks like an ordinary pair of glasses but contains an embedded computer with lenses can display information.

Continue reading →