MOD008905 Relational Database Development Fundamentals (Level 4) Assessment Brief 2026 | a.r.u London

MOD008905 Assessment Brief

INTRODUCTION

This assessment is split into TWO parts:

Part 1 (50% weighted: LO1, LO2, LO5, LO6)

This is the submission of a System Specification Document (3000 words) that includes your analysis of the problem and design solution methods and documentation for the data base implementation. This submission is due at the end of week 10.

Part 2 (50% weighted: LO3, LO4, LO6)

This is a recorded practical demonstration to the tutor of your database implementation. This will include a range of Structured Query Language (SQL) programs. The final deadline for demonstrations will be the end of week 12 however Tutor's welcome early demonstrations where possible.

Please note that it is your responsibility to ensure your demonstration is completed in sufficient time before the deadline. For example, requesting to demonstrate an hour before the deadline will not guarantee completion if Tutors are busy with other student demonstrations.

Part 1: System Specification Document

You are a junior developer working for a database development company. A new Client Stone Stores has requested a database to replace an old system of spreadsheets that are now becoming unmanageable and unreliable. You have been tasked with designing and implementing a database to monitor their stock across their chain of stores and track resupply requests.

The Clients Operation

• Stone Stores are a retail chain of shops selling a variety of items (you may choose which items Stone Stores will sell e.g. Video Games, Books, Magazines, IT equipment etc.
• The company has several stores across the country. Every store sells the same products at the same prices and minimum required quantity of stock they should keep on hand is set on a product level. The products are sourced from a range of third-party suppliers.
• If a store is running low on stock, an employee will raise a request for more (known as a Purchase Order). An employee may request any quantity of any number of products on the same purchase order. The purchase order must be authorised by the store manager before it is submitted.
• Once a purchase order is authorised, the company can send orders to the appropriate suppliers for the products. An order is for a single supplier and may be for more than one product at once. Stone Stores have agreed that managing the order creation would be beneficial, but not essential at this stage.
• Once a product is delivered to the store, the line of the purchase order is marked as received and the quantity of stock for the store is updated. When all items on a purchase order are received, the purchase order is considered complete.

What you need to evidence in your report?

• Analysis of the client's operation to identify (highlight) the Entities, their Attributes and any Relationships between Entities.
• Provide a defined list of assumptions of how the system will operate.
• Document the relations between entities.
• Based on the above, draft an Entity Relationship Diagram (using draw.io) that illustrates all the entities, their attributes and relationships.
• At this point you may want to identify the type of data that users (e.g. shop manager, a supplier or even the client's owner) may want to access. These are referred to as User Stories. You may want to look at part 2 of this brief to get an idea.
• Normalise the initial Entity Relationship Diagram to mitigate data redundancy and improve data integrity such as eliminate any many to many relationships.
• Convert your improved ERD into a Table Diagram (using draw.io) that clearly identifies each entities attributes as a Primary and (or) Foreign Key.
• Create a Table Schema that clearly defines the table diagram and its properties including data types and commentary for expected data inputs.
• When constructing and testing the database you may provide screen shots of the process and comment on the images. 
• Evidence may be placed in an appendix.

Part 2: Practical Demonstration of Structured Query Language (SQL)

You are to demonstrate to your Tutor competence with using SQL. Below are eight data request examples.

From the list:

You MUST demonstrate any four of the eight requests.
You SHOULD demonstrate all eight requests.
In addition to all eight requests, you MAY demonstrate your own search requests with increased complexity to show high level of competence.

Data requests to be written and tested in SQL

1. A list of all stores, their address, and their managers.
2. The top 5 products ordered and the quantity that was ordered of them.
3. A list of all products costing more than £30.
4. The total amount (£) spent by each store across all purchase orders.
5. The total number of purchase orders raised each month over the last year.
6. Assuming that purchase orders are replacing stock which has been sold, they want a list of total profit made by each store in the last 6 months.
7. A list of all purchase orders raised in the 6 months, including the date raised and the employee who raised it. If possible, also display the overall state of the purchase order (outstanding or complete).
8. For a given purchase order (choose one as an example), they need to retrieve a list of each product requested, the quantity needed, the total price that would be (per product), and the supplier it needs ordering from.

The final deadline to demonstrate to your Tutor will be the end of week 12, however it is not advisable to leave your demonstration to the last minute as this may risk in not being completed. During the assessment if you are ready to demonstrate please notify your Tutor at the earliest opportunity. The Tutor will then sit with you and record the demonstration and may ask questions during or after the demonstration.

REMEMBER: IT IS YOUR RESPONSIBILITY TO ENSURE THE DEMONSTRATION IS ARRANGED AND COMPLETED WITH THE TUTOR AHEAD OF THE DEADLINE. THIS ALSO APPLIES WITH RESUBMISSION DEADLINES.