Proceedings 9th International Workshop on Program Comprehension. IWPC 2001
DOI: 10.1109/wpc.2001.921735
|View full text |Cite
|
Sign up to set email alerts
|

Adoption of reverse engineering tools: a cognitive perspective and methodology

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4

Citation Types

0
9
0

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 11 publications
(9 citation statements)
references
References 16 publications
0
9
0
Order By: Relevance
“…The amount of software lifecycle effort consumed during this phase has been estimated to range between 60% and 80% of the entire lifecycle effort [1][2][3][4]. While the empirical basis for such statements is dated and suggestions have been made that it should be revisited [4], the increasing scale and complexity of newer software systems [3,5] implies that the effort invested in maintenance of successful systems can only have increased. Thus, research is required towards the discovery and evolution of supportive approaches or tools, which could improve efficiency in this effort-intensive activity.…”
Section: Introductionmentioning
confidence: 99%
“…The amount of software lifecycle effort consumed during this phase has been estimated to range between 60% and 80% of the entire lifecycle effort [1][2][3][4]. While the empirical basis for such statements is dated and suggestions have been made that it should be revisited [4], the increasing scale and complexity of newer software systems [3,5] implies that the effort invested in maintenance of successful systems can only have increased. Thus, research is required towards the discovery and evolution of supportive approaches or tools, which could improve efficiency in this effort-intensive activity.…”
Section: Introductionmentioning
confidence: 99%
“…software engineering activity, it is estimated that software engineers spend more than half of their time occupied with comprehension tasks (Wilde et al 2001;Zayour and Lethbridge 2001). If we take software maintenance not as a distinct phase but rather as an activity engaged in throughout the entire software lifecycle (Schneidewind et al 1999) then the software comprehension problem can be seen as permeating all aspects of a software system's existence from development through to maintenance and evolution.…”
mentioning
confidence: 99%
“…The manner in which a programmer gets understanding of a software system varies greatly and depends on the individual, the magnitude of the program, the level of understanding needed, the kind of system, ... [18,29,8,23].…”
Section: Introductionmentioning
confidence: 99%
“…Because of the human cognition process [29], program understanding can never be a fully automated process: the programmer should be free to explore the software, with the help of specialized tools [9,6]. These program exploration tools should identify those parts of the program that are likely to be interesting from a program understanding point of view [15,12].…”
Section: Introductionmentioning
confidence: 99%