Dededede

1 Introduction 1.1 SOA and SOC Service-oriented architecture (SOA) and the corresponding service-oriented

SMMA is essentially a model-driven system engineering approach, but it is different from traditional modeldriven approach. Currently, model-driven development (MDD) often emphasizes on OO modeling and analysis using UML. For example, UML 2.0 has 13 models, and an engineer may select few models from these 13 models for modeling, analysis, and code generation. One example is Executable UML approaches where they often pick three or four UML models so that code can be automatically generated. Each UML model is unique and often it is difficult to transform from one model into another. In dynamic SOA, changes are frequent and extensive, and it is desirable that once the model is updated, the model can be automatically re-analyzed and re-simulated, and code can be re-generated and re-deployed, and the execution can be re-monitored. Furthermore, re-analysis, re-simulation, re-generation, re-deployment, and re-monitoring need to be performed

rapidly to meet the changing environment. The SMMA approach supports this approach as it deals mainly with one integrated core model, and once the core model is updated, the rest can be automatically carried out. One example of such modeling language is PSML, which includes a process language for services PSMLS [42], and an extended collaboration description language PSML-C [47]. Furthermore, PSML can generate various other models for analyses such as completeness and consistency checking, and execution thread generation. The PSML ontology is integrated with the process model and with various analysis tools. Any change in one sub-model such as the process model will not cause other sub-models to be updated. Based on PSML model, a variety of operations and analyses (listed in Table 7) can be automated performed to address the SOSE techniques listed in Table 1.

10

SOCA (2007) 1:3–17

Model Checking

Code Generation