User Tools

Site Tools


start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
start [2015/09/16 10:41]
edseidewitz Updated for additional test case coverage
start [2016/12/21 10:54] (current)
edseidewitz [How to Use the Vendor-Provided Test Submissions]
Line 6: Line 6:
    * establish a demonstration infrastructure to support the above, including validation tools, demonstration processes and guidelines    * establish a demonstration infrastructure to support the above, including validation tools, demonstration processes and guidelines
  
-Beginning in December 2008, the MIWG has defined a [[start#​Test Suite|test suite]] of 40 test cases to demonstrate interchange of UML, SysML, SoaML and UPDM models between different modeling tools. Participating tool vendors have agreed to publicly post XMI exports from their tools for the MIWG test cases. ​ The objective is to enable the public at large to assess model interchange capability of the modeling tools by comparing the vendor XMI exports to the expected reference XMI file for each test case. These assessments may be used for a variety of purposes, including:+Beginning in December 2008, the MIWG has defined a [[start#​Test Suite|test suite]] of 48 test cases to demonstrate interchange of UML, SysML, SoaML and UPDM models between different modeling tools. Participating tool vendors have agreed to publicly post XMI exports from their tools for the MIWG test cases. ​ The objective is to enable the public at large to assess model interchange capability of the modeling tools by comparing the vendor XMI exports to the expected reference XMI file for each test case. These assessments may be used for a variety of purposes, including:
  
    * Evaluation of the interchange capability of a particular tool as part of a tool selection process ​    * Evaluation of the interchange capability of a particular tool as part of a tool selection process ​
Line 12: Line 12:
  
 The test suite and guidance for how to assess interchange capability using this test suite are summarized below. Please send any questions or requests for further information to [[[email protected]]]. The test suite and guidance for how to assess interchange capability using this test suite are summarized below. Please send any questions or requests for further information to [[[email protected]]].
- 
- 
- 
- 
- 
- 
- 
  
 ====== Quick Links ====== ====== Quick Links ======
Line 24: Line 17:
    * [[http://​svn.omg.org/​repos/​OMG-Model-Interchange/​branches/​Public/​Tests/​|Vendor Test Submission Repository]] (Username: guest/​Password:​ guest) (see also [[start#How to Use the Vendor-Provided Test Submissions]])    * [[http://​svn.omg.org/​repos/​OMG-Model-Interchange/​branches/​Public/​Tests/​|Vendor Test Submission Repository]] (Username: guest/​Password:​ guest) (see also [[start#How to Use the Vendor-Provided Test Submissions]])
    * [[http://​validator.omg.org/​se-interop/​tools/​validator|NIST Validator]] (see also [[start#How to Use the NIST Validator to Assess Model Interchange]])    * [[http://​validator.omg.org/​se-interop/​tools/​validator|NIST Validator]] (see also [[start#How to Use the NIST Validator to Assess Model Interchange]])
-   * {{MIWG-roadmap-120116-reva-draft-sf.ppt|Roadmap}} 
    * [[MIWGInternal|MIWG Internal Wiki]]    * [[MIWGInternal|MIWG Internal Wiki]]
  
Line 32: Line 24:
    * [[InteropDemo1|OMG Conducts Model Interoperability Demonstration at Long Beach CA, December 7, 2009]] ​    * [[InteropDemo1|OMG Conducts Model Interoperability Demonstration at Long Beach CA, December 7, 2009]] ​
    * [[http://​www.omg.org/​news/​releases/​pr2009/​07-08-09.htm|OMG Announces Model Interoperability Working Group, July 8, 2009]]    * [[http://​www.omg.org/​news/​releases/​pr2009/​07-08-09.htm|OMG Announces Model Interoperability Working Group, July 8, 2009]]
- 
  
 ====== Participating Tool Vendors ====== ====== Participating Tool Vendors ======
  
-^ Vendor ​       ^ Point of Contact ​           ^ Tool                       ^ Version ​+^ Vendor ​       ^ Point of Contact ​           ^ Tool                       ^ 
-| Atego         ​| Simon Moore                 | Artisan<​sup>​®</​sup>​ Studio ​| 7.2m    ​+PTC (Atego)   | Simon Moore                 | Artisan<​sup>​®</​sup>​ Studio | 
-| IBM           ​| ​                            | RSx                        ​| 8.0.3   +| IBM           ​| ​                            | RSx                        | 
-| IBM/​Sodius ​   | Eldad Palachi/​Mickael Albert| IBM Rhapsody ​              | 7.6.x   +| IBM/​Sodius ​   | Eldad Palachi/​Mickael Albert| IBM Rhapsody ​              | 
-| No Magic      | Nerijus Jankevicius ​        | MagicDraw ​                 ​| 17.0    ​+| No Magic      | Nerijus Jankevicius ​        | MagicDraw ​                 | 
-| SOFTEAM ​      | Etienne Brosse ​             | Modelio ​                   ​| 2.4.19  ​+| SOFTEAM ​      | Etienne Brosse ​             | Modelio ​                   | 
-| Sparx Systems | J. D. Baker                 | Enterprise Architect ​      | 9.1     |+| Sparx Systems | J. D. Baker                 | Enterprise Architect ​      |
  
  
Line 51: Line 42:
    * Leonard Levine, DISA    * Leonard Levine, DISA
    * Pete Rivett, Adaptive    * Pete Rivett, Adaptive
-   * Ed Seidewitz, ​Model Driven Solutions ​(Model Interchange SIG Chair)+   * Ed Seidewitz, ​nMeta (Model Interchange SIG Chair)
  
  
Line 59: Line 50:
  
 Each test case consists of one or more diagrams and a corresponding reference "valid XMI" file for the model represented in the diagrams (for Test Case 3 and 19 there are two XMI files). All XMI conforms to either v2.1 of the XMI specification (for UML 2.3, SysML 1.2, SoaML 1.0.1 and UPDM 2.0.1) or v2.4.1 (for UML 2.4.1 and SysML 1.3). Each test case consists of one or more diagrams and a corresponding reference "valid XMI" file for the model represented in the diagrams (for Test Case 3 and 19 there are two XMI files). All XMI conforms to either v2.1 of the XMI specification (for UML 2.3, SysML 1.2, SoaML 1.0.1 and UPDM 2.0.1) or v2.4.1 (for UML 2.4.1 and SysML 1.3).
- 
- 
  
 ===== UML Test Cases ===== ===== UML Test Cases =====
Line 94: Line 83:
       * Test Case 47 ([[Test Case 47 UML 2.4|UML 2.4.1]]) - Information Flows       * Test Case 47 ([[Test Case 47 UML 2.4|UML 2.4.1]]) - Information Flows
 (* These test cases are also applicable to SysML.) (* These test cases are also applicable to SysML.)
- 
- 
  
 ===== SysML Test Cases ===== ===== SysML Test Cases =====
Line 111: Line 98:
       * Test Case 49 ([[Test Case 49 SysML 1.3|SysML 1.3]]) - Nested Ports       * Test Case 49 ([[Test Case 49 SysML 1.3|SysML 1.3]]) - Nested Ports
       * Test Case 50 ([[Test Case 50 SysML 1.3|SysML 1.3]]) - Directed Features       * Test Case 50 ([[Test Case 50 SysML 1.3|SysML 1.3]]) - Directed Features
- 
  
 ===== SoaML Test Cases ===== ===== SoaML Test Cases =====
       * Test Case 17a ([[Test Case 17a SoaML 1.0.1|SoaML 1.0.1]]) - Service Architecture       * Test Case 17a ([[Test Case 17a SoaML 1.0.1|SoaML 1.0.1]]) - Service Architecture
- 
- 
  
 ===== UPDM Test Cases ===== ===== UPDM Test Cases =====
Line 123: Line 107:
       * Test Case 21 ([[Test Case 21 UPDM 2.0.1|UPDM 2.0.1]]) - CV-2 Capability Taxonomy       * Test Case 21 ([[Test Case 21 UPDM 2.0.1|UPDM 2.0.1]]) - CV-2 Capability Taxonomy
       * Test Case 22 ([[Test Case 22 UPDM 2.0.1|UPDM 2.0.1]]) - CV-4 Capability Dependencies       * Test Case 22 ([[Test Case 22 UPDM 2.0.1|UPDM 2.0.1]]) - CV-4 Capability Dependencies
 +      * Test Case 40 - Reserved for future use
 +      * Test Case 41 - Reserved for future use
 +      * Test Case 42 - Reserved for future use
 +      * Test Case 43 - Reserved for future use
  
 ====== How to Use the Vendor-Provided Test Submissions ====== ====== How to Use the Vendor-Provided Test Submissions ======
Line 130: Line 118:
 Each of the participating MIWG vendors have submitted results from the latest version of their tools for all the test cases that their tools support. These test submissions are maintained in a Subversion repository and may be updated from time to time to reflect new releases of the vendor tools. They can be used in two ways: Each of the participating MIWG vendors have submitted results from the latest version of their tools for all the test cases that their tools support. These test submissions are maintained in a Subversion repository and may be updated from time to time to reflect new releases of the vendor tools. They can be used in two ways:
  
-   - You can download a vendor submission for a test case from this repository at any time and run it through the [[http://syseng.nist.gov/​se-interop/​sysml/​validator|NIST Validator]] (as described below) in order to assess XMI conformance of the vendor'​s tool for this test case. +   - You can download a vendor submission for a test case from this repository at any time and run it through the [[http://validator.omg.org/​se-interop/​tools/​validator|NIST Validator]] (as described below) in order to assess XMI conformance of the vendor'​s tool for this test case. 
    - You can take submitted XMI for a test case exported from one tool and attempt to import it into a different tool, in order the assess the actual ability to interchange models between those tools in the area covered by the test case.    - You can take submitted XMI for a test case exported from one tool and attempt to import it into a different tool, in order the assess the actual ability to interchange models between those tools in the area covered by the test case.
  
-The public vendor test submission repository is available [[https://dev.enterprisecomponent.com/​repository/​repos/​OMG-Model-Interchange/​branches/​Public/​Tests/​|here]]. Log in using the user name //guest// with password //guest//.+The public vendor test submission repository is available [[http://svn.omg.org/​repos/​OMG-Model-Interchange/​branches/​Public/​Tests/​|here]]. Log in using the user name //guest// with password //guest//.
  
 The repository has two directories,​ UML2.3-XMI2.1 for UML tests and SysML1.2-XMI2.1 for SysML tests. Within these directories,​ there are subdirectories for each test case, with the following content: The repository has two directories,​ UML2.3-XMI2.1 for UML tests and SysML1.2-XMI2.1 for SysML tests. Within these directories,​ there are subdirectories for each test case, with the following content:
start.1442414515.txt.gz · Last modified: 2015/09/16 10:41 by edseidewitz