Welcome to the InfoSci Platform
A Declarative Approach to Systems Development

A Declarative Approach to Systems Development

Deepak Kumar Sharma
Copyright: © 2020 |Pages: 31
ISBN13: 9781799829751|ISBN10: 1799829758|ISBN13 Softcover: 9781799829768|EISBN13: 9781799829775
DOI: 10.4018/978-1-7998-2975-1.ch003
Cite Chapter Cite Chapter

MLA

Sharma, Deepak Kumar. "A Declarative Approach to Systems Development." Novel Approaches to Information Systems Design, edited by Naveen Prakash and Deepika Prakash, IGI Global, 2020, pp. 40-70. https://doi.org/10.4018/978-1-7998-2975-1.ch003

APA

Sharma, D. K. (2020). A Declarative Approach to Systems Development. In N. Prakash & D. Prakash (Eds.), Novel Approaches to Information Systems Design (pp. 40-70). IGI Global. https://doi.org/10.4018/978-1-7998-2975-1.ch003

Chicago

Sharma, Deepak Kumar. "A Declarative Approach to Systems Development." In Novel Approaches to Information Systems Design, edited by Naveen Prakash and Deepika Prakash, 40-70. Hershey, PA: IGI Global, 2020. https://doi.org/10.4018/978-1-7998-2975-1.ch003

Export Reference

Mendeley
Favorite

Abstract

The declarative approach specifies what is to be done rather than how to do it. When adopted in information systems development, this implies that the system should be seen as a collection of business rules that can be enacted using a business rules engine. Business rules should be expressed in a form that is as close to the one in which business people perceive the rules. A business rules management system is needed to acquire, store, and allow modification of a business rules database. The rules are then handed over to a rules engine for enactment. The BRMS considered in this chapter uses an antecedent-consequent form for representing rules. These are based in a first order logic. Rules are formed with courses of actions and conditions in rules antecedents and courses of actions in rule consequents. It also introduces notions of state change in the business rule and temporal relation within rule and between different rules. Business rules are structured into atomic, complex, and abstract rules. The business rules are translated into enactment rules and converted to Java.

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.