University of Derby

The School of Computing and mathematics

In-course Assignment Specification

Module Code and Title: 7CS082 Database development
Assignment Title:
CW: Database Development

Assessment Tutor: Weighting Towards Module Grade: 100%

Dr. MAQBOOL HUSSAIN
Date Set: 28/09/2022 Hand-In Deadline Date:
Part 1: at 1200pm, 18/11/2022 (Friday, Week 8)
Part 2: at 1200pm, 12/01/2023 (Thursday, Week 12)

Late Submission

Recognising that deadlines are an integral part of professional workplace practice; the University expects students to meet all
agreed deadlines for submission of assessments. However, the University acknowledges that there may be circumstances
which prevent students from meeting deadlines. There are now 3 distinct processes in place to deal with differing student
circumstances:
1) Assessed Extended Deadline (AED): Students with disabilities or long term health issues are entitled to a Support Plan.
2) Exceptional Extenuating Circumstances (EEC): The EEC policy applies to situations where serious, unforeseen
circumstances prevent the student from completing the assignment on time or to the normal standard. Students who
submit a successful EEC claim will usually be required to complete a different assessment to that which was originally
set. http://www.derby.ac.uk/eec
3) Late Submission: Requests for late submission will be made to the relevant Head of Discipline (or Head of Joint
Honours for joint honours students) who can authorise an extension of up to a maximum of one week.
http://www.derby.ac.uk/campus/support

Level of Collaboration:
NONE

Learning Outcomes covered in this Assignment:

1. To demonstrate a critical and in-depth awareness of the theory, methods, design issues, development,
deployment, and maintenance of modern database systems.

2. To demonstrate a mature and culturally sensitive ability to critically evaluate and select database
products, development methodologies and implementation strategies, and apply these to design and
implement database systems to a professional standard within a globalised, industrial context.

Sensitivity: Internal
 Assignment

Airline Company
We want to design a database for an airline company to underpin a system that will store information
on flight schedules, passengers and their bookings, and the staff assigned to the planned flights. There
is a particular need to track pilots and their ability to fly certain aircraft types.

The database will allow users to know:

 The passengers of a flight,
 The crew of a flight,
 What plane is assigned to a particular trip,
 The pilot's type rating.  A type rating is a license a pilot is granted to fly a particular type of
aircraft.
 What are the flight schedules: e.g. Paris-Caracas (weekly schedule), etc?

Staff: Each member of staff in the company is identified by a number (EMPNUM), and is described by
his or her name (SURNAME), given name (NAME), address (ADDRESS), telephone number (PHONE)
and his or her monthly salary (SALARY). Among the staff, pilots are distinguished to indicate the type
ratings they hold and the planes they can fly with these ratings.

Airplane: Each airplane owned by the company has a serial number (NUMSER). Each airplane is also
identified by its manufacturer and model number. Together, these constitute what we call the
aircraft: e.g., BOEING 747.

Passenger: Passengers are identified by their surname (SURNAME), given name (NAME), address
(ADDRESS), telephone number (PHONE). A departure is a flight on a certain date (DATE). Flights are
identified by a number (FLIGHTNUM), origin (ORIGIN) and a destination (DEST) and various
intermediate cities (each pair of connected cities defines a stretch). For each city served, we record
the time of arrival (ARR-TIME) and departure time (DEP-TIME) of the flight concerned.

The planes that can be assigned to a flight needs to be recorded. For each flight, a pilot must have
been appointed and a particular airplane must have been allocated.

You are required to design, develop and produce two implementations of a database for the airline
company. The assignment will be implemented in two parts:
 Part 1: Database design and optimisation (learning outcome 1)
 Part 2: Implementation of queries and interactions with the database (learning outcome 2)

Modelling must be shown in the form of an entity-relationship diagram. For simplicity, it is advised
that in a first stage of the design, assume that each flight has no connection. Later, update the design
to assume that a flight can have several connections and that passengers and crew may change during
travel.

