Proceedings of the 37th Annual Southeast Regional Conference (CD-ROM) 1999
DOI: 10.1145/306363.306381
|View full text |Cite
|
Sign up to set email alerts
|

The role of software measures and metrics in studies of program comprehension

Abstract: Many studies have been conducted into how programmers comprehend software. Models based on these studies have pointed to top-down, bottom-up, and mixed models for describing the comprehension process. In most of these studies, however, a key element of the experiment is largely ignored: the underlying nature of the software being examined by the programmers. This paper discusses software measurements and metrics that must be considered as factors when conducting comprehension studies.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
9
0

Year Published

2005
2005
2020
2020

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 11 publications
(9 citation statements)
references
References 14 publications
0
9
0
Order By: Relevance
“…There are numerous software clustering techniques that can be used during reverse engineering to identify software components (Koschke, 2000). Frank Tip provides a survey of program slicing techniques (Tip, 1995) and Mathias et al discuss the role of various software metrics on program comprehension (Mathias, 1999).…”
Section: Tool Researchmentioning
confidence: 99%
“…There are numerous software clustering techniques that can be used during reverse engineering to identify software components (Koschke, 2000). Frank Tip provides a survey of program slicing techniques (Tip, 1995) and Mathias et al discuss the role of various software metrics on program comprehension (Mathias, 1999).…”
Section: Tool Researchmentioning
confidence: 99%
“…According to Finkelstein and Leaning [2], software measurement is the process of defining numbers or symbols for the attributes of software entities (e.g., the attributes size, maintainability, and efficiency), which is a challenging endeavor given the abstract nature of software [3]. Mathias et al [4] claimed that whenever a value is defined for an attribute, there is a measure, and a measure is a combination of measures. Even though, in practice, the terms "measure" and "measure" are used interchangeably; in this article, we use the term "measure" as defined in ISO/IEC 15939:2007 [5].…”
Section: Introductionmentioning
confidence: 99%
“…According to Mathias et al [13], a * renata.saraiva@embedded.ufcg.edu.br † mirko.perkusich@embedded.ufcg.edu.br ‡ hyggo@embedded.ufcg.edu.br § perkusic@embedded.ufcg.edu.br measurement occurs when an attribute is measured, that is, when a value is assigned to it. By combining this measure with useful information, we have a metric (e.g., average number of defects per module).…”
Section: Introductionmentioning
confidence: 99%
“…By combining this measure with useful information, we have a metric (e.g., average number of defects per module). In practice, the terms "metric" and "measure" are often used interchangeably [13]. In this paper, we use the definitions presented by Mathias et al [13].…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation