Petri nets: an introduction
Coloured Petri nets: basic concepts, analysis methods and practical use, vol. 2
Coloured Petri nets: basic concepts, analysis methods and practical use, vol. 2
The entity-relationship model—toward a unified view of data
ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
Petri Net Theory and the Modeling of Systems
Petri Net Theory and the Modeling of Systems
ICATPN '97 Proceedings of the 18th International Conference on Application and Theory of Petri Nets
Distributed verification with LoLA
Fundamenta Informaticae - Concurrency specification and programming
Case handling: a new paradigm for business process support
Data & Knowledge Engineering
Consistency in model integration
Data & Knowledge Engineering - Special issue: Business process management
Yasper: a tool for workflow modeling and analysis
ACSD '06 Proceedings of the Sixth International Conference on Application of Concurrency to System Design
ExSpect 6.4: an executable specification tool for hierarchical colored Petri nets
ICATPN'00 Proceedings of the 21st international conference on Application and theory of petri nets
CPN tools for editing, simulating, and analysing coloured Petri nets
ICATPN'03 Proceedings of the 24th international conference on Applications and theory of Petri nets
Hi-index | 0.00 |
A case handling system is an information system supporting the handling of cases. The (sub) tasks for a particular case are performed by persons or software agents and the result of a task is the updating of the case data. Case handling systems consist of three parts: (1) a workflow engine that executes the process of a case, (2) a document manager that manipulates the case data and (3) a database manager for manipulation of the global data, i.e., the data that is independent of a particular case. In this paper we present a new methodology for the first four phases of the development of a case handling system: (1) user requirements, (2) functional architecture, (3) software architecture, and (4) the prototyping phase. The methodology is supported by a tool consisting of a Petri net based workflow engine, a standard document manager and a standard database system.