0% found this document useful (0 votes)
12 views

COMP 1845 Coursework Brief Part1 and Part2 2023-24 Term 1

Uploaded by

Chính Khang Mai
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views

COMP 1845 Coursework Brief Part1 and Part2 2023-24 Term 1

Uploaded by

Chính Khang Mai
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Term 1 Coursework Assessment Brief COMP1845 (2023/24) Academic session.

COMP1845 (2023/24) Systems Master CRN: Contribution: 100%


Term 1 Development. Coursework
Module leader Title: Car
Dr Solomon H. Ebenuwa Database System Deadline Date:
Feedback and grades are normally made available within 15 working days of the coursework deadline
1. Demonstrate an understanding of when and how to provide database solutions, based on
organizational needs and user requirements.
2. Use appropriate tools and techniques to design a relational database solution based on
organizational needs and user requirements.
3. Implement a functional relational database solution to meet organizational needs and user
requirements.
4. Test and document the database solution against all established requirements.

Plagiarism
Is presenting somebody else’s 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 student’s 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 referenced correctly according to the reference style you are using.
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.
The A1 rating of this assignment is 2.

Coursework Submission Requirements


An electronic copy of your work for this coursework must be fully uploaded by 11:30 PM. on the
Deadline Date of 14 Dec 2023 using the link on the coursework Moodle page for COMP1845.
• For this coursework, you must submit a single Acrobat PDF document. One single ZIP file of your
development code must be uploaded on the COMP1845 Moodle page using the appropriate submission
link. Your developed system should be standalone on your personal PC or school Server.
• In general, any text in the document must not be an image (i.e., must not be scanned) and would
normally be generated from other documents (e.g., MS Office using "Save As. PDF"). An exception to
this is hand-written mathematical notations, but when scanning, ensure that the file size is not excessive.
• There are limits on the file size. Please ensure that you meet that.
• Make sure that any files you upload are virus-free and not protected by a password or corrupted
otherwise they will be treated as null submissions.

1
• Your work will be marked online and comments on your work and a provisional grade will be available
from the Coursework page. The grade will be made available in the portal.
• You must NOT submit or mail any coursework to your or any tutor.
• All coursework must be submitted on the COMP1845 Moodle page.
Detailed Specification.

This coursework is worth 100% of the total marks for this course. This coursework must be completed
individually. Please read this entire specification very carefully so that you are fully aware of the
requirements.
The University website has details of the current Coursework Regulations, including penalties for late
submission, procedures for Extenuating Circumstances, and penalties for Assessment Offences.
This coursework must be completed individually and made up of two parts, Part 1 and Part 2.

Part 1 (Design and Implementation of Database System) 60%


London Autos has several locations within London and its surroundings, from its humble beginning a
decade ago in an east London garage, the business has expanded into a multi-million-pound business.
Their main business is selling Cars both new and used, Car parts and accessories... The Cars on sale could
either be by finance or customers may choose to pay by themself. Those who choose to pay are usually
the top-end customers who have the habit of changing cars whenever new models are released by the
manufacturer while their old cars are returned to the company for reselling to other buyers interested in
used cars. London Autos has kept most of its records in a flat file in a central location. The following
records are kept.
Car name, model number, description, make, manufacturing date, and other necessary
information. The car accessories on sale are seat covers, wheel covers, floor covers, car manual
locks, and many more. All other records kept are all the information for customers, Sales Agents,
purchases, and many more is kept in flat Excel files, but this has grown astronomically over the years. It
has now become necessary to use a relational database to keep these records and other transactions for
London Autos.
Your task is to design and develop the first prototype relational database that will be used to record
all business transactions at London Autos.
The above scenario is the basic guideline, as a developer, you are free to incorporate any component and
database objects you may deem necessary. A typical database is not a standalone, your design and
implementations should allow for future integration with any external application like the website
backend and usage of other departments for example, accounting, human resources admin etc.
Specifically, your design and implementation must show the following.

1
a. Demonstrate evidence of requirements elicitations to obtain some of the relevant
requirements, you should show clearly the scenario analysis and identify entities from the
scenario for the database design. [15 marks]
From this scenario, I decided to create a survey and do an interview to collect information.
For example, I am going to interview a random customer to get an information about them
we can analysis and identify entities and their attribute for designing the database:

Entity: Car
Attributes:
• Car ID
• Supplier ID
• Car name
• Model number
• Description
• Make
• Manufacturing date
• Type (new or used)
• Quantity
• Price

