Best Practices for Introducing Service-Oriented Architecture Systems and Error Handling Frameworks

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

2. Agenda • Introduction – SOA characteristics • Reference SOA Maturity model • Comparison of the SOAMMs • Key practices • Q&A

3. 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. Reference SOA Maturity model • Stability – mainly for integration needs • Flexibility – composite application • Sense and Respond – optimizing the business processes performance

5. ComparisonoftheSOAMMs

6. KeyPractices • 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. 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. KeyPractices - continued • Security • use the security standards for web serviceswith 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. 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. Q&A