An Object Database Web Implementation in Jasmine
Structure
These diagrams show the structure of the products implementation. The first diagram shows the class inheritance hierarchy structure. The second diagram shows the structure of the objects as they are created by the class hierarchy in memory. It is very important to note how the class hierarchy looks completely different to that of the object structure. A class is a form of an object template. An object is an instance of a particular class in that template of classes. In this example the Abstraction class was created to facilitate the abstraction of functionality, ie. methods. Therefore if the Abstraction class was not created there would be very little inheritance in this class hierarchy. Do not over-use inheritance. Inheritance is a way of abstracting and specialising CLASSES and not OBJECTS. An object is not the same thing as a class. Objects are generated from classes in the memory of your computer when your class hierarchy is instantiated. It is a very common mistake to attempt to create an object structure which is visually verifiable by creating an object structure visually by using classes and inheritance. Remember, classes use inheritance for abstraction and specialisation. An object does not inherit from another object. An object is instantiated by another object. Inheritance does not create objects. In fact inheritance affects the use of methods most significantly.
Class Inheritance Structure
Actual Object Structure
The Complete Picture
The Windows Explorer like open icons in red represent classes. One class contained within another class represents inheritance. The Jasmine icon represents the inclusion of one class into another class. All inclusions in this database are collections.
 |
|
Free Stuff |
 |
|
|
Product |
|
|
|
Person |
|
|
|
Division |
|
|
|
Project |
|
|
|
Demo |
|
|
|
Discussion |
 |
|
|
Reply |
