1. SOMA – Service Modeling and Architecture Elena Epure, 3736229 E.V.Epure@students.uu.nl

2. Agenda  Introduction  Related literature  Meta-modeling  Example

3. Introduction  SOMA – Service Modeling and Architecture  Arsanjani, Ghosh, Allam, Abdollah, Ganapathy and Holley, 2008  Academy of Technology,  IEEE, IBM SOA Community of Practice,  SOA and Web Services Center of Excellence

4. Introduction  Purpose:  To guide the adoption of SOA within an organization  Mistakes regarding SOA adoption  lack of governance  enable everything as a service  use too many details for defining the services  ignore SOA paradigms  IBM solution:  SOMA  Custom tooling: SOMA-ME [CONTINUED]

5. Introduction  Conducting order: Fractal model  Roles: Consumer and Provider [CONTINUED]

6. Related literature  SOA  An evolution of Enterprise Architecture  SOMA  Origins: previous slide  Validation: Resource and Capacity Management (RCM) Center Modernization (Mynampati & Milind, 2010)  Other methods: TOGAF

7. Meta-modeling

8. [CONTINUED]

9. Meta-modeling [CONTINUED]  Final deliverable: SOA Reference Framework

10. Example  Company presentation  ABC, non-life insurance company  Merged with a life insurance company  Problems:  Overlapping processes  Overlapping applications  Complex IT infrastructure  Solution:  SOA adoption

11. Example  Phase 3: Service identification  Three complementary approaches  Goal service modeling  Domain decomposition  Asset analysis  Refactor and Rationalize DomainsFunctional areas Customer Management  Claim registration  Claim administration  Billing and payment Claim Handling [CONTINUED]

12. Questions