https://github.com/bptlab/bpm2019ws-fcm-compliance
Checking Compliance in Data-Driven Case Management
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
○Committers with academic emails
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (10.9%) to scientific vocabulary
Repository
Checking Compliance in Data-Driven Case Management
Basic Info
- Host: GitHub
- Owner: bptlab
- Default Branch: master
- Homepage: https://bptlab.github.io/bpm2019ws-fcm-compliance/
- Size: 1.38 MB
Statistics
- Stars: 0
- Watchers: 4
- Forks: 0
- Open Issues: 0
- Releases: 0
Metadata Files
README.md
Checking Compliance in Data-Driven Case Management
Case management approaches address the special requirements of knowledge workers. In fragment-based case management (fCM), small structured parts are modelled and loosely coupled through data dependencies, which can be freely combined at run-time. When executing business processes, organizations must adhere to regulations, to laws, to company guidelines etc. Business process compliance comprises methods to verify designed and executed business processes against certain rules. While design-time compliance checking works well for structured process models, flexible knowledge-intensive processes have been rarely considered despite increasing interest in academia and industry.
In this paper, we present (i) formal execution semantics of fCM models using Petri nets. We also cover concurrently running fragment instances and case termination. We (ii) apply model checking to investigate the compliance with temporal logic rules; finally, we (iii) provide an implementation based on the open-source case modeler Gryphon and the free model checker LoLA.
Screencast
How to run it yourself
The compliance-enabled fCM system consists of three components:
- Gryphon, a web-based fCM modeller. Use the compliance branch.
- Chimera, an execution engine for fCM. Use the compliance branch.
- LoLA webservice, a web service wrapper for LoLA.
Ideally, the components are used together via Docker Compose:
- Clone the three repositories locally to a new folder.
- Check out Gryphon's compliance branch.
- Check out Chimera's compliance branch.
- Build the Gryphon image:
docker build -t bptlab/gryphon:dev gryphon/ - Build the Chimera image:
cd chimera && make build_docker && cd .. - Download the LoLA webservice image:
docker-compose -f lola-webservice/docker-compose.yml pull - Start all three components:
docker-compose -f chimera/docker-compose.yml -f gryphon/docker-compose.yml -f lola-webservice/docker-compose.yml up -d gryphon database lola-webservice chimera - Navigate to
http://localhost:3000to access Gryphon. - Stop all three components:
docker-compose -f chimera/docker-compose.yml -f gryphon/docker-compose.yml -f lola-webservice/docker-compose.yml down --remove-orphans
In order to check compliance, the case model must be deployed to Chimera.
The example case model
The example Emergency case model can be downloaded and imported into Gryphon.
Owner
- Name: Business Process Technology
- Login: bptlab
- Kind: organization
- Location: Potsdam, Germany
- Website: https://bpt.hpi.uni-potsdam.de
- Repositories: 37
- Profile: https://github.com/bptlab
Business Process Technology @ Hasso Plattner Institute, University of Potsdam
GitHub Events
Total
Last Year
Committers
Last synced: about 1 year ago
Top Committers
| Name | Commits | |
|---|---|---|
| Adrian Holfter | g****t@a****e | 10 |
Committer Domains (Top 20 + Academic)
Issues and Pull Requests
Last synced: about 1 year ago
All Time
- Total issues: 0
- Total pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 0
- Total pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0