A set of activities that includes producing a logical Object Oriented Design Model (OODM) and a Class-Oriented Design Model (CODM) that show the business processes and the data it uses or produces are encapsulated by a set of logical O-O layers, and by a set of physical O-O layers, respectively. The logical O-O design uses Objects that have Characteristics and Behaviors. The physical O-O design uses Classes that have Properties and Methods.
This is a modeling activity that is not part of Data Modeling TDM. The TDM activities that precede this one insures the availability of persistent data the O-O design can encapsulate, and the parallel definitions between subtyping to subclassing. Forms, and the Views that are created from the Forms can be set to mirror the messaging formats used by behavior/methods. TDM suggests the use of the Relational Object Oriented Layered System Architecture (ROOLSA) to create and maintain a proper mapping between Entities and Objects and between Tables and Classes (hint: it’s not 1:1). Such mapping requires the categorization of Entities/Tables TDM proposes, or similar.