Course:COMP1302 Database Engineering Greenwich Coordinator: Ronan Cummins

Coursework Number: 1 of 1 Due: 14/11/2013

Contribution: 50% of course

Plagiarism is presenting somebody elses work as your own. It includes: copying information directly from the Web or books without referencing the material; submitting joint coursework as an individual effort; copying another students coursework; stealing or buying coursework from someone else and submitting it as your own work. Suspected plagiarism will be investigated and if found to have occurred will be dealt with according to the procedures set down by the University. All material copied or amended from any source (e.g. internet, books) must be placed in quotation marks and in italics, with a full reference to the source directly underneath the material. Your work will be submitted for electronic plagiarism checking. Any attempt to bypass our plagiarism detection systems will be treated as a severe Assessment Offence.

Coursework Submission Requirements An electronic copy of your work for this coursework should be fully uploaded by midnight (local time) on the Deadline Date. The last version you upload will be the one that is marked. For this coursework you must submit a single Acrobat PDF document. In general, any text in the document must not be an image (ie must not scanned) and would normally be generated from other documents (eg MS Office 2007 using "Save As ..PDF"). For this coursework you must also upload a single ZIP file containing supporting evidence. There are limits on the file size. Make sure that any files you upload are virus-free and not protected by a password otherwise they will be treated as null submissions. Comments on your work will be available from the Coursework page on the Intranet. The grade will be made available in BannerWeb. You must NOT submit a paper copy of this coursework. Coursework Regulations If no submissions were made before the deadline, coursework submitted up to two weeks late that meets the criteria for a pass will be treated as a referral. It will be subject to university regulations for referral work. Coursework submitted late without an Extenuating Circumstances claim will receive a ZERO

grade. If you have extenuating circumstances you may submit your coursework up to two weeks after the published deadline without penalty but this is subject to acceptance of your claim by the School Extenuating Circumstances Panel. If your claim is rejected then you will receive a zero grade for your work. Coursework submitted more than two weeks late will be given feedback but a grade of nonsubmission will be awarded regardless of any extenuating circumstances. However, if your Extenuating Circumstances claim is accepted then the Extenuating Circumstances Panel will recommend to the Progression and Award Board that you be permitted to retake a different item of assessment at a future assessment point. All courseworks must be submitted as above.

Specification

This is an individual coursework. There are TWO components to the coursework. 1. Your system will be assessed at a laboratory demonstration/viva where the database and any software that you produce will be viewed and you will be asked to answer questions about the system you have developed. This is important and you should treat it as an examination. 2. You will need to produce a shortreportwith some design documents included.

Scenario

Consider a database system for the organisation of fixtures and results in a soccer league. The data requirements are summarized as follows:

The people involved in the league include players, coaches, managers, and referees. Each person is identified by a unique personnel id. They are also described by their first and last names along with the date and place ofbirth.Players are further described by other attributes such as their position on the field (goal-keeper, defender, midfielder, or forward) and have a squad number associated with them.

Teams are uniquely identified by their names. Teams are also described by the city in which they are located and the division and league in whichthey play (such as premier division or first division).Teams have one manager, a number of coaches, and a number of players. One of these players is the captain. At the beginning of each season all fixtures should be available to view in the database. Each team plays every other team twice (once at home and once away). Games are played between two teams with one assigned referee. For any particular game on a particular

date, there is one team designated as the hometeam and the other team designated as the away team. Once the game has taken place, the final result of the game is recorded. The score and the scorersare recorded for each team.

Requirements

1. Using Chens or Crows Foot notation, design an Enhanced Entity Relationship (EER) model for the soccer database in a modelling tool of your choice. All entity types, their attributes and relationships must be clearly shown. You will also be required to show all cardinality and participation constraints. Any enhanced features used (e.g. generalisation/specialisation) must be indicated. 2. Map the EER model devised in (1) into a set of relations in the relational data model. Specifically state anyenhanced features used and indicate how you mapped these to the relational model. Clearly state any de-normalization, if any, in all your relations and clearly state the reasons for de-normalizing relations in your implemented solution. 3. Using appropriate SQLcommands create a set of database tables using any relational database. Your tables should also show all constraints applied at either column or table level. 4. Populate the database with a small amount of data. The data should be meaningful but does not need to be extensive.The following sites may be useful for quickly generating data: http://www.databasetestdata.com/ http://www.generatedata.com/ 5. You should produce, demonstrate, and document the following SQL queries for your system: List the managers of each team. Output the full name of the top scorer in the league with the number of goals scored. Output the average number of goals per game of all games played. List all of the games that were played in a particular city. List all players who have played a game that was refereed by a particular referee (choose any referee).

6. Create a database view for your system as follows: Produce a list of fixtures yet to be played along with the date of each game. Notes [1] You do not need to include an extensive selection of data; the emphasis is on demonstrating your technical and design skills rather than including a wide range of data. [2] Any assumptions above the basic specifications stated must be clearly stated and justified.

Deliverables 1.Interim Submission (Optional)

You should submit your conceptual design of the database for feedback. The idea is to get feedback on conceptual design and its subsequent logical database design mapping.
2. Implementation (Mandatory) You will be required to demonstrate your system in the laboratory.You will be assigned a time to present your work. There are marks available for being prepared and demonstrating your work in a clear and logically coherent manner. Treat the demonstration as an examination.. Failure to demonstrate your work to a tutor will result in a failing grade for the coursework. 3. Report (Mandatory) A short report covering requirements 1 6. Show screen shots as outputs to queries. Write a short paragraph on what you would do differently, if you were to do this again. The report should mostly consist of what you will be demonstrating so it will not be a major task to compile.

Grading Criteria
To pass this coursework you must demonstrate: competence in conceptual database design of database models competence in mapping your conceptual data model to a logical database competence in database implementation competence in querying the database implementation an appreciation of the underlying design and implementation principles

Your grade will depend on how well you meet these criteria. A portion of the available marks will be given for above minimal specification features of your implementation.

You will fail the coursework if you do not demonstrate your system to your tutor.

Assessment criteria: Grading:

You will be graded according to the following criteria:

70-100%

all requirements completed to an excellent standard

60-69% all requirements completed. However, there are a number of minor deficiencies in significant areas. 50-59% all requirements completed. However, significant improvements could be made in many areas. 40-49% all requirements completed. However, significant improvements could be made in all areas. 30-39% all requirements attempted but the overall level of understanding and performance is poor. 0-29% there are requirements missing or completed to a very inadequate standard which indicates a very poor or non-existent level of understanding.

Marking Sheet (Place a tick in the box that you deem to be most indicative of the quality of the work)

No % Conceptual Database Design (EER) Relational schema Database Attempt Poor to Very Poor Fair Good Very Good Excellent

20

10

20

Implementation Views and Queries Report

20

20

15

Demonstration 10 Quality Data Used 5

Totals

100