Rational Rose 2000

Rose Release Notes

 

Thank you for choosing Rational Rose 2000. The Rational Rose 2000 release notes contain last-minute changes to Rational Rose and the Rational Rose Add-Ins. Refer to the readme.txt file, located on the start menu, for last-second changes not available when the hardcopy and online versions of the release notes were published.

 

Documentation CD

The documentation CD contains supplemental product material like tutorials, models, and user manuals. All the supplemental material for Rational Rose is located under the Rational Rose directory.

 

Contacting Technical Support

Contact information for Rational is available on the Rational web page: http://www.rational.com/. If you wish to contact our technical support staff, please have the following information ready:

Technical Support Locations

Please contact the appropriate area for Rational Rose technical support:

North America Technical Support

Telephone:

800-433-5444 or 408-863-4000

Hours:

West Coast: 9:00 - 18:00 PST
East Coast: 9:00 - 18:00 EST

E-mail:

support@rational.com

Language Spoken:

English

 

Europe, Middle East, and Africa Technical Support

Telephone:

+31-20-4546-200

Hours:

9.00 - 17.30 MET

E-mail:

support@europe.rational.com

Languages Spoken:

French, German, and English

Asia Pacific Technical Support

Telephone:

+61 2 9419 0111

Hours:

9.00 - 18.00 EAT

E-mail:

support@apac.rational.com

Language Spoken:

English

 

Trademark Information

The word "Rational" and Rational's products are trademarks of Rational Software Corporation. References to other companies and their products use trademarks owned by the respective companies and are for reference purposes only.

© Copyright 1999 Rational Software Corporation.

 

Installation and Licensing Information

Please refer to the Rose 2000 Installation Guide that is provided as your primary guide for installing and setting up licensing for this product. If you encounter any problems while installing or licensing the Rose product, please check here first to see if it is a known problem. If a problem is not yet documented, please contact Rational Technical Support so we can investigate it, provide you with a workaround, and track the problem for future action.

See one of the following topics for install information:

See one of the following topics for licensing information:

System Requirements

Before installing this software, please verify that your system meets the minimum system requirements listed below. If you do not have the correct operating system level, the product may not install correctly.

The hardware requirements for Rose 2000 are outlined below:

Item:

Requirement:

Processor

An 80486-based or Pentium-based PC-compatible computer system

Memory

64 MB min. (Memory requirements increase with the size of the model)

Disk space

200MB (100 Rose, 100 download/install)

Other

An SVGA-compatible display (256 or more colors recommended) with their solution set at 800 X 600 pixels.

 

Any pointing device with at least two buttons

Rose 2000 will run on the following operating system platforms:

Rose 2000 requires DCOM under Windows 95. If you do not have DCOM on your Windows 95 system, the install will point you to the Microsoft web site to obtain the software.

The VC++ Add-In requires Visual Studio 6.0.

The Rose J add-in requires JDK 1.1.6 or any of the major Java IDEs.

The Globetrotter FLEXlm license server component, which is required for floating licenses, will run on Windows NT 4.0 (with Service Pack 3 or greater) only. It is not designed to run on Windows 9X; however the installation will not prevent you from installing it under Windows 9X. Client licensing will run on both Windows 9X and Windows NT.

General Install Information

As a precaution, always make system back ups of any machines on which you plan to install this software. Specifically, we recommend you make back ups of any Rose model files that you will be accessing with this software. Also, make certain that you have a current back up of your Registry and system directories prior to running the installation program.

This product includes licensing capability based on FlexLM, a licensing product from Globetrotter, Inc. A license certificate shipped with your product includes a startup license key that allows you to start using your product immediately. You must obtain a separate permanent license from Rational in order to continue using this product beyond this startup key expiration date listed on the license certificate. Please refer to the licensing section of the Installation Guide for detailed instructions on obtaining and installing permanent licenses. Also, see the licensing section of this document for any last minute licensing notes.

Installation Notes

Before Installing

Uninstall Notes

To remove Rose 2000 from a Windows NT system, you must have Windows NT administrator privileges on the local machine.

The setup program installs/updates Microsoft shared components into the Windows 9X System, and Windows NT System32 directories that do not get removed after uninstalling the program. These system files will only get updated if the install encounters older versions of these files on the system. Other programs may use these files, so following Microsoft guidelines we do not remove them from your system. These files include:

adme.dll

asycfilt.dll

atl.dll

cmct2de.dll

cmct2fr.dll

cmct2jp.dll

cmctlde.dll.dll

cmctlfr.dll

cmctljp.dll

cmdlgde.dll

cmdlgfr.dll

cmdlgjp.dll

comcat.dll

comct232.ocx

comctl32.ocx

comdlg32.ocx

ctl3d32.dll

dbgrdde.dll

dbgrdfr.dll

dbgrdjp.dll

dbgrid32.ocx

dblist32.ocx

dblstde.dll

dblstfr.dll

dblstjp.dll

dispex.dll

dtccm.dll

dtctrace.dll

dtcutil.dll

flxgdde.dll

flxgdfr.dll

flxgdjp.dll

hlink.dll

hlinkprx.dll

imagehlp.dll

implode.dll

inloader.dll

jscript.dll

jsde.dll

jsfr.dll

jsjp.dll

mfc42.dll

mfc42loc.dll

mscc2de.dll

mscc2fr.dll

mscc2jp.dll

mscmcde.dll

mscmcfr.dll

mscmcjp.dll

mscomct2.ocx

mscomctl.ocx

msdtcprx.dll

msflxgrd.ocx

mshfgde.dll

mshfgfr.dll

mshfgjp.dll

mshflxgd.ocx

msstdfmt.dll

msvbvm50.dll

msvbvm60.dll

msvcirt.dll

msvcp50.dll

msvcp60.dll

msvcrt.dll

msvcrt20.dll

msvcrt40.dll

oleaut32.dll

olepro32.dll

psapi.dll

rchtxde.dll

rchtxfr.dll

rchtxjp.dll

riched32.dll

richtx32.ocx

schannel.dll

scrrnde.dll

scrrnfr.dll

scrrnjp.dll

scrrun.dll

stdftde.dll

stdftfr.dll

stdftjp.dll

stdole2.tlb

tabctde.dll

tabctfr.dll

tabctjp.dll

tabctl32.ocx

tlbinf32.dll

urlmon.dll

vb5db.dll

vb6de.dll

vb6fr.dll

b6jp.dll

vbscript.dll

vbsde.dll

vbsfr.dll

bsjp.dll

wininet.dll

xolehlp.dll

  

 

In addition, a minimal number of files will remain under the directory <Install Path>\Rational\, where the default install path is C:\Program Files. Except for the RSSetup.logfile, you may manually delete these files if you wish to remove them from your system.

 

Known Install / Uninstall Issues

Defect

Description

142285

We recommend that you install Rose to a partition that has 8.3 format filename support. While it is possible to disable this, we recommend that you do not.

149717

With the integrated install, some shared components (both Rational and third party) are updated when you install any new Rational product.
The common install is designed so that when you install a new product (either within a Suite or as standalone) and the install detects other Rational products on the system, it will update some files for the other product as well (to keep the file levels compatible). For example, when you install ClearQuest, it may detect RequisitePro on the system and make some file updates BEYOND what are needed for ClearQuest.
This only affects users that have an older version of the suites already installed.

147294

On Japanese NT4SP3 typical install, several windows in Rose use a non-Japanese font to display text on a Japanese system. This means that non-ASCII characters are garbled.
The workaround is to change the font settings using Tools > Options > General > Fonts to the appropriate font for the language operating system.

148881

Uninstall suites 1.5 leaves numerous Java registry entries.

149343

Rose is left hung upon attaching a Rose model to a repository using Rational Administrator if a Rose session open during this operation.

149562

If you install a suites build over an uninstalled previous version, the install will not complete. It is also not possible to uninstall because Rose cannot be uninstalled from Add/Remove Programs. An error message appears saying that Rose is in the process of installing.
Workaround:

  1. In the registry, delete the following registry key:

HKEY_local_machine/software/rational software

  1. Install again.
  2. Get the RSSetup.exe off the CD; copy it into the target dir (rssetup dir) on your local machine manually.
  3. Restart the install.

149635

