2011 Eighth International Conference on Information Technology: New Generations 2011
DOI: 10.1109/itng.2011.130
|View full text |Cite
|
Sign up to set email alerts
|

Recovering Use Case Diagrams from Object Oriented Code: An MDA-based Approach

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
15
0
3

Year Published

2013
2013
2024
2024

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(18 citation statements)
references
References 6 publications
0
15
0
3
Order By: Relevance
“…WARE tool uses static code as an input and is capable of reverse engineering only when having access to entire source code of web application. In general, when source code is available, reverse engineering UML diagrams seems to have more possibilities for implementation, as source code is a valuable source of information [2,6,9,16]. Unfortunately, the source code is not always available.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…WARE tool uses static code as an input and is capable of reverse engineering only when having access to entire source code of web application. In general, when source code is available, reverse engineering UML diagrams seems to have more possibilities for implementation, as source code is a valuable source of information [2,6,9,16]. Unfortunately, the source code is not always available.…”
Section: Related Workmentioning
confidence: 99%
“…There are several studies on reverse engineering specifically use case diagrams. Some of them are based on source code analysis [6,9,16], which is not applicable to our method. Others have one major disadvantage: they require effort for creating additional specifications which are used as an input for diagram generation.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Missing or outdated documentation in legacy projects is always an issue during reengineering. Many techniques, however, have been presented for reverse engineering artifacts, such as domain models [12], class diagrams [28], sequence diagrams [16,18,23,25,33], and use cases [7] from legacy code. An architecture recovery methodology using feature modeling is described in [24].…”
Section: Overview Of Case Studiesmentioning
confidence: 99%
“…The new, modified, and deleted use cases are assigned to iterations in this step. First, an agile estimation technique such as the poker game [7] is applied to obtain an effort estimate for dealing with each of the use cases. An order to design, implement, delete, and test the use cases is derived, based on their dependencies and priorities.…”
Section: Introductionmentioning
confidence: 99%