To open a Rose model file in a previous version of Rose you need to
use File:Save As, and save the model back to previous version. Otherwise
older version of Rose will not understand new syntax in model file.
Regarding changes from 98 -> 2000e (note that 2000e is now 2 versions
back from latest; 2001, 2001A), also 2000e includes what was added
to 98i (which came after 98).
-------------------------------------------------------------------
Rational Rose 98i picks up where Rose 98 left off. The "i" stands
for "Integration", and true to its name it offers seamless
integration with industry standard products. The following is a
list of features that are present in this new product. Wherever
appropriate the editions in which these features are available
are noted.
Rose 98i supports the following features:
1. Installation and Licensing Features:
Rose 98i is now a licensed product using FLEXlm from Globetrotter
Software.
2. Enterprise Development Features:
* Integration with Visual Studio 6.0: Rose 98i provides a
tight coupling with Visual Studio 6.0 to give developers
a seamless integration.
* Integration with Rational Suite: Rose 98i supports the
Rational suite product by integrating the licensing and
installation features required to function as a part of
the suite.
* Integration with ClearCase:
Rose 98i provides a second generation ClearCase
integration that also works with VSS and other SCC
compliant tools.
* IDL Forward and Reverse Engineering:
In the Rose 98i Enterprise and Professional Editions, the
IDL add-in is replaced with the CORBA add-in which will
allow forward and reverse engineering of CORBA IDL. Rose
98i Modeler Edition will not support IDL.
* Internet Web Publisher:
The Web Publisher will allow Rose customers to publish their
models, and specification as html files so as to better
share information between projects on the intranet.
Available in Enterprise Edition only.
Miscellaneous New Features in Rose 98i
* Rose J Add-in
The JavaTM add-in in Rose 98 has been renamed the Rose J add-
in in 98i.
* Scenario diagrams will now support nested focus of control
and UML legal outline numbering.
* Scenario diagrams can also be linked together.
* Nested classes are now displayed in the browser.
* Specifications for Parameters and specifications for Role
Keys/Qualifiers have been added.
* Add-ins can now configure their context menus. E.g. the Rose
J add-in can have its own context menus which are specific to
the language. This would mean that you could select a Java
class in a diagram, right-click on it, and have a very Java
specific menu appear. This is different from the current
implementation of Rose 98 where the context menus are
dictated by the language selected at installation.
* Manipulation of controlled units has been moved to the
browser and Browse Units dialog has been eliminated.
+ A couple of 100 DEFECT fixes.
98i SP1 added support for activity diagrams.
-------------------------------------------------------------------
What's new in Rose 2000e?
1. Better UML Construct Support
Object flows in activity diagrams show the flow of
information between activities and objects. This allows the
business modeler to show how objects are created,
destroyed, or modified during the flow of control.
"Realize" and "dependency" relationships between use
cases in use case diagrams - "Extend" and "include"
relationships between use cases are stereotyped
dependency relationships. A use case is related to its
realization via a "realize" relationship. Now these
relationships can be fully represented in Rose.
"Realize" and "dependency" relationships between
interfaces and packages in class diagrams - A UML package
contains a collection of related classes. Some of these
classes represent the interface to the package (i.e., how
classes outside the package can communicate with classes
inside the package). Rose now lets you show the interface
to a package on a class diagram so you can visualize the
layers of a system along with the defined interfaces between
the layers.
Shared activities and states - An activity or a state is often
used in more than one diagram. With Rose 2000e, you can
simply drag the activity or state from the Browser onto any
desired diagram. This means you only have to make a
change one time and that change will be reflected
everywhere.
2. Enhanced Spport for Unified Change Management
Unified Change Management (UCM) provides a process for
organizing project activities and managing artifact changes
throughout the life cycle. The technology foundation for
UCM, originally developed for Rational ClearCase and
Rational ClearQuest, has been extended to Rational Rose.
With UCM, you can:
Associate an activity with a Rose unit
Create a new activity to associate with a Rose unit
Update development and integration streams from within
Rational Rose
Access the ClearCase Project Explorer from Rational Rose
Benefits - By using Rational Rose together with Rational
ClearCase, you can easily take advantage of UCM facilities
across the entire project life cycle - from elicitation of user
needs to requirements management, architectural design and
system modeling, and coding and testing.
3. Simplified Model Usage
Workspace support - A Rose model is typically broken up
into individual control units. A large model may have many
control units. With the addition of workspace support you
can specify a set of units to be opened when your
workspace is opened, rather than loading all units initially or
loading units manually as needed.
Benefits - Workspace support saves you time and eliminates
repetitive activity, since loading the entire model can be very
time consuming for complex projects. A workspace lets you
specify a model subset that can later be loaded in a single
operation.
4. New Edition of Rational Rose for UML Data Modeling
New Rational Rose Data Modeler - Typically, application
developers use UML notation while data modelers use ERD
(entity relationship diagram) notation. This means someone
must translate from one notation "language" to another.
With the introduction of Rational Rose Data Modeler, data
modelers and application modelers can now work together to
solve their business problems using one notation and one
tool.
Track changes from data model to object model, beginning
with requirements changes, which you can drive down to
elements in the application and database tables and
columns. This helps the entire team understand how all of
the pieces of development will work together. If a
requirement changes anywhere in the life cycle, it can be
identified for all team members. Changes can even be shared
across models.
DDL generation and reverse engineering - Direct, round trip
engineering of DDL between relational databases and the
data model allow users to document, create, and change
databases.
5. New Rational Rose Add-In for Web Modeling
Web application extension (WAE) stereotypes - Today's
Web applications are growing increasingly complex. The
WAE, a new Rational Rose add-in, extends the UML
notation with additional semantics and constraints to permit
the modeling of Web-specific architectural elements as a part
of the rest of the system's model.
Reverse engineering of ASP applications - Now you can
visualize existing ASP applications. This feature is
especially helpful for applications built without any
documentation and that now they need to be modified. By
creating a model of the application you can visualize how the
pieces of the application fit together.
6. XML/DTD Round Trip Engineering
XML/DTD modeling - An XML/DTD (Document Type
Definition) contains the knowledge about the structure and
format of an XML document. As with application and data
modeling, a picture is worth a thousand words. The
addition of stereotypes in the XML add-in allow you to
create the blueprint of your XML/DTD.
XML / DTD code generation - Once the model has been
approved by all stakeholders, you can automatically create
the XML/DTD document with Rational Rose.
XML/DTD reverse engineering - Now you can create a
blueprint of any existing XML/DTD document. You can
then use this blueprint as the documentation of the
XML/DTD. You can also extend the model to accommodate
new requirements and generate a new XML/DTD.
7. Java Enhancements
Improved Autosync - Many more events, including
relationships and parameter changes, are now supported by
Rational Rose. Class-level autosync is also available.
(Autosync can be set up as a default, or activated on a
class-by-class basis.)
Extensibility - Java code-generation now emits code
generation events that allow for complete customization of
generated code.
8. Rational Rose Visual Studio Enhancements
Improved ATL support, MIDL round trip engineering -
Rational Rose Visual Studio integrates seamlessly with
Microsoft Visual Studio 6.0 to generate and reverse engineer
code. By providing deep support for WinDNA technologies
such as MFC, COM, ATL, MTS, ADO, and ASP, Rose
Visual Studio help developers produce higher quality code
faster by visualizing and round-trip engineering their
WinDNA applications.
Prepackaged code templates let you capture the design and
all required code for building scalable, distributed,
transaction and data-aware applications. Using these
patterns, developers can design and generate working
WinDNA applications faster and with higher quality.
Enhanced code templates support RTE framework SDK -
Design templates provide a way to generate much more than
just skeleton code. You can use them to capture design and
coding patterns for easy reuse in your model as well as to
generate robust real-world code. Rational Rose Visual
Studio is open and extensible. Automation interfaces are
exposed for all code generation, reverse engineering, and
design template objects, allowing you to customize and
extend the round-trip engineering capabilities of Rational
Rose for your specific needs.
-------------------------------------------------------------------
RELNOTES from beta
-------------------------------------------------------------------
New Rational Rose Features and Enhancements
The following list describes the new features added for the Rose
2000e beta 1 release:
Objects and Object Flows on Activity Diagrams
Objects and Object Flows now appear on activity diagrams. Objects
on activity diagrams are similar to objects found on collaboration
and sequence diagrams. However, objects have the ability to appear
in various states on activity diagrams.
Placing an object on a activity diagram:
Select Tools > Create > Object or click the object icon from the
activity diagram toolbox.
Connecting activities and objects with an object flow:
1. Place an activity and object on an activity diagram.
2. Select Tools > Create > Object Flow or click the object flow
icon from the activity diagram toolbox.
3. Click the pointer on the activity and drag an object flow to an object.
Changing the state of an object:
1. Double-click on an object located on an activity diagram.
2. Select New in the State drop-down combo box.
3. Update the new State specification to reflect the state of the
object.
Sharing activities between State Machines
1. You can now share activities between different state machines.
2. Create an activity diagram
3. Place an activity on the diagram.
4. Select and copy the activity.
5. Paste the activity on another activity diagram in a different
state machine. The duplicate or copied activity will have the
original location listed in parenthesis under the activity name
(from state/activity model).
Workspace Configuration Options
A workspace consists of the currently loaded controlled units and
open diagrams in your model. The workspace configuration feature
allows you to save your workspace, so that later you can restore it
that is, you can load the same units and open the same diagrams
with a single action.
Saving the Current Workspace Configuration:
Select File > Save Workspace. Rose saves the state of open
diagrams and loaded units in a file with an extension of .wsp.
Restoring a Saved Workspace Configuration:
1. Select File > Load Workspace.
2. Select the workspace file (*.wsp) to load.
Use Case Dependency
Dependency between use cases is now supported.
Creating a Dependency between Use Cases
1. Place two use cases on a diagram.
2. Select the Dependency icon from the toolbox (or select Tools >
Create > Dependency).
3. Drag the dependency icon from one use case to the other use case.
Package to Interface Realization
You can now model an interface realized by a package.
Modeling an Interface Realized by a Package
1. Place a Package and an Interface on a class diagram in the
logical view.
2. Select the Realize relationship icon on the class diagram
toolbox (or select Tools > Create > Realize).
3. Draw the realize relationship from the package to the interface.
Subsystem Stereotype Package
"Subsystem" is now a predefined stereotype that is available for
packages.
-------------------------------------------------------------------
-------------------------------------------------------------------
To check out what's new in 2001A see,
www.rational.com/products/rose/wn_rose-v2001a.jsp
Patrick Kennedy
Rational Support
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
