Planning_and_Impleme.. - didier beck weblog

More documents

Recommendations

Info

Planning and Implementing SOA www.butlergroup.com Phase 1 – Investigation and Discovery Phase 2 – Development and Deployment Phase 3 – SOA Transformation Phase 4 – SOA Maturity (The Service Oriented Enterprise) Business Vision Define Business Case Education Business Model Development Business metrics Optimisation Process stream analytics Business networks Architecture Develop architecture competency Business and technical architecture Data and application architecture Common service architecture Data Management Service to information mapping Develop information architecture competency. Master Data Management Content in processes Business Activity Monitoring Dynamic process optimisation Develop corporate data dictionary Control and Governance Roles and responsibilities Organisational structures Change management Dynamic governance Policies Infrastructure Messaging infrastructure ESB Services registry and repository Rules Service management infrastructure Autonomic service infrastructure Development methods Acquire serviceoriented expertise Service development and re-use Composite application development Rapid application assembly Business Vision Figure 8.2.1: SOA Roadmap During the discovery phase, it is vital to define the business case – to understand why SOA is needed for the organisation and to establish what is trying to be achieved. Even in an organisation where business management is already pushing for change, it will still be valuable to focus on During the discovery phase, it is vital to define the business case – to understand why SOA is needed for the organisation and to establish what is trying to be achieved. the desired business objectives. Parallel to this is the need to educate, particularly at the higher levels. A large amount of material exists on SOA, and distilling this into usable and inspirational value can be a challenge – some of the more business-focused publications here include Enterprise SOA (Dan Woods and Thomas Mattern, O’Reilly), and Mashup Corporations (Andy Mulholland, Chris S. Thomas, Paul Kurchina, and Dan Woods, Evolved Technologist Press). At the development and deployment phase, the business needs to develop its business models – to understand where it is heading. This will include an understanding of where it fits in a supply chain or similar extended enterprise, and what it could expect partners and customers to demand. 8 Section 1: SOA Deployment December 2006
www.butlergroup.com Planning and Implementing SOA The SOA Transformation stage will involve establishing the business metrics (or Key Performance Indicators – KPIs) that work for the organisation. Whilst there may be some generic KPIs, it is important that the organisation understands what metrics are important to them, and subsequently identifies how to measure and use the information that is then generated. By this phase, alignment should be significantly improved and business and technology working together in partnership. The organisation will be implementing both internal and external processes and services, and working towards optimisation of those services. By the time the organisation has evolved to SOA maturity, it will be receiving feedback from all aspects of the enterprise and can look to using this feedback on an ongoing basis in order to continually optimise business processes. Process optimisation is an ongoing concept, not an end point in itself. Architecture Butler Group has discussed the importance of enterprise architecture many times, and believes that when moving to SOA, the ‘A’ – architecture, as in the fundamental organisation of a system embodied by its components, their relationship to each other and to the environment and the principles guiding its design and evolution (IEEE P1471/D5.3) – becomes critical. This has to include the business (people) side as well as the technology aspects, and may extend outside the enterprise, particularly in collaborative environments. During the discovery phase, an organisation may need to develop an architecture competency if one does not exist – gaining an understanding of architecture concepts and benefits can clarify both business and IT objectives. The development and deployment phase should see this competency then being put to work to define the business and technical architecture for the organisation – and will need to work closely with the business to understand how the business needs will drive the underlying technology structures. The SOA transformation phase will see the full fleshing-out of more formal data and application architectures, as architectural awareness grows and the organisation itself evolves. When an organisation moves into the SOA maturity phase, it will be developing a common service architecture, where reuse of existing services is a given, and new services evolve easily as needs become apparent. Data Management Data is an undervalued area in these days of distributed computing, but developing a corporate data model will be vital in making sense of how data can best be reused in SOA. When Enterprise Resource Planning (ERP) systems were developed, little attention was paid to how information would be used – they were designed to be optimised for transactions but not for information and In the investigation and discovery phase, the organisation should develop an information architecture competency, and start defining a service to information mapping. The SOA Transformation stage will involve establishing the business metrics (or Key Performance Indicators – KPIs) that work for the organisation. reporting. There is a risk with SOA that the data services needed to deliver adequate information and intelligence will be an afterthought as well. In the investigation and discovery phase, the organisation should develop an information architecture competency, and start defining a service to information mapping. This should help clarify what data is stored, where it is duplicated and potentially redundant, and where there may be gaps in corporate data that are filled by personal sources. At this stage, it will be valuable to develop a corporate data dictionary – complete with semantic definitions so that there is a common understanding across the organisation. During the development and deployment phase, master data management will become a necessity. Organisations today have multiple versions of common data items, and whilst this may be necessary in a distributed (both technically and geographically) world, it will also be a major challenge. Understanding where data originates, who the owner should be, and developing a policy for ensuring that master data is rapidly propagated to where it needs to be used, must be addressed during this phase. At this stage, the organisation will need to develop an understanding of where and what content is used in its various processes. December 2006 Section 1: SOA Deployment 9
Page 1 and 2: Technology Management and Strategy
Page 3 and 4: www.butlergroup.com Planning and Im
Page 7: www.butlergroup.com Planning and Im
Page 31 and 32: www.butlergroup.com Technology Mana

Planning_and_Impleme.. - didier beck weblog

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?