Let me propose another slant to the address (phone) issue.

The Navy has a massive database of information that is gather thru a variety of applications. As applications come on-line they either add new information or make use of what's there.

So, as an example, housing addresses are used for the housing people (assigning quarters to people coming on-base), by the safety people for tracking asbestos remediation, and by, say, the commissary which tracks customers and their addresses.

The database can't make the decision to delete an address out of the address table when a customer is deleted from the commissary application. Neither can the application.

So, who's in charge in this case?

Add to this that legacies are being merged into the system over time, so there is no real way to "fix" who needs addresses and who doesn't.

>But if we store deliveries to a certain address, this would be a seperate entity alltogether. Therefore, everything that goes on between those two entities is business logic.