Sanati-Mehrizy, R., & Minaie, A. (2021, July), Writing Triggers to Implement Business Rules in a Relational Database  Paper presented at 2021 ASEE Virtual Annual Conference Content Access, Virtual Conference. 10.18260/1-2--38223

\bibitem{asee_peer_38223}
  Sanati-Mehrizy, R., \& Minaie, A. (2021, July), \emph{Writing Triggers to Implement Business Rules in a Relational Database}
  Paper presented at 2021 ASEE Virtual Annual Conference Content Access, Virtual Conference.
  10.18260/1-2--38223

Reza Sanati-Mehrizy and Afsaneh Minaie.  "Writing Triggers to Implement Business Rules in a Relational Database".  2021 ASEE Virtual Annual Conference Content Access, Virtual Conference, 2021, July.  ASEE Conferences, 2021.  https://strategy.asee.org/38223 Internet.  19 Jul, 2024

\bibitem{asee_peer_38223}
  Reza Sanati-Mehrizy and Afsaneh Minaie.
  "Writing Triggers to Implement Business Rules in a Relational Database".
  \emph{2021 ASEE Virtual Annual Conference Content Access, Virtual Conference, 2021, July}.
  ASEE Conferences, 2021.
  https://strategy.asee.org/38223 Internet.  19 Jul, 2024

@INPROCEEDINGS{asee_peer_38223
author = "Reza Sanati-Mehrizy and Afsaneh Minaie"
title = "Writing Triggers to Implement Business Rules in a Relational Database"
booktitle = "2021 ASEE Virtual Annual Conference Content Access"
year = "2021"
month = "July"
address = "Virtual Conference"
publisher = "ASEE Conferences"
note = {https://strategy.asee.org/38223}
number = {10.18260/1-2--38223}
}

TY  - CPAPER
AB  - Abstract

Organizations have many business rules (constraints) to implement in their daily operations. This is done mainly by action assertions traditionally implemented in procedural logic buried deeply within user’s application program in a form that is virtually unrecognisable, unmanageable, and inconsistent. This approach places a heavy burden on the programmer, who must know all the constraints that an action may violate and must include checks for each of these constraints. An omission, misunderstanding, or error by the programmer will likely leave the database in an inconsistent state.

Entity Relationship (ER) model is a common conceptual database design tool used for relational database design.  To enforce the business rules, some business rules can be included in this ER model in the form of constraints. However, including constraints in this graphical model is just a reminder for the programmer to include them in his database implementation. The problem is that constraint is very rigid and the database becomes programmer dependent and there is no grantee that programmer will include them in his implementation. 
 
An alternative solution for this problem is to implement the constraints in the form of triggers. Trigger is a program and is more flexible than a constraint. Trigger has Event, Condition and Action (ECA) property. When an event take place and consequently a condition becomes true, the trigger takes action automatically and modifies the database as needed. 

In this paper, we use the ER notation to represent some business rules (constraints) graphically for a university database and write triggers to implement them to ensure the consistency of the data in the database. 



AU  - Reza Sanati-Mehrizy
AU  - Afsaneh Minaie
CY  - Virtual Conference
DA  - 2021/07/26
PB  - ASEE Conferences
TI  - Writing Triggers to Implement Business Rules in a Relational Database
UR  - https://strategy.asee.org/38223
DO  - 10.18260/1-2--38223
ER  -