Requirements
Part 1: Database design and optimisation
Weighting: 60%

Individual student must produce a comprehensive ER diagram of the database and produce two
implementations of the design. To produce the ER diagram, you may use the ER modelling
facilities of either MS Access or MySQL Workbench. The implementations must be done in a
relational data base management system (DBMS) of your choice, such as MySQL, PostgreSQL,

Sensitivity: Internal
 Oracle Database, Microsoft SQL Server, MS Access etc. You need to implement your design in two
different DBMS. Moreover, upon completing the schema design, you will need to populate the
databases with some test data (i.e., random fake data) to validate the design. The
implementations should include sufficient test data to demonstrate necessary functionalities.

Follow these STEPS carefully. You are required to:

1. Produce a database design report to detail the implementation process including the
Entity Relationship Model; normalisation process; detailing of data types, candidate keys,
primary keys, constraints (foreign key and CHECK), etc.; Coding of tables and primary and
foreign key creation; Query statements; Values insertion; Update and Delete data, etc.
2. The report should provide a justification and a critical evaluation of the two different
implementations provided. Normalisation, optimisation and performance of the database
design should also be discussed in the report.
3. A copy of source code and database files for the two implementations should be
uploaded with the report.
4. The word limit for Part 1 report is 1500 words.

Part 2:
Implementation of queries and interactions with the database
Weighting: 40%

You are required to use one of the implementations produced in Part 1 to develop and
implement a front-end system that enables end-users to interact with your database. The system
should include sufficient test data to demonstrate the core functionalities of querying and
interactions. (Note: Your MS-Access (or other front-end) must connect to the SQL database
backend. Use of MS-Access to construct both a front-end and a back-end without connection to
one of your SQL back-end implementations will receive a failing grade).

Follow these STEPS carefully. You are required to:

1. Take into account the feedback given to the first part of your assignment to improve
your database design.
2. Produce a detailed report of approximately 1500 words in length where you provide
justifications/evaluations for the database selection, and upgraded database schema
design if needed. In addition, you will need to detail
a. the front-end user interface, frontend and
b. backend functionalities,
c. the SQL queries you developed.

Note: you can update the database design in the light of feedback provided in Part 1 but
bear in mind that this will not affect awarded grade for Part 1. However, it might
increase your marks in Part 2 of the assignment.
3. Provide details about the front-end development and implementation process including
the navigation map and a user manual explaining the operation and functioning of the
system. The report should also provide a reflection on the use of the chosen
technology.
4. An assignment demo and peers’ feedback will take place during the teaching session of
Week 12.
5. A copy of the complete source code and database files for developed queries and
front-end system should be uploaded with the report.
6. The queries and interactions should reflect the use of the system described above.

You must demonstrate the following basic functions:

1. Manage staff (add/delete/update and view)
2. Manage flights (add/delete/update and view)
3. Manage machines (add/delete/update and view)

Sensitivity: Internal
 4. Browse/search:
o Booking details
o Machine details and list of pilots eligible to fly it
o Passengers and their list of bookings
5. Make a new booking:
o For one or more passengers
6. Generate reports:
o Pilots schedule by month
o Number of passengers by flight
o Number of working hours for all pilots (ascending and descending order)
o List of the company destinations and their schedule
7. Cancel or amend a flight booking.

Apart from the above 7 functions, correctly implementing more relevant functionality will increase
your marks.

Feedback
An in-progress check will take place during the practical sessions on week 6 and week 11. The in-
progress check is to provide you a formative feedback of the progress made so far and recommend
you possible areas for improvement prior to the formal submission. Summative feedback and marks
will be given in Turnitin within 15 working days after your submission.

Formal submission
For both parts of the assignment, you will have two submission points for report and source code,
respectively:
1. Turnitin submission point for reports

