The two previous articles in this series described data models used to represent the business owners' views and the architect's view. This final article is concerned with the logical models used by both relational and object- oriented designers.

Designers are not looking at things of significance to the business. They want the boxes of a data model to represent something meaningful to a computer application. In the case of relational database designers, their boxes represent database tables; and where the architect had attributes, they put columns. Relationships are implemented with foreign keys, and unique identifiers become primary keys. (Object-oriented designers, on the other hand, are concerned with classes and associations, as will be described.)

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access