Explication of object-oriented databases: a software engineering perspective

Authors:
Adair Dingle;David Umphress;Russ Moul
Affiliations:
Computer Science and Software Engineering Department, Seattle University, Seattle, WA;Computer Science and Software Engineering Department, Seattle University, Seattle, WA;Information Resource Management, Boeing, Defense and Space.Group, P.O. Box 3999 M/S 3E-LU, Seattle, WA
Venue:
SIGCSE '98 Proceedings of the twenty-ninth SIGCSE technical symposium on Computer science education
Year:
1998

Citing 6
Cited 0

Normalization in OODB design

ACM SIGMOD Record
Database: models, languages, design

Database: models, languages, design
A relational model of data for large shared data banks

Communications of the ACM
Object Database Standard: ODMG-93

Object Database Standard: ODMG-93
Normalization of Object-Oriented Conceptual Schemes

CAiSE '93 Proceedings of Advanced Information Systems Engineering
Deriving Normalized Is_a Hierarchies by Using Applicability Constraints

CAiSE ;96 Proceedings of the 8th International Conference on Advances Information System Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

The growing use of Object-Oriented Databases (OODBs) has necessitated the inclusion of OODBs in introductory database courses. Typically, such an analysis is conducted after the explication of the dominant industry standard: the Relational Database model (RDB). Like the RDB model, the OODB model can be easily motivated. Unlike the RDB model, an established data model with defined normal forms, the OODB model cannot be easily evaluated for "goodness". We address this deficiency by examining the criteria of coupling and cohesion in database design. This approach affords the instructor the ability to better present OODBs as well as the opportunity to re-emphasize critical software engineering concepts.