Modeling coordination in organizations and markets
Management Science
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Designing hard software: the essential tasks
Designing hard software: the essential tasks
A Roadmap of Agent Research and Development
Autonomous Agents and Multi-Agent Systems
Software Architecture in Practice
Software Architecture in Practice
Linking usability to software architecture patterns through general scenarios
Journal of Systems and Software - Special issue on: Software architecture - Engineering quality attributes
Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools
Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools
Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services
Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services
Implementing norms in electronic institutions
Proceedings of the fourth international joint conference on Autonomous agents and multiagent systems
Service-Oriented Architecture: Concepts, Technology, and Design
Service-Oriented Architecture: Concepts, Technology, and Design
IBM Systems Journal
Model-driven development: the good, the bad, and the ugly
IBM Systems Journal - Model-driven software development
Model-driven development: assets and reuse
IBM Systems Journal - Model-driven software development
Enterprise Interoperability II: New Challenges and Approaches
Enterprise Interoperability II: New Challenges and Approaches
Web services and business process management
IBM Systems Journal
Hi-index | 0.00 |
Multiagent systems have been proposed in the literature as a suitable architectural and implementation approach for cross-enterprise collaboration, due to their support for decentral decision-making and peer-to-peer coordination, loosely coupled interaction, modeling support for the notion of electronic institutions, and built-in adaptability mechanisms. While we agree with this general view, we argue that different application domain and different market constellations require different types of architecture. In this paper we look at the specific problem of selecting an information and communication technology (ICT) architecture for cross-enterprise business process (CBP) design and enactment. Therefore we identify three important architectural patterns for CBP enactment. We then propose a decision method for architecture selection based on the analytic hierarchy process (AHP) approach. Finally we illustrate the method by applying it to two application scenarios with differing characteristics. Robustness of the decision method is analyzed by performing a sensitivity analysis.