Interaction Protocols as Design Abstractions for Business Processes
IEEE Transactions on Software Engineering
Semi-automated adaptation of service interactions
Proceedings of the 16th international conference on World Wide Web
Semantic model-driven architecting of service-based software systems
Information and Software Technology
A conceptual architecture for semantic web services development and deployment
International Journal of Web and Grid Services
Data & Knowledge Engineering
On the enactability of business protocols
AAAI'08 Proceedings of the 23rd national conference on Artificial intelligence - Volume 2
Handling transactional business services
Proceedings of the 15th Conference on Pattern Languages of Programs
A pi-calculus-based business process formal design method
CSCWD'06 Proceedings of the 10th international conference on Computer supported cooperative work in design III
Layered ontological modelling for web service-oriented model-driven architecture
ECMDA-FA'05 Proceedings of the First European conference on Model Driven Architecture: foundations and Applications
Ontology transformation and reasoning for model-driven architecture
OTM'05 Proceedings of the 2005 OTM Confederated international conference on On the Move to Meaningful Internet Systems: CoopIS, COA, and ODBASE - Volume Part II
Hi-index | 0.02 |
Business processes are conventionally modeled as monolithicflows that capture the desired business logic. However,developing process flows is challenging. Because aflow specifies what its participants should do, it restrictsthe autonomy of its participants, thus limiting their abilityto exploit opportunities or accommodate exceptions accordingto their business preferences.We take a dual perspective wherein business processesare modeled as compositions of (instantiated) business protocols.Each business protocol specifies interactions amongits partners; each protocol serves a unique business purpose,e.g., processing a payment or shipping an item. Thus,modularizing a monolithic business process via businessprotocols allows clear separation of concerns for modelingand enacting the process.We develop an approach in which protocols are compiledinto local skeletal flows for each participant that can befleshed out with local business logic as needed. Such flowsare naturally distributed but can be enacted using commercialbusiness flow engines. Thus, our protocol-based approachcombines the benefit of improved modeling with simplifiedimplementations.