Deliverable D4.2. SHAPE MDE Toolset User s Guide

Transcription

1 Service and Software Architectures, Infrastructures and Engineering Small or Medium-scale Focused Research Project Semantically-enabled Heterogeneous Service Architecture and Platforms Engineering Acronym SHAPE Project No Flexible Business Models Web Grid Services Service Variability UPMS Agents Semantic Web P2P Services Heterogeneous Platforms Deliverable D4.2 SHAPE MDE Toolset User s Guide Work Package # 4 Leading partner: SOFTEAM Editor: Andrey Sadovykh Authors: A. Sadovykh, D. Panfilenko, O. Shafiq, S. Warwas Dissemination level: Public Date: Version: final version Copyright SHAPE Consortium

2 Versioning and contribution history Version Description Contributors 0.1 Initial Version A. Sadovykh 0.2 Updates A. Sadovykh 0.3 Added WSMT installation and usage section, updates in Annex (Acronyms) O. Shafiq 0.4 Editorial corrections of WSMT section A. Sadovykh 0.5 Added PIM4Agents usage section, updated Annex (Acronyms) S. Warwas 0.6 Added CIMFlex description and acronym D. Panfilenko 0.7 Prefinal version A. Sadovykh 0.8 Editorial changes. Correction of issues identified by the review A. Sadovykh 1.0 Final Editing A. Sadovykh Copyright SHAPE Consortium Page 2 / 31

3 Executive Summary This report presents Deliverable 4.2 "SHAPE MDE Toolset" of the SHAPE project, including the results of the tasks T4.1 T4.3 as defined in the Description of Work. This document provides the user guides for the initial version of the SHAPE Toolset. It contains installation instructions and user guides for the following tools: Objecteering CIMFlex PIM4Agents WSMT. Copyright SHAPE Consortium Page 3 / 31

4 Table of contents EXECUTIVE SUMMARY... 3 TABLE OF CONTENTS INTRODUCTION SCOPE INTENDED AUDIENCE DOCUMENT STRUCTURE BACKGROUND INSTALLATION PACKAGING PROCEDURE GETTING AROUND GETTING STARTED OBJECTEERING (SOFTEAM) Deploying SoaML Profile Creating SoaML models Exporting/Importing SoaML Models CIMFLEX (IWI) Configuration Creating business rule views Creating process views PIM4AGENTS (DFKI) Configuration Importing PIM4Agents projects Creating a new PIM4Agents project Importing SoaML models WSMT (STI) Configuration Browsing ontologies, goals and Web Service Descriptions in WSMT WSML Visualizer WSML Text Editor Importing SoaML model TROUBLESHOOTING ANNEXES ACRONYMS REFERENCES Copyright SHAPE Consortium Page 4 / 31

5 1 Introduction 1.1 Scope This document accompanies the SHAPE Toolsuite delivery and represents a User s Guide for installation and usage. The Toolsuite usage is described briefly covering only the detailed not described in the documentation of individual tools. This document is a living document, which is updated with each release of the Toolsuite. 1.2 Intended Audience This document is mainly dedication to SHAPE participants, but will also serve in future as the main User Guide for the SHAPE Tool Suite. 1.3 Document Structure The document is structured as follows: Section 1 is the introduction; Section 2 describes the installation procedure; Section 3 provides a getting started information for all tools; Section 4 addresses the troubleshooting; Section 5 presents annexes. 1.4 Background The SHAPE Toolsuite is dedicated for modelling of Semantically-enabled Heterogeneous Service Architectures. The modelling activities should cover all MDA abstraction layers: CIM, PIM, PSM and realization. For this different Toolsuite components should act on different levels and deal with different aspects of Services Oriented Architectures. The [3] and [4] details the tool usage in the frame of the SHAPE methodology. Currently the following components are available in the SHAPE Toolsuite: Objecteering covering BMM, BPMN, SoaML, UML and platforms such as C++, Java, C#, J2EE; CIMFlex covering business process modelling and rule design (EPC and etc.); PIM4Agents covering multi-agent system modelling; and WSMT addressing semantic web services modelling. The following table gives an overview of the SHAPE Toolsuite components. The table also provides links to documentation available, since the current User s Guide covers only few getting started issues. The table covers only the components available in SHAPE Toolsuite version 1. Layer SHAPE Toolsuite Components Documentation references CIM Objecteering SOA and Scope, CIMFlex Objecteering SOA and Scope [7], CIMFlex section 3.2 PIM Objecteering SOA, UML and SoaML, Objecteering SOA and UML [7], Copyright SHAPE Consortium Page 5 / 31

