SOA Delivery Strategies and Service Oriented Analysis I

1. SOA Delivery Strategies and Service Oriented Analysis I 605.702 Service Oriented ArchitectureJohns-Hopkins University Montgomery County Center, Spring 2010 Session 8, Lecture 7: March 25, 2010 Instructor: T. Pole

2. Lecture #7 Goals • Learn the three primary delivery strategies • Understand Service Oriented Analysis Basics • Become familiar with SOA Design Process Outline • Understand the goals for Exercise #4

3. Session #8 Today’s Agenda • Required Reading for This Week • Chapter 10: SOA Delivery Strategies • Chapter 11: Service Oriented Analysis Part I: Introduction • Today’s Lecture • Questions about Lecture 6 • Lecture Chapters 10 and 11 • Exercise #4

4. Ch 10 Delivery Strategies • Overview • 10.1 SOA Delivery lifecycle phases • Series of steps required to construct the services for a given service oriented solution • 10.2 Top Down Strategy • Analysis first approach, aligned with biz model • 10.3 Bottom Up Strategy • Create service to fulfill application requirements • 10.4 Agile Strategy • Biz analysis concurrent with service design & dev.

5. 10.1 SOA Delivery Life Cycle • Typical system development phases • Service Oriented Analysis • Service Oriented Design • Service Development • aka Creation Implementation • Service Testing • Service Deployment • Service Administration • Operation, Monitoring and Maintenance

6. 10.2 Top Down Strategy • Analysis First Approach • Assume that business requirements have already been collected • Probably derived from existing business process definitions • Business model driven • Can result in high quality, organizationally agile, evolvable SOA implementation • Requires substantial pre-work (business process engineering, etc.)

7. 10.3 Bottom Up Strategy • Encourages creation of services specifically for application centric needs • Integration is often the primary motivation • Services are built as needed • Approach used by majority of “SOA” development projects • But not really service oriented

8. 10.4 Agile Strategy • Combination of the two: top down and bottom up • Initial top down analysis • Followed by iterations through the rest of the life cycle • Some services are being developed while additional analysis is being performed for future changes to existing services, and creation of new services. • Best fit for fulfilling immediate needs while minimizing impact on organization’s business model and service oriented qualities of the architecture.

9. Ch 11 Service Oriented Analysis Part I - Introduction • Determine the scope of the SOA • Analysis of requirements • Derive additional functional requirements • Derive system level requirements • Identification of business processes that will be automated in the SOA • Map out the (candidate) service layers • Identify individual service operations modeled as candidate services • Chapter 11 Structure • Intro to SOA Analysis • Benefits of a Biz Centric SOA • Deriving Biz Services • Analysis process defined in chap’s 11 and 12

10. SOA Design Process – An Outline (1 of 2) • Analyze Domain • Define Business Processes • Survey Legacy Software • Define Architecture Model • Determine layer model • Establish links between biz processes and legacy software • Define candidate services • Defines candidate operations

11. SOA Design Process – An Outline (2 of 2) • 3. Define SOA Services (iteratively) • Assign operations to services • Link Biz Processes to Operations • Add/Delete Services • Add/Delete Operations • 4. Link Biz Processes to Service Operations • Tasks to operations • Entities to services

12. Exercise #4 • Review the assignment from last week • Altered schedule • Due date moved back to midnight April 3 • Legacy software will be delivered to you by midnight March 25 • Interface definition by midnight March 24 • Additional details and discussion

13. Mid Term/Exercise #4 TestConsumerUI RegisterPatient ------------------ RegisterNewPatient FindPatient ResearchPatient------------------ Getreports( PatientID) Patient------------------ GetReports( DocTypeList [optional] )QueryIndex PatientIndex------------------ RegisterPatient( Name, SSID, DoB, Gender) GetPatientID( Name, SSID, DoB, Gender ) DocumentRepository------------------ AddContent( PatientID, DocType, Doc ) SearchForContent( PatientID [optional], DocType [optional] ) RetrieveContent( ContentAssetID )

14. Exercise #4 Assignment • Title/Name the types of layers in the architecture • Implement the services • RegisterPatient • Research Patient • Patient • PatientIndex • DocumentRepository • I will supply for you in one week, the “Legacy” document management component you will need to implement the lgacy software this service “wraps” • Implement a client to test your SOA Solution

15. Exercise 4: Details and Discussion • Document types: • Only straight text files are supported • Interface to Legacy Software • Although it publishes a SOAP interface, the interface is not to for implementing other services’ operations. • A new utility service “DocumentRepository” must be implemented as part of your exercise submission • Q&A

16. Summary • Read Chapter 12 for next week • Work on your exercise #4 submission • We will have another opportunity for Q&A on Exercise #4 next class • Legacy software will be available, on the class web site by midnight Saturday 3/27 • Interface will be available by midnight 3/26