If the database is outside of your development scope - if you just use it,
and this is just the external interface of the database you are using, model
it as an actor. As soon you need to know the internals of the database, and
maybe even change it, this is not an actor any more.
Davor
-----Original Message-----
From: payam` zahadat [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 16, 2001 12:40 AM
To: [EMAIL PROTECTED]
Subject:
Hi
Im trying to model a system that interacts with a
DataBase ,is it correct that in use case view I must
model DataBase System as an actor? or is it valid if I
do this?
Thanks for your answers
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
************************************************************************
* 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
*
*************************************************************************
************************************************************************
* 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
*
*************************************************************************
