Advertisement

A Cutting-Edge Unified and Stable Rule Design Pattern

  • Mohamed E. FayadEmail author
  • Gaurav Kuppa
  • Siddharth Jindal
  • David Hamu
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 1069)

Abstract

Often, changing market dynamics require business applications to quickly and efficiently adapt to the needs of the ensuing business environment. Business Rules excel in delivering software solutions that are implicitly adaptable to changing business requirements; thus they can prove to be an effective tool to provide necessary flexibility and control for rapidly deploying changes across a wide array of business operations. When a proper design is employed, business rules provide a robust and capable way of enabling enterprise software that adapts to changing business needs. In other words, business rules find varied applications and ways of use, for example, managing a pending problem, using it as production rules and for facilitating collaboration between various systems, etc. However, despite a plethora of tools and technologies available, most organizations still find it difficult to define or model workable business rules explicitly. Furthermore, from a macroscopic point of view, rules are important and inseparable artifacts in governing a software application to make it comply with the system goals. In this paper, the current ways to manage business rules along with their pitfalls are discussed, and therefore, a new approach for developing rule-based business architectures is proposed. The proposed approach allows for both managing and reusing business rules.

Keywords

Software reuse Stable design patterns Software Stability Model Business Rules Knowledge map Adaptability 

References

  1. 1.
    Griss, M.L.: Software reuse: from the library to the factory. IBM Syst. J. 32(4), 1–23 (1993)CrossRefGoogle Scholar
  2. 2.
    Griss, M.L., Wentzel, K.D.: Hybrid domain-specific kits for a flexible software factory. In: Proceedings: SAC 1994, Phoenix, Arizona, March 1994Google Scholar
  3. 3.
    Gaffney, J.E., Cruickshank, R.D.: A general economics model of software reuse. In: Proceedings: 14th ICSE, Melbourne Australia, May 1992Google Scholar
  4. 4.
    Mahdy, A., Fayad, M.E., Hamza, H., Tugnawat, P.: Stable and reusable model-based architectures. In: ECOOP 2002, Workshop on Model-Based Software Reuse, Malaga, Spain, June 2002Google Scholar
  5. 5.
    Hamza, H., Fayad, M.E.: Model-based software reuse using stable analysis patterns. In: ECOOP 2002, Workshop on Model-based Software Reuse, Malaga, Spain, June 2002Google Scholar
  6. 6.
    Fayad, M.E.: Stable Design Patterns for Software and Systems. Auerbach Publications, Boca Raton, FL (2015)Google Scholar
  7. 7.
    Fayad, M.E., Altman, A.: Introduction to software stability. Commun. ACM 44(9) (2001)CrossRefGoogle Scholar
  8. 8.
    Fayad, M.E.: Accomplishing software stability. Commun. ACM 45(1) (2002a)Google Scholar
  9. 9.
    Fayad, M.E.: How to deal with software stability. Commun. ACM 45(4) (2002b)CrossRefGoogle Scholar
  10. 10.
    Ross, R.G.: Business Rule Concepts: Getting to the Point of Knowledge, 4th edn. Business Rule Solutions, LLC, April 2013Google Scholar
  11. 11.
    Jindal, S.: Stable Business Rule Standards. Masters Thesis, San Jose State University (2015)Google Scholar
  12. 12.
    Fayad, M.E., Sanchez, H.A., Hegde, S.G.K., Basia, A., Vakil, A.: Software Patterns, Knowledge Maps, and Domain Analysis. Auerbach Publications, Boca Raton (2014)CrossRefGoogle Scholar
  13. 13.
    Fayad, M.E., Cline, M.: Aspects of software adaptability. Commun. ACM 39(10), 58–59 (1996)CrossRefGoogle Scholar
  14. 14.
    Muehlen, Z., Michael, M.I., Kittel, K.: Towards integrated modeling of business processes and business rules. In: ACIS 2008 Proceedings, vol. 108 (2008). [Arch]Google Scholar
  15. 15.
    Arsanjani, A.: Rule object 2001: a pattern language for adaptive and scalable business rule construction. In: PLoP 2001 Conference on Business Rule Construction. National EAD Center of Competency, p. 12. IBM, Raleigh (2001)Google Scholar

Copyright information

© Springer Nature Switzerland AG 2020

Authors and Affiliations

  • Mohamed E. Fayad
    • 1
    Email author
  • Gaurav Kuppa
    • 1
  • Siddharth Jindal
    • 1
  • David Hamu
    • 2
  1. 1.San Jose State UniversitySan JoseUSA
  2. 2.Liberty ConsultingPhoenixUSA

Personalised recommendations