Entities

We certainly care about the identity and lifecycle of the following classes:
  1. Customer- Represents a person and is thus easy to identify as an entity.
  2. Agent - Represents a person and is thus easy to identify as an entity.
  3. MarketingGroup -
  4. Order - Needs to be an entity as we wouldn't want to treat two Orders as being the same simply because they have the same attributes.

Value Objects

The following two classes are easy to categorize as Value Objects:
  1. Money
  2. Name
In our system we are unlikely to share instances of either class but if we thought it could help the design/performance then there is no reason that we couldn't rethink.

The following two classes are both Value Objects:
  1. Address
  2. BankAccount
Addresses could be shared, for example if two people lived at the same address then we could have them share the address object. The same could be true of bank accounts but it is probably less likely that people will share bank accounts so copying rather than sharing might be the better option.

Factories

Services

Last edited Aug 27, 2007 at 3:15 PM by colin_jack, version 2

Comments

No comments yet.