2014 6th International Workshop on Empirical Software Engineering in Practice 2014
DOI: 10.1109/iwesep.2014.14
|View full text |Cite
|
Sign up to set email alerts
|

Extraction of Conditional Statements for Understanding Business Rules

Abstract: In the maintenance of a business system, developers must understand the computational business rules implemented in the system. Computational business rules de¿ne how an output value of a feature is computed from inputs; the rules are represented by conditional statements in the source code. Unfortunately, understanding business rules is a tedious and error-prone activity. Since a feature computes various outputs, developers must analyze the implementation of the feature and extract the conditional statements … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2016
2016
2023
2023

Publication Types

Select...
3

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 17 publications
0
3
0
Order By: Relevance
“…Such conditions are then captured, translated, and recorded as business rules which are then evaluated by domain experts. In their works, Hatano et al [8] discussed an approach for understanding business rules in software systems in which the source code of the system is analyzed to determine conditional statements that affect the computation of variables used to generate system outputs.…”
Section: White-box Business Rule Extraction Approachesmentioning
confidence: 99%
See 1 more Smart Citation
“…Such conditions are then captured, translated, and recorded as business rules which are then evaluated by domain experts. In their works, Hatano et al [8] discussed an approach for understanding business rules in software systems in which the source code of the system is analyzed to determine conditional statements that affect the computation of variables used to generate system outputs.…”
Section: White-box Business Rule Extraction Approachesmentioning
confidence: 99%
“…Thus, many organizations evolve their legacy software systems through redevelopment or replacement of these systems to sufficient support business goals. Such goals may include (1) switching from a legacy programming language to a modern language, (2) adopting a flexible software architecture for the software system (such as switching from a monolithic architecture to a microservice architecture), and (3) targeting a new operational environment (such as switching from Mainframe environment to Cloud environment) [6][7][8]. To accomplish such evolution activities, the replacing software system is often needed to fully or partially satisfy the business rules embedded in the legacy software system.…”
Section: Introductionmentioning
confidence: 99%
“…In f ormal verif ication shown in Section IV, a rule-form formula composed of conditions and conclusions is extracted from the DTEM. Extracting a specification from a program in the form of rules has been studied [22] [23] [24] [25] [26] [27] [28]. In these studies, the control path of the program is extracted by static analysis or symbolic execution, and the rule is created on the basis of the branch condition that constitutes the control path.…”
Section: Related Workmentioning
confidence: 99%