6 PSM PIM4Agents, WSMT Objecteering C++, Java, CORBA and J2EE. PIM4Agents, WSMT Objecteering SoaML section 3.1 and [8], PIM4Agents section 3.3 WSMT section 3.4 and [9]. Objecteering [7], PIM4Agents section 3.3 WSMT [9]. Table 1 SHAPE Toolsuite Components Documentation References Copyright SHAPE Consortium Page 6 / 31

7 2 Installation In the chapter the installation procedure is described. 2.1 Packaging The installation bundle is packaged in the single executable installer: SHAPE_Toolsuite_Install.exe The package contains the following items: required prerequisites: o Java Development Kit 6; o Objecteering 6.1 Enterprise Edition; Eclipse bundle containing all the tools; this User s Guide; and examples. Note: You will need a license for Objecteering 6.1 Enterprise Edition. Ask SOFTEAM representative at andrey.sadovykh@softeam.fr for a free license for the SHAPE project purposes. The package can be downloaded from Procedure Execute SHAPE_Toolsuite_Install.exe file and you will be prompted to choose the installation path (Figure 2). Figure 1 Welcome Dialogue. Copyright SHAPE Consortium Page 7 / 31

8 Figure 2 Installation Destination Dialogue. The installer will unzip all the content to the chosen folder and configure the tools. During the installation a notification may be shown if one of prerequisite requirements is not satisfied. Figure 3 JDK Installation Dialogue. One may choose to install these prerequisites during the bundle installation (Figure 3). 2.3 Getting Around The Start Menu will be created for SHAPE Toolsuite shortcuts. Figure 4 SHAPE_Toolsuite Link Group SHAPE_Toolsuite will run the Eclipse bundle with all SHAPE tools; Uninstall shortcut will start the uninstaller procedure if you wish to remove the SHAPE Toolsuite from your PC; UsersGuide shortcuts links with this document; Shape Project Website is a link to the project site. Copyright SHAPE Consortium Page 8 / 31

9 3 Getting Started 3.1 Objecteering (SOFTEAM) This section provides a brief description on how to (1) deploy a SoaML profile in Objecteering; (2) to create simple SoaML models and (3) to export/import models. The complete User s Guide for Objecteering can be found at Deploying SoaML Profile After the SHAPE Toolsuite installation as it was described above, start the Objecteering modeller and create a simple UML model. Figure 5 Creating Default Model with Objecteering. Go to Tools menu and choose Deploy an MDAC (Figure 6). Figure 6 MDAC Deployment. Copyright SHAPE Consortium Page 9 / 31

10 You will be led to mdastore folder. Please proceed to shape folder (Figure 7). Figure 7 "shape" MDAC Folder You need to choose soaml_ xx.yy.zz.jmdac and click Open. Repeat the procedure for XMI_ xx.yy.zz.jmdac. soaml_xx.yy.zz.jmdac contains SoaML UML2 Profile. It is compatible with all Objecteering 6.1 editions including Free Edition. XMI_xx.yy.zz.jmdac contains XMI export/import feature. It is compatible with Objecteering 6.1 Enterprise Edition only. You will need a license to use this feature. Note: The whole procedure should be repeated for each new SoaML model you create Creating SoaML models Create any UML element. Go to Auxiliary Properties window and choose stereotype button (Figure 8). Copyright SHAPE Consortium Page 10 / 31

