SOA lecture 1 by 888P3q



                               ITEC 4100:
                   Topics in Information Technology
            “Introduction to Service-Oriented Architecture”

                          Professor: Eduardo Bresani
          Course site: http://
                              Classroom: ACE 003

Introduction to Service-Oriented Architecture
                              Eduardo E. Bresani

    Not academic but practitioner in the IT industry
    Academic Degrees:
         Master of Science in Computer Science
         Master of Science in Information Systems
         Master of Business Administration (MBA)
    Professional certifications
         Certified in the Governance of Enterprise IT (CGEIT)
         Project Management Professional (PMP) from the PMI
    Previous professional experience
         IT Operations, DBA, PM, Systems Manager in the Peruvian Navy
         Systems Analyst, Project Manager, Program Manager at IBM Canada
         Director of Information Systems, Chiquita Brands International
         Vice President of Information Technology, Aviva Canada Inc.
    Currently: Chief Information Officer and Vice President of IT for Toronto
     Hydro Corporation

Introduction to Service-Oriented Architecture
                                        General                                         1
    Text:
          An Implementor’s Guide to Service Oriented Architecture - Getting It Right
          Download PDF at

    Classes: Tuesdays 19.00 – 22.00

    Office Hours: by appointment only.
    Topics to be covered:

      Business drivers for SOA
      Designing Services
      Registries and Repositories
      Enterprise Service Buses
      Runtime Management
      Organizing For Success
      Capability Development
      Technology Options
      SOA Governance
      SOA vendor presentations

Introduction to Service-Oriented Architecture
                                Marking Scheme

    Class attendance & participation : 10%
    Assignment #1 ( paper ): 15%
    Assignment #2 ( paper ): 15%
    Group Presentation: 40%
    Final exam ( in class ): 20%

Introduction to Service-Oriented Architecture
                      Presentation topics
   SOA in the context of TOGAF (open group architecture framework)
   Business Process Management (BPM) in the context of SOA
   J2EE SOA platform
   Dot NET SOA platform
   SOA security discussion / solutions
   SOA performance discussion / solutions
   SOA as an EAI solution
   SOA governance discussion / solutions
   SOA development lifecycle
   Future of SOA. How will it evolve
   Application Server vs ESB for SOA
   Case study of actual SOA implementation
Introduction to Service-Oriented Architecture
                   What are the business drivers for SOA?

   Heterogeneity: Most enterprises today contain a range of different
    systems,applications, and architectures of different ages and technologies.
    Integrating products from multiple vendors and across different platforms
    were almost always a nightmare. But we also cannot afford to take a single-
    vendor approach to IT, because application suites and the supporting
    infrastructure are so inflexible.
   Business Change: Globalization and e-business are accelerating the pace
    of change. Globalization leads to fierce competition, which leads to
    shortening product cycles, as companies look to gain advantage over their
    competition. Customer needs and requirements change more quickly driven
    by competitive offerings and wealth of product information available over the
    Internet. In response the cycle of competitive improvements in products and
    services further accelerates.
   Technology Change: Improvements in technology continue to accelerate,
    feeding the increased pace of changing customer requirements. Business
    must rapidly adapt to survive, let alone to succeed in today’s dynamic
    competitive environment, and the IT infrastructure must enable businesses’
    ability to adapt.

Introduction to Service-Oriented Architecture
 What is SOA? … is an integration paradigm that encourages
organizations to re-think how their IT capabilities are organized

                                             Aligning architecture to          The fundamental
            Capabilities performed by         enable a collection of     organization of a system by
           one for another to achieve a       services to be linked          its capabilities, their
                 desired outcome          together to solve a business      interactions, and the
                                                    problem                enterprise environment

               SOA is an architecture approach for
             organizing and using services to support
             interoperability between enterprise data
                     assets and applications

Introduction to Service-Oriented Architecture
    SOA benefits uniquely address a rapidly changing environment

          Agility                      Process                 Interoperability                   Costs
   Focus more on core           Increase business          Facilitate integration       Reduce development
    competencies and              flexibility through         with multiple solutions       costs by acquiring
    missions by creating          plug-and-play               via open IT standards         pre-built capabilities
    a network of                  architecture and re-       Remain platform,             Leverage previous IT
    producers-suppliers           use of existing             language, and vendor          investments through
    with intense                  services                    independent to                re-use of assets
    interactions                 Ensure system               remove IT barriers for       Lower maintenance
   Improve access to             change is not a             using best-of-breed           costs and TCO
    information to enable         constraint on               software packages             through fewer
    faster cycle times            business or mission                                       “instances” of a
   Enable enterprises to         change                                                    function, and fewer
    be more agile and            Allow interoperation                                      software licenses
    respond quickly to            with other systems &
    business needs                partners without

                                  IT alignment with an organization’s mission

              Improved agility, focus on core competencies, IT efficiencies, and ROI for IT assets

Introduction to Service-Oriented Architecture
            SOA allows end-to-end flexibility in meeting user needs

           Consumer            Product       Service Interface   Infrastructure    Provider

               User              Data           Web Service         Network        Database

             DVD Player        Electricity     Electric Outlet     Power Grid     Power Plant

        Web Services provide standard interfaces between disparate systems

        Introduction to Service-Oriented Architecture
Web services are a tactical means to achieve the strategic SOA goal   1

       Web Services are a technical solution
        to enable SOA
       SOA codifies the organization’s
        enterprise strategy for connecting
        systems to provide common discovery,
        security, and management of those
       Web services have specific guidelines          SOA
        on messaging interactions between
        services – the tactical implementation
        of an SOA model
       Thus, Web Services are a specific
        subset of how an SOA can be

                                                       Web Services

       Introduction to Service-Oriented Architecture
          SOA transactions require answering five key questions
   Application 1
“Service Consumer”                  1.   How can the Consumer dynamically discover the existence
                                         of a Provider, which can provide the services being

                                    2.   Assuming the Consumer knows of the Provider’s existence,
                                         how can it locate the Provider?

                                    3.   Assuming the Consumer has located the Provider, how can
                                         the two describe how to connect to each other, in a standard
                                         format which can be understood regardless of their IT

                                    4.   Assuming they have described themselves, how can they
                                         exchange messages in a common messaging format which
                                         is independent of their underlying platforms?

    Application 2
  “Service Provider”                5.   Assuming they have agreed upon a common messaging
                                         format, what data format can they use to exchange data
                                         independent of their underlying database technologies?

 Introduction to Service-Oriented Architecture

To top