1 / 13

Enterprise Integration Architecture

Enterprise Integration Architecture. IPMA Professional Development Seminar June 29, 2006 Scott Came Director, Enterprise Architecture Program Washington State Department of Information Services. EA Integration Architecture Initiative.

siusan
Download Presentation

Enterprise Integration Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Integration Architecture IPMA Professional Development Seminar June 29, 2006 Scott Came Director, Enterprise Architecture Program Washington State Department of Information Services

  2. EA Integration Architecture Initiative • In December, the ISB EA Committee chartered an initiative to look at integration architecture • Team of architects, developers, IT managers, and integration experts from agencies have been meeting to develop an architecture • Materials endorsed by EA Committee in June, out for CAB review now

  3. Motivation • Reduce costs and risks of integration • Reuse system interfaces • Leverage common infrastructure • Improve agility and responsiveness of IT • Accommodate different software platforms, COTS/package application architectures

  4. S O A Service Oriented Architecture Capabilities performed by one for another to achieve a desired outcome Aligning architecture to enable a collection of services to be linked together to solve a business problem The fundamental organization of a system by its capabilities, their interactions, and the enterprise environment SOA is an architectural approach for organizing and using services to support interoperability between enterprise data assets and applications Approach: Service Oriented Architecture Slide courtesy Booz Allen Hamilton

  5. What is a service? • An explicit, focused agreement between the provider and the users of a capability as to how the interaction with the capability will take place • Services support integration by: • Establishing an agreement as to the purpose of the interaction and how the interaction will take place (e.g., agreement on meaning of data) • Hiding the implementation of one system from another, avoiding technical dependencies

  6. Tight Coupling of Systems Effect Desires Uses Causes Technology Dependency Accesses System in Agency B (Capability) System in Agency A

  7. How do we tightly-couple systems? • Sharing databases • Integrating user interfaces • Integrating with technology specific/proprietary to one system (versus open standard technologies) • Exchanging files

  8. Loose Coupling of Systems Effect Desires Uses Causes Technology Dependency (Standards) Service Interface Accesses Accesses System in Agency B (Capability) System in Agency A

  9. How do we loosely-couple systems? • Exchange messages specified by service (explicit, focused agreement) • Leverage open standards for message structure • Use infrastructure to route messages, rather than direct addressing • Asynchronous, reliable transport of messages

  10. Natural Boundaries • When systems are likely to change at the same time, tight coupling is OK • Performance • Simplicity • A “natural boundary” identifies sets of features that are implemented as a unit (and change as a unit) • Integrate across natural boundaries; consolidate within natural boundaries

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

  12. Deliverables from EA initiative • Integration Domain (principles, business drivers, environmental trends) • Conceptual Architecture • Service Interaction Profiles (Web Services, Websphere MQ, File Drop) • Solution Integration Design Guidelines • Service Modeling Guidelines

  13. For more information… • EA Committee Website (includes deliverables) • http://isb.wa.gov/committees/enterprise/index.aspx • EA Program Website and Contact • http://dis.wa.gov/enterprise/enterprisearch/index.aspx • Scott Came, EA Program Director • scottca@dis.wa.gov, 360-902-3519

More Related