[1993] Proceedings Working Conference on Reverse Engineering
DOI: 10.1109/wcre.1993.287769
|View full text |Cite
|
Sign up to set email alerts
|

An approach for reverse engineering of relational databases

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
56
0
3

Publication Types

Select...
6
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 58 publications
(59 citation statements)
references
References 3 publications
0
56
0
3
Order By: Relevance
“…Here let us mention the work of Chris Date [16,15,14], Michael Blaha [8,7,53], Peter Aiken [2] and Kathie Hogshead-Davis [17]. In Europe Jean-Luc Hainaut [18] and Jean Henrard [28,26,27] have worked on the re-engineering of databases to promote performance.…”
Section: Related Workmentioning
confidence: 99%
“…Here let us mention the work of Chris Date [16,15,14], Michael Blaha [8,7,53], Peter Aiken [2] and Kathie Hogshead-Davis [17]. In Europe Jean-Luc Hainaut [18] and Jean Henrard [28,26,27] have worked on the re-engineering of databases to promote performance.…”
Section: Related Workmentioning
confidence: 99%
“…Homogenizing means to remodel tables in the ODMG object model. In the FIHD approach, we incorporate ideas developed in the context of reverse engineering and semantic enrichment (Chiang et al (1994), Premerlani and Blaha (1994), Castellanos and Saltor (1991), Hohenstein and Korner (1995)). Hence, tables are not just converted to object types that possess the simple table structure, i.e., object types without relationships and without subtyping.…”
Section: Semantic Enrichmentmentioning
confidence: 99%
“…Reverse engineering goals are multiple, e.g., coping with complexity, generating alternate views, recovering lost information, detecting side effects, synthesizing higher abstractions, and facilitating reuse. Examples of problem areas where reverse engineering has been successfully applied include redocumenting programs [11] and relational databases [94], identifying reusable assets [23], recovering architectures [67], recovering design patterns [2,53,68,108], building traceability between code and documentation [1,76], identifying clones [7,10,62,81], code smells [111] and aspects [79,106], computing change impacts [6], reverse engineering binary code [29], renewing user interfaces [84,89], translating a program from one language to another [19], migrating [22] or wrapping legacy code [99]. Although software reverse engineering originated in software maintenance, its definition is sufficiently broad so as to be applicable to many problem areas, for example to create representations necessary for testing purposes [82], or to audit security and vulnerability [34].…”
Section: Introductionmentioning
confidence: 99%