Formatting Requirements: Please submit each report as a single Word or PDF document in the
Blackboard Assignment Submission link for the module. The file name must use the following format:
For part 1: nnnnnnnnn-7CS082-report-part1.docx
For part 2: nnnnnnnnn-7CS082-report-part2.docx
where nnnnnnnn is you student number

2. Submission point for the source code, database files of design, implementations, and the
front-end development. If the student is using a specific database development tool outside
of those mentioned above, it has to be provided as well.

Formatting Requirements: All data and source code should be included in a single zip file and submit
in the Blackboard Assignment Submission link for data. The file name must use the following format:
For part1: nnnnnnnnn-7CS082-data-part1.zip
For part2: nnnnnnnnn-7CS082-data-part2.zip
where nnnnnnnn is you student number

Please note that all assignments will be checked for plagiarism. The students will be provided with a
“Plagiarism Check-points”. Before submitting to original submission point, you can generate
plagiarism report. Any submission with more than 20% plagiarism resulting in degradation of
points.

Failure to submit all these items by the specified deadline and without an authorized extension will
result to a FAIL grade. For detailed information about Late Submissions terms see the “In Course
Assignment Specification” page.

Sensitivity: Internal
 Submission of your work
The University of Derby has now implemented a general policy of anonymous marking and all the
Turnitin Submission system will hide your name from your tutors, until after moderation. This module
has an exemption due to the face-to-face nature of the formative reviews; your tutor will need the
student number to link your source-code with your report for your course work. As a result, you
MUST ensure that you include your student number in the submission title of your work for both
your completed report and source code.

If you do not do this, it will be impossible for your tutor to provide any formative or summative
feedback during the face-to-face formative reviews and final marking, because they will not be able to
find your work.

Marking Scheme
The following is an ‘indicative’ marking scheme and seeks to outline some broad concepts and
principles by which the assignment will be marked.

Sensitivity: Internal
 Assessment Criteria for assignment 1: Database design and optimisation (60%):
Criteria 5-39% 40 – 49% 50 – 59% 60 – 69% 70-79% 80-89% 90-100%
Choice of material. Superficial. Little Inadequate evidence All of the material is Report High academic Very high standard
Academic research. insight shown in of some insight into appropriate. The student demonstrates a learning ability ability achieved.
Introduction and outline selection of the subject area. has covered most good achieved.
of the key issues material. Covers subject areas but understanding Exceptional
identified. few/none of key contains a few errors. of the subject quality of output Referencing is
(including the subject issues. area covering all showing creative consistently used,
introduction of the key issues. and innovative complete and accurate.
system and the Contains very flair.
justification of selection few errors.
of the database)
(20%)

Logical organisation of Little originality. Arguments are The student has A clear and High Very high standard
thoughts and arguments; Has failed to get to unclear and demonstrated a clear useful theme is understanding ability achieved. Meets all criteria in
brevity, clarity, and grips with the underdeveloped. understanding of the developed. and exposition of 80-89% range, plus
understanding. subject. Inadequate problem area. A theme Insight into relevant issues Relevant technical skills demonstrates
(including Normalisation, discussion Does not Failing to is present, but implications. that shows insight are demonstrated at a exceptional ability
E-R diagram and Query show full demonstrate an underdeveloped and Clear and and draws very high level. and insight,
statements) understanding of adequate contains a few errors. concise together the indicating the highest
(60%) what is required. understanding. arguments. chosen subject Referencing is level of technical
Statements contain Contains very key features into consistently used, competence.
many errors. few errors. a theme, no complete and accurate.
errors.
Summary and Little or no Failing to draw out Analysis draws out Analysis draws Innovative and Very clear future work
Conclusions rationale. Limited if basic lessons learned. important lessons out appropriate well-formed and improvement have
(10%) any conclusions / None or inadequate learned and tries to conclusions recommendation been discussed.
recommendations recommendations develop a theme. Some with supporting s made. Clearly
missing or given. supported recommendatio structured and
inappropriate recommendations are ns. logically
reached given. developed

Sensitivity: Internal
 arguments.