11 Figure 8 Creating UML Class. You may choose any of applicable SoaML stereotypes (Figure 9) Figure 9 SoaML Stereotypes. This mechanism is also applicable for all stereotypes described in the SoaML specification Exporting/Importing SoaML Models For exporting/importing a SoaML profiled model, right-click on Model node in the model explorer. Choose MDA Components -> XMI and select required functionality (Figure 10). Copyright SHAPE Consortium Page 11 / 31

12 Figure 10 SoaML Model Export. A dialogue will appear proposing to choose the XMI model location (Figure 11). Figure 11 XMI Export Dialogue. Hint: In order to modify the default location of the exported file, you may consider to change the default generation path in the Tools->MDAC Options. Copyright SHAPE Consortium Page 12 / 31

13 Figure 12 MDAC Options. For more information on SoaML modelling please visit [8]. 3.2 CIMFlex (IWI) The CIMFlex Tool (Flexible Business Model Tool) is based on the Eclipse Tool using the GMF/EMF plugins. In the current state it is integrated as plugin project within the Eclipse While the Eclipse Modeling Framework serves for the automated generation of Source Code on base on structured models, the Graphical Modeling Framework provides a generative component and runtime infrastructure for developing graphical editors based on EMF. This section provides following usage descriptions on the creation of the business rules and process models, which will be later transformed to SoaML and used for further design at PIM-level: (1) How to configure the CIMFlex plug-in (2) How to create a new business rule view (3) How to create a new process view Configuration The SHAPE Toolsuite comes with installed and configured version of the CIMFlex tool. In order to be on sure that CIMFlex plugin is properly delivered, please follow the steps below: Step 1. Run the SHAPE tool suite (see Section 2.3) Step 2. Open the new wizard either from the project explorer tree or from File New Other Step 3. See if the section CIMFlex is present containing different diagram types of the CIMFlex tool (See Figure 13). If you see at least this section with wizards for different views, then the plugin is configured correctly. Copyright SHAPE Consortium Page 13 / 31

14 Figure 13. CIMFlex diagrams The following diagrams are present and can be modelled in the current SHAPE tool suite bundle: CIMFlex Diagram a process view diagram containing both BPMN and EPC notation for process modelling Visual Business Rules Diagram a view that is allowing for modelling business rules and introduces constraints for the process views Creating business rule views In this section a business rule model diagram is being created. Before that, there has to exist a general project. So, in the first step, we have to create a new project. Step 1. Create a project File New Project General Project. In this guide we name it CIMFlex. Step 2. Next, create a business rule diagram like follows: in the newly created project CIMFlex rightclick on the project an choose New CIMFlex Editor Visual Business Rules Diagram. Let us name it Data.Check. Step 3. In the business rule diagram editor, add the following objects from the business rule palette (see Figure 14): a business rule container Process Choice, a keyword IF, a condition Well temperature rises, a keyword THEN, a term Start Statoil, a keyword THEN and a term Start Saarstahl inside it. Copyright SHAPE Consortium Page 14 / 31

15 Figure 14. Business rule view palette Step 4. After modelling is finished the rule model may look like in Figure 15. Three views are now complete data, organization and business rule. The process model itself is the next step. Figure 15. Business rule view simple rule model Creating process views In this step a process model diagram is being created. We assume the first way of creating a diagram, namely from scratch through New menu in project tree has been used. First, a pool objects is created in order to represent a process flow and then other two objects representing different kinds of notation are added to the process view. Step 1. First, create a CIMFlex Diagram like the following: in the newly created project CIMFlex rightclick on the project and choose New CIMFlex Editor CIMFlex Diagram. Let s name it Statoil. Step 2. Next step is to create a pool object. For that you will need to choose the pool element from the process view palette (see Figure 16) and click-and-drag draw the pool on the diagram canvas. You Copyright SHAPE Consortium Page 15 / 31

