2012
DOI: 10.1007/978-3-642-32689-9_3
|View full text |Cite
|
Sign up to set email alerts
|

A Model Driven Reverse Engineering Framework for Extracting Business Rules Out of a Java Application

Abstract: Context: Most companies, independently of their size and activity type, are facing the problem of managing, maintaining and/or replacing (part of) their existing software systems. These legacy systems are often large applications playing a critical role in the company's information system and with a non-negligible impact on its daily operations. Improving their comprehension (e.g., architecture, features, enforced rules, handled data) is a key point when dealing with their evolution/modernization.Objective: Th… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

2
11
0

Year Published

2013
2013
2022
2022

Publication Types

Select...
4
2
2

Relationship

2
6

Authors

Journals

citations
Cited by 21 publications
(13 citation statements)
references
References 19 publications
2
11
0
Order By: Relevance
“…When understanding computational business rules, developers must answer which of the conditional statements correspond to the computational business rules for each output of a feature. Backward program slicing [5] is used to understand business rules [2]- [4], [6], [7]. Cosentino et al [4] proposed an application of program slicing to extract statements corresponding to business rules that compute a particular variable.…”
Section: Introductionsupporting
confidence: 43%
See 1 more Smart Citation
“…When understanding computational business rules, developers must answer which of the conditional statements correspond to the computational business rules for each output of a feature. Backward program slicing [5] is used to understand business rules [2]- [4], [6], [7]. Cosentino et al [4] proposed an application of program slicing to extract statements corresponding to business rules that compute a particular variable.…”
Section: Introductionsupporting
confidence: 43%
“…They concluded that techniques for data flow analysis and extracting partial paths are required for understanding business rules. The framework is extended for COBOL [6], C/C++ [2], Java [7], respectively. Furthermore, Cosentino et al [4] extended the framework for COBOL programs based on the principles of Model Driven Engineering.…”
Section: Related Workmentioning
confidence: 42%
“…Besides, we are aware that business rules can be enforced in any layer of a software system (e.g., including front-end validations, database triggers and checks,...) so we envision to complement this framework with additional modules covering other technologies (see our work with Java [12]), maximizing the reuse opportunities and providing auxiliary modules in charge of merging and checking the consistency of the obtained rules.…”
Section: Discussionmentioning
confidence: 46%
“…For instance, [11] and [12] propose BREX frameworks respectively for C/C++ and Java; despite our framework shares the same conceptual steps of those approaches, the corresponding heuristics cannot be reused in our context due to the huge differences between COBOL and those languages.…”
Section: Related Workmentioning
confidence: 43%
“…For each output, developers are required to answer a question: which conditional statements are relevant to this output value? The developers must then analyze the implementation of the feature and extract the relevant conditional statements in order to understand the business rules Backward program slicing [3] is used to understand business rules [2], [4], [5], [6], [7]. Cosentino et al [2] propose an application of program slicing to extract statements relevant to business rules that compute a particular variable.…”
Section: Introductionmentioning
confidence: 40%