Page 6 of 6 pages ‹ First  < 4 5 6

Support for the ‘AFs - Wiki Now Live

Wiki- With Spaces for TRAK, MODAF, DODAF and Common Process/Problems

After a long time - some months - of effort the wiki has got to the point where it’s sensible to let it loose.

It has something over 200 pages (a devil to keep consistent) and there’s inevitably a lot of explanation to support the recent release of TRAK. It does have a comparison between TRAK and MODAF 1.2 and sections for MODAF, DODAF, NAF as well as for the modelling process.

Any site member can add content as with the rest of this site - if you don’t see the page you wanted help create it!

There’s lots still to do both in terms of content and adding functionality

• wiki page heading links
• linking the wiki to the discussion forums so that comments can be made on each page

Visit the wiki now!

Comments

Comment on this article

Forums

• See discussion thread in forums

TRAK is in the Wild - Now an Open Source Enterprise Architecture Framework

TRAK has been released, thanks to the foresight of London Underground Ltd., under an open source license.

Releasing TRAK under open source is important because

• it is a standard to facilitate the exchange of architecture models
• it recognises that there are many who could contribute expertise if allowed to do so - any with the need or energy/motivation can participate
• it provides a feasible maintenance and support system - one where TRAK has the wherewithall to heal itself
• it keeps the cost of using the standard to a minimum - since architecture is a form of communication we shouldn’t tax it!
• it represents pragmatism in terms of releasing early, not waiting for perfection and in collaborating for the common good

The UK Department for Transport are the sponsor of TRAK as part of a wider systems engineering initiative.

The release of TRAK has been split into 4 products.

The first 2 parts form the logical definition of TRAK.

• the TRAK metamodel. This specifies the allowable object types and relationships that can be used. In essence it provides the language that an architect can use through the set of nouns and verbs. It includes a simplified metamodel for easy reference. It also includes a detailed comparison against MODAF 1.2 in order to set an initial baseline. One of the reasons for release using the GNU Free Documentation License (GFDL) is that the History section is preserved together with attribution to those who help develop TRAK. The metamodel is at trakmetamodel.sourceforge.net
• the TRAK architecture viewpoint definitions. TRAK adopts ISO 42010 / IEEE 1471 practice by having a viewpoint for each architectural view that specifies the concerns addressed, the allowable objects (from the metamodel), the suggested presentation format and the consistency rules. It includes a comparison against MODAF 1.2 view set. It is released as open source under the GFDL at trakviewpoints.sourceforge.net

The second 2 parts are implementations against the logical definition.

• the MDG Technology for TRAK. This is a Sparx Systems Enterprise Architect (EA) file that contains the architectural model used to create both the MDG plugin that implements TRAK in Enterprise Architect and the UML profile for TRAK which is used by Enterprise Architect and any other UML modelling tool. It represents the implementation of both the TRAK metamodel and the TRAK viewpoint definition as far as is possible. It contains the EA plugin and the source EA project file. It is released under the GNU Public License version3 (GPL v3) at mdgfortrak.sourceforge.net
• the UML profile for TRAK. This provides the set of objects and relationships defined within the TRAK Metamodel in a way that any decent UML modelling tool can use. It is released under the GPL v3 at trakumlprofile.sourceforge.net

Not saying it’s perfect - we know it isn’t. It’s good enough for practical purposes and we have a list of things that need looking at. What I hope is, being open source, that anyone needing to apply it in a particular situation and finding it lacking can then get involved to solve the problem. Application and usability are all important - more so than any theoretical underpinning. The framework is not a system - this only arises when you add tools, people, organisations and therefore you always have to address visibility, navigation, affordance etc - in short the user interface for the whole thing. We hope in this way that TRAK will be user-centric and problem-led rather than specification-centric.

If you do want to get involved there are forums set up at the TRAK Viewpoints and TRAK Metamodel sites.

Comments

Comment on this article

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 http://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 http://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

Page 6 of 6 pages ‹ First  < 4 5 6