1. SOAD - 1 Analysis and Design of Service Processes Kiersten Fox MBA 731 October 22, 2007

2. SOAD - 2 History of Service-Orientation Definition of Service-Orientation: A design paradigm that specifies the creation of automation logic in the form of services Thomas Erl first publisher of service-oriented design process from and industry perspective in his book, “Service-Oriented Architecture: Concepts, Technology, and Design” As part of Erl’s process, services produced by the service-oriented analysis process are used as input for service-oriented design

3. SOAD - 3 What is Service-oriented analysis and design (SOAD)? Created by IBM No formal definition An approach to software modeling and development specially designed for service- oriented architecture (SOA) As introduced by Mark Colan, SOA is an emerging architectural style for crafting next generation enterprise applications In SOA, applications can be structured from reusable components, instead of creating one huge application SOA adds additional themes such as service choreography and service repositories

4. SOAD - 4 Existing Approaches to Analysis and Design Existing Approaches –Object-Oriented Analysis and Design (OOAD) –Enterprise Architecture frameworks (EA) –Business Process Modeling (BPM) Assist with identifying and defining appropriate concepts within an architecture However, may not be adequate for SOA when used independent of each other

5. SOAD - 5 BPM, EA, and OOAD Positioning (from IBM)

6. SOAD - 6 Shortcomings of Existing Approaches Enterprise architecture –Usually generic –High-level architectures fail too broad for developers BPM –Can be used as a starting point –Not synchronized with design-level use case modeling OOAD –Too specific –One use case model created per problem –Big picture problem unclear –Use case models are not synchronized with their BPM counterparts

7. SOAD - 7 Need for New Approach OOAD, EA, and BPM only cover part of the requirements needed to support SOA SOA approach reinforces general principles, but also adds new themes such as service choreography, service repositories, and the service bus middleware pattern SOAD –Hybrid of approaches –Combines OOAD, EA, and BPM and new themes

8. SOAD - 8 SOAD, EA, BPM, and OOAD (from IBM)

9. SOAD - 9 Example from IBM: Automotive Work Order Process of how an automotive maintenance company manages its customer operations Business scenario

10. SOAD - 10 Flow of Work Order Process (from IBM)

11. SOAD - 11 Services Model (from IBM)

12. SOAD - 12 BPM for Work Order (from IBM)

13. SOAD - 13 SOAD (from IBM)

14. SOAD - 14 Strengths and Weaknesses of SOAD Strengths Built on strong foundation Innovative Meet-in-the-middle approach supporting analysis and design Weaknesses No formal definition of SOAD Notation and processes are not defined UML may continue to be notation of choice on the process side Will require further enhancements Why not build on a previous approach instead of adding complete new one?

15. SOAD - 15 Why do we care? Besides difference in modeling… Systematical difference between traditional approach and SOA approach In traditional approach, business systems analyst compiles information and hands it over to architect In SOA projects, business systems analyst and developer define conceptual design together to ensure business logic is accurate SOAD is a “meet in the middle approach” –Fills in gap between business perspective and IT

16. SOAD - 16 References 1.“Service-oriented analysis and design.” Wikipedia. http://en.wikipedia.org/wiki/Service- oriented_analysis_and_design. http://en.wikipedia.org/wiki/Service- oriented_analysis_and_design 2.“Service orientation.” Wikipedia. http://en.wikipedia.org/wiki/Service-orientation. http://en.wikipedia.org/wiki/Service-orientation 3.Saran, Cliff. “SOA Toolbox.” Computer Weekly. Com. 17 May 2007.. 4.Erl, Thomas. “SOA Methodology: Mainstream Processes for Service-Oriented Analysis & Design.” http://www.soamethodology.com. http://www.soamethodology.com 5.Gee, Clive, Pal Krogdahl, and Olaf Zimmerman. “Elements of Service-Oriented Analysis and Design.” 2 June 2004 http://www.ibm.com/developerworks/library/ws- soad1/. http://www.ibm.com/developerworks/library/ws- soad1/