DEVELOPMENT OF RULE-BASED REMINDER SYSTEM MODEL
Reminder application serves to remind the target party of important things. In the reminder application for corporate needs, sending a reminder message is based on the terms, policies or rules of the company. In general, this rule is written as part of the program code, so changes or additions to th...
Saved in:
| Main Author: | |
|---|---|
| Format: | Final Project |
| Language: | Indonesia |
| Online Access: | https://digilib.itb.ac.id/gdl/view/28439 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Institution: | Institut Teknologi Bandung |
| Language: | Indonesia |
| Summary: | Reminder application serves to remind the target party of important things. In the reminder application for corporate needs, sending a reminder message is based on the terms, policies or rules of the company. In general, this rule is written as part of the program code, so changes or additions to the reminder rule cause rewriting of the program code. To overcome these shortcomings, in this final project, a generic reminder system model was developed to enable reminder system users who were not software developers to define reminder rules. The reminder system model consists of three main components, namely ontology generator, defining rules, and reminder rules executors. The rule defining component provides an interface for the user to define the reminder rules that will be used. Reminder rules are formulated using the Event-Condition-Action (ECA) format and will be stored as data. To facilitate the definition of the data involved in the rules, the user is presented with a conceptual image in the form of an ontology component produced by the ontology generator component. The reminder rules executor component will execute reminder rules in order to send reminder messages. Reminder system uses two Database Management Systems (DBMS), namely MongoDB and MySQL. MongoDB is used to store reminder rule data while MySQL is used to store ontology maps of the company's relational database scheme. In addition, the reminder system also uses Windows schtask to schedule a check of the reminder rules for the company's database data instances. Reminder messages are sent via two different media, namely sms and email. Based on the test results it can be concluded that the reminder system model developed is generic. Defining reminder rules can be done by someone who is not a software developer. The reminder system does not require recoding when the database scheme changes. |
|---|