There is a Flex Lm Error with minimal install.
When Flex lm is installed on a server and the license file is entered, it appears in the License Administrator. When you bring up the Flex lm License Manager - License and select the Show License file, the License Manager states that the License File does not exist.
If you check the setup Imgrd.exe and License File, the paths appear but are not registered. If you browse to the same paths showing in these two files, select each file, and then press OK, the License works.

147119

Uninstall while Rose is running does not give error or warning.

147897

"Can't find entry point dll register server in schannel.dll" will appear in on Windows 2000 systems during Suite install. This does not effect the usage of the suite products on this platform.

148600

The License Key Administrator allows a client installation to install node-locked keys in server mode. When this happens, Rose can’t find the key and launch.
Workaround: Do not install node-locked keys in server mode or a floating key in a client mode.

 

Install Defects Fixed Since the Last Release

See the online help version of release notes for a list of Install defects fixed since the last release.

Licensing Information

There are two license types supported by Rose 2000:

For a full description of license types, installation and usage please consult the Installation Guide.

The software you receive includes a temporary startup license. You must install the software and follow the steps detailed in the Installation Guide to acquire a node-locked or floating license for your product. For users who are upgrading from Rose98i, you may use your existing license key to run Rose 2000.

Additional information on licensing can be found in the online help for the License Administrator application. This application is used to administer your product license files and to request a "permanent" license.

NOTE: You cannot request both a client license key and a server license key from the same system. You can request a node-locked license key from a client system and floating license keys from a server system.

Known Licensing Issues

Not Known to Work:

Not Supported:

Licensing Defects Fixed Since the Last Release

See the online help version of release notes for a list of Licensing defects fixed since the last release.

 

Rational Rose

Rational Rose, the world's leading visual modeling tool, allows you to define and communicate a software architecture, resulting in accelerated development, improved quality, and increased visibility and predictability.

The Rational Rose release notes describe new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Rational Rose 2000 release note information at the following locations:

You can find Rose Extensibility Interface (REI) release note information at the following location:

 

New Rational Rose Features and Enhancements

 

The following Rational Rose features are either new or have been enhanced. See the following sections for more feature information:

Rational Rose Tutorial

The Rose 2000 release contains a new Rose tutorial. The tutorial is distributed as a self-extracting archive file that is meant to be placed on the hard drive of the machine that Rose 2000 is installed on.

The filename is RoseTutorialFiles.exe and is located on the Rational Solutions for Windows Online Documentation CD in the \RationalRose\Tutorials\Rose2000 directory.

This file is approximately 4MB in size. When extracted, it requires approximately 28MB of free disk space. Refer to the Rational Rose 2000 Tutorial Read Me file located on the Start menu for more tutorial information.

The Rational Rose Classics Inc. tutorial:

Tutorial Notes:

Please keep in mind that the self-extracting file that contains the tutorial does not uninstall when you uninstall rose from your system. You must uninstall the tutorial files when you uninstall Rose.

For best viewing of the tutorial, set your display's Color Palette to True Color or the highest number of colors possible (click Start > Settings > Control Panel > Display > Settings).

New Format Menu

The new Format menu provides a common menu for performing activities such as editing model elements, changing the layout of the diagram, and changing the line style.

The commands that previously resided on the Edit > Diagram Object Properties menu are now located on the format menu. The stereotype display command now contains the Decoration option.

Printing Enhancements

Print Dialog Box

The previous version of Rose supported printing of diagrams and specifications through two separate dialog boxes. Printing options are now specified within one dialog box with separate tabs for diagrams, specifications, and layout.

Print Preview

Rational Rose contains a print preview feature that enables you to view a diagram as it appears in print.

Apply Filter Dialog Box

The Apply Filter dialog box enables you to search for diagrams and specifications within your model. The filter is especially useful when you print diagrams from large models.

New Toolbar Icons

New icons for the tool palette have been added. Also, the icons on toolbars in Rational Rose 2000 no longer look like three-dimensional tiles; they now appear flat. This change affects both the standard toolbar (default horizontal) and the tool palette (default vertical).

Rose Events

The addition of the following new events provides a tighter integration between Rose and Requisite Pro. This functionality will allow use cases to participate in the requirements management process. The events are documented in the online help.

The following additional events are now documented in the online help. You can look up the details of each prototyped event by event name or the "Events (COM)" index entries:

Additional Information:

Overview Window

The Overview Window is a navigational tool that helps you move to any location on all Rational Rose diagrams. When a diagram is larger than the viewable area within the diagram window, it is not possible to see the whole diagram without scrolling. The overview window provides a scaled-down view of the current diagram so you can see the entire diagram.

Stereotype Icons

Stereotype icons can appear as small "decoration" stereotype icons embedded in the standard UML symbol. You can turn this feature on or off by selecting or de-selecting Decoration located at the bottom of the Tools > Options > Diagram tab.

Memory Footprint Reduction

The current Rose product is capable of loading extremely large models. However, it requires immense amounts of memory to do so. The memory footprint reduction addresses these requirements and implements practical changes to Rose to substantially reduce the memory footprint of Rose models.

Stereotype decoration icons appear on printed diagrams.

 

Known Rational Rose Problems and Limitations

 

The following list contains the known problems and limitations of Rational Rose 2000:

Defect:

Description:

121877

OLE linking only pastes what is visible in the window.
To see the entire diagram in another application, choose View > Fit in Window in Rose before you copy and paste into the other application.

121919

Copy and Paste into PowerPoint with "visibility as icons" does not work correctly. If you encounter this problem, restart PowerPoint and copy/paste again with "visibility as icons" off.

133266

REI: RoseModel.FindItems() does not find attributes or operations.

133312

IME composition window is shown when type DBCS on label.
This is a problem in certain double-byte character sets, such as Korean. If you select a diagram element and begin to edit the label without selecting the label (by slowly double-clicking on the element), the first keystroke will remain invisible until you type another key or end the editing session by clicking outside the element. The data is not lost.

133370

Cannot run Rose after installing to root directory. Rose will not run if it is installed into a root directory. Work-around is to install into a subdirectory of the root.

133606

Drag and Drop of multiple selection from browser not supported.
The browser can be used to select multiple items, and the context menu can be used for that selection, but drag and drop of multiple items from the browser to a diagram is not supported.

134583

Korean character input; slow display for question marks.
If a class name contains a question mark (?), Rose takes longer than expected to display the class name. Turning autosize off will help alleviate the delay.

140938

24-bit stereotype bitmaps don't work in toolbars.
If you use non-standard colors in a 24-bit stereotype bitmap, the icon becomes distorted when you define a stereotype toolbar button or a list (browser) icon.

143292

Default font settings are currently stored with the model, and not with the. cat files.
Items will only store font settings in a .cat file if the font is different from the default. As a result, text for model elements in units will be formatted, by default, according to the settings of the model. If one team member formats diagrams relying on a specific default color and font, that formatting will not be rendered for other team members with different default settings.
To work around this problem, explicitly format text using a font that is different than the default setting.

143413

A general protection fault (GPF) appears when you drag a state that was located in a deleted swimlane on to an activity diagram.

143458

If you create two activities with a state transition between them and then change one activity to a state (using the Edit > Change Into command), the state transition will disappear.
Workaround: Select Query > Filter Relationship and the state transition will appear as it should.
If you create two states with a state transition between them and then change one state to an activity (using the Edit > Change Into command), the state transition will disappear.

143699

Opening a model from Explorer produces error message.
On slower machines, an error message may appear when opening a model by double clicking on the model file name in Windows Explorer if Rose has not yet been started. The error message indicates that the file or one of its components cannot be found, and appears while Rose is initializing. If you encounter this problem, simply dismiss the error message and double-click on the model file again, or simply open the model file from within. If your startup license is about to expire, the warning dialog will produce the same results here.

144271

All Rose scripts compiled prior to Rose 98I Service Pack 1 that reference state objects must be recompiled because of a change in the Rose hierarchy.

145281

If you start up Rose, the introductory splash screen takes over the entire screen and you cannot do anything else until Rose is loaded. A command line switch, - no SplashScreen, was added to allow disabling display of the splash screen.

144627

Minimal Install: Online Help has fewer items than Typical, Custom or Compact install.

145977

