Abstract
More work is needed on devising practical, but theoretically well-founded procedures for doing object-oriented database (OODB) design [17]. Design procedures should also be flexible enough to take into account various application characteristics (such as whether objects are very large or are read-only). In this paper, we present and discuss an OODB design procedure that addresses these problems. The procedure is practical in the sense that it is based on a common family of conceptual models and in the sense that it does not expect users to supply esoteric, difficult-to-discover, and hard-to-understand constraints (such as multivalued dependencies), nor does it make hard-to-check and easy-to-overlook assumptions (such as the universal relation scheme assumption). At the same time, the procedure is well-founded and formal, being based on NNF (Nested Normal Form [21]), a new theoretical result that characterizes properties of interest in designing complex objects. It is also adaptable to various applications characteristics.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
