My Chief Architect Recommends SOA What Should I Do

1. My Chief Architect Recommends SOA � What Should I Do?

2. (C) The Open Group 2008 The Open Group Vendor-neutral and technology-neutral consortium Vision of Boundaryless Information Flow� Access to integrated information, within and among enterprises, based on open standards and global interoperability Forums and Work Groups Consortia and Program Management Certification

3. (C) The Open Group 2008 The Home of Enterprise IT Architecture The Open Group Architecture Framework (TOGAF�) Certification for architects and for architecture products and services The Association of Open Group Enterprise Architects (AOGEA)

4. (C) The Open Group 2008 The SOA Working Group Develops and fosters common understanding of SOA in order to facilitate alignment between the business and information technology communities. By conducting producing definitions, analyses, recommendations, reference models, and standards More than 300 participants from over 50 companies

5. (C) The Open Group 2008 My Chief Architect Recommends SOA � What Should I Do?

6. (C) The Open Group 2008 My Chief Architect Recommends SOA � What Should I Do? Ask �What�s SOA?� Ask �How much will it cost?� Ask �Why?� Say �Our new strategy is cloud computing� Fire the Chief Architect

7. (C) The Open Group 2008 This Presentation Is About How to Work with Enterprise IT Architects What�s Special about SOA SOA Return On Investment

8. Working With Enterprise IT Architects Why have Enterprise IT Architecture? How the architect works How to work with the architect

9. (C) The Open Group 2008 Why have Enterprise IT Architecture

10. (C) The Open Group 2008 Enterprise IT Architecture Provides the fundamental technology and process structure for an IT strategy Provides a strategic context for the evolution of enterprise IT systems in response to the constantly changing needs of the business environment Allows individual business units to innovate safely in their pursuit of competitive advantage within the context of an integrated IT strategy

11. (C) The Open Group 2008 Enterprise IT Architecture Long-term Costly But gives identified return Allows executive control And delivers value

12. (C) The Open Group 2008 The Benefits of Enterprise IT Architecture (1) More efficient IT operation: Lower software development, support, and maintenance costs Increased portability of applications Improved interoperability and easier system and network management Improved ability to address critical enterprise-wide issues like security Easier upgrade and exchange of system components

13. (C) The Open Group 2008 The Benefits of Enterprise IT Architecture (2) Better return on existing investment, reduced risk for future investment: Reduced complexity in IT infrastructure Maximum return on investment in existing IT infrastructure The flexibility to make, buy, or out-source IT solutions Reduced risk overall in new investment, and the costs of IT ownership Faster, simpler, and cheaper procurement: Buying decisions are simpler. The procurement process is faster.

14. (C) The Open Group 2008 The Benefits of Enterprise IT Architecture (Summary) Your IT will be cheaper in the long run

15. (C) The Open Group 2008 The Benefit of Business/IT Architecture Partnership Your IT will support the business more effectively

16. (C) The Open Group 2008 How the Architect Works

17. (C) The Open Group 2008 The IT Architecture Context

18. (C) The Open Group 2008 The Architect as Communicator The architect must address stakeholder concerns Talk to everybody! Build models to show the system from different viewpoints Cost Functionality Software design . . .

19. (C) The Open Group 2008 Producing an Architectures

20. (C) The Open Group 2008 The TOGAF� Architecture Development Method Set up the architecture process TOGAF is a good framework for SOA. Defining the business vocabulary is crucial for SOA and should be performed, in conjunction with a business process analysis, in Phase B. This forms the basis for addressing (in Phase C) the enterprise�s particular business patterns of service use. Phase C identifies functions to be performed by services, without identifying individual services. Service identification and detailed definition is part of the implementation. Phase C also identifies existing applications that should be given service �wrappers�. Phase D establishes the enterprise�s particular technical patterns of service use. It defines the enterprise service standards. These should include and extend common standards such as SOAP and WSDL. They might, for example, include service contract templates. Phase D also identifies the infrastructure needed by the enterprise to support its particular technical patterns of service use.TOGAF is a good framework for SOA. Defining the business vocabulary is crucial for SOA and should be performed, in conjunction with a business process analysis, in Phase B. This forms the basis for addressing (in Phase C) the enterprise�s particular business patterns of service use. Phase C identifies functions to be performed by services, without identifying individual services. Service identification and detailed definition is part of the implementation. Phase C also identifies existing applications that should be given service �wrappers�. Phase D establishes the enterprise�s particular technical patterns of service use. It defines the enterprise service standards. These should include and extend common standards such as SOAP and WSDL. They might, for example, include service contract templates. Phase D also identifies the infrastructure needed by the enterprise to support its particular technical patterns of service use.

