The purpose of the content model is to define the main content classes in the system and how they relate to each other. It is a high-level view of the system; details of each of the content classes will be defined later in the specification. This model becomes the foundation for the solution. The approach used here is based on object role modeling, which maps the traditional concept of an object model with relational database schemas (for more information, see http://www.orm.net). It is not the only way to capture this information but one that works well in this environment. You can replace this with your own form of modeling—the key is to understand the objects and the relationships within the business environment.
The following diagram outlines the main content classes, and relationships between them. The example used here is from the Studies In Australia website (http://www.studiesinaustralia), which provides detailed information on all tertiary...