Minimal Install - can't find DDL1.SQL for DDL & Oracle.
When presented with the dialog that lists DDL1.SQL, select the Browse button and select a different location to which the file will be saved. Currently, the file DDL1.SQL is saved to the network drive, which is read-only. Make sure that the specified local or network location for DDL1.SQL is writeable.

146278

Object flows, signals not supported by activity diagrams
The following UML symbols are not supported in activity diagrams:

  • Objects
  • Signal sending
  • Signal receipt
  • Dashed arrow.

146336

Abnormal Exit Causes COM Error.

If Rose 98i SP1 exits abnormally (for example, due to a crash or when ended via the Task Manager), you may get a COM error when restarting. This problem will be cleared when the machine is rebooted.

146367

Shallow Deletion of States, Activities in Activity Diagrams.

If you use the DEL key to delete an activity or state from an activity diagram(referred to as a "shallow delete"), the activity or state is only deleted from the diagram, not from the model. As a result, if you perform a shallow delete on an activity or state that is connected to a synchronization, you may see an error message when you try to connect another state or activity to that synchronization.
The error message will indicate that "a synchronization may have one input and many outputs, or many inputs and one output." Because the state or activity that was shallow-deleted still exists in the model, the synchronization will not allow additional transitions.
To resolve the problem, select the synchronization in the diagram. Then, use the Query/Expand Selected Elements menu option to expand related items on the diagram. This will cause the state or activity that was shallow deleted to reappear on the diagram.
To completely delete the element, select it and press [CTRL+D]. You can now connect a new state or activity to the synchronization.

147348

The Tools menu has some shortcut keys for the Add-Ins that are not documented:

  • Ctrl-h Browse Header
  • Ctrl-k Browse Body
  • Ctrl-g Code generation/update

147454

If you change the font size (through Tools > Options > Diagram tab) of a model element that is already on a diagram, the model element may not correctly resize. This happens frequently on activity and sequence diagrams.
Workaround
You can clean up the diagram using the Edit > Refresh command.

147469

Scenario diagrams limited to 96 messages under Windows 98.
When Rose is running under Windows 98, scenario diagrams will not display more than 96 object messages. Setting the Tools >Options >Diagram >Focus of Control option to "off" works around this limitation. This is not a problem under Windows NT.

147910

In Windows 98, Rational Rose deletes association role names from the unidirectional association specification and the diagram.
This only occurs when exactly following this specific sequence:

  1. Start Rose (Exit and restart if you already have it open)
  2. Place 2 classes on the class diagram
  3. Connect them with a Unidirectional association
  4. Double click on the association
  5. Select the Role A General Tab
  6. Type in a name of A
  7. Select the Role B General Tab
  8. Type in a name of B
  9. Hit the Apply button
  10. Select the Role A Detail Tab
  11. Select a Cardinality of 0..1 and hit the Apply button.

Result: The Role names disappear from the dialog and the diagram.

148115

When you minimize the main class diagram window and then click the close button (X), Rational Rose reopens the screen instead of closing it.

148124

The name of an activity/state overlaps with the stereotype signature if you perform the following steps:

  1. From the browser create a State/Activity.
  2. Open the State/Activity's specification and enter a stereotype in the stereotype drop-down box;
  3. Drag the State/Activity from the browser onto an activity diagram.

Result: the name of the element and its stereotype are incorrectly displayed.

148125

Format > Autosize All does not work on activity diagrams.

148158

Drawing a state transition is blocked if you draw a state transition the wrong way (from activity to start state), click OK on the resulting warning dialog box, and then attempt to draw another state transition.
Workaround
Click the arrow button on the statechart diagram or activity diagram toolbar and then click the state transition icon. Continue to add state transitions toy our diagram.

148165

Choosing a pathname with foreign characters causes Rose to crash. The error occurs in the rscnpb22.dll (Page fault). This also happens in German Win95 (try using "ß" in the pathname) and in French & German Win98. It does not happen in French or German Windows NT.

148174

A business actor loses (changes) its fill color if it is moved around in the browser. For example, change the fill color of the business actor from yellow to green and then move the business actor to a different package.

148175

If text is entered into a text box that exceeds the dimensions of the textbox, the text will appear truncated at the bounds of the text box immediately after editing the text box is complete. Pressing F2 to refresh the diagram will redraw the text box correctly.

148316

Symbol names for path maps can consist of ASCII characters, provided that the first character is alphanumeric. Entering non-ASCII characters for a symbol name invokes an error message that indicates that only alphanumeric characters maybe used.

148471

The Help > About contact information is out of date. Support for Scandinavian customers can be found here.

148534

Rose scripts don't show up correctly on foreign language machines. In most of the windows, some sentences are cut off. Compared to other languages (EN, DE,FR), the font looked very large. On Win 95 FR, one line was cut off in the last window.

148554

If you delete a swimlane that contains a state or activity with nested elements in the browser, the state and activity with nested elements will be deleted also.
Workaround: relocate items to another swimlane before deleting the swimlane.

148624

The Reset button on the Customize Toolbar dialog box does not work. You can add a bunch of icons to the toolbar, but the reset button does not restore the default icons.

148685

It is possible to place two start states on a statechart diagram even though it is illegal by UML standards. The Query > Add Elements dialog box enables you to place multiple start states on a diagram.

148831

Rosescript: New keyword with RoseItem crashes Rose. RoseObject works properly.

148893

Online help book under "Rational Rose Extensibility Reference" that jumps to the new event topics is missing. You can find these topics through the index and indirectly through other contents books and pages.

148917

Cloning a parameterized class does not work as designed. The new clone will not be the same type, it will be of the type class.

148932

A class of one assigned language is assigned to a component of another assigned language. You will have two components with the same class. In one scenario, it is possible to have a VB and Java Component with the same VB class assigned(realized) to each other. Notice that once the package is unloaded from the model, the class will not show up as being realized by a component.

148939

Rose will generate an error in the log when opening a model that contains an activity diagram that contains a swimlane whose name matches that of the activity diagram.
Workaround: Avoid assigning activity diagrams and swimlanes with identical names.

148965

The online help topic named "Events Registry" contains CanDropFileOnItem and DropFileOnItem events.

148882

There is a problem when generating a SODA report in Rose - Word reports files that are damaged or missing. The following steps generate the error message in Enterprise Suite:

  1. Open ordersys.mdl in Rose.
  2. Select Report >SODA Report.
  3. Select 498 IRS and check the Generate Web Page checkbox.
  4. Select OK.

Word reports "The Windows registry has reported that one or more required files are damaged or missing. To correct the problem, run the Word Setup program."

148987

The REI online help lists an incorrect return type for the method: Class.GetInheritRelations. It should be InheritRelationCollection.

149007

If you undo a delete of a large number of classes the hourglass cursor will not appear and Rose may appear to be "hung" for a number of seconds. This can be a lengthy and computation-intensive operation; simply allow Rose to complete the Undo.

149036

There is a misbehavior that may be encountered in collaboration diagrams when following a specific set of steps. The misbehavior stems from relocating an endpoint of a link between two views of the same object to a different object.

  1. Create a collaboration diagram
  2. Place two objects on the diagram, name them both "aa"
  3. Create a third object and name it "bb"
  4. Drag a link from "aa" to "aa" and give the link a message named "123"
  5. Press F5 to open the corresponding sequence diagram, notice the message link"123" to self which is correct
  6. Close the sequence diagram and return to the collaboration diagram
  7. Drag the message link which goes from "aa" to "aa" to "aa" to "bb"
  8. Press F5 again to open sequence diagram - the incorrect message link representation of "123" should go from "aa" to "bb", instead it sort of goes from "aa" to "aa"

Workaround
Remove the link and recreate a new one between the desired objects.

149052

Help 129 context-sensitive error message appears when you F1 on the Printer, context-sensitive, and toolbox buttons for the new process elements. The RUP business icons also need context-sensitive help.

149052

Context sensitive help is not available for the following buttons:

  • Printer button
  • Context Sensitive Help button
  • All new toolbox buttons for the new 'Process' elements:
  • Rational Unified Process Stereotype Icons.

149053

If you change printers and then delete the original printer while Rose is running, Rose will crash when you select File > Print. If you do not delete the original printer, Rose will not crash. You can exit and restart Rose during the printer change without a crash.

149072

The Activity icon does not display the history graphical depiction on it. Further, it is not possible to drag the "History" icon from the browser to the diagram either.

