Page 15 of 16 pages ‹ First  < 13 14 15 16 > 

OMG - Multiple tool vendors demonstrate exchange of UML models using XMI

From the Object Management Group (OMG) website:

OMG’s Model Interoperability Demonstration a Success
Multiple tool vendors demonstrate exchange of UML models using XMI

Needham, MA, USA - January 4, 2010 - Members of OMG’s™ Model Interchange Working Group (MIWG) held an Interoperability Demonstration on December 7, 2009 at the OMG Technical Meeting in Long Beach, California. This event demonstrated an initial capability to interchange UML® models between six tools from five different vendors. The participating vendor tools included Artisan Studio, IBM Rhapsody, IBM RSx, SOFTEAM Modelio, No Magic MagicDraw, and Sparx Systems Enterprise Architect. The MIWG has posted a recording of the demonstration, as well as an introductory presentation at https://www.omgwiki.org/model-interchange/doku.php.

During the demonstration, the test conductor provided a reference diagram to the participating vendors that they had not previously seen. Each participating vendor used their tool to create a diagram that was intended to replicate the reference diagram, and then generate and export the corresponding XMI to a shared work area. The participating vendors then used their tool to import the XMI® created in the other tools, and regenerate the diagram.

“This event not only demonstrates a level of interchange, but more importantly, it demonstrates the willingness of the vendors to work together to satisfy a critical need among the user community,” said Sanford Friedenthal, chair of the MIWG.

“I congratulate all the participants on achieving this significant milestone on the path to demonstrating complete XMI interoperability between tools supporting OMG modeling standards”, said Richard Mark Soley, Ph.D., OMG President and CEO. “Exchanging UML, OMG SysML and UPDM models with customers and suppliers helps realize the full benefits of capturing hardware and software designs and enterprise architectures using these widely-used precise modeling notations. I believe this demonstration will accelerate the adoption of model-driven engineering techniques in general, and OMG’s Model-Driven Architecture in particular, by guaranteeing the ability to combine best-of-breed modeling tools in both inter- and intra-enterprise tool chains.”

The MIWG was established in December 2008 to demonstrate and enhance the interoperability among UML-based modeling tools using XMI. The XML Metadata Interchange (XMI) format is the OMG standard for exchanging models. The group’s focus is on model interchange between UML, OMG SysML™, and Unified Profile for DoDAF and MODAF (UPDM) -capable tools. The MIWG comprises end users, tool vendors and experts in the UML and XMI standards. The US National Institute of Standards and Technology (NIST) is providing an XMI validation tool that forms a key part of this process. Model Driven Solutions (MDS) and Adaptive have been providing additional technical expertise and configuration management support of the modeling artifacts.

The MIWG uses an incremental testing approach to demonstrate interchange with increasing levels of interchange. To date, the MIWG has completed six test cases encompassing class models, activity models, composite structure models, and simple profiles. Issues resulting from the testing are identified and addressed. The testing results to date demonstrate a significant level of interchange capability across multiple tools. The plan is to complete interchange testing of the majority of UML functionality by the end of March 2010, and then to proceed with SysML interchange testing. Following the completion of the base level of SysML testing, the group will proceed with UPDM interchange testing, which leverages both UML and SysML. The US Department of Defense, the UK Ministry of Defence, and NATO have all emphasized the criticality of this capability, and are closely monitoring the results from this effort. Information on the MIWG, the test cases, testing approach, and plans are available on the group’s Wiki page at https://www.omgwiki.org/model-interchange.

Participants

The organizations currently participating are:

• Artisan (participating tool)
• IBM (participating tool)
• SOFTEAM (participating tool)
• No Magic (participating tool)
• Sparx Systems (participating tool)
• Adaptive (Test case construction, validation and support)
• MDS (Test case support and version control)
• NIST (Independent test case validation)
• Lockheed Martin (Chair)

How to get involved

The MIWG will continue to conduct interoperability test coverage for UML, SysML and UPDM. Any organization wishing to participate in the MIWG is encouraged to join OMG. For more information on OMG membership, please contact Ken Berk, vice president, business development at .(JavaScript must be enabled to view this email address) or +1-781-444-0404.

Comments

Comment on this article

Building Knowledge of the World, in Small Steps - “Wikitecture”

One of the purpose in standardising architecture models is making it easier to share. This isn’t the whole story, however, if all we end up doing is starting afresh or recreating models. The point of re-use isn’t just financial (although it saves money) - it’s that it allows us to add to what has been modelled before.

If everyone keeps adding to the model what we are effectively adding is knowledge through the elements and relationships. If many organisations or individuals add to the model(s) we have the modelling equivalent of a wiki - hence the term “wikitecture”. This makes much more sense that hiding models behind corporate walls.

If anyone is interested in adding to the demo model or wants part of it to develop using TRAK then please contact .(JavaScript must be enabled to view this email address)
- it’ll be open source. I have some ideas in terms of how this might work using open source code repositories.

Comments

Comment on this article

Thoughts - “The TRAK Enterprise”

This article presents some musings on how TRAK as an enterprise might be represented and how it might work. Needless to say there is an architecture description underpinning this!

• Capability Perspective - what are the likely goals?
• Concept Perspective - logical needs, connectivity & exchanges
• Solution Perspective - aspects of a possible solution

Concept Perspective

What Does the TRAK Enterprise Consist of - Conceptually?

If TRAK is considered to be a standard then what would we need to maintain it, what would would we need to support the users (architects, tool vendors, browsers etc) and how does it fit together? Indeed where does it stop and something else start i.e. what is the boundary of the ‘TRAK Enterprise’ "system"?

Fig. 1 - CV-01 The Needs of "The TRAK Enterprise"

Figure 1, TRAK::CV-01 - The Needs of "The TRAK Enterprise", attempts to show a boundary - light blue background - within which the ‘TRAK Enterprise’ might exist and logically how it depends on things outside the boundary (and vice versa).

The logical things inside the ‘TRAK Enterprise’ boundary listed below in Table 1.

The logical things outside the ‘TRAK Enterprise’ boundary are listed below in Table 2.

Of course this isn’t quite right yet as it should also include ‘Training Providers’. This is one of the points of modelling and trying to draw something visually - it slows you down and forces you to think. The metamodel provides the skeleton upon which you hang your ideas and it also provides a sort of filter to view the real world and tease of the types of thig it consists of.

Anyway, more to follow as the thoughts unfold ....

Comments

Comment on this article

Page 15 of 16 pages ‹ First  < 13 14 15 16 >