Thanks
for your help, David, but I have doubts: Since the Data Modeler has some mapping
for the transformation to an object model I fear that I might loose information.
As a matter of fact all I need is a 1 to 1 transformation, i. e. one
table maps exactly to one class, one column to one attribute and one data
model association to one object model association without changing things like
aggregations, compositions and so on. AFAIK the transformation mapping is more
complex but not configurable.
Any
other suggestions?
-----Urspr�ngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet am: Dienstag, 11. M�rz 2003 16:01
An: G�ntsch, Alexander
Betreff: Re: (ROSE) Removing stereotypes
Alexander,
With the DataModeler addin enabled, select the highest-level package of the Data Model. Use right-mouse button to bring up the pop-up menu. From the DataModeler sub-menu, choose "Transform to Object Model...".
Complete instructions are contained in the Rational Rose Data Modeler guide ("Rose_dm.pdf") which is on the Documentation CD that was packaged with the software distribution.
Sincerely,
David Hoffman
Information Management Group
Convergys Corporation
600 Vine Street
Cincinnati, Ohio 45202 USA
Phone: 513.784.7419 FAX: 513.241.4826
Internet: [EMAIL PROTECTED]
"G�ntsch, Alexander" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]03/11/2003 09:21 AM
Please respond to "G�ntsch, Alexander"
To: [EMAIL PROTECTED]
cc:
Subject: (ROSE) Removing stereotypes
I am working a a rose model with a lot of tables that are modelled using the Data Modeler. But actually all the "tables" are simply classes.So I removed the stereotype "table" so they look like classes. But when I open the specification dialog I still get the table specification as long as the Data Modeler addin is active. I have figured out that the Data Modeler uses a set of properties an probably the "dmItem TRUE" indicates that the class is a Data Modeler item.
So what do you recommend to make the tables be just a plain class? Should I set this property to FALSE? That just leaves a lot of dispensable information in the file. Is there a possibility to remove a set of stereotypes from a model?
Thank you in advance,
Alexander
