Yes you can model business data requirements using UML.  Data modeling is a requirements gathering and documenting process.  Its goal is to eliminate redundency in the database.  It is inherently different than building a class model for an application.  The application class model includes behavior as well as data when constructing the model.  So you can't just model the application, indicate which attributes are persistent, transform the class diagram to a data model, and expect a good database.  So to answer your question, yes you need to model the database and no it does not have to be in the same diagram (but it can help).  The appropriate stereotype is Entity.
Walter

>>> "Chris Condos" <[EMAIL PROTECTED]> 03/22/01 10:18AM >>>

Folks,

just a quick question:

say, you have to produce a class diagram for a system that needs to access
an external database. would you actually show the database on the class
diagram (as a stereotype class maybe) or isn't that necessary?

Chris

---
Chris Condos,
School Of Mathematical & Information Sciences,
Computer Science Subject Group,
Coventry University,
Priory Street, CV1 5FB,
Coventry,
UK

Tel: +44 - 24 - 76 88 8519
e-mail: [EMAIL PROTECTED]

************************************************************************
* 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
*
*************************************************************************

Reply via email to