Migrate RIM Maintenance to OTS UML Modeling Tool

Current RIM Maintenance (since 1997)

RIM maintained in Rational Rose (UML 1.0 modeler). It includes Properties either:

• as markup in Descriptions OR

• in property set added to UML 1.0 model

RIM is extracted from Rose with Visual Basic (using Rose APIs) into Design Repository (in Access DB). The process builds a traceable archive of all substantive changes.

RIM publishing:

• semantics extracted from DB to XML and then transformed to coremif in V3 Generator

• Graphics are "copied" from Rational Rose and pasted into Visio where they are scaled and saved as GIFs and/or PDFs

Objectives of New Process

• Maintain RIM in an OTS UML modeler

• Retain the traceable archive in MIF

• Create an HL7 mini-Profile for RIM

• Transfer properties from description tags to Profile

• Retain existing graphics.

Conversion Steps

1. Converted existing Rational model to Rational Software Architect (RSA) using stock IBM importer.

2. Export model from RSA to XMI 2.2 using stock IBM exporter (also creates HL7 Profile from old Rose properties)

3. Create XMI-MIF transform as
   1. Proof of concept

   2. Identify missing data, if any

   3. identify needed additions to Profile

4. Create new HL7 Profile based on properties, etc. from MIF 2.2

5. Create "temporary" transform to convert the RSA "emx" file (primary RSA file) in order to
   • update and populate the new Profile

   • delete the old Profile; and

   • remove properties from descriptive tags as they are moved to Profile.

6. Verify RSA model remains " valid" and then export anew to XMI 2.2

7. Revise transform of Step 3 to use the new Profile rather than descriptive tags.

8. Integrate Step 7 into V3 Generator

9. Set plan for releases - coremif files only; remove DB from releases; and announce.

10. Convert Access RIM Archive DB to MIF file

    (Export to XML and transform to MIF)

11. Create transform (and source data format) to designate substantive changes and then
    1. Save changed element to MIF Archive

    2. Assign new GUID to changed element

12. Document the whole schmeer so that can be executed by other than this author.