Entity: The car accessory


Attributes:
• Accessory ID
• Accessory Name
• Color code
• Size
• Description
• Quantity
• Price

Entity: Supplier
• Attributes:
• Supplier ID
• Supplier Name
• Contact Number
• Email
• Address
1
• Supplier Type (customer supplier or dealer supplier)
• Company Name
• Additional notes (e.g., reputation, duration of cooperation, pricing policy...)

Entity: Car Supplier


• Attributes:
• Car Supplier ID
• Supplier ID
• Car ID

Entity: Accessory Supplier


Attributes:
• Accessory Supplier ID
• Supplier ID
• Accessory ID

Entity: Sale Agent


Attributes:
• Sale Agent ID
• First Name
• Last Name
• Phone Number
• Email Address
• Address
Entity: Car Sale Agent
Attributes:
• Car Sale Agent ID (CSA ID)
• Car ID
• Sale Agent ID
Entity: Customer
Attributes:
• Customer ID
• First Name
• Last Name
1
• Phone Number
• Email Address
• Comment
• Customer Type (New customer, Potential customer, Regular customer and Vip customer)

Entity: Car Purchase


Attributes:
• Car Purchase ID
• Car Supplier ID
• CP date (Car Purchase date)
• Quantity
• Amount

Entity: Accessory Purchase


Attributes:
• Accessory Purchase ID
• Accessory Supplier ID
• AP Date (Accessory Purchase Date)
• Quantity
• Amount
Entity: Car Sale
Attributes:
• Customer ID
• Car ID
• Sale Agent ID
• Sale Date
• Quantity
• Amount
• Payment Status
Entity: Car Installment
Payment of Customer’s Car ID (PCC ID)
CSA ID
P
1
Entity: Company Payment
Attributes:
• Company Payment ID (COP ID)
• Car Purchase ID
• Accessory Purchase ID
• Payment Method
• Amount Paid

b. Draw and design a full-fledged ER diagram from the above scenario with the physical
properties of the entities like relationships, datatypes, cardinality etc from the scenario. [10
marks]

c. Demonstrating evidence of normalization to 3rd Normal from the above scenario. [10 marks]

d. Demonstrating the implementations by creating tables and other necessary database objects
[10 marks]
e. Demonstrate the insertion of more than ten data into each table in the database
[5 marks]
f. To show that your database is functional, you must state two SQL queries that involved
joining two or more of your tables and execute them.
[10 marks]
The answers to Part 1 (a to g) must be evidenced with clear screenshots annotation and explanations of
each answer where necessary.

Part 2 (Data Manipulation) (5 * 8 = 40%)

You have been provided with a database called “AdventureWorks ”. Please attach this database on the
MySQL (DBMS) and use it to answer the following questions.

a. write a query in SQL to return all rows and columns from the employee table in the
Adventureworks database. Sort the result set in ascending order on jobtitle.
1
b. write a query in SQL to return all rows and columns from the person table using table aliasing in
the Adventureworks database. Sort the output in ascending order on lastname.

1
c. write a query in SQL to return all rows and a subset of the columns (FirstName, LastName,
businessentityid) from the person table in the AdventureWorks database. The third column
heading is renamed to Employee_id. Arranged the output in ascending order by lastname.

1
d. write a query in SQL to return only the rows for product that have a sellstartdate that is not NULL
and a productline of 'T'. Return productid, productnumber, and name. Arranged the output in
ascending order on name.

1
e. write a query in SQL to return all rows from the salesorderheader table in Adventureworks
database and calculate the percentage of tax on the subtotal have decided. Return salesorderid,
customerid, orderdate, subtotal, percentage of tax column. Arranged the result set in ascending
order on subtotal.

1
f. write a query in SQL to create a list of unique jobtitles in the employee table in Adventureworks
database. Return jobtitle column and arranged the resultset in ascending order.

1
g. write a query in SQL to calculate the total freight paid by each customer. Return customerid and
total freight. Sort the output in ascending order on customerid.

h. write a query in SQL to find the average and the sum of the subtotal for every customer. Return
customerid, average and sum of the subtotal. Grouped the result on customerid and salespersonid.
Sort the result on customerid column in descending order.

1
For each answer in Part 2 (a to h), you must show the screenshot of each query and the result of executing
the queries.

End:

You might also like