16 can change the pool s name by double-clicking on its label and entering a new name, for example Statoil Product Optimization. Figure 16. Process view palette Step 3. You can model the processes only if you add a lane to the pool in the CIMFlex modelling suite, so please click on the ELane representing EPC modelling container and add it to the newly created pool. We name this container EPC Product Optimization for this guide. Step 4. Repeat the step 3 for BLane and name it BPMN Product Optimization. Step 5. After modelling the use case for Statoil from the deliverable 1.1 you may get the model to look like in the Figure 17. The next steps in this guide are dealing with this model exclusively. Copyright SHAPE Consortium Page 16 / 31

17 Figure 17. Statoil use case modelled Step 6. The next important feature in CIMFlex besides being able of modeling in two different notations is mapping between EPC and BPMN constructs. In this guide, we demonstrate it in the Statoil example. Firstly, click on the EPC lane and take a look at its properties (see Figure 18). Figure 18. Statoil EPC lane properties Step 7. As you can see, there is a mapping feature BE Lane (meaning mapping of BLane to the current ELane) for this type of lanes providing for semantic comparison between model objects. To perform the mapping, you have to click on the choose button in the value field of the Mapping BE Lane feature. You should see the following then in Figure 19. Statoil BLane mapping Step 8. After choosing the mapping object you can also set the appropriate mapping type from the list of available types represented in the CIMFlex metamodel. This can be done by choosing the type from the drop-down list in the Mapping Role feature (see Figure 20). Figure 20. Statoil mapping types Copyright SHAPE Consortium Page 17 / 31

18 3.3 PIM4Agents (DFKI) PIM4Agents is the metamodel that specifies the abstract syntax of the Domain Specific Language for Multiagent Systems (DSML4MAS). The PIM4Agents plug-in provides different views for modelling with the DSML4MAS. Moreover, it offers code generation functionality for agent execution environments like Jack and Jade. This section provides an overview on (i) the configuration of the PIM4Agents plugin, (ii) how to load a PIM4Agents example project, and (iii) how to setup a new PIM4Agents project Configuration The SHAPE Toolsuite already contains a preconfigured version of the PIM4Agents modelling tool. To assure that the PIM4Agents plug-in is properly working, do the following: Step 1. Run SHAPE Toolsuite Eclipse bundle (see Section 2.3) Step 2. Open File New Other Step 3. There should be a section called DSML4MAS that contains the different diagram types of the PIM4Agents modelling tool (see Figure 21). The plug-in is properly working. Figure 21 PIM4Agents diagrams. Here is a short overview of the different diagram types: Agent Diagram: for modelling agents and their performed roles, capabilities, and behaviors Role Diagram: for modelling roles Organization Diagram: for modelling organizations and their roles, capabilities, behavior, instances, and protocols Collaboration Diagram: for modelling collaborations inside an organization Protocol Diagram: for modelling the message exchange between actors Behavior Diagram: for modelling the behavior of agents and organizations Environment Diagram: for modelling resources that can be accessed by agents Deployment Diagram: for modelling concrete agent and organization instances Copyright SHAPE Consortium Page 18 / 31

19 3.3.2 Importing PIM4Agents projects In this section we explain how to import the SenderReceiver PIM4Agents example project that is delivered with the SHAPE Toolsuite into the workbench. The example is kept simple and demonstrates the usage of the different diagram types of PIM4Agents. Step 1. Run SHAPE Toolsuite Step 2. Open File Import... Step 3. Select General Existing Projects into Workspace and click on Next Step 4. Select the Select archive file option and click on Browse Step 5. Choose the provided <SHAPE_Toolsuite>/examples/example.zip file and click on Open. <SHAPE_Toolsuite> is the installation folder of the SHAPE Toolsuite. Figure 22 Import dialog. Step 6. Make sure that the SenderReceiver project is selected. Otherwise click on Select All (see Figure 22) Step 7. After clicking on Finish, you have imported the example project into your workspace. Figure 23 depicts the structure of the imported SendReceive project. The *.pim4agents file contains the actual PIM4Agents model. The diagram files provide different views on the PIM4Agents model. Copyright SHAPE Consortium Page 19 / 31

