The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Goal Question Metric ( GQM ) Approach
Abstract
As with any engineering discipline, software development requires a measurement mechanism for feedback and evaluation. Measurement supports creating a corporate memory and is an aid in answering a variety of questions associated with the enactment of any software process. Measurement also helps, during the course of a project, to assess its progress, to take corrective action based on this assessment, and to evaluate the impact of such action. According to many studies made on the application of metrics and models in industrial environments, measurement in order to be effective must be. Focused on specific goals Applied to all life‐cycle products, processes, and resources Interpreted on the basis of characterization and understanding of the organizational context, environment, and goals This means that measurement must be defined in a top‐down fashion. It must be focused, based on goals and models. A metric‐driven, bottom‐up approach, will not work because there are many observable characteristics in software (e.g., time, number of defects, complexity, lines of code, severity of failures, effort, productivity, defect density). A context specific selection of metrics and guidelines on how to use and interpret them should be made, based on the appropriate models and goals of that environment. The most common and popular mechanism for goal‐oriented software measurement is the Goal Question Metric approach which is presented in this article in combination with examples from GQM application in industry
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Software Metrics: A Rigorous and Practical Approach
Fenton, N., & Pfleeger, S. L. (2013) · Cited by 2,509
The TAME Project: Towards Improvement-Oriented Software Environments
Basili, V. R., & Rombach, H. D. (2005) · Foundations of Empirical Software Engineering · doi:10.1007/3-540-27662-9_8 · Cited by 1,411
Self-citationA Methodology for Collecting Valid Software Engineering Data
Basili, V. R., & Weiss, D. M. (1984) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1984.5010301 · Cited by 1,149
Self-citationThe Goal/Question/Metric Method : A Practical Guide for Quality Improvement of Software Development
Berghout, E. W., & van Solingen, R. (1998) · Cited by 483
Software metrics: Establishing a company-wide program
Joseph, M. (1988) · Information and Software Technology · doi:10.1016/0950-5849(88)90108-5 · Cited by 223
Cited by
Challenges and barriers in virtual teams: a literature review
Morrison-Smith, S., & Ruiz, J. (2020) · SN Applied Sciences · doi:10.1007/s42452-020-2801-5 · Cited by 633
Perseverations of the academy: a survey of wearable technologies applied to autism intervention
Williams, R. M., & Gilbert, J. E. (2020) · International Journal of Human-Computer Studies · doi:10.1016/j.ijhcs.2020.102485 · Cited by 74
A mapping study on documentation in Continuous Software Development
Theunissen, T., van Heesch, U., & Avgeriou, P. (2022) · Information and Software Technology · doi:10.1016/j.infsof.2021.106733 · Cited by 40
Information Quality Assessment for Data Fusion Systems
Becerra, M. A., Tobón, C., Castro-Ospina, A. E., & Peluffo-Ordóñez, D. H. (2021) · Data · doi:10.3390/data6060060 · Cited by 36
A Survey on Feedback Types in Automated Programming Assessment Systems
Frankford, E., Antensteiner, T., Vierhauser, M., Sauerwein, C., Wallner, V., Groher, I., Plösch, R., & Breu, R. (2026) · ACM Transactions on Computing Education · doi:10.1145/3773911 · Cited by 10
Metadata
- Authors
- van Solingen, R., Basili, V., Caldiera, G., & Rombach, H. D.
- Venue
- Encyclopedia of Software Engineering
- Publisher
- Wiley
- Published
- 2002-01-15
- OpenAlex
- W1913969462
- Cited by
- 300
- References
- 5
- Type
- reference entry
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.