The enterprise service bus: making service-oriented architecture real
IBM Systems Journal
SOMA: a method for developing service-oriented solutions
IBM Systems Journal
Implementing Service-Oriented Architecture in Organizations
Journal of Management Information Systems
Variability in quality attributes of service-based software systems: A systematic literature review
Information and Software Technology
Service Oriented Enterprise and Contracted Profit Sharing
International Journal of Systems and Service-Oriented Engineering
The influence of SOA governance mechanisms on IT flexibility and service reuse
The Journal of Strategic Information Systems
Ontological map of service oriented architecture for shared services management
Expert Systems with Applications: An International Journal
Factors affecting the organizational adoption of service-oriented architecture (SOA)
Information Systems and e-Business Management
| Hi-index | 0.00 |
Most organizations understand the need to address service-oriented architecture (SOA) governance during SOA adoption. An abundance of information is available defining SOA governance: what it is and what it is not, why it is important, and why organizational change must be addressed. Increasingly business and information technology (IT) stakeholders, executive and technical, acknowledge that SOA governance is essential for realizing the benefits of SOA adoption: building more-flexible IT architectures, improving the fusion between business and IT models, and making business processes more flexible and reusable. However, what is not clear is how an organization gets started. What works and what does not work? More importantly, what is required in SOA governance for organizations to see sustained and realized benefits? This paper describes a framework, the SOA governance model, that can be used to scope and identify what is required for effective SOA governance. Based on client experiences, we describe four approaches to getting started with SOA governance, and we describe how to use these four approaches to make shared services (services used by two or more consumers), reuse, and flexibility a reality. We also discuss lessons learned in using these four approaches.