Description Conceptual Classes

From: Bala Paranj (bxparanj_at_yahoo.com)
Date: 06/20/04 

Date: 20 Jun 2004 02:40:44 -0700

Hi,

This question is related to objects which are descriptions of other
objects. For example TicketDescription class for a Ticket Entity
class.

Description conceptual class actually deals with data normalization
and persistency issues. In this case we are talking about solution
domain issues. These issues are not the concern of the analysis phase.
These issues are addressed during the design or is it implementation
phase?). The main purpose of the domain model is to show the most
important conceptual classes in the problem domain.

Therefore, my opinion is that the domain model should not have any
description conceptual classes. This does not lead to loss of any
information while communicating with the stakeholders since they are
not knowledgeable in solution
domain concepts.

Larman in his book gives the advice of having description conceptual
classes in the domain model. I don't find the reason for why we should
do it. Can someone give some feedback on this issue?

Thanks in advance,
Bala
69BP1N-NCRDU
http://uml.zepho.com