| Previous | ReadyNotes | Next | |
|
A Survey of 3D Graphics Software ToolsRN0067905
List Price: $19.00
|
|
Amount:
|
|
The typical practice for building database applications is to use a direct representation, that is, directly map application concepts to the database structure. The direct approach is effective for applications with well-defined classes and attributes. However, it fails for applications with open-ended classes and attributes. Consider an application for managing equipment data. The pertinent data varies widely by equipment type. For example, storage tank data includes physical dimensions, materials of construction, and rated pressure. In contrast, pump data include flow rate, power consumption, pressure differential, and materials of construction.
Any attempt to hardcode equipment data is doomed to be fragile. New types of equipment and attributes would frequently arise, requiring model extensions, and disrupting the corresponding application.
With hardcoding, classes and attributes must be known at compile time as an application is being built. With softcoding, classes and attributes need not be known until runtime when the application executes. Softcoding lets both data and metadata (definitions of classes and attributes) be determined at runtime. Softcoding can be configurable, giving users the flexibility to define their own data structures.