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

Individual Project Front Sheet: Qualification BTEC Level 5 HND Diploma in Computing Unit Number and Title Submission Date

This document summarizes a student's individual project for a computing qualification. It includes the student's name, ID number, class, and assessor. The project involves developing a website for an online store. The summary provides an overview of the system design, including a sitemap showing user roles and key site sections, and an entity relationship diagram describing the database structure with 7 tables for users, roles, orders, carts, products, categories, and suppliers.
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
40 views

Individual Project Front Sheet: Qualification BTEC Level 5 HND Diploma in Computing Unit Number and Title Submission Date

This document summarizes a student's individual project for a computing qualification. It includes the student's name, ID number, class, and assessor. The project involves developing a website for an online store. The summary provides an overview of the system design, including a sitemap showing user roles and key site sections, and an entity relationship diagram describing the database structure with 7 tables for users, roles, orders, carts, products, categories, and suppliers.
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 12

INDIVIDUAL PROJECT FRONT SHEET

Qualification BTEC Level 5 HND Diploma in Computing

Unit number and title Project WEB

Submission date Date Received 1st submission

Date Received 2nd


Re-submission Date
submission

Student Name Nguyen Van Manh Student ID BHAF200048

Class BPIT17101 Assessor name Le Van Thuan

Student declaration

I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I
understand that making a false declaration is a form of malpractice.

Student’s signature manh

Grading grid

P5 P6 M4 D4

1|Page
❒ Summative Feedback: ❒ Resubmission Feedback:

Grade: Assessor Signature: Date:


IV Signature:

2|Page
I. USER REQUIREMENTS
II. SYSTEM DESIGN
1. Sitemap
Based on the user stories and use case diagram, we have designed a sitemap for both client and administrator
sites. The sitemap is shown as follow:
Components
Store

Login/
Register

Home
DashBoard(ad
page(custome
min)
r)

Manage Manage Manage


Manage user List product
product category supplier

CRUD
CRUD product CRUD supplier CRUD user Detail product
category

Cart

3|Page
Our system, as shown in the sitemap, has two main user groups: administrators and clients.
All features are available to administrators.
Administrators can access all client and admin sites. Meanwhile, the clients have limited rights; they can only
access the websites of clients.
2. Entity relationship diagram
We have designed an Entity relationship diagram (ERD) based on the requirements as follow:

4|Page
5|Page
This is the entity relationship diagram of our sales site system.
Our database design for the system has 7 tables including: User, Role, Oder, Cart, product, Category, supplier. In
the tables there are constraints and relationships as follows
 The relationship between the Role table and the User table is a One-to-many relationship because a role
has only one user but a user will have many roles.
 The relationship between the User table and the cart table is a one-to-many relationship because a user
has only one cart but one cart will contain many products of a single user.
 The relationship between the Cart table and the Order table is a one-to-many relationship. Because a
shopping cart can contain many products and many products can only be in one user's cart
 The relationship between the product table and the supplier table is a one-to-many relationship. Because
a product has only one supplier but a supplier has many product
 The relationship between the product table and the category table is a one-to-many relationship. Because
a product has only one category but a categoryhas many product
ERD documentation:
User

Field name Data type Constraint Explanation


userID int Primary key An identification of a
Auto increment specific user
userName Varchar(50) Not null Account name of a user
in the system
userEmail Varchar(50) Unique, not null Email of a user
userPassword Varchar(50) Not null Password of a user
account. It is used with
username to login to the
system
userRole Varchar(50) Foreign key, notnull Role of the account in
6|Page
the system
Product

Field name Data type Constraint Explanation


producID int Primary key,Auto ID of product
increment
ProductName Varchar(500) Not null Account name of a user
in the system
productDescription Varchar(1000) Unique, not null Email of a userv (can be
used as an alternate
key)
productPrice Varchar(50) Not null Password of a user
account. It is used with
username to login to
the
system
productImage Varchar(500) Not null Role of the account in
the system
supplierID Int Foreign key is a foreign key that
references the
supplierID of the
supplier table
categoryID int Foreign key is a foreign key that
references the
categoryID of the
category table
Cart

Field name Data type Constraint Explanation

7|Page
cartID int Primary key ID of carrt
Auto increment
userID int Foreign key is a foreign key that
references the userID of
the user table
productID int Foreign key is a foreign key that
references the
productID of the product
table
Supplier

Field name Data type Constraint Explanation


supplierID int Primary key ID of carrt
Auto increment
supplierName Varchar(100) Not null Name of supplier
supplierDescription Varchar(10000) none Description for dupplier
Category

Field name Data type Constraint Explanation


categoyID int Primary key ID of carrt
Auto increment
categoryName Varchar(100) Not null Naem of category
categoyDescription Varchar(10000) none Description for category

3. Wireframes
Login page

8|Page
Register page

9|Page
Home Page

10 | P a g e
Detail page

11 | P a g e
12 | P a g e

You might also like