149085

It is possible to load a controlled unit as read-only after it has been deleted from the model.

149092

Rose hangs when checking out a controlled unit named with a special character.

149093

Rose should report an error for an invalid package name. If you create a package, delete the default name, leave the name blank, and then control the package, the shortcut menu reload option is grayed out. If you unload the package, and then try to load the package, the shortcut menu load option is grayed out. You can load the package by double clicking on it.

149095

The mouse (pointer) disappears when the "hide pointer while typing" option is set using an intelipoint mouse. The pointer hides but will not reappear unless user puts focus outside of Rose. Then it will reappear.

149243

A Booch Error Message appears when synchronizer is selected via Tools >Synchronizer where there is no model opened. If you have a model open, selecting Tools >Synchronizer opens the Synchronizer dialog box.

149247

A statechart diagram disappears after reloading the model when you perform the following steps:

  1. Create a statechart diagram.
  2. Add some states to it.
  3. Add an activity diagram to the same statemachine as the statechart diagram.
  4. Name the activity diagram the same as the statechart diagram.
  5. Add some activities and swimlanes to the activity diagram.
  6. Save the model.
  7. Reload the model.

Notice that the model no longer has the statechart diagram and the activity diagram has the items from the statechart diagram on it.

149255

The elements on an activity diagram may appear "rearranged" after you save and then reopen the Rose model.
Synchronizations have been designed to have the transitions come into them from on one side, and then exit on the other side. For Horizontal synchronizations, they are designed to have transitions enter on top and exit on the bottom. If you draw them the other way, the next time you load the model Rose will "rearrange" them for you.

149257

The use case view package allows you to deletion of the Top level Diagram if you perform the following steps:

  1. Open Use case view package specification > Detail tab.
  2. Right mouse click on the Main diagram > Delete.

Notice that the Main diagram disappears from the model. An error message should appear that says "Can't delete Top level Diagram."

149270

REI: Rose crashes after Removing class name with RemoveNoteView (Diagram class).

149271

To close the print preview window, use the "close" button. Do NOT attempt to close Rose using the following steps because Rose will crash:

  1. File -> Print -> Print Preview.
  2. Click the small, Rose icon in the upper-left hand corner of the Print Preview window.
  3. Select Close.

149303, 149525

Rational Administrator can't re-attach a rose model to the repository. The following error message is received: "Rose model is already attached to this repository.

149337

A machine running Rose may not be able to read a model created on another machine with a different operating system language version.

149355

On Sequence diagrams, messages do not show up after a paste. The diagram is updated properly when one of the objects is relocated.

149339

Rose crashes while dealing with an association class that is also the supplier class.

149368

Copying and pasting elements on a nested activity diagram causes an Application Error.

149103, 148192

If you select the class icon from the toolbox and select the Add-In menu, a textbox appears on the diagram when you place the pointer on the diagram. It should place a class.

149395

Deleting a swimlane results in different behaviors depending on how the delete is initiated and what views are present on diagrams.

149420

The Logical View package->New does not provide the ability to add use cases. However, a use case can be added in the Use Case View and dragged to the Logical View. Likewise, a class cannot be directly added to Use Case View packages but it can be dragged from the Logical View. If the drag and drop operations are allowed, the New menu selections should be added.

149462

ATL bug prevents Rose DLLs from registering.

149668

Rose crashes after naming objects in a sequence diagram. The crash happens only if you leave the log window in the background.

REI Online Help

Online help topic, Events Registry, erroneously contains unsupported events (CanDropFileOnItem, DropFileOnItem) in the sample registry graphic.

.ebx

Recompile compiled scripts (.ebx) before running them.

Rational Rose Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Rose defects fixed since the last version.

Rose Extensibility Interface (REI) Release Notes

The following classes, properties, and methods are documented in the online help. You can look up the new help topics by keyword (Class name, Method name, Property Name) or through the contents tab.

Application Class

Property

IsInitialized : Boolean

ClassView Class

Methods

GetDisplayedAttributes ( ) : AttributeCollection

GetDisplayedOperations ( ) : OperationCollection

ConnectionRelation Class (New)

Properties

Characteristics : String

SupplierIsDevice : Boolean

ConnectionRelationCollection Class (New)

Device Class

Property

Connections : ConnectionRelationCollection

Diagram Class

Method

GetParentContext ( ) : RoseItem

Element Class

Methods

GetIconIndex ( ) : Integer

RenderIconToClipboard ( ) : Boolean

ExternalDocument Class

Properties

ParentDiagram : Diagram

ParentItem : RoseItem

Methods

GetIconIndex ( ) : Integer

RenderIconToClipboard ( ) : Boolean

Message Class

Method

GetSequenceInformation ( ) : String

Model Class

Method

FindDiagramWithID (strUniqueID : String) : Diagram

NoteView Class

Methods

AddAttachmentToView (objRoseItemView : RoseItemView, strLabelText : String) :RoseItemView

GetDiagramLink ( ) : Diagram

Processor Class

Property

Connections : ConnectionRelationCollection

StateVertex Class

Method

AddTransitionToVertex (strOnEvent : String, objTarget : StateVertex) :Transition

Transition Class

Methods

GetSourceStateVertex ( ) : StateVertex

GetTargetStateVertex ( ) : StateVertex

C++ Add-In

Using the Rational Rose C++ Add-In, you can produce C++ source code from the information contained in a Rational Rose model. The code generated for each selected model component is a function of that component’s specification and code generation properties, and the project’s properties. These properties provide the language-specific information required mapping your model onto C++, and allow you to control the code generated for each component.

You can find C++ Add-In release note information in the following locations:

Upgrading from a Previous C++ Add-In Release

The Rose 2000 C++ Add-In release contains two major changes in the Code Generator that you should understand when upgrading:

The following new code generator properties have been introduced. However, they are not present in the Rose 2000 C++ Add-In documentation:

C++ Code Generator Versioning

The C++ code generator uses annotations (protected regions) in the code in order to support non-destructive code regeneration (code updating). The C++ Analyzer takes advantage of the annotations as well.

As the code generator advances using code generators of different versions, the same code base becomes problematic. This is the case when the annotations format changes. A code generator versioning stamp and a surrounding mechanism has been introduced to address this problem.

A particular code generator will produce a version stamp that characterizes the annotations format used and the version of the code generator relative to this annotation format. They are called annotation version and minor version. The version stamp itself has the form of a protected/preserved region. It is not meant to be modified or deleted by the user in any way because it is used differently than other preserved regions. Text added in the region will not be maintained. In addition, the preserve tag must not be set to false.

A particular code generator version will only write the newest version of annotations. However, it can read and interpret older versions of the prior annotation version. How far the backward compatibility goes depends on the kind of change introduced. The code generator will issue a warning message when an annotation upgrade occurs. Refer to the C++ Annotation Upgrade topic to read more about the implications of upgrading the annotation format. Upgrading to a higher minor version is the recommended path and does not cause any problem because it does not require any transformations. The annotation format has not changed.

Downgrading code, which is updating code produced by a higher version code generator, is a risk. The exact risk depends on the usage of newer code generator features and how models that produce the code are going to be shared. In order to allow the user to decide what downgrading risk to engage, two Boolean project properties AllowGenerateOverNewerAnnotations and AllowGenerateOverNewerVersion have been introduced. The default property sets assumes that no risk should be taken. They are both set to false. If the property does not allow overwriting newer code, the code generation displays an error message and skips the module. Otherwise, it will issue a warning and continue.

There are some additional considerations when using an older code generator that is not aware of version stamps. The first version of the version stamp aware code generator is version 1.1. If it does not find a version stamp, it will assume that the file had been written by an older code generator. The behavior is as if found a stamp denoting version 0.0. The C++ version comment orphaned topic contains more information about the effects when using a version 0.0 code generator on newer version stamped code.

C++ Version Comment Orphaned

If you are using an older, version stamp unaware code generator to update version stamped code (C++ code generator versioning) the version stamp comment will end up in the orphaned section at the end of the module. This raises the same issues as described in the C++ annotation downgrade topic. The recommended action is to use the newer code generator.

It is likely that other preserved regions will also end up in the orphaned section. If you decide to undo this operation, you will have to manually revive the written backup files.

C++ Annotation Upgrade

