Need help? We are here

Task 1.1: Selection of the case upon which the database design and implementation is to be based
First, you need to identify a suitable case study (your choice or a choice from the list provided in the appendix) from which to derive your database requirements. This may be a situation based on a company with which you are familiar or in which you are (or have been) employed, or may be one (or based on one) that you have read about within the trade or academic literature or identified from their web presence. You need to ensure that your business situation is suitably complex to provide you with at least four strong entities, and at least one specialisation: generalisation structure, yet suitably scoped so as to not require a huge quantity of resultant tables (i.e., normally no more than 15) and subsequent input of sample data for querying purposes. It must not be based on a library (video, book, CD or film) and not just solely about orders of products. It should not be one that is based on any previous examination scenarios for this module, nor any exercises given to you within your DS&D module lecture material and/or module pack. Once researched and identified, a written scenario needs to be produced that (a) provides relevant background information on the organisation (e.g., its purpose, its principal operations/structure, its products/services, its target
markets, etc.), and (b) provides an overview of what operations a database would need to support. Your scenario will probably be no less than one side of A4, but no longer than three slides of A4.You should aim to complete this task by the end of Week 8.
Task 1.2: Provide a conceptual database design for your scenario & the list of enterprise rules being modelled.
The second task is to develop an EER Diagram that captures the detailed requirements for the database system that you identified within the scenario you wrote to satisfy Task 1.1. The EER Diagram needs to show any weak and strong entities, the primary keys for strong entities, and any relationships between entities (including any generalisation: specialisation structures). *:* relationships must be decomposed, and any actual traps identified should be eliminated using appropriate methods. For each entity, there should be an associated written list of all the attributes that the entity possesses which are not written on the EER Diagram. Any assumptions made during conceptual database design (i.e., anything that you assume that is not written in your Task 1.1 scenario) should be listed.As well as the conceptual database design, you also need to provide the exact list of enterprise rules that your EER Diagram is diagrammatically representing. (Every relationship will need at least one enterprise rule, depending on its multiplicity and degree. Each binary relationship will typically have two enterprise rules associated with it, for instance.)