KitchenhamMadeyskiBudgen16.COCOMO: KitchenhamMadeyskiBudgen16.COCOMO data
In reproducer: Reproduce Statistical Analyses and Meta-Analyses

KitchenhamMadeyskiBudgen16.COCOMO

R Documentation

KitchenhamMadeyskiBudgen16.COCOMO data

Description

If you use this data set please cite this R package and the following paper when accepted: Barbara Kitchenham, Lech Madeyski, David Budgen, Jacky Keung, Pearl Brereton, Stuart Charters, Shirley Gibbs, and Amnart Pohthong, 'Robust Statistical Methods for Empirical Software Engineering', Empirical Software Engineering, vol. 22, no.2, p. 579-630, 2017. DOI: 10.1007/s10664-016-9437-5 (https://dx.doi.org/10.1007/s10664-016-9437-5), URL: https://madeyski.e-informatyka.pl/download/KitchenhamMadeyskiESE.pdf

Usage

KitchenhamMadeyskiBudgen16.COCOMO

Format

A data frame with variables:

Project: Project ID
Type: A categorical variable describing the type of the project
Year: The year the project was completed
Lang: A categorical variable describing the development language used
Rely: Ordinal value defining the required software reliability
Data: Ordinal value defining the data complexity / Data base size
Cplx: Ordinal value defining the complexity of the software / Process complexity
Aaf: ??
Time: Ordinal value defining the stringency of timing constraints / Time constraint for cpu
Stor: Ordinal value defining the stringency of the data storage requirements / Main memory constraint
Virt: Virtual Machine volatility
Turn: Turnaround time
Type2: A categorical variable defining the hardware type: mini, max=mainframe, midi
Acap: Ordinal value defining the analyst capability
Aexp: Ordinal value defining the analyst experience / application experience
Pcap: Ordinal value defining the programming capability of the team / Programmers capability
Vexp: Ordinal value defining the virtual machine experience of the team
Lexp: Ordinal value defining the programming language experience of the team
Cont: ??
Modp: / Modern programming practices
Tool: Ordinal value defining the extent of tool use / Use of software tools
ToolCat: Recoding of Tool to labelled ordinal scale
Sced: Ordinal value defining the stringency of the schedule requirements / Schedule constraint
Rvol: Ordinal value defining the requirements volatility of the project
Select: Categorical value calculated by BAK for an analysis example
Rvolcat: Recoding of Rvol to a labelled ordinal scale
Modecat: Mode of the projects: O=Organic, E=Embedded, SD-Semi-Detached
Mode1: Dummy variable calculated by BAK: 1 if the project is Organic, 0 otherwise
Mode2: Dummy variable calculated by BAK: 1 if the project is Semi-detached, 0 otherwise
Mode3: Dummy variable calculated by BAK: 1 if the project is Embedded, 0 otherwise
KDSI: Product Size Thousand of Source Instructions
AKDSI: Adjusted Product Size for Project in Thousand Source Instructions - differs from KDSI for enhancement projects
Effort: Project Effort in Man months
Duration: Duration in months
Productivity: Productivity of project calculated by BAK as AKDSI/Effort, so the the larger the value the better the productivity

Details

Data set collected at TRW by Barry Boehm see: B.W. Boehm. 1981. Software Engineering Economics. Prentice-Hall.

Explanations by Barbara Kitchenham / https://terapromise.csc.ncsu.edu:8443/!/#repo/view/head/effort/cocomo/cocomo1/nasa93/nasa93.arff

COCOMO.txt: pro type year Lang Rely Data CPLX aaf time store virt turn type2 acap aexp pcap vexp lexp cont modp TOOL TOOLcat SCED RVOL Select rvolcat Modecat Mode1 Mode2 Mode3 KDSI AKDSI Effort Dur Productivity