Quantifying the value of new technologies for software development

David L. Atkins, Audris Mockus, Harvey Pe Siy

Research output: Chapter in Book/Report/Conference proceedingChapter

1 Citation (Scopus)

Abstract

Introducing relevant software technologies may provide significant advantages to a software organization. Unfortunately, the value the technology may provide is almost never quantified. We describe a methodology for precise quantitative measurement of the value a software technology may add to the project in terms of the impact on quality and lead time. The methodology employs measures derived from version control and problem tracking repositories to determine the value of technology. We illustrate this approach in a detailed case study on the impact of using two particular technologies-a version-sensitive source code editor and a domain engineered application environment-in a telecommunications product. In both cases use of technology had a strong positive impact on the considered quality measures. The methodology relies on information commonly available in project version control and problem tracking systems and, therefore, can be widely and easily applied.

Original languageEnglish (US)
Title of host publicationValue-Based Software Engineering
PublisherSpringer Berlin Heidelberg
Pages327-344
Number of pages18
ISBN (Print)3540259937, 9783540259930
DOIs
StatePublished - Dec 1 2006

Fingerprint

Software engineering
Telecommunication

Keywords

  • Statistical models
  • case studies
  • database
  • development lead time
  • domain engineering
  • editing
  • empirical studies
  • large-scale software development
  • software change
  • software metrics
  • software quality
  • technology evaluation
  • technology transfer
  • versionsensitive

ASJC Scopus subject areas

  • Computer Science(all)

Cite this

Atkins, D. L., Mockus, A., & Siy, H. P. (2006). Quantifying the value of new technologies for software development. In Value-Based Software Engineering (pp. 327-344). Springer Berlin Heidelberg. https://doi.org/10.1007/3-540-29263-2_16

Quantifying the value of new technologies for software development. / Atkins, David L.; Mockus, Audris; Siy, Harvey Pe.

Value-Based Software Engineering. Springer Berlin Heidelberg, 2006. p. 327-344.

Research output: Chapter in Book/Report/Conference proceedingChapter

Atkins, DL, Mockus, A & Siy, HP 2006, Quantifying the value of new technologies for software development. in Value-Based Software Engineering. Springer Berlin Heidelberg, pp. 327-344. https://doi.org/10.1007/3-540-29263-2_16
Atkins DL, Mockus A, Siy HP. Quantifying the value of new technologies for software development. In Value-Based Software Engineering. Springer Berlin Heidelberg. 2006. p. 327-344 https://doi.org/10.1007/3-540-29263-2_16
Atkins, David L. ; Mockus, Audris ; Siy, Harvey Pe. / Quantifying the value of new technologies for software development. Value-Based Software Engineering. Springer Berlin Heidelberg, 2006. pp. 327-344
@inbook{7e64d7dd7d82403088df99830e381e1e,
title = "Quantifying the value of new technologies for software development",
abstract = "Introducing relevant software technologies may provide significant advantages to a software organization. Unfortunately, the value the technology may provide is almost never quantified. We describe a methodology for precise quantitative measurement of the value a software technology may add to the project in terms of the impact on quality and lead time. The methodology employs measures derived from version control and problem tracking repositories to determine the value of technology. We illustrate this approach in a detailed case study on the impact of using two particular technologies-a version-sensitive source code editor and a domain engineered application environment-in a telecommunications product. In both cases use of technology had a strong positive impact on the considered quality measures. The methodology relies on information commonly available in project version control and problem tracking systems and, therefore, can be widely and easily applied.",
keywords = "Statistical models, case studies, database, development lead time, domain engineering, editing, empirical studies, large-scale software development, software change, software metrics, software quality, technology evaluation, technology transfer, versionsensitive",
author = "Atkins, {David L.} and Audris Mockus and Siy, {Harvey Pe}",
year = "2006",
month = "12",
day = "1",
doi = "10.1007/3-540-29263-2_16",
language = "English (US)",
isbn = "3540259937",
pages = "327--344",
booktitle = "Value-Based Software Engineering",
publisher = "Springer Berlin Heidelberg",

}

TY - CHAP

T1 - Quantifying the value of new technologies for software development

AU - Atkins, David L.

AU - Mockus, Audris

AU - Siy, Harvey Pe

PY - 2006/12/1

Y1 - 2006/12/1

N2 - Introducing relevant software technologies may provide significant advantages to a software organization. Unfortunately, the value the technology may provide is almost never quantified. We describe a methodology for precise quantitative measurement of the value a software technology may add to the project in terms of the impact on quality and lead time. The methodology employs measures derived from version control and problem tracking repositories to determine the value of technology. We illustrate this approach in a detailed case study on the impact of using two particular technologies-a version-sensitive source code editor and a domain engineered application environment-in a telecommunications product. In both cases use of technology had a strong positive impact on the considered quality measures. The methodology relies on information commonly available in project version control and problem tracking systems and, therefore, can be widely and easily applied.

AB - Introducing relevant software technologies may provide significant advantages to a software organization. Unfortunately, the value the technology may provide is almost never quantified. We describe a methodology for precise quantitative measurement of the value a software technology may add to the project in terms of the impact on quality and lead time. The methodology employs measures derived from version control and problem tracking repositories to determine the value of technology. We illustrate this approach in a detailed case study on the impact of using two particular technologies-a version-sensitive source code editor and a domain engineered application environment-in a telecommunications product. In both cases use of technology had a strong positive impact on the considered quality measures. The methodology relies on information commonly available in project version control and problem tracking systems and, therefore, can be widely and easily applied.

KW - Statistical models

KW - case studies

KW - database

KW - development lead time

KW - domain engineering

KW - editing

KW - empirical studies

KW - large-scale software development

KW - software change

KW - software metrics

KW - software quality

KW - technology evaluation

KW - technology transfer

KW - versionsensitive

UR - http://www.scopus.com/inward/record.url?scp=84892139081&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84892139081&partnerID=8YFLogxK

U2 - 10.1007/3-540-29263-2_16

DO - 10.1007/3-540-29263-2_16

M3 - Chapter

SN - 3540259937

SN - 9783540259930

SP - 327

EP - 344

BT - Value-Based Software Engineering

PB - Springer Berlin Heidelberg

ER -