soa development organization n.
Skip this Video
Loading SlideShow in 5 Seconds..
SOA – Development Organization PowerPoint Presentation
Download Presentation
SOA – Development Organization

SOA – Development Organization

110 Views Download Presentation
Download Presentation

SOA – Development Organization

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. SOA – Development Organization Yogish Pai

  2. IT organization are structured to meet the business needs • LOB-IT Aligned to a particular business unit for delivering business capability consisting of • Project Managers, Projects Architects, Functional Analyst, Developers • CM/RM & QA (Optional – Recommended), PMO (Optional) • Centralized team that provide enterprise wide capability • Network & Data Center Services, collaboration capability such as eMail, Calendar, IM, etc., Enterprise Architects • Shared Services team (optional - recommended), centralized CM/RM and QA team (optional - recommended) • The right IT organization structure also helps reducing the overall cost of resources • Fewer highly specialized resources required • Outsource non-specialized task

  3. Reference Architecture understanding is a must to develop the governance & organization model for SOA • Presentation Tier – Always On • Integrated with Enterprise Security & Service Registry • Single-point of entry for all users (Customers, Partners, Employees, etc.) Enterprise Role based Portal Enterprise Role based Portal Enterprise Role based Portal Cluster • Portal Applications • Portals providing Enterprise wide, LOB or specific point solutions • Each portal has it’s specific SLA and maintenance window • Business required flexibility to manage / modify these applications • Custom or COTS Portal Applications WSRP WSRP WSRP Outsourced Portal Applications LOB-Portal Application Enterprise Portal Applications Security, Service Registry • Route service requests / messages to the appropriate locations Enterprise Service Bus Enterprise Business Process • Provide Enterprise Data Model • Abstract packaged ./ legacy applications from the business process & presentation tier Shared Data Services • COTS / Legacy Applications • COTS / Legacy applications deployed to provide business capability • Limit custom development to a minimum Legacy Application COTS Applications Mainframe Applications

  4. The organization structure based on the reference architecture facilitates modularization - first step towards creating a grid • Responsible for providing the SOA Dial tone (keep the services up an running) • Administration, CM & RM of all the components Operations Team (20%) • Develop Enterprise or LOB applications based on Portal • Development team assigned to projects based on demand • Leverage (Re-Use) Shared Services (including BP), either by submission into a common repository or creating dedicated team Project Teams (30%) • Responsible for Service & Security Management) Services Mgmt Team (10%) • Dedicated to developing the shared data services • Eliminate developers from knowing about the data source SDS Team (10%) • Dedicated team (preferably SI) to gather requirements, configure and deploy COTS applications • Dedicated (preferably outsourced) team to maintain the COTS applications COTS Team (30%) Enterprise Architecture team responsible for ensuring consistency across the enterprise by defines the building blocks for putting this together.

  5. Reference Model reduced overall resources required to provide enterprise wide solutions Development Teams Support Teams Dedicated Project team to develop business capability Dedicated support team (preferably outsourced) to maintain applications Portal Applications (Custom & COTS) Resources Required by Tiers Dedicated small team to manage the Services layer. Services and business processed developed as part of each project Services Management / Business Process Enterprise Architecture team pull this all together Dedicated small team to develop and support shared data services (EII & ETL) that exposes Enterprise or Project Objects to the services team Shared Data Services Large team size (preferably SI) for initial implementation or upgrade Small teams (preferably outsourced) for supporting this layer Case-by-Case basis COTS/ Legacy Applications

  6. Implement the organization changes in phases • Phase 1: Focus on the Service Orchestration and Management • Adopt the Shared Data Service and dedicate a small team to develop and provide the shared data services to the project teams • Project teams eliminate the need of developing entity beans/repository layers • As number of services grow – adopt the Enterprise Service Bus • Phase 2: Focus on externalizing Business process • Leverage COTS for business process provided out of the box • Project team to implement custom shared business process (create shared business process development team, if required) • Upgrade/Migrate packaged applications to standards (JSR-168 & WSRP) • Phase 3: Implement the SOA (Portal) Dial Tone • Configure role based portals to create a personalized user desktop/workbench/portal Phased approach to deliver capability over time

  7. Phase 1: Focus on Service Orchestration and Management • Criteria for starting with Shared Data Services • Applications that access multiple data sources using JDBC, JCA, WebServices, MQ, etc. • Multiple teams accessing the same data source – customer master, user profile, etc. independent of the protocol • Criteria for starting with Enterprise Service Bus • Number of shared services growing exponentially - 200+ shared services being consumed by client applications • Multiple versions of the same shared services consumed by different clients

  8. Phase 2: Focus on Externalizing Business Process • Criteria for leveraging business process within COTS, Legacy or Custom applications • Business process does not require integration with external data sources or business logic • Capability already provided by the COTS, Legacy or Custom application • Criteria for externalize the business process • Business process requires access to multiple data sources and other business process provided by other COTS, Legacy or Custom application • All Services or business process required by the business process are exposed by the COTS, Legacy or Custom applications • Criteria for selecting the runtime engine for executing business process • Select software company that is most likely to adopt new standards or design patterns

  9. Phase 2: Focus on Externalizing Business Process • Expose all user interface leveraging the portal • URL transfer using SSO could be transition state and would be at the cost of session management, performance and developing multiple presentation tier • Upgrade / Migrate COTS to standards based UI (WSRP) • Criteria for selecting service orchestration development tools • All major COTS and Platform vendors provides tools for developing standards based (BPEL) development tool • Standardize on a single tool across the enterprise (eliminate re-training of resources as they move between projects) • Select software company that is most likely adopt new standards or industry patterns • Leverage development tools based on Eclipse (the defacto standard in the industry)

  10. Phase 3: Implement the SOA (Portal) Dial tone • Pre-Requisite Infrastructure • Implemented Enterprise/LOB wide Enterprise Security Service consisting of • Delegated Admin, Security Provisioning, Single Sign-On, Identity Management, Resource Registration, etc. • Implemented true Service Management providing following capabilities • Service Repository, Service Registration, Version Management, Service Hierarchy, Service (Development) Management, Service Configuration, etc. • Most (if not all) COTS, Legacy & Custom applications expose information/business process using standards (WSRP) • What benefit does this provide ? • Single entry point for all users across the enterprise / LOB • Dynamically render new business capability (create an agile enterprise)

  11. Approach works independent of the governance model • Service Registry and Routing Policy enables routing within or outside the organizations • Service discovery and management capability enables creating a single service repository for the enterprise (independent of the governance model) • Service registry caching and administration capability on the ESB enables IT to meet the required SLA

  12. Summary • Fewer highly skilled resources required • Standardizing on architecture approach, process, tools and Open Standards reduces Total Cost of Ownership • Phased approach reduces risk and enables enterprises / LOB adopt SOA • Leverage COTS for Business Capability and Platform for pulling it all together

  13. SOA – Development Organization Yogish Pai