Results 1 -
2 of
2
Reengineering Object-Oriented Applications
"... Semantics Graph (ASG) [BC00]. An ASG is graph is representing an abstract syntax tree (AST) with additional semantic information such as identifiers' scope, variables ' type, etc. The goal of the Datrix ASG model is completeness -- any kind of reverse engineering analysis should be doable on an ASG ..."
Abstract
-
Cited by 2 (0 self)
- Add to MetaCart
Semantics Graph (ASG) [BC00]. An ASG is graph is representing an abstract syntax tree (AST) with additional semantic information such as identifiers' scope, variables ' type, etc. The goal of the Datrix ASG model is completeness -- any kind of reverse engineering analysis should be doable on an ASG without having to return to the source code -- and language independence -- the model should be the same for all common concepts of C++, Java and other languages. 4.3 Why FAMIX? UML is currently embraced as "the" standard in object-oriented modeling languages [OMG99], the recent work of OMG on the Meta Object Facility (MOF) being the most noteworthy example. We welcome these standardization efforts, yet warn against the tendency to use UML as the panacea for all exchange standards or meta-models. In particular, we argue that UML is not sufficient to serve 4.3. WHY FAMIX? 37 as a meta-model for reengineering applications because (1) one is forced to rely on UML's built-in extension mechani...
RECAST: Evolution of Object-Oriented Applications
"... This research project is about reengineering object-oriented applications. Reengineering such applications inherits complex problems related to software maintenance, i.e., program understanding, program analysis, and program transformation and adds to them (1) the complexity introduced by late bindi ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
This research project is about reengineering object-oriented applications. Reengineering such applications inherits complex problems related to software maintenance, i.e., program understanding, program analysis, and program transformation and adds to them (1) the complexity introduced by late binding, dynamic typing, and incremental definition specific to object-oriented programming, and (2) the complexity related to the new way of software development (multiple parallel versions, frameworks, and products lines). Based on our research experience, this research project is structured in three non-orthogonal directions: (a) reengineering, (b) analysis of versions and (c) migration of object-oriented applications towards components.

