The Dark Side of SOA Testing: Towards Testing Contemporary SOAs Based on Criticality Metrics

Transcription

1 The Dark Side of SOA Testing: Towards Testing Contemporary SOAs Based on Criticality Metrics Philipp Leitner 1, Stefan Schulte 1, Schahram Dustdar 1, Ingo Pill 2, Marco Schulz 2, Franz Wotawa 2 1 Distributed Systems Group, Vienna University of Technology, Austria 2 Institute for Software Technology Graz University of Technology, Austria

2 Introduction -based systems promise many advantages loosely coupled interoperable reusable aligned with business goals etc However, this generally comes with a price: Complexity / Error-proneness 2

3 SOA Testing General Overview SOA Model Test Criteria Specification User Model Test Suite Test Bed Runtime Testing Discriminating Tests Test Result Fault Diagnosis YES Fault(s) Detected? NO End YES Fault(s) Isolated? NO 3 Active Diagnosis

4 State of the Art There is some related work on testing But mostly: Testing of single services, e.g. S. Zhao, X. Lu, X. Zhou, and T. Zhang, A Reliability Model for Web s - From the Consumers Perspective, in Proceedings of the 2011 International Conference on Computer Science and System (CSSS), Testing of service compositions, e.g., Z. Zakaria, R. Atan, A. A. A. Ghani, and N. F. M. Sani, Unit Testing Approaches for BPEL: A Systematic Review, in Proceedings of the th Asia-Pacific Software Engineering Conference (APSEC 09). Washington, DC, USA: IEEE Computer Society, 2009 Very little related work on how to test SOAs in its entirety 4

5 Contemporary SOA Registry CRM Billing s Consumers Compute 5

6 Contemporary SOA Frontend Application Business Processes Monitor Registry Message Bus Mediators Aggregator s Billing CRM Compute 1 Compute 2 Backend Applications 6

7 SOA Testbeds What is currently missing? Approaches to test not only ONE service or ONE process, but an entire service ecosystem (including complex dependencies and cross-references) In the end, you require complex testbeds to test run your SOA components before deployment However, how do you build such testbeds? 7

8 Criticality Metrics Our idea: Use criticality metrics to identify which components of your SOA are most relevant (and hence need to be part of your testbed) Based on the concept of complexity metrics from software engineering (e.g., cyclomatic complexity) Those metrics are heuristics to help human users identify critical SOA components 8

9 Some Initial Example Metrics (1) Short Name Range Name SSF Statefulness {stateful, stateless} NOSV NOPU IMR Number of Versions Number of Process Usages Interface Mediation Required N 1 N 0 {yes,no} 9

10 Some Initial Example Metrics (2) Short Name CPC CMEP Name Cyclomatic Process Complexity Complexity of Message Exchange Pattern Range PLC Process Landscape {core, support} Categorization DIR Dynamic Invocation Ratio 0; 100] N 1 N 1 10

11 Next Steps Clearly, our initial metrics (some more are in the paper) are only a rather simplified first step Next steps: Survey more metrics / validate existing ones Define a more concrete process for using those criticality metrics to build better testbeds 11

12 Acknowledgements P23313-N23 (Audit 4 SOAs) P22959-N23 (MoDiaForTed)

13 Position Statement Software Engineering (in for) the Cloud Current research is somewhat awkward: A lot of research is done w.r.t. VM placement, energy efficiency, multi-tenant clouds, Issues that only interest cloud providers More important (I think): Consumer side issues How to build applications for the cloud? How to migrate between clouds? How to ensure privacy in the cloud? 13

14 Position Statement Software Engineering (in for) the Cloud Current problems for SE in the cloud: Lack of understanding what the cloud is and does Solution:?? Educating people better / more truthfully?? Lack of good tooling to build cloud services Solution: build better tools For instance CloudScale (which we will hear about in a later talk) 14