Skip to main content
SpringerLink
Log in

Enterprise Modeling and Decision-Support for Automating the Business Rules Lifecycle

  • Published:
Automated Software Engineering Aims and scope Submit manuscript

Abstract

Business rules represent policies, procedures and constraints regarding how an enterprise conducts its business. To get the full benefits of modeling business rules requires an approach to managing them through their full lifecycle, from acquisition through deployment and evolution. The research reported in this paper is aimed at determining what infrastructure capabilities are needed to provide this lifecycle support. The solution embodies a modeling framework that captures the structure of the enterprise, in terms of which the business rules can be expressed, and decision-support capabilities for reasoning about and deriving business rules. The paper demonstrates the possibility of automatic support of the business rules lifecycle by automatically generating business rules from the captured information, along with data representing domain assumptions in a case study (the London Ambulance System). A system was implemented to illustrate the methodology and to demonstrate the feasibility of the approach. The methodology also gives guidance on how to deal with pragmatically important situations such as rules that involve both automated and human tasks, nondeterministic rules, and goal-oriented versus operational rules.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  • Balzer, R. 1991. Tolerating inconsistency. In Proceedings ICSE'91, Silver Spring, MD: IEEE Computer Press, pp. 158–165.

    Google Scholar 

  • Basili, V. and Weiss, D.M. 1984. Amethodology for collecting valid software engineering data. IEEE Transactions on Software Engineering, 10(6):728–738.

    Google Scholar 

  • Boehm, B., Bose, P., Horowtiz, E., and Lee, M.J. 1995. Requirements negotiation and renegotiation aids: A theory-w based spiral approach. In Proceedings ICSE'95, Silver Spring, MD: IEEE Computer Society Press, pp. 23–30.

    Google Scholar 

  • Bubenko, Jr. J. and Wangler, B. 1993. Objectives driven capture of business rules and of information systems requirements. In Proceedings of the International Conference on Systems, Man and Cybernetics, pp. 670–677.

  • Champion, R. and Moores, T. 1996. Exploiting an enterprise model during systems' requirements capture and analysis. In Proceedings of the International Conference on Requirements Engineering ICRE'96, Silver Spring, MD: IEEE Computer Society Press.

    Google Scholar 

  • Chen, Y., Segarra, G., and Chong, P. 1992. Visualizing business rules in corporate databases. IndustrialManagement and Data Systems, 92(7):3–8.

    Google Scholar 

  • Chung, L., Nixon, B., and Yu, E. 1995. Using non-functional requirements to systematically support change. In Second IEEE International Symposium on Requirements Engineering.

  • Chung, L., Nixon, B., Yu, E., and Mylopoulos, J. 1999. Non-Functional Requirements in Software Engineering. Norwell, MA: Kluwer Academics.

    Google Scholar 

  • Conklin, J. and Begeman, M. 1988. gIBIS: A hypertext tool for exploratory policy discussion. ACM Trans. Office Info. Systems, 6(4):303–331.

    Google Scholar 

  • Easterbrook, S. and Nuseibeh, B. 1995. Managing inconsistencies in an evolving specification. In Proceedings RE'95, Silver Spring, MD: IEEE Computer Press, pp. 48–55.

    Google Scholar 

  • Feuerlicht, G. and Blair, A. 1990. An architecture for managing business rules using knowledge engineering techniques in RDBMS environment. In Proceedings 4th Australian Joint Conference on Artificial Intelligence, pp. 384–393.

  • Fickas, S. and Feather, M. 1995. Requirements monitoring in dynamic environments. In Proceedings of IEEE International Symposium on Requirements Engineering.

  • Finkelstein, A. and Dowell, J. 1996. Acomedy of errors: The London Ambulance Service case study. In Proceedings of the 8th International Workshop on Software Specifications and Design (IWSSD'96), Silver Spring, MD: IEEE Computer Press.

    Google Scholar 

  • Finkelstein, A., Gabbay, D., Hunter, A., Kramer, J., and Nuseibeh, B. 1994. Inconsistency handling in multiple-perspective specifications. IEEE Transactions in Software Engineering, 20(8):569–578.

    Google Scholar 

  • Ghezzi, C. and Nuseibeh, B. 1998. Special issue on managing inconsistency in software development. IEEE Transactions on Software Engineering, 24(11):906–907.

    Google Scholar 

  • Gotel, O. and Finkelstein, A. 1994. An analysis of the requirements traceability problem. In Proceedings of the International Conference on Requirements Engineering, Silver Spring, MD: IEEE Computer Society Press.

    Google Scholar 

  • Greenspan, S. and Feblowitz, M. 1993. Requirements engineering using the SOS paradigm. In Proceedings of IEEE International Symposium on Requirements Engineering, San Diego.

  • Hammer, M. 1990. Reengineering work: Don't automate, obliterate. Harvard Business Review.

  • Hauser, J. and Clausing, D. 1988. The house of quality. Harvard Business Review, 63–73.

  • Herbst, H. 1995. A meta-model for specifying business rules in system analysis. In Proceedings of CAiSE'95, pp. 186–199.

  • Herbst, H. and Myrach, T. 1995. A repository system for business rules. Technical Report 57, Institute of Information Systems, University of Berne.

  • Intellicorp. 1995. LiveModel User's Guide.

  • Jarke, M. and Kurki-Suonio, R. 1998. Special issue on scenario management. IEEE Transactions on Software Engineering, 24(12):1033–1035.

    Google Scholar 

  • Kilov, H. 1997. Business rules: From business specification to design. Technical Report, IBM, T.J. Watson.

  • Lamsveerde, A.V., Darimont, R., and Massonet, P. 1995. Goal-directed elaboration of requirements for a meeting scheduler: Problems and lessons learnt. In Proceedings of RE'95, Silver Spring, MD: IEEE Computer Society Press.

    Google Scholar 

  • Lee, J. 1991. Extending the Potts and Bruns model for recording design rationale. In International Conference on Software Engineering, pp. 114–125.

  • Lee, J. 1992. Capturing, reusing, and managing the reasons for decisions. Ph.D. Thesis, Department of Computer Science, MIT.

  • Leite, J. and Leonardi, C. 1998. Business rules as organizational policies. In Proceedings of the International Workshop on Software Specifications and Design, Silver Spring, MD: IEEE Computer Society Press.

    Google Scholar 

  • Loucopoulos, P. and Karakostas, V. 1995. System Requirements Engineering. New York: McGraw Hill.

    Google Scholar 

  • Loucopoulos, P. and Katsouli, E. 1992. Modelling business rules in an office environment. SIGOIS Bulletin, 13(2):28–37.

    Google Scholar 

  • MacLean, A., Young, R., Bellotti, V., and Moran, T. 1991. Questions, options, and criteria. Human-Computer Interaction, 6:201–250.

    Google Scholar 

  • Martin, J. and Odell, J. 1995. Object-Oriented Methods: A Foundation, ch. 20. New York: Prentice Hall.

    Google Scholar 

  • Nuseibeh, B., Kramer, J., and Finkelstein, A. 1994. A framework for expressing the relationships between multiple views in requirements specification. IEEE Transactions on Software Engineering.

  • Paul, L. 1995. Hidden assets. PC Week.

  • Paulk, M. Curtis, B. and Chrisis, M. Capability maturity model for software, version 1.1. Technical Report, Software Engineering Institute.

  • Phol, K. 1996. Process-Centered Requirements Engineering. New York: John Wiley.

    Google Scholar 

  • Pohl, K., Domges, R., and Jarke, M. 1997. Towards method-driven trace capture. In Proceedings of CAiSE'97.

  • Quinlan, J. 1986. Induction of decision trees. Machine Learning, 1:81–106.

    Google Scholar 

  • Quinlan, J. 1987. Generating production rules from decision trees. In Proceedings IJCAI, pp. 304–307.

  • Quinlan, J. 1993. C4.5: Programs for Machine Learning. Los Altos: Morgan Kauffmann.

    Google Scholar 

  • Ramesh, B. 1991. Process Knowledge Based Support for Systems Development. Ph.D. Thesis, Leonard Stern School of Business, New York University.

  • Ramesh, B. 1992. Supporting systems development by capturing deliberations during requirements engineering. IEEE Transactions on Software Engineering, 18(6):498–510.

    Google Scholar 

  • Reubenstein, H. 1995. An analysis of a business rules sampler. Technical Report 0304–09–95–163, GTE Laboratories.

  • Rosca, D. and D'Attilio, J. 2001. Interoperability of distributed systems through XML-encoded business rules. In Proceedings Software Engineering and XML Technologies Workshop, ICSE'01, pp. 56–61.

  • Rosca, D., Greenspan, S., Feblowitz, M., and Wild, C. 1997. A decision making methodology in support of the business rules lifecycle. In Proceedings of the International Symposium on Requirements Engineering RE97 Conference, pp. 236–246.

  • Rosca, D., Greenspan, S., Wild, C., Reubenstein, H., Maly, K., and Feblowitz, M. 1995. Application of a decision support mechanism to the business rules lifecycle. In Proceedings of the Knowledge Based Software Engineering KBSE95 Conference, pp. 114–122.

  • Rosca, J. and Rosca, D. 1989. Knowledge acquisition facilities within an expert system toolkit. In Proceedings of the Seventh International Symposium on Computer Science, Jassy, Romania.

  • Rosca, D. and Wild, C. 2001. Towards a flexible deployment of business rules. Journal of Expert Systems with Applications, Special Issue on SEKE'01, to appear.

  • Ross, R. 1997. The Business Rules Handbook: Classifying, Defining and Modeling Rules. Database Research Group, Inc., Boston, MA.

    Google Scholar 

  • Sandifer, A. and von Halle, B. 1993. Business rules: Capturing the most elusive information asset. In B. von Halle and A. Kull, editors, Handbook of Data Management. Philadelphia, PA: Auerbach.

    Google Scholar 

  • Shannon, C.E. 1964. The Mathematical Theory of Communication. Champaign, IL: University of Illinois Press. [c1949].

    Google Scholar 

  • Sibley, E., Wexelblat, R., Michael, J., Tanner, M., and Littman, D. 1992. The role of policy in requirements definition. In Proceedings of the International Conference on Requirements Engineering, Silver Spring, MD: IEEE Computer Society Press.

    Google Scholar 

  • Snedecor, G. and Cochran, W. 1980. Statistical Methods. Iowa State University Press.

  • Taveter, K. 1999. Business rules approach to the modeling, design, and implementation of agent-oriented information systems, In Proceedings of The Agent-Oriented Information Systems Workshop, CAiSE'99.

  • Taveter, K. and Wagner, G. 2000. Combining aor diagrams and ross business rules' diagram for enetrprise modeling. In Proceedings of The Agent-Oriented Information Systems Workshop, CAiSE'2000.

  • Terveen, L. and Selfridge, P. 1995. “Living Design Memory”— Framework, implementation, lessons learned. Human Computer Interaction, 6(1):1–37.

    Google Scholar 

  • Ullman, J. and Widom, J. 1997. A First Course in Database Systems. New York: Prentice Hall.

    Google Scholar 

  • van Lamsverde, A. 2000. Requirements engineering in the year 00: A research perspective. In Proceedings ICSE 2000, IEEE Computer Press, pp. 5–19.

  • van Lamsweerde, A., Darimont, R., and Letier, E. 1998. Managing conflicts in goal-driven requirements engineering. IEEE Transactions in Software Engineering, 24(11):908–925.

    Google Scholar 

  • von Halle, B. 1993a. Staying the course. Database Programming Design, August:13–16.

  • von Halle, B. 1993b. Making business rules real. Database Programming Design, September:13–15.

  • Wangler, B., Wingstedt, U., and Wohed, R. 1995. Requirements capture in practice: Experiences from a case study at Sweden Post. Technical Report, SISU.

  • Wild, C. and Rosca, D. 1994. Evolution and reuse of formal specifications using decision structures. In Proceedings of the KBSE94 Conference, pp. 108–115.

  • Wood, J. and Silver, D. 1995. Joint Application Design. New York: Wiley.

    Google Scholar 

  • Yu, E. 1994. Modelling Strategic Relationships for Process Reengineering. Ph.D. Thesis, University of Toronto.

  • Yu, E. 1997. Towards modeling and reasoning support for early-phase requirements engineering. In Proceedings RE'97, IEEE Computer Press, pp. 226–235.

  • Yu, E. and Mylopoulos, J. 1996. Using goals, rules, and methods to support reasoning in business process reengineering. International Journal of Intelligent Systems in Accounting, Finance and Management, 5(1):1–13.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Department of Software Engineering, Monmouth University, W. Long Branch, NJ, 07764, USA

    Daniela Rosca

  2. Department of Computer Science, Old Dominion University, Norfolk, VA, 23529-0162, USA

    Sol Greenspan (Consultant) & Chris Wild

Authors
  1. Daniela Rosca
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Sol Greenspan
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Chris Wild
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

About this article

Cite this article

Rosca, D., Greenspan, S. & Wild, C. Enterprise Modeling and Decision-Support for Automating the Business Rules Lifecycle. Automated Software Engineering 9, 361–404 (2002). https://doi.org/10.1023/A:1020372710433

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1023/A:1020372710433

Search

Navigation