Abstract
Active rules (i.e., event condition action rules, triggers) have been put forward as a technique for reacting to important events, and thereby avoiding polling or embedding rule processing in applications. Despite the promises of active rules technology, the usage of active rules is low in practice. It has often been claimed (by database researchers) that the reason why few active rules applications have been built is due to the lack of support in analysis and design phases. Hence, there are very few notations or guidelines available for software engineers who develop active rules applications.In this paper, we propose modelling templates for UML state-charts and UML-A statecharts for how software engineers can capture the fundamentals of active rules. By following the proposed modelling templates and notations for active rules, it will be easier for software engineers to develop applications that rely on active rules technology.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