A major annotation upgrade happens when code is updated that had been written with an older code generator that supports an older annotations format.

An annotation upgrade is introduced to put more information in the code in order to find preserved regions properly in complex situations. For example, support for recognizing the preserved regions for property generated operations(such as assignment operators) copy constructor when the class name changes.

Changing the annotation format has disadvantages, which is the reason why they occur only after careful consideration of alternatives. One disadvantage is that upgrading to a new format can create problems if the upgrade occurs at the wrong time. Whether this is true or not depends on the particular format change introduced. In addition, upgrading is in general restricted to a particular number of versions.

A particular code generator will support upgrading from the next lower annotation version under stable conditions. Stable conditions means that the upgrade should occur on code that has been successfully updated using the code generator from which to upgrade. If the current code does not fit the model, upgrading and synchronizing at the same time may fail. The steps to assure stable conditions are:

  1. Update the code with the code generator version you want to update from.
  2. Do not change the code and the model.
  3. Update the code with the target code generator version.

C++ Annotation Downgrade

A major annotation downgrade occurs when you update code that had been written with a newer code generator supporting a newer annotation format.

Refer to the C++ annotation upgrade topic for reasons why the annotations format may change. It must be expected that the older code generator may not be able to recognize the code regions with the newer annotation. It is particularly problematic to share code using code generators, which support different annotation versions. The exact risk depends on the usage of newer code generator features and how models and especially the produced code are going to be shared.

Downgrading annotations is neither recommended nor automatically supported. You may have to do manual work.

However, you may have valid reasons to dismiss all these considerations. Setting the Boolean project property AllowGenerateOverNewerAnnotations to True will allow you to perform the downgrade. The code generator will still insist to issue a warning though.

The default setting is false, which makes the code generator to issue an error and to skip this module.

C++ Minor Version Downgrade

A minor version downgrade occurs when you update code that had been written with a newer code generator, which supports the same annotation format.

Minor downgrades may introduce problem if your current model/code depends on capabilities that have been introduced in the newer code generator. Note that minor upgrading will remedy those problems. Therefore minor downgrades will not raise problems which may require manual work. However, you should allow the downgrade only if you are sufficiently certain that you are not causing problems.

The capability to honor a minor version attempt can be controlled in the same way as the annotation version downgrade. So even though minor downgrading is far more reasonable, the behavior regarding error/warning messages and default setting is the same. Setting the Boolean project property AllowGenerateOverNewerVersion to True will allow you to perform the downgrade. The code generator will still issue a warning in order to make you aware of the potentially unintended downgrade.

The default setting is false which makes the code generator issue an error and skip this module.

AllowGenerateOverNewerVersion (Project Property) - C++

The Boolean AllowGenerateOverNewerVersion property enables you to allow the code generator to update code that has been generated by a newer Code Generator version. The difference to the property AllowGenerateOverNewerAnnotations is that both code generators use the same Annotation Format. They only differ in that the present code may have been generated by a newer Code Generator. This may cause problems if the code depends on new Code Generator features.

Refer to the C++-Minor Version Downgrade topic to learn more about this operation.

Note: This property is not documented in the Rose 2000 C++ Add-In documentation.

The following table summarizes the possible values for AllowGenerateOverNewerVersion:

If you enter:

The action is:

True

The C++ Code Generator allows you to update code that has been generated by a newer version with the same Annotation Format. A warning will still be issued in order to notify you of this unintended operation.

False

(Default) The C++ Code Generator will issue an error when it encounters code generated by a newer Code Generator. The file will be skipped.

 

AllowGenerateOverNewerAnnotations (Project Property) - C++

The Boolean AllowGenerateOverNewerAnnotations property allows you to force the code generator to update code generated by a newer Annotation Format.

This is a risky operation and should only be considered after taking safeguards such as backing up sources. Refer to the C++-Annotation Downgrade topic to learn more about this operation.

Note: This property is not documented in the Rose 2000 C++ Add-In documentation.

The following table summarizes the possible values for AllowGenerateOverNewerAnnotations:

If you enter:

The action is:

True

The C++ Code Generator allows you to update code that has been generated by aversion using a newer Annotation Format. A warning will still be issued in the Log Window.

False

(Default) The C++ Code Generator will issue an error when it encounters code with a newer Annotation Format. The file will be skipped.

 

GenerateAbstractBody (Operation Property) - C++

The Boolean GenerateAbstractBody property specifies whether or not a member function definition is generated for operation with the OperationKind property set to Abstract.

Note: The GenerateAbstractBody property is not documented in the Rose 2000 C++ Add-In documentation.

The following table summarizes the possible values for GenerateAbstractBody:

If you enter:

The action is:

True

A member function definition is generated. Note that the C++ language allows to define and use member functions even for pure virtuals (abstract) member functions.

False

(Default) Only a member function declaration is generated. This is what most users expect when they set the Operation Kind to Abstract.

Note: You cannot define that a member function definition is generated for automatically generated operators such as assignment operators and the like. You must model these operations explicitly if you need to have a member function definition generated.

Note: An earlier version of Rose always generated member function definitions for abstract operations. If you depended on this feature, it is suggested that you change the value in the default property set to true.

 

Known C++ Add-In Problems and Limitations

Defect:

Description:

126216

The Analyzer does not handle most template specializations. How they should map to a UML model has not been determined. They should be put in protected regions by Action:CodeCycle, but they are not.

126217

Argument, parameter, and result type specifications are textual even when they are references to elements in the model. This gives you the impression that they will change as you change the elements referenced (like other fields in the model). Because they are just text, they do not.

145958

After a round-trip engineering update the font in Rose is changed from whatever it was to 9 pt.

146046

Nested Foo is incorrectly qualified.

147019

AHIR gives duplicate includes in .cpp file.

148508

Browse source/body in C and Java. Browse Header and Body of C and Browse java Source of Java did not invoke editor, thus, did not show the code.

C++ Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of C++ defects fixed since the last release.

Visual C++ Add-In

The Rational Rose Visual C++ Add-In provides the interface between the Rational Rose modeling environment and Microsoft Visual C++. The main features of Rational Rose Visual C++ include:

You can find Rational Rose 2000 Visual C++ Add-In release note information at the following locations:

New Visual C++ Add-In Features and Enhancements

Upgrading from a Previous Visual C++ Add-In Release

The Rose 2000 Visual C++ Add-In is backward compatible with previous versions of the add-in. Models created with the beta version of Rose 2000 may exhibit some incompatibilities with the released version of the Visual C++ Add-In.

The model formats used by the Visual C++ and Classic C++ Add-Ins are not interchangeable. If you want to use the Visual C++ Add-In on models created for use with the Classic C++ Add-In, a model conversion utility is provided as a 98idownload on the Rose Product Support page located atwww.rational.com/rose/support.

Known Visual C++ Add-In Problems and Limitations

Defect:

Description:

143162

Code Update
Code update for large models or large Visual C++ projects can take a long time and use a lot of memory. To prevent out of memory crashes, use the Window or Windows NT control panel to increase the size of your virtual memory.

143670

Code Update / Model Assistant
Extra message map entry may be added to implementation file. If an implementation file (.cpp file) is referenced by a project, but not part of that project, when Rose VC++ generates the implementation code, an extra message map entry is added to the file.
Workaround is to open the class in the Model Assistant; go to the "MFC" tab; uncheck the box labeled "Generate Message Map".

144363

Code Update / Model Update
Attempting to RTE a project when the Visual C++ IDE is blocked waiting for the user to close a modal dialog can cause failures in the Visual C++ IDE. Always make sure that you unblock the Visual C++ IDE before running Model Update or Code Update.

144897

Code Update / Model Update
Methods with arguments of the form: method (void f(Graph&, arc, void*), void*client_data) can not be generated. Other constructs not supported:

  • Methods that return pointers to functions.
  • Typedef statements,
  • Nested classes.
  • C++ preprocessor macros.

144961

Code Update / Model Update
Inheritance from a parameterized class is not supported.

145021

Model Update
You must run Rational Rose once after installation while Visual Studio is inactive in order to activate the Visual Studio Add-in supplied by Rational.

145395

Code Update / Model Update
On Win98, if you start Visual Studio by double-clicking on a .dsp file, Code/Model Update may not work.
Workaround is to always double-click the .dsw file or open the project using Visual Studio’s File/Open command.

