Modeling Environment for the Communication Virtual Machine

1. Modeling Environment for the Communication Virtual Machine Team 2 Date: 12/03/2008

2. Purpose of system and scope • Allow teams to create communication models that can be later executed on the Communication Virtual Machine (CVM). • CME created using model driven software development techniques in an easy to use graphical modeling framework • Will eventually allow us to deploy a communication application employing the features already present in applications (Skype or Smack APIs) • Able to load and display schemas in the modeling environment. The system will also store models in GCML and XCML format, including layout information.

3. Implemented Use cases

4. Convert Model from XCML to GCML Actors: Modeler Description: The modeler will give CME as input an XCML file and the CME will return the GCML version of the input file Trigger: The Modeler selects the Convert from XCML to GCML option on the menu. The system responds by … • CME reads the XCML text into memory as a data structure of CML objects. • CME checks if it has a GCML file associated with this XCML file in the repository. If that is the case, CME compares the 2 files to see if they are equivalent (by comparing all objects). • If they are equivalent, CME uses the stored GCML and goes to the last step; • For each of the objects, CME initializes an empty layout entry. • CME opens the GCML file in the Modeling Environment.

5. Convert Model from XCML to GCML Post-conditions: the GCML version of the file is generated and the model is displayed on the CME canvas. Alternative courses of action: This use case can be called from T2_CME_SYSE2E_12_ImportModelFromXCML Decision Support… Frequency: Moderate to high - Performed for every time the Modeler wants to import an existing XCML model (8 times per day). Criticality: High. This is one of the 2 main uses of the system. Risk: High. This requires algorithms and data structures that complicate the programming.

6. Create File Transfer Model Actors: Modeler Description: The Modeler drags Shapes and Edges to the CME in order to create a File Sharing Model that users will execute later. Pre-conditions: Modeler has the CME open and has access to save created models to the Repository. Trigger: The Modeler Starts a new model by selecting the create new option in the CME The system responds by … 1. The CME creates a new model • The Modeler drags to the Canvas : Person1, Person2, Device1, Device2, Connection1 • The Modeler creates edges from Connection1 to Device1, Device2, and Medium1. • The Modeler drags isAttached1 to the canvas and creates edge from isAttached1 to Device1. • The Modeler drags isAttached2 to the canvas and creates edge from isAttached2 to Device2. • The Modeler saves the model to the repository.

7. Create File Transfer Model Alternative courses of action: The Modeler can instantiate all fields in the modeled objects (i.e. set all properties) in which case the model created can be executed with prompting the final user to fill any other input. Post-conditions: After this use case is complete, the created model has been saved to the repository and is ready to be used by the GUI user. Decision Support… Frequency: Low - This model would have to be created only once, it will be modified sporadically. Criticality: High - Directly support one of the main uses of the system Risk: Medium

8. Software architecture diagram

9. Minimal Class Diagram

10. Convert XCML to GCML

11. State Machine

12. TCS_5.1(Convert the model form the XCML to GCML)

13. TCS_5.3(Convert the model form the XCML to GCML)

14. Screenshots • Login • Environment • Convert GCML to XCML

18. Thank you Questions ?Comments ?