20 Figure 23 SendReceive project structure. Step 8. The different views can be opened by double-clicking on the diagram files. Figure 24 shows the agent diagram of the SendReceive example. We can see the two agent types SenderAgent and ReceiverAgent that perform different roles and have different plans. The lower part of the figure depicts the properties view of the SenderAgent which can be opened by right-clicking on a diagram element and selecting Show Properties View. The properties view allows the user to edit all (also not visualized) properties of a selected diagram element. Figure 24 PIM4Agents agent diagram Creating a new PIM4Agents project Unfortunately, we currently do not provide an own project type for PIM4Agents. Therefore, it is necessary to create an ordinary project and adapt some settings. Step 1. Open File New Project... Step 2. Select General Project and click on Next Step 3. Insert a <project_name> and click on Finish Copyright SHAPE Consortium Page 20 / 31

21 Step 4. Right-click on the new project and select New Folder Step 5. Enter the Folder name models and confirm with Finish Step 6. Right-click on the just created models folder and select New Others... Step 7. Select DSML4MAS Agent Diagram and click on Next (see Figure 21) Step 8. Enter the <diagram_name> of the diagram (see Figure 25). Step 9. Click on Next Figure 25 New agent diagram wizard. Step 10. Now, you have to enter the name of the model file. The name should be similar to the project name since the model contains all model elements of the modelled multiagent system. Step 11. Click on Finish Step 12. To initialize a new diagram/view for the same model file we just created, right-click on the.pim4agents file (see Figure 23). Step 13. Select Initialize <type> diagram file, where <type> is one of the PIM4Agents diagram types introduced in Section (see Figure 26). Copyright SHAPE Consortium Page 21 / 31

22 Step 14. Enter the name of the new diagram Step 15. Click on Finish Figure 26 Initialization of new diagrams Importing SoaML models This section is to be completed once the SoaML transformation is completed. However, expected steps are as follows: 1. A function to import a SoaML model 2. A function to transform a SoaML model into a PIM4Agents model 3. Modification and refinement of the generated PIM4Agents model 4. A function to transform the PIM4Agents model to the agent execution platforms 3.4 WSMT (STI) Configuration The WSMT (Web Service Modeling Toolkit) is installed within the SHAPE_Toolsuite. WSMT may work in conjunction with Web Service Execution Environment (WSMX) 1. You may consider configuring WSMT in order to make it aware of the execution environment. Step 1. Run SHAPE_Toolsuite Eclipse bundle (see section 2.3) Step 2. Open SEE perspective of WSMT. Step 3. On the left panel, right click on the server and open properties to set the IP and ports in order to connect the WSMT to Web Service Execution Environment (WSMX). In this case, IP is localhost, HTTPport is 8080 and servlet port is 8050 Note: WSMT is an ongoing development will have many updated versions in near future. The latest versions of the WSMT can be downloaded from 1 Web Service Execution Environment (WSMX) Copyright SHAPE Consortium Page 22 / 31

23 3.4.2 Browsing ontologies, goals and Web Service Descriptions in WSMT The WSMT is a part of the SHAPE_Toolsuite Eclipse bundle. In order to start using it, change the perspective to WSML. After the WSMT is started, on the left side of WSMT GUI, the Navigator view shows all the projects in your workspace. For this tutorial session, the WSMT contains all the WSMO Ontologies, Web Services and Goals needed to execute the use case in the project called WSMO Tutorial. The workspace also contains some other WSML examples that you can use to understand the WSMT functionality. Figure: WSMT Navigator There are two main editors for viewing and manipulating WSMO descriptions in the WSML formalism, which are the required features of WSMT in context of SHAPE. These are the WSML Visualizer and the WSML Text Editor and instructions for using them are provided in sections 3.1 and WSML Visualizer Copyright SHAPE Consortium Page 23 / 31

