1 / 11

Database Design Enhanced entity-relationship modelling

Database Design Enhanced entity-relationship modelling. John Wordsworth Department of Computer Science The University of Reading J.B.Wordsworth@rdg.ac.uk Room 129, Ext 6544. Lecture objectives. To review other kinds of relationships between entities, especially hierarchical relationships

pricek
Download Presentation

Database Design Enhanced entity-relationship modelling

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Database DesignEnhanced entity-relationship modelling John Wordsworth Department of Computer Science The University of Reading J.B.Wordsworth@rdg.ac.uk Room 129, Ext 6544 2/CS/3X

  2. Lecture objectives • To review other kinds of relationships between entities, especially hierarchical relationships • To consider how constraints on relationships are expressed • To review the notion of object-oriented design and its relationship to database design 2/CS/3X

  3. UML diagram for different kinds of rooms Survey of rooms available to the university: 0..1 1..* 1..* 1..1 Department Room Building LectureTheatre Seminar Room Office Laboratory 2/CS/3X

  4. Analysis • The diagram shows a simple application in which rooms are of various types (Office, Lecture Theatre etc.) • An Office is a room; a Lecture Theatre is a room, etc. • Some of the attributes of rooms (those common to all types) are recorded in Room • Others are recorded in Office, Lecture Theatre etc. 2/CS/3X

  5. Superclasses and subclasses • Room is a superclass: it is an entity type that includes distinct subclasses • Office, Lecture Theatre etc. are subclasses: they have distinct roles and are all members of the superclass Room 2/CS/3X

  6. Hierarchies • type hierarchy • specialization hierarchy • a top-down approach • start with the highest level of superclass • establish the set of subclasses by identifying attributes that are peculiar to each subclass • generalization hierarchy • a bottom-up approach • establish superclasses by identifying common attributes of a group of entity types • IS-A hierarchy (an office is a room, and so shares the properties of a room) 2/CS/3X

  7. Hierarchical relationships • IS-A links a class representing a generic type of object with a class representing a specific category of object • HAS-A links a class representing components with a class representing assemblies (of components) 2/CS/3X

  8. Constraints An annotation {participation, disjointness} describes the constraints on a hierarchical relationship. • participation • mandatory: an entity is obliged to belong to one of its subclasses • optional: an entity need not belong to any of its subclasses • disjointness • or: the subclasses do not overlap; an entity may be in only one subclass • and: the subclasses overlap; an entity may be in more than one subclass 2/CS/3X

  9. Object-oriented design • Each entity type is modelled as an object class. • An object class is associated with attributes and operations (methods). • Inheritance: each subclass has the attributes and methods of its superclass, and might have attributes and methods of its own. 2/CS/3X

  10. Furniture Dimensions Weight Cost Location Buy Sell Move Upholstered Furniture Wood Furniture Dimensions Dimensions Weight Weight Cost Cost Location Location Fabric Finish Pattern Buy Buy Sell Sell Move Move Polish Re-cover Extending Sofa Table Dimensions Dimensions Weight Weight Cost Cost Location Location Finish Fabric SeatsMax Pattern SeatsMin Seats Buy Buy Sell Sell Move Move Polish Re-cover Extend Contract A class hierarchy 2/CS/3X

  11. Key points • UML can be used to express hierarchical relationships between entity types. • Annotations specify the participation and disjointness of entity types in a hierarchical relationship. • The hierarchical relationships of entity types are very similar to the inheritance relationships among object-oriented classes. 2/CS/3X

More Related