Using Business Rules within a Design Process of Active Databases

Using Business Rules within a Design Process of Active Databases

Youssef Amghar, Madjid Meziane, Andre Flory
Copyright: © 2002 |Pages: 24
ISBN13: 9781931777025|ISBN10: 1931777020|EISBN13: 9781931777216
DOI: 10.4018/978-1-931777-02-5.ch008
Cite Chapter Cite Chapter

MLA

Amghar, Youssef, et al. "Using Business Rules within a Design Process of Active Databases." Data Warehousing and Web Engineering, edited by Shirley Becker, IGI Global, 2002, pp. 161-184. https://doi.org/10.4018/978-1-931777-02-5.ch008

APA

Amghar, Y., Meziane, M., & Flory, A. (2002). Using Business Rules within a Design Process of Active Databases. In S. Becker (Ed.), Data Warehousing and Web Engineering (pp. 161-184). IGI Global. https://doi.org/10.4018/978-1-931777-02-5.ch008

Chicago

Amghar, Youssef, Madjid Meziane, and Andre Flory. "Using Business Rules within a Design Process of Active Databases." In Data Warehousing and Web Engineering, edited by Shirley Becker, 161-184. Hershey, PA: IGI Global, 2002. https://doi.org/10.4018/978-1-931777-02-5.ch008

Export Reference

Mendeley
Favorite

Abstract

Modeling behavior is an important task of the information system engineering process. This task is especially important when information systems are centered on active databases, which allow the replacement of parts of application programs with active rules. To relieve programmers from using either traditional or ad hoc techniques to design active databases, it is necessary to develop new techniques to model business rules. For that reason, inclusion of rules during analysis and design stages becomes an actual requirement. In this paper, we propose a uniform approach to modeling business rules (active rules, integrity constraints, etc. ). To improve the behavior specification, we extend the state diagrams that are widely used for dynamic modeling. This extension is a transformation of state transitions according to rule semantics. In addition, we outline new functionalities of Computer Aided System Engineering (CASE) to take into consideration the active database specificities. In this way, the designer can be assisted to control, maintain, and reuse a set of rules.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.