24 Figure: WSMT Visualizer The WSML Visualizer provides a graphical representation of the information contained within a WSML document, using a directed graph. In this part of the tutorial we will look at the Simpsons ontology, which is a schema and some instances related with the Simpsons television show. This example wsml file can be found in SHAPE_Toolsuite Installation Folder / examples / the-simpsons-ontology.wsml. Copy it in a Simpsons project. Step 1. Open The Simpsons example project by clicking the plus on the left hand side of the folder icon. Step 2. Right click on the-simpsons-ontology.wsml in the navigator view, choose Open With WSML Visualizer In the visualizer you will see the blue node at the centre that represents the ontology contained within this WSML file. The other nodes in the representation are concepts (yellow) and instances (red). The graph is automatically layed-out using a spring layout algorithm however the representation is fully interactive and by clicking on a node and dragging it the representation can be moved to obtain the best layout. Step 3. Manipulate the graph using the dragging feature to get the best representation. The visualization provided in this editor is fully interactive and allows the user to edit the WSMO Ontology, Web Service, Goal or Mediator being visualized. In the following steps we will add a new concept, some attributes and an instance to the Simpsons ontology. The concept that we shall add will represent the concept of a public park and the instance will represent the park located in Springfield. Step 4. Right click on the yellow concept node called place and choose Add Sub Concept Step 5. In the Identifier dialog enter public_park and select OK (NOTE: a new concept node is added to the visualization). The visualizer separates the complexities in the ontology into multiple levels, in order to start manipulating the attributes of a concept we need to step down to the concept semantic level. We do this by double clicking on a concept. Copyright SHAPE Consortium Page 24 / 31

25 Step 6. Double click on the public_park concept node (NOTE: the view is constrained to information about the selected concept). Step 7. Right click on the public_park concept node and choose Add Attribute Step 8. In the Identifier field enter haslocation. Step 9. In the range form click on Add concept button. Step 10. In the Select a Concept dialog, expand the place concept in The Simpsons Ontology, choose town and select OK. Then select OK in the previous New Attribute dialogue. Now that we have created our concept and added an attribute we can create an instance of that concept. Note that there are two attributes available for use on the instance. The first is the haslocation that we just created and the second is the hasname attribute inherited from the place super concept of public park. Step 11. Right click on the public_park concept again and choose Add Instance. Step 12. In the Identifier dialog enter springfield_public_park and select OK. Step 13. Double click on the new springfield_public_park instance node to move to the instance semantic level. We have created our instance, but we still need to assign values to the attributes of the instance. Step 14. Right click on springfield_public_park and choose Add Attribute Step 15. Choose the haslocation attribute from the public_park concept and select Add for adding a value. Step 16. Choose the Springfield instance from the town concept and select OK. Then select OK in the previous Attribute Value dialogue. Step 17. Right click on springfield_public_park and choose Add Attribute Step 18. Choose the hasname attribute from the place concept and select Add. You will automatically be shown the Specify a Data Value dialog. Step 19. In the Data Value text field enter Springfield Public Park and select OK. In the previous Attribute Value dialogue select OK. Step 20. Save the ontology by using the Ctrl-S shortcut or File Save WSML Text Editor Copyright SHAPE Consortium Page 25 / 31

26 Figure: WSMT Text-based Editor The WSML Text Editor shows the contents of a WSML document, in the WSML human readable syntax, to the user with syntax highlighting, content assistance and many other features that help advanced users who are familiar with WSML to create and manage their WSML documents more efficiently. Step 21. Right click on the-simpsons-ontology.wsml in the navigator view, choose Open With WSML Text Editor Step 22. Use the Ctrl-F shortcut to bring up the find dialog Step 23. In the find enter public_park and click Find. You can now see the human readable syntax of the concept that we created in the visualizer. Step 24. In the find dialog click Find again. You can now see the human readable syntax of the instance that we created in the visualizer Importing SoaML model This section is to be completed once the SoaML transformation is completed. However, expected steps are as follows: 1. A function to import SoaML model 2. A function to transform SoaML model into WSML 3. Display generated WSML in Text based editor or formed-based editor Copyright SHAPE Consortium Page 26 / 31