21. (C) The Open Group 2008 What the Architect Expects from the Client

22. (C) The Open Group 2008 How to Work With the Architect

23. (C) The Open Group 2008 Say Why You Want the Architecture Architecture work starts with a request from the client The architect needs to know why you want it, as well as what you want

24. (C) The Open Group 2008 Share your Business Vision The architect will ask about business principles and processes Make sure you share the vision too!

25. (C) The Open Group 2008 Explain What Information You Need The architect prepares different views of the system to address different concerns These should include your concerns Cost Benefits ROI Customer satisfaction Improved efficiency . . .

26. (C) The Open Group 2008 Give the Architect Access to the Stakeholders The architect needs to talk to everybody concerned with the new system Users Customers Developers Operations staff Management staff (including security) . . .

27. (C) The Open Group 2008 Discuss the Architecture Vision The Architecture Vision phase of TOGAF includes Creating an initial (�Version 0.1�) description of the architecture Developing a Vision Statement to �sell� the architecture Discuss the initial description Be prepared for it to include changes to business processes or even principles

28. (C) The Open Group 2008 Agree the Scope of the Architecture Work What systems/business units/geographical locations does the architecture cover? Does the work include definition and supervision of implementation projects? Does it include responsibility for detailed implementation planning? Does it include definition of implementation governance procedures?

29. (C) The Open Group 2008 Agree How You Will Accept the Architecture Work What are the deliverables? How will they be accepted?

30. (C) The Open Group 2008 Don�t Sign Until You Are Happy With the vision With the scope With how the work will be approved This is your contract for architecture work

31. (C) The Open Group 2008 But First, Pick Your Architect! Enterprise IT Architecture requires skill and judgement It can have a major impact on the business You should look for someone with professional standing

32. (C) The Open Group 2008 IT Architect Certification www.opengroup.org/itac/

33. (C) The Open Group 2008 TOGAF Certification for Architects Shows knowledge of TOGAF Either training-based Or exam-based

34. (C) The Open Group 2008 (IT Specialist Certification) Verifies the professional qualities and skills that enable the effective development, implementation and operation of IT solutions An IT Specialist typically concentrates on one of two Technical Focus areas Solution Development Solution Delivery Within each of these two Technical Focus areas, various Streams and Sub-Streams are identified against which the individual IT Specialist may certify.

35. (C) The Open Group 2008 Working With Enterprise IT Architects: Conclusions Business/Architecture Teamwork Share your business vision Discuss and agree the architecture vision Give the architect access to stakeholders and clear terms of reference But first, pick your architect!

36. What�s Special About SOA? SOA Benefits SOA Implications The SOA Future

37. (C) The Open Group 2008 SOA Benefits

38. (C) The Open Group 2008 The Benefits of SOA Improved information flow Agility Ability to develop new function combinations rapidly Ability to develop new functions rapidly Ability to adapt quickly to different external environments Configuration and organizational flexibility Ability to scale operations to meet different demand levels Ability to expose internal functionality Lower software development and management costs Ability to optimize performance, functionality, and cost Easier introduction of system upgrades . . .

39. (C) The Open Group 2008 Boundaryless Information Flow Permeable boundaries between Nations Enterprises Organizational levels Departments Deliver Productivity Agility

40. (C) The Open Group 2008 Enterprises Want This�

41. (C) The Open Group 2008 But Have This

42. (C) The Open Group 2008 The Effect of SOA SOA re-structures applications as loosely-coupled, modular services And provides for data flow between them

43. (C) The Open Group 2008 So Enterprises Can Have This

44. (C) The Open Group 2008 SOA Implications

