1. 1 12 th SE Workshop Practices for introduction of systems based on service oriented architecture Duško Vukmanović, Mr.sc, dusko.vukmanovic@ieee.org Damir Kalpić, PhD, Professor, damir.kalpic@fer.hr 12 th SE Workshop Software Engineering Education and Reverse Engineering Opatija, Croatia, September 2-9, 2012

2. 2 12 th SE Workshop Agenda Introduction – SOA characteristics Reference SOA Maturity model Comparison of the SOAMMs Key practices Q&A

3. 3 12 th SE Workshop SOA characteristics SOA foundation is a service. Services on network are integrated in composite applications. Services promotes (re)usability. SOA services and BPM processes convergence. Panacea for IT challenges – application and data integration, connect applications and business processes, reduce costs and flexible and rapid application development.

4. 4 12 th SE Workshop Reference SOA Maturity model Stability – mainly for integration needs Flexibility – composite application Sense and Respond – optimizing the business processes performance

5. 5 12 th SE Workshop Comparison of the SOAMMs HP SOAMM IBM SIMM /OSIMM IT Service CMMOracle SOAMMNEW SOAMM Microsoft SOAMM STABILITY Ad-hocSiloInitial LevelAd hocInitial ServicesBasic Integrated Repeatable level Opportunistic Architected Services ComponentizedSystematicStandardized FLEXIBILITY StandardizedDefined a. Business serv. b. Collaborative s. Service ManagedCompositeManaged Measured Advanced SENSE AND RESPOND ServicesBusiness Serv. Adaptive Virtualized services OptimizingOptimized Dynamic Dynamically Re- Config. Serv. Business Services

6. 6 12 th SE Workshop Key Practices Service layers –utility, (hybrid), business and the orchestration layer Business object services –standard definition for business data objects Integration centre –someone to lead the SOA effort Error handling framework –a consistent way to manage errors through technology

7. 7 12 th SE Workshop Error handling framework Technical errors –Infrastructure errors Service not available, network outage, backend database not available –Data format error Inadequate data structures, damaged messages They can occur on any service call. Handling in the process - repeated code in all processes, difficult to maintain. The concept of "error hospital" - a specialized process to handle errors, also requires a common code in all processes. Recovery for multiple service calls is hard. Unlike simple Commit work / Rollback work in classical DB transactions Technical errors – Challenges in SOA environment

8. 8 12 th SE Workshop Key Practices - continued Security –use the security standards for web services with understanding of the threats faced Versioning –through versioning that we want to ensure the necessary service autonomy Basic governance –shared life cycle management is different from the traditional applications life cycle

9. 9 12 th SE Workshop Expected scientific contribution Identification of crucial activities for successful introduction of SOA into an organisation A framework to handle business and technical errors in SOA systems Easier application of SOA for business improvement Risk reduction in introduction of SOA and in development of composite applications Practices for introduction of systems based on SOA and the proposal for an error handling framework

10. 10 12 th SE Workshop Q&A