147367

Code Update
Window hangs during Roundtrip Engineering without reload of the modified files(NT). Build 6.5.9173.

148560

Rose crashed when you click New Model Conp

148808

Rose 2000 reverse engineering does not handle certain macros.

148838

Model Update
When Model Update Tool creates an Overview Diagram, associations are not added to the diagram. The overview Diagram shows the classes assigned to the component and their immediate superclasses. User modifications to the Overview Diagram will be preserved across subsequent Model Updates. If you want to view the association, use the Query > Expand feature.

148888, 149026

Reverse-engineering an ATL component that implements custom interfaces generates bad code on forward engineering.

148907

Code Update ATL/MIDL
In some cases, extra IDR_XXX resource ID’s and .rgs files are generated. They cause no compilation/link errors.

148908

Code Update ATL/MIDL
MIDL code generation does not support forward references.
Workaround is to enter forward references manually.

148997

Code Update ATL/MIDL
"default value" on a method parameters in an interface class is not generated into the MIDL source file.
Workaround is to manually enter default values.

149027

Code Update ATL/MIDL
Reverse engineering a component that has a dependency on an outside type library. The type library importer fails to show methods that exist on the imported interfaces. This causes problems if you later code-gen because we do not inject the function prototypes.

149064

Code Update ATL/MIDL
If a VC Add-In project name is different than a component name, problems occur on forward engineering.

149112

Code Update / Model Update
Rose 2000 does not reverse engineer optional template parameters.

149317

Model Update ATL/MIDL
There are some defects in the Microsoft-supplied ITypeInfo interface that cause fidelity problems in MIDL. For example, if you MIDL source references the data type "BOOL" and you run Model Update, it will appear in the model as "long". If you then run Code Update, it changes to "long" in the MIDL source and you will get a compilation error. The work around is to use the type VARIANT_BOOL in your MIDL source. Another alternative is to go to the Operation specification for the interface class and set the "Generate" model property on the "COM" language tab to "False".

Visual C++ Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Visual C++ defects fixed since the last release.

Rose J Add-In

The Rose J Add-In supports true round-trip engineering and has support for large frameworks. The Rose J release notes describe new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Rose J release note information at the following locations:

New Rose J Add-In Features and Enhancements

Flexible Comment Generation

There are now a number of options that enable you to specify (at the project level) how you would like to generate element comments. The options include:

Automatic Java Doc tag generation: If you select the Java Doc style of comment generation, you have the option of having rose automatically generate Java Doc tags based on model relationships and property settings.

Round-trip engineering of *.java classes from cabs, jars and zips are now supported.

Known Rose J Add-In Problems and Limitations

Defect:

Description:

Rose J Documentation

The Rose J documentation (online help and Using Rose J) states that Rose uses the same algorithm to determine the classpath that the JDK uses and that if the JDK does not require a classpath setting, then Rose J also will not require the setting. This is not true in this release. You must create a classpath entry for all JDK class libraries in the Rose J project specification or Rose J will not be able to resolve references to those libraries.

Rose J Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Rose J defects fixed since the last release.

Visual Basic Add-In

The Visual Basic Language Support Add-In enables Rational Rose to model, generate, and reverse engineer code for applications written in Microsoft Visual Basic. The Visual Basic Language Support Add-In tools in Rose are tightly integrated with the Microsoft Visual Basic environment, allowing you to seamlessly progress through the round-trip engineering process.

The Visual Basic Add-In release note describes new features and enhancements, known problems and limitations, and fixed defects since the last release.

The Visual Basic Add-In tools are:

You can find Visual Basic Add-In release note information in the following locations:

New Visual Basic Add-In Features and Enhancements

Imported project references

The Rose Visual Basic Add-In uses the new Type Library Importer Add-In when importing project references during reverse engineering of a Visual Basic project. This means that the entire type library of a referenced component is imported—including interfaces, dispinterfaces, coclasses, enums, structs, unions, and modules—whereas the previous version of the Type Library Importer imported a simplified view of the type library.

The new Type Library Importer allows you to show how classes in the model use and depend upon classes in other components regardless of their implementation language. However, some of the imported type library items are not needed in Visual Basic. For example, the Object Browser in Visual Basic does not list the default interfaces of the co classes because Visual Basic assumes the default interface when referring to a coclass. Just as the Object Browser hides some type library items you can hide the same items in the imported type library. To do that, click Tools > COM > Properties dialog box in Rational Rose before importing a type library, and clear the Show hidden items option. All hidden type library items will be inserted into a separate package. Also, the hidden items will not be displayed on the type library’s overview diagram.

Also, a new menu item, Tools > Visual Basic > Add Reference has been added, which allows you to import the type library of a COM component into the model. If a Visual Basic component is selected when performing this command, Rose adds a dependency relationship between the selected Visual Basic component and the imported COM component.

Refreshing default bodies

The Model Assistant provides a mechanism for refreshing the default body of methods. When you click the refresh button— —above the Default Body box on the Method tab, the Model Assistant overwrites the default body of that method with the default body defined by the current class template.

Upgrading from a Previous Visual Basic Add-In Release

Models and Visual Basic code created and generated in Rose98i or Rose 98iService Pack 1 are compatible with Rose 2000—i.e. the Visual Basic classes in Rose 98i models and the corresponding Visual Basic projects do not need to be upgraded for Rose 2000. However, any type libraries (project references) that have been imported using the Type Library Importer in Rose 98, Rose 98i, or Rose 98i Service Pack 1 must be upgraded.

To upgrade a previously imported referenced component, delete the corresponding type library from the model—both from the logical view and from the component view. Import the type library of the component again by reverse engineering the Visual Basic project that is referring to it.

Known Visual Basic Add-In Problems and Limitations

Defect:

Description:

Problem:

Rose Visual Basic does not work properly if Microsoft Visual Modeler is installed on the same computer.
Solution: Before installing Rose Visual Basic 2000 you must uninstall Microsoft Visual Modeler.

Problem:

The shortcut keys in the Visual Basic IDE are sometimes disabled when the Rose Tool Window in Visual Basic is opened.

Solution: Switch applications back and forth in the taskbar, or open and then close any dialog box in Visual Basic.

146221

Problems may occur when reverse engineering a Visual Basic project that is being debugged in Visual Basic at the same time.
Solution: Stop the debugging before using the Model Update Tool Problem.

146276

Rose Visual Basic cannot handle code lines that are longer than 1023characters in the General Declarations section of a project item.

Solution: Make sure that the length of each declaration (including the code following any line-continuation characters) is less than 1024 characters.

149099

Model Assistant requires VB5 or VB6 to be installed.
Possible workaround if you do not intend to install VB5 or VB6:
Create the following registry key:
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Visual Basic\5.0"
and the string value:
"InstallDir" = "c:\"

Visual Basic Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Visual Basic defects fixed since the last release.

Oracle8 Add-In

Rational Rose Oracle8 enables you to create object models from Oracle8relational schemas and extend them to exploit Oracle8’s object capabilities.

Rational Rose Oracle8 visualizes existing relational databases and facilitates the discovery and composition of existing business objects. This enables you to preserve your investment in existing relational databases while taking advantage of all the benefits that object modeling and development bring to desktop and server applications.

The Oracle8 Add-In release note describes known problems and limitations and fixed defects since the last release. The Rational Rose 2000 Oracle8 Add-In only includes defect fixes. It does not include any new features.

You can find Rational Rose Oracle8 release note information at the following locations:

Known Oracle8 Add-In Problems and Limitations

Defect:

Description:

128252

The Wizard and Syntax Checker permit entries that create invalid column name in Oracle. DDL Execution Error - Syntax Checker does not catch this and the Wizard permits it. Error - ORA-00904: invalid column name.

Oracle8 Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Oracle8 defects fixed since the last release.

Web Publisher Add-In

The Rational Rose Web Publisher Add-In allows you to publish Rational Rose models in html. The Web Publisher Add-In exports your Rose model to HTML(including diagrams) so you can view them using a standard browser such as Microsoft Internet Explorer or Netscape Communicator. The Web Publisher also produces metatags for use by search engines.

The Web Publisher Add-In release notes describe new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Web Publisher Add-In release note information at the following locations:

New Web Publisher Add-In Features and Enhancements

