Search for project
More than 2000 projects issued through our platform and this
amount increases very fast.
SQL DATABASE WITH REPORT (ID:4188)
| Project Creator: |
creesi
FC Member For 6257 Days
Credits 20 Completed Proj. Num. 0 / 5 Total payment USD 500.00 Avg Daily Online 0.00 h (From 21/5/2007) Available on MSN/Skype Yes Last Login 4/17/2008 Peers Rating 0.00% 
|
|---|---|
| Budget: | 250 - 500 |
| Created: | 4/14/2008 8:49:39 AM EST |
| Bidding Ends: | 4/17/2008 8:49:39 AM EST ( Expired ) |
| Development Cycle: | 2 Days |
| Bid Count: | 3
|
| Average Bid: | 460.00 |
| Project Description:
CASE STUDY: A DBMS for a Record Label Badnoise Records have decided to update the system used to store their information on musicians. They have wisely chosen to hire you as a database designer (at your usual consulting fee of ?2000/day). Each musician that records at Badnoise must provide a National Insurance (NI) number, a name and a date of birth. Musicians, being ill-paid, often share the same address, and no address has more than one phone. Each instrument that is used in a song recorded at Badnoise Records has a name (e.g. guitar, bass, piano, bongo, etc.). Albums recorded at Badnoise Records have a title, a copyright date, an album identifier and both the start date and the end date of production. Each song recorded at Badnoise Records has a title, an author, a length (i.e. how many minutes it lasts) and a production date. Each musician may play several instruments, but a given instrument may be played by only a musician at the time (for example, a guitar cannot be shared between musicians). Each album must have at least one song on it, but a song cannot appear on more than one album. Moreover, songs do not have to be associated to an album. Each song is performed by one or more musicians, and a musician may perform a number of different songs. For each album there is exactly one musician that acts as its producer. A musician may produce several albums. YOU ARE REQUIRED TO: 1. Develop an E-R Model based on the above case study, including any necessary assumptions. 2. Normalise the E-R model produced in 1 above. 3. Implement a relational database based on the normalised E-R model produced in 2 above. 4. Accommodate SQL queries both for base relations and views, such as ??ist all musicians collaborating on an album?? from the relational database produced in 3 above. DELIVERABLES: A 5000-word coursework report, including diagrams where necessary, but not exceeding 25 pages in length documenting 1 to 4 above, i.e. the development of the E-R model, its normalisation, the implementation of the relational database and the query transactions. Query results should be in the form of taking screenshots of the results of your queries produced by the database and attached to the project document. Query results do not count towards either the 25 page or the 5000 word limits and diagrams do not count towards the 5000 word limit. Please number your pages and include your student registration number on every page. Please use word format, and use your registration number as your file name. Your coursework report must include a table of contents which does not count towards either the 25 page or the 5000 word limits. You should prepare and submit the coursework report according to the Department's instructions for assessments. All the submissions have to be done via u-Link. You should make sure that you are fully aware of the Department's policy on plagiarism and the marking of joint work. You should be aware that you cannot later claim that you did not know the rules and regulations; like all of us working at Brunel, you must make yourself familiar with them. If you cannot do any work on time, you should look at the Department's instructions on what to do. DO NOT ASK FOR EXTENSIONS!!! (look at the Department's instructions on what to do instead) Coursework deliverable deadline: 11pm, Friday 18/04/08 YOUR COURSEWORK REPOPRT SHOULD CONTAIN: All Assumptions ??From the description of the case study given, make your assumptions on the usage, e.g. most frequently used query types, how many queries will be performed, number of users etc. Identified Entities and their Attributes ??From the description of the case study given, identify the main entities you think may be appropriate and their attributes. Identified Relationships between Entities ??Identify and show the relationships between the entities, indicating participation and cardinality constraints. Conceptual model ??Construct the conceptual model and state any assumptions you have made about the entities, their attributes or relationships. Logical model ??Using the correct procedures, construct the logical model from the conceptual model and explain what you have done. If your conceptual model is already logical, explain why. ??Explain how your model supports query transactions for base relations and views. You need to demonstrate that your database stores the required data and that the required relationships between different entities are maintained. Relations ??Now produce your tables from the logical model Normalised Relations ??Normalise your tables to 3NF, showing all dependencies etc. If certain tables (or all) are already normalised, say why. This step includes showing all dependencies and explaining step-by-step the process of normalisation (e.g. if you think that the tables are in 2NF say why and then convert them to 3NF) and having practical demonstrations. Query transactions using SQL ??You must justify why the person using the application may want to do the type of query you are doing. Make sure you say why the query is being done. ??All queries should be (briefly!) justified, i.e. you should explain why a particular query is needed. ??Once you have carried out a query, say if your results were as expected - if not, why not? ??All results should be confirmed and explained. ??If all of your queries are very simple then you will not gain a lot of marks. The mark will depend on the appropriateness and complexity of queries/views/reports, as well as the quality of explanations given. The appropriateness of queries refers to their relevance to the business case (i.e. different queries would be required by different people within the same business). Complex queries would include joins (perhaps more than one) and/or subqueries. A short (1-3 pages) discussion reflecting on the process of conducting the coursework and discussing the resulting system. For example: ??Discuss any problems you encountered. What was the most difficult step? ??Discuss your solutions. What are the strengths and limitations of your proposed solutions? ??How would you improve your system? What extensions would you suggest? ??Discuss any alternative design solutions, are there any? |
|
| Job Type | Other |
| Attached Files: | N/A |
