https://training-course-material.com/index.php?action=history&feed=atom&title=SOA_Introduction_Course_OutlineSOA Introduction Course Outline - Revision history2026-04-14T23:41:33ZRevision history for this page on the wikiMediaWiki 1.45.1https://training-course-material.com/index.php?title=SOA_Introduction_Course_Outline&diff=7252&oldid=prevIzabela Szlachta at 18:46, 8 November 20122012-11-08T18:46:04Z<p></p>
<p><b>New page</b></p><div>{{Cat|SOA}}<br />
{{Soa Links}}<br />
<br />
= Description =<br />
This course has been created for managers and architects planning to implement or currently implementing SOA solutions.<br />
It gives the overview of pros and cons of SOA and explains when, why and which part of SOA you should use.<br />
<br />
Some of the questions the course can answer:<br />
* What are the benefits of employing SOA<br />
* What are the risks associated with the SOA approach<br />
* What are the trade-offs<br />
* How to assess potential profit with SOA<br />
* What real business case studies has been already made<br />
* When and to what extent SOA should be implemented<br />
* What are simplification and decomposition benefits<br />
* How to migrate from existing solutions to SOA and why migration to SOA does NOT require rebuilding the whole existing infrastructure<br />
* How to extend legacy applications with SOA<br />
* What are the existing SOA suites and platforms<br />
<br />
= Course Outline =<br />
== A Service Oriented Methodology ==<br />
* Introduction to a SOA adoption roadmap<br />
* Three analysis approaches<br />
* Service oriented analysis<br />
== Advantages of SOA ==<br />
* Traditional EAI Approach<br />
* Problems With Traditional EAI Approach<br />
* Enter Service Oriented Architecture (SOA)<br />
* We Can Easily Change the Process<br />
* Changing Flow Using Legacy Approach<br />
* Replacing an Application<br />
* Other Advantages<br />
* Business Advantages<br />
* Adoption Stages<br />
== SOA Past and Present ==<br />
* From XML to Web Service to SOA<br />
* How SOA was done before<br />
* Emerging standards for SOA<br />
* Compare SOA with other architectures<br />
== What is service oriented architecture? ==<br />
* What is SOA?<br />
* Creating a common understanding of SOA<br />
* The evolution of SOA<br />
* Introducing the concepts of services and SOA<br />
* Design principles of SOA<br />
* The relationship between SOA and web services<br />
* The advantages and risks of SOA<br />
== Introduction to Business Processes ==<br />
* How a collection of services performs a task<br />
* Simple request response interaction<br />
* Complex interaction involving many services<br />
* Need for a coordinator service emerges<br />
* Birth of orchestration or business process<br />
* Composing processes using Business Process Execution Language (BPEL)<br />
* BPM based solutions for orchestration<br />
* Example business processes<br />
== Web Services ==<br />
* Basic web services elements<br />
* Core web services standards stack<br />
* The Importance of WSDL<br />
* The design of SOAP<br />
* The use of registries via UDDI<br />
* The basic concepts of service orientation<br />
== Enterprise Service Bus (ESB) ==<br />
* Objectives<br />
* Service Invocation<br />
* Legacy System Integration<br />
* Web Services to the Rescue<br />
* The role of ESB in SOA<br />
* Security and ESB<br />
== Process Driven Services ==<br />
* Service layer abstraction<br />
* Introduction to business process layer<br />
* Process patterns<br />
* Orchestration and choreography<br />
== Service Oriented Reference Model ==<br />
* Reference models and reference architectures<br />
* The IMPACT SOA reference model and architecture<br />
* SOA vendors and their relationship with SOA<br />
== Layered Architecture ==<br />
* The layers pattern<br />
* Classic three-tier architecture<br />
* Connecting to the domain layer<br />
* Linking to the User interface<br />
* Using packages to decompose a system<br />
* Avoiding mutual dependencies<br />
* What is layering and why do we need it?<br />
* Application service layer<br />
* Business service layer<br />
* Orchestration service layer</div>Izabela Szlachta