Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

AddIn-Development for Rational Rose

IP.com Disclosure Number: IPCOM000010696D
Original Publication Date: 2003-Jan-09
Included in the Prior Art Database: 2003-Jan-09
Document File: 4 page(s) / 29K

Publishing Venue

IBM

Abstract

Disclosed is an approach to implement model driven architecture on standard UML tools like the Rational Rose. Instead of using meta case tools, well known and widely used UML modeling tools can be enhanced with additional features to support domain specific modeling. Based on extension of UML modeling elements and with respect to the target environment (Rational Rose), specific semantics can be implemented easily. The existing modeling environment based on this approach allows rapid development of new semantic models which can be plugged into Rose as AddIn's.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 39% of the total text.

Page 1 of 4

AddIn-Development for Rational Rose

Summary

Disclosed is an approach to implement model driven architecture facilities on standard CASE tools like the Rational Rose modeling software. Instead of using or developing new specialized meta modeling tools, well known and widely used UML modeling tools can be enhanced with additional features to support domain specific modeling. The realization can be done as a pluggable module, called Add-In.

    For UML-based case development environments like Rational Rose it is a simple but effective complement to reduce the gap to meta case tools like MetaCase or DOME.

Starting point

    Rational Rose is a recognized case tool in the area of UML-based object oriented software modelling. Thru it's open extensibility API it is possible to extend the tool in a defined way. Menus and properties can be programmatically customized to capture requirements used for realizing domain specific or model driven architecture development. The implementation of such an extension is called an Add-In.

    However, the development of such Add-In's is not structured, time consuming and therefore not appropriate for project specific customization tasks which have to take place in short time frames. However, this is the base for popular development techniques called domain specific modeling or model driven architecture.

    UML is the modeling language specified by the OMG (Object Management Group) and used largely in the development of object oriented software. The language contains a fixed set of elements but also extension mechanism thru so called 'stereotypes' and tag/value property lists, which can be attached to each model element. The UML language itself is an instance of the MOF (Meta Object Framework), a framework to describe modeling languages. As an important prerequisite, MOF uses UML for describing the meta models. Typically, meta case tools operate on the MOF layer 1, while standard UML tools work on MOF layer 2.

The approach

    The disclosed approach combines the programmable extensibility features of standard case tools (like Rational Rose' REI) and the UML extension mechanism. It supports the canonical development of new semantic extensions in a formalized way according to the modeling scopes defined by the UML and MOF meta models. The approach has been described for Rational Rose, but is itself not limited to this tool, and can be used with different modeling environments also.

    Logically, the disclosed approach uses semantic extensions of the UML model, located at the MOF layer 1 according to the OMG's modeling classification scheme. Because only standard mechanism of the UML and MOF models are used, the resulting extensions will be MOF compliant automatically.

Implementation Considerations

    Typically, the implementation of this approach will be separated into two components, a development and configuration component and a runtime component, which is hooked into the targeted runtime environment (CASE tool). The next parag...