The era where business rules are buried in Cobol code is coming to an end, and users themselves may seek to dynamically change their business rules. Customers require systems that more easily adapt to changing business needs, meet their unique requirements, and scale to large and small installations. On the other hand, the same technique is adequate for the slightly different purpose of producing a whole line of software products. Of course, a line of products may be obtained by variously instantiating an abstract model, and by adapting a given initial system to various requirements that appear simultaneously instead of evolving in time. Moreover the diversification of a successful product may also be seen as a form of re-engineering. This paper analyzes the so-called exceptions and adaptive changes in modern enterprise-wide information systems and advocates a generic mechanism for handling them.
[1]
Christoph Bußler.
Specifying Enterprise Processes with Workflow Modeling Languages
,
1996
.
[2]
ShethAmit,et al.
An overview of workflow management
,
1995
.
[3]
Amit P. Sheth,et al.
A Taxonomy of Adaptive Workflow Management
,
2002
.
[4]
Christoph Bussler,et al.
Workflow Management: Modeling Concepts, Architecture and Implementation
,
1996
.
[5]
Amit P. Sheth,et al.
On Adaptive Workflow Modeling
,
1998
.
[6]
Grzegorz Rozenberg,et al.
Dynamic change within workflow systems
,
1995,
COCS '95.
[7]
Amit P. Sheth,et al.
Supporting State-Wide Immunisation Tracking Using Multi-Paradigm Workflow Technology
,
1996,
VLDB.