It is important for the developer to work closely with the DBMO throughout the analysis and design process to identify which classes in the analysis object model need to be persisted. The Object Model is often a starting place for discussions with DBMO about the data model. However, it should not be expected that the data model and the object model should look the same. Objects representing data that need to be persisted are typically entity classes. These objects could also be needed to handle nonfunctional requirements in general. Examples are objects needed to maintain information relevant to process control or to maintain state information between transactions. Identifying such objects serves to notify the DBMO that the data requires special attention to its physical storage characteristics. It also indicates that the data needs to be persistent and that instances of the data need to be made persistent.