From COBOL to Business Rules—Extracting Business Rules from Legacy Code

Abstract

General rightsCopyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights.• Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal Take down policyIf you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim.

Implementation of Vue Js and Laravel on Monitoring Battery Management System

“…The functional requirements describe the performance of the current system. Software and hardware specifications required to construct a system are examples of non-functional requirements [11]. Use case diagrams are visual representations of the interactions between the system's actors developed by accounting for the system's use.…”

On the design of an advanced business rule engine

“…Many authors have worked on mining business rules from application code, namely: Sneed and Verhoef 25 focused on COBOL, Cosentino et al 26 on Java, Hnatkowska and Wazelinski 27 on C#, and Barbosa and Maia 28 or Mesbahi et al 29 on SQL procedures. Chittimalli et al 30 reported on a more ambitious goal: a language‐independent framework to extract the rules, 31 to create new ones, to verify them using the logs, and to analyze them.…”