27 4 Troubleshooting The bug reports should be submitted to Figure 27 Bug Reports Summary Open the summary table (Figure 27) and choose new entry button to add a new report. You can also follow the bug tracking status and review the comments by editing the bug entry. For easy navigation, use search and Group by facilities. Copyright SHAPE Consortium Page 27 / 31

28 Figure 28 Bug Report Form When the adding a new entry, the Bug Report form is shown. The following fields are to be filled in: Version choose the version of the SHAPE Toolsuite you have encountered a problem with. Component choose the component you would like to complain about. Currently the following ones are listed: o Toolsuite in general suggestions about the toolsuite in general; o Installation problems during the installation and errors of the installer; o Objecteering SOAML problems or errors encountered during usage of SoaML UML2 Profile in Objecteering; o Objecteering XMI problems or errors encountered in Objecteering during export/import of SoaML UML2 models; o PIM4Agents problems or errors encountered during elaboration of PIM4Agents models; o CIMFlex problems or errors encountered during elaboration of CIMFlex models; o o WSMT problems or errors encountered while using Web Service Modelling Toolkit; SoaML tree editor problems or errors encountered while using SoaML tree editor for elaboration of metamodel instances. Bug Title a short description of the bug; Bug Description details concerning the bug; Status bug tracing status. Currently the following options are available (Figure 29): Copyright SHAPE Consortium Page 28 / 31

29 o New newly entered bug reports should be tagged new. This status is chosen by reporter; o Assigned when the bug is acknowledged and accepted, the WP4 lead assigns a bug to a team member; o Fixed the WP4 lead changes the status to Fixed when a response to the report or a bug fix is delivered; o Closed the Bug reporter acknowledges the bug fixing by assigning this status. Assigned to this field is filled in during the assignment process by WP4 lead.. : WP4 Lead. : Bug Reporter Report Bug [ne w] Assigne Bug [assigned] [closed] Close Bug [fixed] Fix Bug Figure 29 Bug Status Flow The WP4 team will do the best to respond to all requests in a brief delay. Copyright SHAPE Consortium Page 29 / 31

30 5 Annexes 5.1 Acronyms Acronym ATL BMM BPDM BPEL BPMN CIMFlex DSL DSML4MAS EMF EPC GMF MAS MDA MDAC MDD MDE OWL PIM4Agents SHAML SOAML UML WSDL WSMO WSML WSMX WSMT XSD Description ATAS Transformation Language Business Motivation Metamodel by OMG Business Process Definition Metamodel by OMG Business Process Execution Language by W3C and OASIS Business Process Modelling Notation by OMG Computation Independent Model Flexible Domain Specific Language Domain Specific Modelling Language for Multiagent Systems Eclipse Modelling Framework Event Driven Process Chain by SAP implemented in ARIS Graphical Modeling Framework by Eclipse Multi Agent Systems Model Driven Architecture, trademark by OMG MDA Tool Component Objecteering CASE Tool extension module Model Driven Development Model Driven Engineering Web Ontology Language by W3C Platform Independent Metamodel for Agents UML (formerly UPMSHA) Profile for Modelling for Semantically-enabled service Architectures by the SHAPE consortium (formerly UPMS) SOA Modelling Language by OMG with contributions by the SHAPE consortium Unified Modelling Language by OMG Web Service Definition Language by W3C Web Service Modeling Ontology Web Service Modeling Language Web Service Modeling Execution Environment Web Service Modeling Toolkit XML Schema Definition by W3C Table 2 Acronyms Copyright SHAPE Consortium Page 30 / 31

31 5.2 References [1] SHAPE Document of Work [2] D1.1 Case study scenario descriptions and requirements specifications [3] D2.1 Model-driven methodology and architecture specification [4] D2.2 SHAPE integrated and tool supported methodology [5] D3.1 Consolidation of common basis for metamodels and languages for SHA [6] D4.1 MDE toolset and architecture specification [7] Objecteering CASE Tool User s Guide [8] SOFTEAM s R&D team page for tutorials [9] WSMT web-site Copyright SHAPE Consortium Page 31 / 31