Wow. This approach kind of defeats the purpose of having the little checkbox that
indicates that the class is persistent. Although it does get around the pitfall of
having persistent and non-persistent attributes in the same class. If I have to write
scripts to keep my data model diagram in sync with my data model class diagram and I
have to write scripts to keep my data model class diagram in sync with the application
class model diagram, how is this an improvement over just doing you application
modeling in Rose and doing the data modeling in Data Architect or ERwin?
Walter.
-----Original Message-----
From: "Gornik, Davor" <[EMAIL PROTECTED]>
Sent: Wednesday, November 29, 2000 11:55 AM
To: <[EMAIL PROTECTED]>, "Gornik, Davor" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Subject: RE: (ROSE) Data modeler & Oracle 8
Oliver,
i tried to clarify my thoughts...
> Hello Davor,
>
> i fear, that is misunderstood something. You wrote:
>
> > the logical database model is a model of the database design without any
> > considerations of the physical implementation. This means the logical
> > model must NOT be denormalized because of performance or any other
> > implementation issue.
>
> Ok i totally agree. But pls. explain, which model you exaclty mean with
that?
> When i read the following text, i think that you have not meant the
"object
> model". Did you?
My thoughts are realy about the part of the object model. I clasify the
object model into the application related object model and the database
related object model (persistence object model), which are related, but not
the same.
You would create two packages with different objects for this.
>
> > The logical model (object model) is not just another view to the
> > database as many of other tools try to describe it because of the lack
> > of tool capabilities it is an independent view, which has to develop
into
> > the physical model and manage the traceability to it and vice versa.
> [...]
> > Actually to be absolutely clear the object model must not be the
> > model the application developer uses for the application design.
>
> Do you mean, that i have to _duplicate_ all persistent classes from all
class
> diagrams into an own data model and than i have to do design activities?
Yes, this is the approach I would suggest.
>
> If yes: How do i keep the traceability between the class diagrams and my
data
> model. We are developing software using the Unified Process. Developers
add,
> modify and delete attributes to their classes. How do i keep up to date
with my
> data model when not using "their" classes?
My suggestion is to use dependecies and write some scripts to do it.
>
> Thank you for your efforts with my questions.
>
> Regards
> Oliver
************************************************************************
* 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: rose_forum [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
************************************************************************
* 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
*
*************************************************************************
