Using rules to adapt applications for business models with high evolutionary rates

Abstract

Nowadays, business models are in permanent evolution since the requirements belongs to a rapidly evolving world. In a context where communications all around the world travel so fast the business models need to be adapted permanently to the information the managers receive. In such world, traditional software development, needed for adapting software to changes, do not work properly since business changes need to be in exploitation in shorter times. In that situation, it is needed to go quicker from the business idea to the exploitation environment. This issue can be solved accelerating the development speed: from the expert to the customer, with no –or few, technical intervention. This paper proposes an approach to empower domain experts in developing adaptability solutions by using automated sets of production rules in a friendly way. Furthermore, a use case that implements this kind of development was used in a real problem prototype

Self Learning Computer Troubleshooting Expert System

“…Each predecessor of a rule specifically looks the given problem instance that satisfies the given conditions. When the consequents of the rules are executed, the rule is said to be fired [16].…”

Pervasive Systems Development: A Stepwise Rule-centric Rigorous Service-Oriented Architectural Approach

“…Boosted by technological advances in networking, context-sensing and computation and pressed by stiff and global competitiveness, most of organizations are opportunistically joining their know-how into dynamic giant cross-organizational alliances. Striking features of any of such alliances, include: (1) process-centricity, that is, they exhibit very complex business processes with composing activities; (2) high-agility, where involved business processes and their activities / tasks are often governed by adaptive and evolving business rules [6,9,10,11,16]; (3) contextdependency, with user-preferences, adopted sensing devices and surrounding environment conditions as driving forces [4,5,28]; (4) strong-dependability, where the fatality of malfunctioning and failures may be economical und humanistic disastrous. Precise conceptualizations and formal techniques are thus highly required before investing any final deployment.…”

“…[Rule-centric architectural handling]: Towards intuitively coping with agility in such volatile business applications, we are capitalizing on the ubiquity of business rules in such applications. Indeed, business rules reflect evolving policies and laws for doing / collaborating business [6,9,10,16]. Furthermore, to enhance agility and bridge the gap to service-orientation, we shift any intuitive business rule towards transient architectural ECA-driven connectors [13].…”