Toward Measurement-Based Software Engineering

We were delighted to have the paper “A Methodology for Collecting Valid Software Engineering Data”, by Victor Basili and David Weiss (1984) considered one of the most influential papers of IEEE Transaction of Software Engineering’s first decade. The paper discusses data or information on software quality and what were the most effective software development techniques. It was published in November, 1984. It was written at a time when software development was just becoming widespread practice, but it was not common to use data or information on software quality in order to learn what were the most effective software development techniques under different conditions. To try to alleviate this problem, we suggested that when people (or organizations) developed software, they should try to measure the effectiveness of their development techniques. In particular, since software is typically long-living, change data should be collected so that methods and processes could be managed.

Authors

Institutions

Publication Details

Journal
IEEE Transactions on Software Engineering
Published
2025-02-13
DOI
https://doi.org/10.1109/tse.2025.3541922
Primary Topic
Advanced Software Engineering Methodologies
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

Toward Measurement-Based Software Engineering

Victor R. Basili, David M. Weiss, Dieter Rombach
IEEE Transactions on Software Engineering
Advanced Software Engineering Methodologies
article

Toward Measurement-Based Software Engineering

Victor R. Basili, David M. Weiss, Dieter Rombach
article en

Abstract

We were delighted to have the paper “A Methodology for Collecting Valid Software Engineering Data”, by Victor Basili and David Weiss (1984) considered one of the most influential papers of IEEE Transaction of Software Engineering’s first decade. The paper discusses data or information on software quality and what were the most effective software development techniques. It was published in November, 1984. It was written at a time when software development was just becoming widespread practice, but it was not common to use data or information on software quality in order to learn what were the most effective software development techniques under different conditions. To try to alleviate this problem, we suggested that when people (or organizations) developed software, they should try to measure the effectiveness of their development techniques. In particular, since software is typically long-living, change data should be collected so that methods and processes could be managed.

IEEE Transactions on Software EngineeringVol. 51(3)
University of Kaiserslautern (DE), Avaya (United States) (US), Avaya (Bermuda) (BM), University of Maryland, College Park (US)
Openalex Percentile: Top 99%
Advanced Software Engineering Methodologies
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.