Abstract
Adaptive Case Management (ACM) has emerged as a key BPM technology for supporting the unstructured business process. A key problem in ACM is that case schemas need to be changed to best fit the case at hand. Such changes are ad hoc, and may result in schemas that do not reflect the intended logic or properties. This article presents a formal approach for reasoning about which properties of a case schema are preserved after a modification, and describes change operations that are guaranteed to preserve certain properties. The approach supports reasoning about rollbacks. The Case Management model used here is a variant of the Guard-Stage-Milestone model for declarative business artifacts. A real-life example illustrates applicability.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