The following list contains enhancements to the Rational Rose Web Publisher Add-In for the Rational Rose 2000 release:

Known Web Publisher Add-In Problems and Limitations

Defect:

Description:

148477

An error message appears when you try to publish a model using Netscape 4.6.The error message appears as: ""Netscape is unable to find the file or directory named c:/test/contents.html;c/test/webviewer/intro.html"

149219

Web Publisher keeps two Internet Explorer windows open.

Web Publisher Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Web Publisher defects fixed since the last release.

 

Microsoft Repository Add-In

Microsoft Repository Add-In (Overview)

Rational Rose allows you to exchange model information with other modeling tools by providing an integration with the Microsoft Repository and Visual Component Manager (VCM) – the Repository Add-In.

The Microsoft Repository Add-In release notes describe known problems and limitations and defects fixed since the last release.

You can find Microsoft Repository Add-In release note information at the following locations:

Known Microsoft Repository Add-In Problems and Limitations

Defect:

Description:

145627

When you do an "Export to repository" on a model containing relationships, then open a new model and do an "Import from repository", some of the relationships and their related information (e.g., stereotypes, multiplicity, role names, etc.) are lost. Generalizations, realizes and dependency relationships remain unsupported specifically.

145975

Republishing model to VCM ruins ability to double-click model to import to Rose.

Microsoft Repository Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Model Integrator defects fixed since the last release.

 

Version Control Add-In

The Version Control Add-In, formerly known as the Source Code Control Add-In, provides integration between Rational Rose and any SCC-compliant version control system. It makes the most frequently used version control commands accessible directly from the Tools menu and from shortcut menus in Rose.

The Version Control Add-In release notes describe new features and enhancements, upgrading information, known problems and limitations, and fixed defects since the last release.

New Version Control Add-In Features and Enhancements

The Version Control Add-In, formerly known as the Source Code Control (SCC)Add-In, has been updated to allow you to version control your Rose models in aversion control tool like Clear Case or Visual SourceSafe (VSS).

The list below contains changes to the Version Control Add-In:

Upgrading from the Visual SourceSafe Add-In

The specific Visual SourceSafe (VSS) integration available in Rose 98i has been incorporated into the Version Control Add-In which now handles a super set of the VSS specific features. To upgrade a model that has been put under version control through the VSS Add-In, use the following steps:

  1. Make sure that the model is not opened in Rational Rose.
  2. In Microsoft Visual SourceSafe, check out all the controlled units that belong to the model.

Note: This cannot be done through the Version Control add-in because the add-in does not know the model is under version control.

  1. In Rational Rose, open the model.
  2. For each set of units that are located in the same SourceSafe project:

A. Click Add to Version Control on the Tools menu's Version Control menu.

B. Select the units.

C. Click the Browse button and search for the project that corresponds to the working folder where the unit files are located.

D. Clear the Keep Checked Out option (if you want to check in the units again).

E. Click OK.

As the model is already under version control, the Version Control Add-In only updates the controlled units with additional version control information. From now on you can use the Version Control commands to check out and check in the units.

Known Version Control Add-In Problems and Limitations

Defect:

Description:

148511

When attempting to remove from Version Control, if the parent of a unit is write protected, the unit will be removed from the SCC provider, but will not be uncontrolled. The user will get a message stating the parent is read only. If the user wishes to then uncontrol it, they should write enable the parent and use the Units\Uncontrol menu item.

149380

The "Get Latest" menu option for the source control add-in may not work correctly with Visual Source Safe. This has been identified as a problem when working with nested units.
Workaround:
When you are ready to do a "Get Latest," bring up the VSS explorer through Tools > Version Control > Start Version Control Explorer and then select the appropriate files. Next, select "Get Latest" from within the VSS Explorer to actually obtain the latest version of the files into your working folder.

Version Control Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Version Control defects fixed since the last release.

 

Model Integrator Add-In

The Rose Model Integrator Add-In lets you compare model elements from up to seven contributor files, discover their differences, and merge them into the base model.

The Model Integrator Add-In release notes describe new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Model Integrator Add-In release note information at the following locations:

New Model Integrator Add-In Features and Enhancements

View Mode

Model Integrator now supports a view mode for viewing the contents of a single model file. To use this mode, select a single file in the Contributors dialog and press the button labeled View.

Note: If two files are displayed, or if you have begun to enter a second filename, the button text will change from View to Compare. When the button displays Compare but you have only entered a single file name, pressing the Compare button will still enter view mode.

Drag and Drop

With this release, Model Integrator supports drag and drop of contributor filenames from Windows Explorer. When you first drop files onto the Model Integrator window, the Contributors dialog will be opened and the dropped files added to the list of contributors. While the Contributors dialog is open, you can drag and drop additional files onto the dialog box up to the limit of seven contributors. You must drop them onto the dialog box when it is open, not on the main Model Integrator window.

Note: When you drop a group of file names onto Model Integrator at the same time, the order in which they appear in the Contributors dialog is not necessarily the order in which they appeared in the Explorer window or the order in which you selected the files. Make sure that you have selected the correct file for your base contributor, which must be the first file name listed in the Contributors dialog. You can use the arrow keys at the top right corner of the Contributors dialog to change the ordering of files in the list box.

Check Merge

This version of Model Integrator includes a new feature on the Merge menu called Check Merge. This menu item checks the merge output file for internal consistency. Check Merge scans the model and if it finds a problem it will display dialog box showing you the error and allowing you to repair it. See the Model Integrator online help for more information. The Check Merge function is run on the merged model automatically before it is saved, and if problems are detected, Model Integrator will not let you save the merged model.

Command Line Parameters

With this release Model Integrator supports a simplified command line interface. This discussion assumes that the Rose bin subdirectory is on your path.

modelint file.mdl

brings up Model Integrator with file.mdl in the View mode.

modelint file1.mdl file2.mdl

brings up Model Integrator in Compare mode for the two files.

modelint file1.mdl file2.mdl file3.mdl

brings up Model Integrator in Merge mode with the first file named on the command line selected as the base contributor.

Additionally the following command line options can be used. You can use either the slash character (/) or the minus sign (-) to begin each option:

/xcompare

Starts Model Integrator in Compare mode for the files named on the command line. This is the default mode for two files, but must be specified when comparing more than two files.

/xmerge

Starts Model Integrator in Merge mode for the files named on the command line. This is the default mode for three or more files.

/compare

Starts Model Integrator in Compare mode but does not display the results in graphical mode. This mode performs the compare operation and then exits to the operating system with an exit code indicating the result of the compare operation: 0 for identical models or 1 for models with differences.

/merge

Starts Model Integrator in Merge mode but does not display the results in graphical mode. If the merge algorithm detects conflicts, the merge is aborted and the program returns an exit code of 1. If the merge can be completed without conflicts, the merged file is written to disk to the file named by the /out parameter. If no /out parameter is specified, the Save dialog will be displayed. The Subunits dialog will also be displayed unless a subunit policy choice is made.

/out filename

Specifies the name of the file to write the merged output file to. You must specify an
absolute or relative pathname for the file. Either of the following are valid:
/out c:\models\test.mdl
/out .\test.mdl
but this is not valid: /out test.mdl

/all
/none
/ask

Subunit policy options. The /ask option is the default in the graphical mode of Model Integrator. By default when reading and writing models, Model Integrator will display a subunit dialog that allows you to specify whether they want to load/save subunits. The /all option will load/save all the subunits without prompting the user with subunit dialogs. The /none option will suppress the loading/saving of subunits.

Known Model Integrator Add-In Problems and Limitations

Defect:

Description:

Online Help

The online help states that you can use Model Integrator to compare and merge any combination of model files (.mdl) and subunit files ( .cat, .sub, .pty,.prc, .prp). This is inaccurate. You can compare and merge any of the listed file types, but you can only do so with the same file types. For example, you can compare several .cat files or several .sub files, but you cannot compare .cat files with .sub files.

147403

If you use Model Integrator with Clear Case, you must be running Clear Case3.2.1 patch 10 or later.

146825

Merging models with state/activity diagrams where the start state has been changed can cause Model Integrator to create diagrams with more than one start state. The workaround is to change the start state names to be the same in Rose before merging the files.

146900

