code prole


coding for the proletariat since 1977

Model Management

As a professional consultant I use the tools provided by the client. On occasion, when allowed, I make suggestions and try to steer the tool set towards what I am familiar with, and what I think works best. My present engagement is heavy into the IBM/Rational suite of software development tools. The trinity of WSAD, XDE, and ClearCase allows us to develop collaboratively, a large scale application. There are times however when this industrial strength solution leaves me wanting more.

The weakest piece of his trio is ClearCase. It is intrusive, sluggish performing, and occasionally cantankerous. The layered architecture we are using for this application results in extremely long package names, which combined with any kind of decent path name in the files system, overruns the 256 character limit imposed by ClearCase. In other words, it is possible to create a new package in XDE, fill it with objects and save your work, only to have ClearCase truncate the path/file name to 256 characters WITHOUT TELLING YOU. The next time you open your model, you get missing unit errors. Very messy to resolve. We are in the midst of a migration to a later release of CC, which should expand our file name limit to 1000 characters.

We are also in preparation to migrate to RSM/RAD, or Rational Software Modeler and Rational Application Developer – WSAD 6 and XDE++. (I know about RSA, Rational Software Architect, and it would be ideal to have and use. Licensing costs make it prohibitive for this client, unfortunately.) This is not as easy and simply opening new software and importing your model. It seems that XDE, in trying to be all things to all people, supports multiple model types whereas RSM supports only one. The RSM model is pure UML, which is a Good Thing. However, since we were utilizing the code generation feature of XDE (auto sync on), we were using Java Code Models. In a JCM an interface is really a Java class with a special stereotype. In a UML model (or Basic as it is called in XDE) an interface is represented by, well, an interface. Converting to RSM will result in all the interfaces being converted to java classes, that happen to have a stereotype of interface. We will have to either convert the model and then clean up all the now broken interface touch points, or convert the model to UML in XDE and then import it into RSM.

Both XDE and RSM support configurable transforms that would allow the correction of our interfaces to be scripted. However, this is not a trivial task itself, and we are under tight deadlines. As we sort out the steps, and the transforms required, I’ll try to post a guideline here. Maybe we are the only ones in this pickle, but I suspect not.


Filed under: Software

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: