Creating Semantic Web Contents with Protégé-2000
IEEE Intelligent Systems
Using dependency models to manage complex software architecture
OOPSLA '05 Proceedings of the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
A Feature-Oriented Approach to Modeling Requirements Dependencies
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Pellet: A practical OWL-DL reasoner
Web Semantics: Science, Services and Agents on the World Wide Web
Control and data dependencies in business processes based on semantic business activities
Proceedings of the 10th International Conference on Information Integration and Web-based Applications & Services
Context-sensitive adaptation of workflows
Proceedings of the doctoral symposium for ESEC/FSE on Doctoral symposium
Analysing dependencies in service compositions
ICSOC/ServiceWave'09 Proceedings of the 2009 international conference on Service-oriented computing
| Hi-index | 0.00 |
Complex business processes in the form of workflows or service compositions are built from individual building blocks, namely activities or services. These building blocks cooperate to achieve the overall goal of the process. In many cases dependencies exist between the individual activities, i.e. the execution of one activity depends on another. Knowledge about dependencies is especially important for the management of the process at runtime in cases where problems occur and the process needs to be adapted. In this paper we present and compare two approaches for modeling dependencies as a base for managing adaptations of complex business processes. Based on two use cases from the domain of workflow management and service engineering we illustrate the need for capturing dependencies and derive the requirements for dependency modeling. For dependency modeling we discuss two alternative solutions. One is based on an OWL-DL ontology and the other is based on a meta-model approach. Although many of the requirements of the use cases are similar, we show that there is no single best solution for a dependency model.