Merging models where one of the models deletes model elements can leave dangling references to the deleted elements elsewhere in the merged model file. The Check Merge function will detect most dangling references caused by deleted model elements and notify the user. However, with this release there are still some references that are not checked and which can therefore remain in the model. There is no workaround for this problem; however, the problem can be mitigated for models with subunits by always loading all subunits in the merge.

146922

Merging models in which model elements have been deleted can create dangling references to the deleted elements in the merged model. Check Merge may catch these references and prompt the user to restore the deleted model element by choosing a different contributor to resolve the conflict. However, if there is no conflict to resolve because the merge is trivial, then Model Integrator will not display the deleted model element and the user will not be able to restore it. This can result in a merged model file which cannot be corrected from within Model Integrator, but which Model Integrator will not let you save because it has errors. The workaround for this is to delete the model elements in all contributors in Rose and then merge the models.

Model Integrator Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Model Integrator defects fixed since the last release.

 

Clear Case Add-In

The Clear Case Add-In is a new add-in which provides a tight integration between Rational Rose and the Rational Clear Case version control system. This add-in is intended as a replacement for the Clear Case capabilities provided through the generic Version Control Add-In. Unlike the Version Control Add-In, the Clear Case Add-In does not use the Microsoft SCC API to communicate with Clear Case. This has and will continue to allow Rational to provide more Clear Case specific customization to this add-in.

If you are already familiar with the Version Control Add-In, you should find the transition to the Clear Case Add-In simple because the majority of the dialogs and menu items are identical.

The Clear Case Add-In release notes describe new features and enhancements, known problems and limitations, and fixed defects since the last release:

New Clear Case Add-In Features and Enhancements

In addition to the commands and features provided in the generic Version Control Add-In, the Clear Case Add-In provides:

Known Clear Case Add-In Problems and Limitations

Defect:

Description:

148766

Performing an undo checkout on a parent unit will cause the children to become unloaded. It will be necessary to reload the child units manually if desired.
You should not select both a parent and child unit when using the undo checkout command as this will cause unexpected behavior when reloading the units. If this operation is performed inadvertently, you should reload the model and subunits afterward. It is recommended that you not use multi-selection with the undo checkout command.

148951

Rose adds a model to version control without any error messages indicating that the model is write protected.

148953

Rose adds a package to Version Control despite of error message indicating that the .cat file is write protected.

  1. Create a Vob & View.
  2. Add model directory to Clear Case.
  3. Create a package.
  4. Control the package.
  5. Write-protect the package.
  6. Add to version control.
  7. Error message "File .cat is write protected by the operating system", click OK.
  8. Rose adds a package to Version Control despite of error message indicating that the .cat file is write protected.

If you skip step 5, the problem is eliminated.

149246

At present, the Clear Case Add-In does not fully support snapshot views. If you are using snapshot views, you may experience problems with the browser icons not being updated to reflect the current CM state. You can correct this problem by unloading and reloading the Clear Case Add-In from the Add-In Manager. In addition, you should not use the Get Latest menu item to update your snapshot view. Instead, you should update the snapshot view using one of the external Clear Case mechanisms (such as the Clear Case menu items in the Windows Explorer). These problems should be resolved in a future release.
IMPORTANT NOTE FOR USING ROSE WITH CLEAR CASE.
In order to effectively control and use Rose models/units with Clear Case, you must set a Path Map symbol to the Clear Case view in which you are working. Otherwise, the full path to the units will be saved in the model making them unusable from any other Clear Case view.
For example, if you are controlling Rose units in the view X:\MyView, you should set a Path Map variable, such as "CCVIEW", to the value "X:\MyView" using the File >Edit Path Map... dialog. This will ensure that when the model and sub units are saved, references to the views path will be replaced with $CCVIEW. If you wish to work with the model from another view, such as "Y:\MyOtherView", just bring up the File >Edit Path Map... dialog again and change the CCVIEW variable to the new view and reload the model.

149267

In general, icons in the browser should accurately reflect the Clear Case status for the associated unit. If, however, the Icons in the browser do not reflect the current Clear Case status (as might occur if the state is changed from outside of Rose), you can force a refresh of the browser icons by unloading and then reloading the Clear Case Add-In from the Add-In Manager.

149386

After creating a new VOB and a dynamic view, if you try to add any object to it, the version control (using the Clear Case Add-In) will fail.
This happens only if no operations have ever been performed on the VOB.
Workaround:
Add an element (such as a file or directory) to the VOB using one of the external Clear Case mechanisms (such as the Windows Explorer interface). Once you have performed any Clear Case operation in the VOB, you will be able to use the VOB with the Rose Clear Case Add-In.

149567

Selecting the Remove from Clear Case command while doing a check in causes an error loop.

Clear Case Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Clear Case defects fixed since the last release.

 

DDL Add-In

The Data Definition Language (DDL) Add-In release note contains known problems and limitations as well as fixed defects since the last release.

The gap between object technology and relational databases is closed by providing a mapping interface to relational databases through generation of persistent classes to Structured Query Language (SQL) and Data Definition Language (DDL).

You can find DDL Add-In release note information in the following locations:

Known DDL Add-In Problems and Limitations

Defect:

Description:

000000

There are no known problems and limitations for the DDL Add-In.

DDL Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of DLL add-in defects fixed since the last release.

Type Library Importer Add-In

The TLI allows you to import a type library of a COM component into the model by dragging the COM component from Windows Explorer and dropping it in Rational Rose.

You can control several aspects of how type libraries are imported into the model. For example, you can control:

The Type Library Importer (TLI) Add-In release note describes new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Type Library Importer release note information in the following locations:

New Type Library Importer Features and Enhancements

The previous version of the Type Library Importer did not import all items in a COM component’s type library—that is, it did not import all the items shown in the Microsoft OLE View. In Rational Rose 2000, the entire type library of the COM component is imported into the model—including interfaces, dispinterfaces, coclasses, enums, structs, unions, and modules. Also, there are now two different ways to import a type library; either by using drag and drop, just as before, or by using a new menu item, Tools > COM > Import Type Library.

There is also a new dialog box available from the Tools > COM > Properties command, which allows you to control how type libraries are imported into the model. For example, you can control the following:

For detailed information about the Type Library Importer and how imported type libraries are represented in the model, please refer to the Rational Rose online help. Open the "Type Library Importer" book on the Contents tab of the help window or search for "Type Library Importer" on the Index tab.

Known Type Library Importer Problems and Limitations

Defect:

Description:

149402

TLI does not use the Rose Path Map when storing the "filename" property for components

Type Library Importer Add-In Defects Fixed

See the online help version of the release notes for a list of Type Library Importer defects fixed since the last release.

Corba Add-In

Rational Rose Corba Add-In allows you to forward engineer Rose model elements into Corba-compliant IDL code and it allows you to reverse engineer CORBA IDL code into appropriate Rose model elements.

The Corba Add-In release notes describe new features and enhancements, upgrade information, known problems and limitations, and fixed defects since the last release.

You can find Corba Add-In release note information at the following locations:

New Corba Add-In Features and Enhancements

There is better Round – Trip Engineering support for multiline comments, #defines, and #pragma definitions.

Known Corba Add-In Problems and Limitations

Defect:

Description:

149285

You can create a nested class in CORBA typedef. You are not supposed to use nested classes in a typedef. This is spelled out in the online documentation for CORBA.

Corba Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Corba defects fixed since the last release.

Framework Wizard Add-In

The Framework Add-In provides a library of frameworks that can be used as templates when creating new models. The Framework Add-In also provides a wizard that helps you add additional frameworks.

The Framework Wizard Add-In release note describes new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Framework Wizard Add-In release note information in the following locations:

New Framework Wizard Add-In Features and Enhancements

Other than defect fixes, the Framework Wizard Add-In functionality has not been enhanced in Rational Rose 2000. However, there are several new frameworks including jdk12 and the RUP.

Known Framework Wizard Add-In Problems and Limitations

Defect:

Description:

148079

The Framework Wizard jfc-11 loads, but if you select File > New, Rose hangs.

148383

Rose hangs when you attempt to create a new model after you open jdk-12 or jfc–11.

148973

Get rfwframewrk - Run Time Error "53" Related to Professional Edition defect147394.

Framework Wizard Add-In Defects Fixed since the Previous Release

See the online help version of the release notes for a list of Framework Wizard defects fixed since the last release.