2010
DOI: 10.1109/ms.2010.65
|View full text |Cite
|
Sign up to set email alerts
|

Reverse Engineering on the Mainframe: Lessons Learned from "In Vivo" Research

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
7
0

Year Published

2011
2011
2020
2020

Publication Types

Select...
6
1

Relationship

1
6

Authors

Journals

citations
Cited by 10 publications
(8 citation statements)
references
References 6 publications
0
7
0
Order By: Relevance
“…It is clear that the availability of open-source systems lowered the entry-barrier for conducting casestudies, however as a community we should not only go for the low-hanging fruit. Consequently, we should move the "in vitro" research out of the labs and into an "in vivo" environment [16]. • Thirdly, we should pay close attention to the newer platforms used by practitioners.…”
Section: Threats To Validitymentioning
confidence: 99%
“…It is clear that the availability of open-source systems lowered the entry-barrier for conducting casestudies, however as a community we should not only go for the low-hanging fruit. Consequently, we should move the "in vitro" research out of the labs and into an "in vivo" environment [16]. • Thirdly, we should pay close attention to the newer platforms used by practitioners.…”
Section: Threats To Validitymentioning
confidence: 99%
“…It combines a Feature-Oriented perspective with reverse engineering techniques by fulfilling the requirements as proposed in [31,32]:…”
Section: Envisioned Approachmentioning
confidence: 99%
“…As Van Geet and Demeyer show, migration approaches for legacy systems evaluated in vitro are often of limited usage in practice [32]. Therefore, industrial case studies should be applied to show the usefulness and effectiveness of FeatureOriented Reflexion Modelling.…”
Section: Empirical Studies In Industrial Practicementioning
confidence: 99%
See 2 more Smart Citations