A rule language to capture and model business policy specifications

McBrien, Peter; Niezette, Marc; Pantazis, Dionysios; Seltveit, Anne Helga; Sundin, Ulf; Theodoulidis, Babis; Tziallas, G. D.; Wohed, Rolf

doi:10.1007/3-540-54059-8_91

Cited by 13 publications

(5 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Most often, such rules are implemented directly in source code. In information systems, this represents potential problems since business policy may change over time, making current information systems obsolete (McBrien et al 1991). Historical data should always be viewed in context with the rules that were current at the time in question.…”

Section: Rules Knowledge and Business Policymentioning

confidence: 99%

See 1 more Smart Citation

Modelling the Real World: Conceptual Modelling in Spatiotemporal Information System Design

Renolen

2000

Transactions in GIS

View full text Add to dashboard Cite

Throughout the relatively young history of research on spatiotemporal modelling, a substantial number of models have been presented. However, since a spatiotemporal model represents a closer approximation to the real world than is the case for traditional models, such models must be based on a thorough understanding of how objects`behave' in reality. One way to acquire such knowledge is using conceptual modelling methodologies. In this paper, an overview of different modelling principles and a selection of conceptual modelling languages are presented together with examples related to a selection of spatiotemporal problems.

show abstract

Section: Rules Knowledge and Business Policymentioning

confidence: 99%

“…The rule can then be viewed as describing some logical constraint on the model, which must hold at every moment (or tick) whilst the information system is active (McBrien et al 1991).…”

Section: Rules Knowledge and Business Policymentioning

confidence: 99%

Modelling the Real World: Conceptual Modelling in Spatiotemporal Information System Design

Renolen

2000

Transactions in GIS

View full text Add to dashboard Cite

show abstract

“…IF processing-unit (X) consists-of equipment (Y) [has weight --'heavy', has price = 'expensive'] THEN high-pressure-process (Y) An action rule expresses what actions to be taken if an event occurs and the conditions evaluate to true. For example, stating that upon receiving a change request provided that information about compressor conditions is available, new separator conditions will be computed, can be expressed as: WHEN change-request (Separator, Temperature) IF compressor-condition (Condition) AND calculate-pressure (Temperature, Condition, Pressure) THEN separator-condition (Pressure) AND processing-unit consists-of separator (Separator) [has operational-conditions has pressure = Pressure] For a detailed description of ERL, see [17,29,31].…”

Section: Simplified Oil Processing Examplementioning

confidence: 99%

“…The conceptual model has three components: the ERT Model [18,31], the Process Model [3,19], and the External Rule Language [17,29,31]. The ERT Model is an extended Entity Relationship Model and describes the static aspects of the real world, whereas the Process and Rule Models describe the dynamic aspects including the temporal dimension.…”

mentioning

confidence: 99%

An abstraction-based rule approach to large-scale information systems development

Seltveit

1993

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

View full text Add to dashboard Cite

By introducing a rule language in IS development business rules can be explicitly represented. However, the use of rules implies that we have to find ways to deal with rule capture and complexity of large rule bases. The paper argues for an abstraction-based rule approach to information systems development. Simplifications of a specification are provided by allowing different views (abstractions) of the rule base and a framework for describing abstractions is suggested. A view is generated by a set of expficitly defined abstraction mechanisms, manually produced by a developer, or a combination of the two. Rather than operating on a full specification, relevant views can be applied at different stages of the development process (e.g., in rule capture) and then eventually integrated into a new version of the full specification. Views may be updated and multiple views are allowed to co-exist. Supporting multiple views and various versions of views demands for a versioning mechanism to keep track of the various versions of a full specification.

show abstract

“…This theoretical framework has been developed in the context of a number of large, industrial-size applications (Loucopoulos et al, 1991a, b;McBrien et al, 1991;Loucopoulos and Katsouli, 1992;Loucopoulos et al, 1998;Prekas and Loucopoulos, 2000;Wangler et al, 1999). The empirical evidence obtained from these projects has been instrumented in influencing the roadmap presented in this paper.…”

Section: Introductionmentioning

confidence: 99%

A roadmap for the elicitation of business rules in information systems projects

Kardasis¹,

Loucopoulos

2005

Business Process Management Journal

View full text Add to dashboard Cite

Purpose-In this paper we present a roadmap for the elicitation of business rules based on different stakeholders' perspectives, in order to facilitate the processes of structuring, organizing and expressing business tactic and policy in a way that it is close to the business milieu and stakeholders' viewpoints. Design/methodology/approach-This paper has derived from a combined research practice. Initially, the development of a roadmap for understanding different stakeholders' perspectives and for identifying their views on business tactics and policies was based on well-grounded work on enterprise goal modelling, combined with a theoretical study of business rule-related concepts. The outcome of this work was tested against a real business case dealing with the development of an electronic procurement system in the prefabricated construction sector. Findings-As a conclusion, the paper put forward a comprehensive methodological framework for dealing with rule-intensive projects. The proposed roadmap can help IT practitioners in collecting and organizing business rule statements that apply within a particular organization, either towards the implementation of change on a business level, or in the context of specifying the (existing or future) functionality of supporting information systems (IS). Research limitations/implications-The rule roadmap presented here has been coupled with a modelling approach for expressing rules in a structured, consistent manner and for organizing them in a rule repository. Future work includes the extension of this approach to cover design and implementation as part of rule-centric information systems engineering. Practical implications-Therefore, the overall contribution of this work relates to the provision of guidance for identifying business policy and tactics at an intentional level (through the investigation of the rationale behind them) and for transforming relevant models to the operational level, where business rules are linked to business processes, information and systems. Originality/value-Although the business rule concept has been examined from different points of view over the past years, the paper attempts to bridge the gap between approaches that see rules as extensions of business goals, other approaches that consider rules as limitations on the way business activities are performed, and finally, approaches according to which rules constrain the creation, modification and deletion of information entities.

show abstract

A rule language to capture and model business policy specifications

Cited by 13 publications

References 6 publications

Modelling the Real World: Conceptual Modelling in Spatiotemporal Information System Design

Modelling the Real World: Conceptual Modelling in Spatiotemporal Information System Design

An abstraction-based rule approach to large-scale information systems development

A roadmap for the elicitation of business rules in information systems projects

Contact Info

Product

Resources

About