This assignment requires the development of a database design (both conceptual and logical) for an appropriate business situation of your choice, and then implement and subsequently query an ORACLE database that is derived from your database design. The assignment is divided into two stages, with each stage carrying 50% of the assessment mark. The first stage involves selecting a case study and providing a conceptual database design, while the second stage involves providing a logical database design and Oracle SQL implementation/querying. The deliverables include the case scenario, enterprise rules, conceptual and logical database design, SQL code for creating tables and indexes, and six queries with brief explanations.
| 4 pages
| 1389 words
| 126 views
Trusted by 2+ million users, 1000+ happy students everyday
Title of the Assignment: EER and SQLName:Database Systems and DesignThe learning outcomes that are assessed by this coursework are:1.Select and analyse a problem domain so as to identify data requirements in businesses.2.Design and implement a database system for the identified requirements using database modelling techniques and appropriate data description and manipulation languages.Tasks to be undertaken:You are to develop a database design (both conceptual and logical) for an appropriate businesssituation of your choice, and then implement and subsequently query an ORACLE database that is derived from your database design. For this assignment you must work individually. There are two stages to the work you need to undertake: each stage is worth 50% of the assessment mark. Perform Stage 1 first, then Stage 2!Tasks to be undertaken:You are to develop a database design (both conceptual and logical) for an appropriate business situation of your choice, and then implement and subsequently query an ORACLE database that is derived from your database design. For this assignment you must work individually. There are two stages to the work you need to undertake: each stage is worth 50% of the assessment mark. Perform Stage 1 first, then Stage 2!Stage 1 (Scenario and Conceptual Database Design):Task 1.1: Selection of the case upon which the database design and implementation is to be basedYou need to identify a suitable case study 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. 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. Also provide assumptions for your scenario.You should aim to complete this task by the end of Week 6.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.)Stage 2: Logical Database Design and Oracle SQL Implementation/queryingTask 2.1: Provide a Logical Database Design for your scenarioFrom your conceptual database design, derive a corresponding set of well-normalised tables. Remember to indicate all primary and foreign key fields for each of the tables using suitable and consistent notation. All key and any non-key attributes should be listed within each table.Task 2.2: Create the tables using Oracle DBMSYou need to create all the tables that you identified within your logical database design. Make sure the appropriate fields are defined as key, and that other suitable data integrity rules are enforced. Each of your tables should contain your user name as part of the table name. E.g. if your user name is ‘mit10sf’, then if you needed a Car table then you would create a table ‘mit10sfCar’. (Hint: make sure you create the tables in an appropriate order – for instance, those that have foreign keys cannotbe created first – why? Think about it!).Task 2.3: Create the four most useful indexes on your tablesYou need to create a total of FOUR appropriate indexes on the tables using the CREATE [UNIQUE]
Found this document preview useful?
You are reading a preview Upload your documents to download or Become a Desklib member to get accesss