Report writing: Riddled with errors, Frequent errors. Occasional errors. Few errors. Free of errors. Very high standard
(10%) incoherent and Somewhat Generally coherent. Lack Coherent and High coherence ability achieved.
disjointed. incoherent and of clarity in places. clearly and clarity of
disjointed. expressed. expression. Referencing is
Many references Referencing and citation consistently used,
are inconsistent Some references are style is consistent Referencing and Referencing and complete and accurate.
between the text inconsistent between between the text and citation style is citation style is
and the list; a the text and the list; the list; reference list consistent correct and
number of mistakes reference list with with some mistakes. between the consistent
in the reference many mistakes. text and the list;between the list
list. reference list and the text;
with only a few reference list
minor mistakes. completely
concise without
errors.
% Mark Nothing of Merit: Nothing of value is contained in the submitted work. The work presents information that is irrelevant and unconnected to the task; no evident
1-4% awareness of appropriate principles, theories, evidence or techniques

NS Non-submission: No work has been submitted

Z Academic offence notation Applies to proven instances of academic offence

Assessment Criteria for assignment 2: Implementation of queries and interactions with the database (40%):

Criteria 5-39% 40 – 49% 50 – 59% 60 – 69% 70-79% 80-89% 90-100%

Sensitivity: Internal
Design and Failed to demo the Failing to present Appropriate design and Good design Very good design Very high standard
Implementation of the system properly; basic knowledge and implementation of the and and ability achieved.
system (40%) Failed to present understanding of the system, but few errors implementation implementation
the knowledge and main concepts and found in SQL query of the system, of the system; no Relevant generic skills
understanding of key theories. The SQL statements; very few errors error found inside are demonstrated at a
the main concepts query statements found in SQL SQL query very high level.
and key theories. contains many No reflection to the query statements;
errors; feedback of the statements; Referencing is
assignment 1. Clearly reflection consistently used,
less reflection to the feedback complete and accurate.
and of the assignment
improvement to 1;
the feedback of
the assignment; Meets all criteria in
80-89% range, plus
Operation and Failed to provide Failing to The student has Include all the Include all the Very high standard demonstrates
functioning of the the basic functions demonstrate basic demonstrated a clear necessary necessary and/or ability achieved. exceptional ability
system (50%) of the system; operations and understanding of the functions, and additional and insight,
functions of the system and provide very few errors functions, and no Relevant technical skills indicating the highest
system; Failing to adequate operation and found; good errors found; very are demonstrated at a level of technical
show a basic functions of the system. description good description very high level. competence.
understanding of May contain few errors. about the front- about operation
their end and function of
implementations. development the front-end
Descriptions contain and development and
many errors. implementation implementation,
process; Not provide the
include the navigation map in
navigation map details as well;
or that is not
well presented.
Report writing: Riddled with errors, Frequent errors. Occasional errors. Few errors. Free of errors. Very high standard
(10%) incoherent and Somewhat Generally coherent. Lack Coherent and High coherence ability achieved.

Sensitivity: Internal
 disjointed. incoherent and of clarity in places. clearly and clarity of
disjointed. expressed. expression. Referencing is
Many references Referencing and citation consistently used,
are inconsistent Some references are style is consistent Referencing and Referencing and complete and accurate.
between the text inconsistent between between the text and citation style is citation style is
and the list; a the text and the list; the list; reference list consistent correct and
number of mistakes Reference list with with some mistakes. between the consistent
in the reference many mistakes. text and the list;between the list
list. reference list and the text;
with only a few reference list
minor mistakes. completely
concise without
errors.
% Mark Nothing of Merit: Nothing of value is contained in the submitted work. The work presents information that is irrelevant and unconnected to the task; no evident
1-4% awareness of appropriate principles, theories, evidence or techniques

NS Non-submission: No work has been submitted

Z Academic offence notation Applies to proven instances of academic offence

Sensitivity: Internal
 University Grid (PG):

10

Sensitivity: Internal