Database Conceptual Design Problem

Part 1: CIOM Design Design a CIOM conceptual schema that incorporates the specification described below. You should use the notation given in the class. Your diagram should indicate all the classes, subclasses, set operator classes, attributes, attribute value classes, inverse attributes, and cardinalities. In your design, you can make and state reasonable assumptions if they are not specified in the specification. Part 2: EER Design Design a conceptual schema using the Extended ER data model that incorporates the specification described in part 1. In this diagram, indicate all the entities, subclasses, relationships (weak & strong), relationship cardinalities and degrees, total participations, attributes, and primary keys. In addition, specify whether each attribute is single-valued or multi-valued, stored or derived, and atomic or composite. In your design, you can make and state reasonable assumptions if they are not specified in the specification. Part 3: CIOM & EER Compare and contrast “CIOM?? with the “Enhanced Entity-Relationship Model??. (Please use part 1 and part 2 to provide examples in your discussion.) ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform N/A