45. (C) The Open Group 2008 New Skills Needed Service and service-based solution Design Implementation Testing Operation Management

46. (C) The Open Group 2008 But TOGAF Can Be Used for SOA Set up the architecture process TOGAF is a good framework for SOA. Defining the business vocabulary is crucial for SOA and should be performed, in conjunction with a business process analysis, in Phase B. This forms the basis for addressing (in Phase C) the enterprise�s particular business patterns of service use. Phase C identifies functions to be performed by services, without identifying individual services. Service identification and detailed definition is part of the implementation. Phase C also identifies existing applications that should be given service �wrappers�. Phase D establishes the enterprise�s particular technical patterns of service use. It defines the enterprise service standards. These should include and extend common standards such as SOAP and WSDL. They might, for example, include service contract templates. Phase D also identifies the infrastructure needed by the enterprise to support its particular technical patterns of service use.TOGAF is a good framework for SOA. Defining the business vocabulary is crucial for SOA and should be performed, in conjunction with a business process analysis, in Phase B. This forms the basis for addressing (in Phase C) the enterprise�s particular business patterns of service use. Phase C identifies functions to be performed by services, without identifying individual services. Service identification and detailed definition is part of the implementation. Phase C also identifies existing applications that should be given service �wrappers�. Phase D establishes the enterprise�s particular technical patterns of service use. It defines the enterprise service standards. These should include and extend common standards such as SOAP and WSDL. They might, for example, include service contract templates. Phase D also identifies the infrastructure needed by the enterprise to support its particular technical patterns of service use.

47. (C) The Open Group 2008 New Culture? Is the enterprise ready for Service re-use? Rapid business process changes? Visibility of integrated information?

48. (C) The Open Group 2008 Changed Enterprise Structure

49. (C) The Open Group 2008 The SOA Future

50. (C) The Open Group 2008 Cloud Computing

51. (C) The Open Group 2008 Software Services Market

52. (C) The Open Group 2008 Software Services Market: Implications for the Enterprise Shorter time to establish Focus on core competencies

53. (C) The Open Group 2008 What�s Special About SOA: Conclusions SOA can deliver major business benefits It requires new implementation skills and culture, but not new architecture skills For the future, it can be the basis of an open market in software services

54. SOA Return on Investment

55. (C) The Open Group 2008 SOA ROI Outline Investment Architecture development Tools and infrastructure Skills: training and new people Culture change Enterprise change

56. (C) The Open Group 2008 What Is Your SOA ROI? The ROI varies, depending on: The scale of enterprise The kind of enterprise The kind of SOA Ask your architect Initial estimates in phase A Improved estimates as the architecture work progresses

57. (C) The Open Group 2008 FBI Analysis - 1

58. (C) The Open Group 2008 FBI Analysis - 2

59. (C) The Open Group 2008 FBI Analysis - 3

60. (C) The Open Group 2008 FBI Analysis - 4

61. (C) The Open Group 2008 You Need the Whole Picture Investment Architecture development Tools and infrastructure Skills: training and new people Culture change Enterprise change

62. (C) The Open Group 2008 Getting the Whole Picture Much more complex than a simple features/benefits chart Needs detailed consideration of possibilities and their implications Your chief architect should be able to Present the possibilities Discuss the implications Help you to reach the answer

63. In Conclusion

64. (C) The Open Group 2008 Summary Enterprise IT architecture takes a long-term, strategic view of enterprise IT It is a discipline that should be carried out by competent and experienced professionals SOA is a style of enterprise architecture that can deliver major benefits The ROI on SOA varies from one enterprise to another A competent enterprise architect can determine the kind of SOA you need and estimate its ROI

65. (C) The Open Group 2008 My Chief Architect Recommends SOA � What Should I Do?

66. (C) The Open Group 2008 A Competent Professional Architect Will have understood your business vision Will have discussed the possibilities with you Will have worked with you to evaluate the ROI Will not recommend SOA unless it is right for the business and will give a positive return

67. (C) The Open Group 2008 My Chief Architect Recommends SOA � What Should I Do? Tell your chief architect to go ahead.

68. (C) The Open Group 2008 My Chief Architect Recommends SOA � What Should I Do? Thank you!