On Thu, 29 Mar 2001, Rich Denis wrote:
> Why is it not reccomended to add attributes as part of an interface? If I
> createan interface in Rose and "realize" that interface in another class
> then only the Operations show up. When I read the Online Docs under
> interface it says that Attributes as part of the interface is not
> recomended? Why is that?? And is there any way to force the attributes to
> be inherited within the Rose IDE
IHO, at least one reason is that typical subsystem implementation
technologies such as COM and CORBA don't provide for interface attributes.
Further, there may (I'm not sure) be C++ implementation constraints that
preclude interface attributes, given the basic "subsystem replacement
without client package recompile" requirement.
Finally, from rose's perspective; it implements the UML, and the UML 1.3
specification is very clear on what an interface is:
"An interface is a specifier for the externally-visible operations of a
class, component, or other classifier (including subsystems) without
specification of internal structure."
last paragraph, page 3-46 of OMG-UML V1.3, available at:
ftp://ftp.omg.org/pub/docs/formal/00-03-01.pdf
Unfortunately, the UML spec doesn't provide any rationale...
--
William Blew, [EMAIL PROTECTED] Gamer by Choice, Geek by Birth
************************************************************************
* 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
*
*************************************************************************
