This is a decision of your design. I don�t know any rule for this.
You can package these attributes (and operations) in an abstract class. But you should decide, whether there is a drawer-specific reason for this.
Mit freundlichen Gr��en
Jan Mat�rne
RZF NRW
Sachgebiet 314-P Software-Entwicklungs-Methoden
Fiscus AFG NW 42 SoftwareEntwicklungsUmgebung
Internet: [EMAIL PROTECTED]
-----Urspr�ngliche Nachricht-----
Von: Pankaj Chatterjee [SMTP:[EMAIL PROTECTED]]
Gesendet am: Donnerstag, 23. November 2000 12:13
An: 'Rose Forum'
Betreff: (ROSE) Designing Objects
Hi Folks,
I was wondering :-
While designing a database, stress is given on normalizing the data
structure. Do we have something similar in OO terms while designing objects,
or is it acceptable for two related classes to have some common attributes ?
Thanks
************************************************************************
* 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
*
*************************************************************************
