DD COMP08002 CW Reqs T2 2010 2011 with updates

8/7/2019 DD COMP08002 CW Reqs T2 2010 2011 with updates

1/6

2010/2011 (Trimester 2)

1

Database Development

(COMP08002)

Coursework

Work Mode: 2 -3 students

Contribution: 50% of final mark

Submission date: By 3.00 pm Tuesday of Week 11

Demonstration date: During DD labs of Week 11

Coursework Overview

Your group is part of a consultancy company that specialises in the provision of database

systems. You are required to apply you expertise in the design and implementation of a

prototype database system that meets the requirements of a particular case study. There are

three case studies and each relates to the particular specialism of the student groups within

the class. You should use the case study that is most closely associated with your

programme.

You should not change any aspects of the case studies that are clearly stated. However, the

case studies are sometimes vague in places and so you may make some assumptions of your

own to clarify some aspects. However, if you do make assumptions, it is important that I

know what they are so that I understand the impact on your version of the database design

and implementation. Any assumptions/extensions to a case study should be documented in

your submitted report.


2/6

2010/2011 (Trimester 2)

2

Coursework Requirements

1. Entity-relationship (ER) model (20%)

Objective: To create an Entity-Relationship (ER) model of the data requirements for

your case study.

The information required to fulfil this part of the coursework is to create an ER model

(using UML notation) showing all entities, relationships (with names and multiplicity)

and all attributes (identifying any primary keys and foreign keys). This ER model

will represent the data and the relationships between the data of your case study.

2. Database Relational Schema (20%)

Objective: To derive a database relational schema from your ER model.

The information required to fulfil this part of the coursework is to create a database

relational schema, which has been mapped from your ER model. This schema will

represent the data and the relationships between the data of your case study as relations.

Please use the following notation to describe each relation of your database relational

schema.

Staff(staffNo, fName, lName, address, NIN, sex, DOB, deptNo)

Primary Key staffNo

Alternate Key NIN

Foreign Key deptNo references Department(deptNo) on Delete No Action on Update Cascade

Derived attribute age

Please check that each relation is in third normal form (3NF). Please consult with your

lecturer if you are unsure how to use normalisation to validate your relations as being in

3NF.


3/6

2010/2011 (Trimester 2)

3

3. Data Dictionary (10%)

Objective: To create a data dictionary to provide details about the attributes of the

database relational schema.

The information required to fulfil this part of the coursework is to provide a data

dictionary of all of the attributes listed in your database relational schema for your case

study in preparation for building these relations as SQL Server tables. A data dictionary

can have various columns but please include for each relation at least the following

columns: attribute name, description (meaning), data type (length), nulls (Yes or No)

and constraint (PK, AK or FK). The constraint column should also be used to identify

three examples of non-key constraints for example; gender column only accepts F or

M.

Three examples of derived attributes should also be included showing how the

associated calculations are to be performed. If you are unable to easily fit this

information into a column of your data dictionary, then present this information after the

data dictionary.

[On completion of the sections above, you may submit your coursework to your lecturer

for informal feedback on your proposed design. Any major errors will be identified and

should be corrected before proceeding to the sections that follow.]

4. SQL Server Database (25%)

Objective: To create a SQL Server Database to store the data required for your case

study.

To fulfil this part of the coursework is create a database with tables as described in your

data dictionary using Microsoft SQL Server 2008. Where appropriate set any table

constraints necessary to ensure that the data remains correct. Ensure that referential


4/6

2010/2011 (Trimester 2)

4

integrity (RI) is established between related tables. Createa diagram showing all of the

related tables in your implemented database. This diagram will be viewed during the

demonstration and should be included in your coursework submission.

Enter test data (approximately 5-10 rows) into each table. (Please ensure that your tables

contain sufficient data to demonstrate the queries in Section 5.)

5. Database Queries (20%)

Objective: To create and save SQL Server T-SQL queries in your database.

To fulfil this part of the coursework provide examples of the following queries that can

achieve the following.

(i) Retrieve all records and all columns from a single table.

(ii) Retrieve some records and only some columns from a single table.

(iii) Retrieve all related records and all columns from two tables.

(iv) Retrieve some related records and only some columns from two related tables.

(v) Retrieve all related records and only some columns from three related tables.

(vi) Retrieve all records and all columns from a single table and include a single

calculated column. Give the calculated column an appropriate name.

(vii) Retrieve all records and some columns from two related tables and include a

single calculated column based on columns from both tables. Give the calculated

column an appropriate name.

(viii) Retrieve some records from a single table using pattern matching.

(ix) Retrieve records from a single table that contain nulls in one or more columns.

(x) Retrieve records from a single table that do not contain nulls in one or more

columns.

(xi) Retrieve all related records from a single table that are ordered using two non-

primary key columns.

(xii) Retrieve one or more aggregate values (such as average or sum) for a single

table.

(xiii) Retrieve groups of records from a single table.


5/6

2010/2011 (Trimester 2)

5

(xiv) Retrieve some groups of records from two related table.

(xv) Retrieve aggregate values (such as count) for groups of records from a single

table.

(xvi) Retrieve some records and some columns from a table based on the value(s)

retrieved from another table.

(xvii) Retrieve some records and some columns from a table based on the value(s)

retrieved from another table, which are based on the value(s) from another table.

(xviii) Retrieve all records from one side of two related tables.

(xix) Retrieve all records from both sides of two related tables.

(xx) Retrieve all records from three related tables.

6. Coursework Demonstration (5%)

Objective: To discuss and demonstrate your coursework.

Your group is requested to discuss and demonstrate your coursework on Tuesday of

Week 11 to your lecturer. This will include discussions about your case study, how

you organised the coursework and demonstrations of your implemented database.

Marking Scheme

The marks allocated to the parts of the coursework are as follows.

Entity-Relationship (ER) Model (20)

Database Relational Schema (20)

Data Dictionary (10)

SQL Server Database and Tables (25)

SQL Server Database Queries (20)

Coursework Demonstrations (5)


6/6

2010/2011 (Trimester 2)

6

Paisley Campus

You are required to submit your coursework report to the School of Computing Student Office

(E217) on or before 4.00pm on Tuesday of Week 11. A copy of your SQL Server data and log

files and a SQL CREATE DATBASE script for your database should be uploaded to the

digital dropbox in the Database Development folder of Blackboard.

Please note that Database Development students at other UWS campuses should follow the

submission instructions issued by your lecturer.

Documents

DD COMP08002 CW Reqs T2 2010 2011 with updates