The transformation schema: An extension of the data flow diagram to represent control and timing
IEEE Transactions on Software Engineering
An overview of workflow management: from process modeling to workflow automation infrastructure
Distributed and Parallel Databases - Special issue on software support for work flow management
ICSE '97 Proceedings of the 19th international conference on Software engineering
A Knowledge-based Approach to Handling Exceptions inWorkflow Systems
Computer Supported Cooperative Work
Business Modeling With UML: Business Patterns at Work
Business Modeling With UML: Business Patterns at Work
Improving Business Process Quality through Exception Understanding, Prediction, and Prevention
Proceedings of the 27th International Conference on Very Large Data Bases
A Comprehensive View of Process Engineering
CAiSE '98 Proceedings of the 10th International Conference on Advanced Information Systems Engineering
Little-JIL 1.0 Language Report TITLE2:
Little-JIL 1.0 Language Report TITLE2:
Interaction Protocols as Design Abstractions for Business Processes
IEEE Transactions on Software Engineering
YAWL: yet another workflow language
Information Systems
What business process modelers can learn from programmers
Science of Computer Programming
Representing process variation with a process family
ICSP'07 Proceedings of the 2007 international conference on Software process
Formalisms to support the definition of processes
Journal of Computer Science and Technology
Integrating clinical pathways into CDSS using context and rules: a case study in heart disease
Proceedings of the 2nd ACM SIGHIT International Health Informatics Symposium
Hi-index | 0.00 |
In many modern enterprises, explicit business process definitions facilitate the pursuit of business goals in such ways as best practice reuse, process analysis, process efficiency improvement, and automation. Most real-world business processes are large and complex. Successfully capturing, analysing, and automating these processes requires process definition languages that capture a variety of process aspects with a wealth of details. Most current process modeling languages, such as Business Process Modeling Notation (BPMN), focus on structural control flows among activities while providing inadequate support for other process definition needs. In this paper, we first illustrate these inadequacies through our experiences with a collection of real-world reference business processes from the Australian lending industry. We observe that the most significant inadequacies include lack of resource management, exception handling, process variation, and data flow integration. These identified shortcomings led us to consider the Little-JIL language as a vehicle for defining business processes. Little-JIL addresses the aforementioned inadequacies with a number of innovative features. Our investigation concludes that these innovative features are effective in addressing a number of key reference business process definition needs.