This is a work product created from an Enterprise Architecture view and thought processes around the integration of two agile frameworks (SOA and ITIL) in Enterprise Computing Practice.
Introduction
- SOA and ITIL are two major frameworks to build an agile enterprise by integrating business and IT organizations of an enterprise using proven methodologies and standards. ITIL is the answer to IT responsiveness and SOA is the answer for BUSINESS responsiveness. IT and BUSINESS responsiveness together will bring the agility to an enterprise.
- This work product will look into an Architecture approach to integrate ITIL and SOA so that the organization can make use of these two agile frameworks for the best interest of the business with a low cost of ownership and high return of investment.
- One of the core ideologies followed throughout of this work product is that "An Architectural approach" should support the needs in conceptual and logical views. SO if each recommendation is not meeting the core ideology, it will be changed through a continuous improvement process.
SOA by Definition
Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed business capabilities that may be under the control of different business ownership domains. Service-oriented architecture is an architectural discipline that centers on the notion that Business and IT assets are described and exposed as Services. A service is a reusable asset exposed using implementation independent service definition. A service definition should adhere to the SOA principles such as- Service encapsulation - Many web-services are consolidated to be used under the SOA Architecture. Often such services have not been planned to be under SOA.
- Service loose coupling - Services maintain a relationship that minimizes dependencies and only requires that they maintain an awareness of each other
- Service contract - Services adhere to a communications agreement, as defined collectively by one or more service description documents
- Service abstraction - Beyond what is described in the service contract, services hide logic from the outside world
- Service re-usability - Logic is divided into services with the intention of promoting reuse
- Service composability - Collections of services can be coordinated and assembled to form composite services
- Service autonomy – Services have control over the logic they encapsulate
- Service optimization – All else equal, high-quality services are generally considered preferable to low-quality ones
- Service discover-ability – Services are designed to be outwardly descriptive so that they can be found and accessed via available discovery mechanisms
SOA Concepts
SOA back bone
SOA need service oriented technologies, frameworks and products
SOA products could able to facilitate the business computing by reusing the service candidates and provide suitable governance and management around the service life cycles
SOA is not web services
Web service is a widely accepted SOA technology . Not all web service implementations are not SOA based services. For example fine grained RPC web services are SOA services
SOA can be implemented using variety of technologies
J2EE, J2SE POJO, and .NET component service enablement, Legacy component service enablement using adaptor technologies etc
SOA Changes
SOA change the IT enablement of business needs across the enterprise as explained below.| Non SOA based IT Enablement of Business Needs | SOA based IT Enablement of Business Needs |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
Why SOA
Every enterprise demand SOA enablement of their business & IT operations due one or many reasons outlined below.- Software complexity
- Dynamic business changes
- Forced to be Agile
- Increased demand of merger and acquisition integration
- Re-usage of existing assets
- Demand of increased visibility and accountability of IT investment
- Reaching new threshold of connectivity and computing power using distributed, parallel and a-synchronized computing mechanism
- Get ready for on demand computing needs
- Justified by low Time to Market and Total Cost of Ownership (TCO) and High Return of Investment (ROI)
- Supported by modern IT innovation and investment
What is ITIL
- Widely accepted IT service management specification
- Service centric approach to IT asset management
- Stage centric decomposition of service management
- Principles
- Processes
- Activities
- Functions
- Technology considerations
- Implementation
- Challenges, critical success factors and risks
- Principles
Why ITIL
- Widely successful in management of large IT systems
- Past credibility and IT service customer satisfactions
- Better asset utilization
- Allow business to concentrate on business issues than support issues
SOA & ITIL Common Grounds
- Business Responsiveness: Ability to respond to dynamic business requirement changes by implementing the realization of business requirements by loose coupled services visible to business communities across the enterprise.
- IT Responsiveness: Ability to respond to the environmental changes on which the IT realization of business critical applications deployed and maintained.
SOA & ITIL Life Cycle Integration
Life Cycle Integration Approach
This comment has been removed by the author.
ReplyDelete