Java Reference
In-Depth Information
Account
Account
a pool of dollars
a pool of dollars
members
members
collaborations
collaborations
* name - a String
* owner - a User
* amount - an SAMoney object
* children - an ArrayList (of Accounts)
* parent - an Account
* name - a String
* owner - a User
* amount - an SAMoney object
* children - an ArrayList (of Accounts)
* parent - an Account
* persistence (CRUD)
* User
* persistence (CRUD)
* User
Figure 12.1
Account CRC card
User
someone who manages budget dollars
members
collaborations
* name - a String
* home - an Account
* persistence (CRUD)
* Account
Figure 12.2
User CRC card
be dozens).
2
The first step should always be the nomination of the real-world
objects. Don't edit or critique at this point. If someone says “computer” as an
object, write “Computer” on the top of a card and put it on the table. If
someone says “Manager” write it on a card and put it on the table.
2. It is fun to gloss over such a complex topic with a single sentence! Obviously, the composi-
tion of a design team is a complicated matter. At the very least, a design team must include a
representative from the programming team and a future user of the system. On small, simple
projects, that may be all you need. On more complex or mission-critical systems, there will
have to be additional representatives, such as people from Operations, Support, Training,
Quality Assurance, and so on.
