The following is a note that I wrote to myself sometime back, as part of
my ongoing attempt to clarify all of my implicit assumptions, or to
round the Cape of Good Hope, or something like that.

In each processor, there needs to be at least one boundary object that
is instantiated all the time.  Otherwise, you would have to violate the
rule that says an actor can only talk to a boundary object.  The
"essential boundary object" need not be displaying a window (for
example) at all times, it only needs to be capable of receiving a
message and instantiating other objects.

Persistence is a separate issue.  The persistence of the essential
boundary object will never be tested, its state will never be lost.

I don't understand why controls should not be persistent.  I don't see
the payoff in destroying the state of the control object when the object
is destroyed.  I don't see the problem with having one or more
"essential" controls, that are instantiated whenever the system is.

These factors affect multiplicity in class diagrams. 

Multiplicity is determined by considering how many objects may exist in
a given association at a given instant.  For any given association, this
analysis covers the entire population of scenarios for the use cases
that employ the objects, or all paths through those use cases.  At a
given moment in the project, the analysis covers the scenarios that have
been analyzed into objects and classes by sequence diagrams or by other
means.

-Eric
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Post or Reply to: [EMAIL PROTECTED]
* Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
*    http://www.rational.com/support/usergroups/rose/rose_forum.jsp
* 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