Más contenido relacionado
Similar a Extracting Business Rules from COBOL: A Model-Based Framework (20)
Más de Valerio Cosentino (18)
Extracting Business Rules from COBOL: A Model-Based Framework
- 1. Valerio Cosentino - IBM, AtlanMod, INRIA & EMN, Nantes - valerio.cosentino@fr.ibm.com
Jordi Cabot - AtlanMod, INRIA & EMN, Nantes - jordi.cabot@mines-nantes.fr
Patrick Albert – IBM - albertpa@fr.ibm.com
Philippe Bauquel – IBM - bauquel.p@fr.ibm.com
Jacques Perronnet – IBM - jacques_perronnet@fr.ibm.com
Extracting Business Rules from COBOL:
A Model-Based Framework
1
WCRE 2013, Koblenz, Germany – 14-17 October
© 2009 IBM Corporation
- 2. Outline
Introduction
– Problem
– Running example
Framework overview
– Model Discovery
– Business Term Identification
– Business Rule Identification
– Business Rule Representation
Early validation
Conclusion & future work
2
© 2009 IBM Corporation
- 8. Problem
Poor/outdated system documentation
The original developers/business analysts may have left the
organization
Business rules spread in the source code
8
© 2009 IBM Corporation
- 9. Problem
Understanding and evolving the business policies together with
the corresponding business rules is not trivial
9
© 2009 IBM Corporation
- 10. Problem
Understanding and evolving the business policies together with
the corresponding business rules is not trivial
Specially true for legacy systems
10
© 2009 IBM Corporation
- 11. COBOL
Largely used:
– 200 billion lines of code in existence
– 70%-75% of business and transaction systems
– 90% of global financial transactions
11
© 2009 IBM Corporation
- 12. COBOL
Largely used:
– 200 billion lines of code in existence
– 70%-75% of business and transaction systems
– 90% of global financial transactions
Shortage of COBOL developers:
– Study on 357 Information Technology professionals
– 46% says they already notice a shortage
– 50% says the average age is > 45
– 22% says the age is > 55
12
© 2009 IBM Corporation
- 13. Running example
Need
Bag
Money
13
Is open
Quantity
Price
Business rules in the program:
–If the shop is open, then the customer can buy products
–If a product P is needed, then the customer buys P
–If the client has enough money, then he can buy products
–If the client has enough room in his bag, he can buy products
–If a product is available, then it may be bought
–If a product is bought, its quantity is decreased by one
© 2009 IBM Corporation
- 18. Framework overview
Model Driven Engineering:
– Modular framework
– Internal/external representation of BRs
– Traceability between rules and source code
– Mature tools available for model manipulations, visualizations
and transformations (e.g., ATL, Xtext, ...)
18
© 2009 IBM Corporation
- 21. Business Term Identification
Manually: the user selects the variables
Automatically: heuristic-based strategy
1) Statements are separated in groups:
– Conditional
– Computational
– ...
21
© 2009 IBM Corporation
- 22. Business Term Identification
Manually: the user selects the variables
Automatically: heuristic-based strategy
1) Statements are separated in groups:
– Conditional
– Computational
– ...
2) Variables in statements are classified in:
– Condition
– Index
– Source
– Target
22
© 2009 IBM Corporation
- 23. Business Term Identification
Manually: the user selects the variables
Automatically: heuristic-based strategy
– all target variables in computational statements
– all variables in conditional statements
– ...
23
© 2009 IBM Corporation
- 36. Early validation
Does the framework find complete business rules?
Are the extracted rules understandable?
36
© 2009 IBM Corporation
- 37. Early validation
Does the framework find complete business rules?
Are the extracted rules understandable?
Analysis of an IBM COBOL application:
– 14 programs
– 130 variables
– 6500 lines of code
4 internal IBM COBOL experts:
– They knew the application
– They analysed the business rules generated by our framework
37
© 2009 IBM Corporation
- 38. Early validation
Does the framework find complete business rules?
Are the extracted rules understandable?
Analysis of an IBM COBOL application:
– 14 programs
– 130 variables
– 6500 lines of code
4 internal IBM COBOL experts:
– They knew the application
– They analysed the business rules generated by our framework
The framework is able to identify the complete business rules
– But some extracted rules include technical knowledge
38
© 2009 IBM Corporation
- 39. Conclusion and future work
MDE benefits:
– Modular framework
– Internal/external representation of BRs
– Traceability between rules and source code
39
© 2009 IBM Corporation
- 40. Conclusion and future work
MDE benefits:
– Modular framework
– Internal/external representation of BRs
– Traceability between rules and source code
Future work:
– Complete the early validation on a real system
– Extract and unify the rules buried in other layers (presentation,
data, logic)
40
© 2009 IBM Corporation