Asm Semi-Project Maihuunambs00152.Pdf

ASSIGNMENT 1 FRONT SHEET

Qualification

BTEC Level 5 HND Diploma in Computing

Unit number and title

Unit 14:SEMI

Submission date

28/04/2023

Re-submission Date

Date Received 1st submission

28/04/2023

Date Received 2nd submission

Student Name

MAIHUUNAM

Student ID

BS00152

Class

IT17101

Assessor name

THAI THI THANH THAO

Student declaration
I certify that the assignment submission is entirely my work and I fully understand the consequences of plagiarism. I understand that
making a false declaration is a form of malpractice.
Student’s signature
Grading grid
P

M

D

NAM


❒ Summative Feedback:

Grade:
IV Signature:

❒ Resubmission Feedback:

Assessor Signature:

Date:


Contents
I.Introduction .................................................................................................................................. 5
II.

System analysis.................................................................................................................... 5
1.

System requirements ....................................................................................................... 5

2. Structure of symfony .......................................................................................................... 8
3. System consumers............................................................................................................. 10
4. Non-functional and Functional ......................................................................................... 10
5. Risk management plan ..................................................................................................... 11
6. Models ............................................................................................................................... 13
Use case description using a diagram. .................................................................................. 14
6.2 Schematic of the steps (2-3) ............................................................................................ 17
6.3 . Activity flowchart .......................................................................................................... 19
6.4 ERD................................................................................................................................... 25
7. screen ................................................................................................................................ 27
Some pages ........................................................................................................................... 27
a.

The login page ................................................................................................................ 27

b.

logout ............................................................................................................................. 28

c.

Registration page ............................................................................................................ 28

d.

HOMEPAGE ..................................................................................................................... 28

e.

Contacting page.............................................................................................................. 29

f.

Detail page for the category ........................................................................................... 30

Admin pages, some ............................................................................................................... 30
Category and genre ............................................................................................................... 30
The page for the product in product management ............................................................... 32
8. Github ................................................................................................................................ 32
CONCLUSION ................................................................................................................................ 33
REFERENCES .................................................................................................................................. 35


Figure 1 HTML,CSS,PHP................................................................................................................... 6
Figure 2 Symofony 6 ........................................................................................................................ 6
Figure 3 Github................................................................................................................................ 7
Figure 4 MySQL ............................................................................................................................... 7
Figure 5 Php strom .......................................................................................................................... 8

Figure 6 MVC ................................................................................................................................... 9
Figure 7. MVC ENTITY.................................................................................................................... 10
Figure 8 UCD USER ........................................................................................................................ 13
Figure 9 USC ADMIN ..................................................................................................................... 14
Figure 10 Login .............................................................................................................................. 17
Figure 11 Display a product's detail page. .................................................................................... 18
Figure 12 Login and register .......................................................................................................... 19
Figure 13 Review and include the user's product. ........................................................................ 20
Figure 14 Take a look at the product review's content. ................................................................ 21
Figure 15 ADD PRODUCT .............................................................................................................. 22
Figure 16 EDIT PRODUCT .............................................................................................................. 23
Figure 17 DELETE........................................................................................................................... 24
Figure 18 ERD ................................................................................................................................ 25
Figure 19 LOGIN PAGE ................................................................................................................... 27
Figure 20 Logout ........................................................................................................................... 28
Figure 21 REGISTER ....................................................................................................................... 28
Figure 22 HOMEPAGE.................................................................................................................... 29
Figure 23 CONTACT ....................................................................................................................... 29
Figure 24 Detail ............................................................................................................................. 30
Figure 25 Category and genre ....................................................................................................... 31
Figure 26 Product in product ........................................................................................................ 32
Figure 27 Github ........................................................................................................................... 33

Table 1 Risk arrangement .............................................................................................................. 12
Table 2 USECASE ADMIN ............................................................................................................... 15
Table 3 USD USER .......................................................................................................................... 16
Table 4 USD REGISTER ................................................................................................................... 17
Table 5 IMPORTGOODS ................................................................................................................. 25
Table 6 EMPLOYEE ......................................................................................................................... 26
Table 7 SUPPLIER ........................................................................................................................... 26

Table 8 Export ............................................................................................................................... 26
Table 9 Export ............................................................................................................................... 26


Table 10 Items ............................................................................................................................... 27

I.Introduction
For this assignment, I'll create a project using the Symfony framework and design it using
HTML, CSS, and bootstrap 4. Before creating the website for selling cars, I also created an
appropriate database and several models and diagrams, including ERDs and Use Case
Diagrams. I've decided to develop a web program for assessment.

II. System analysis
1. System requirements
I designed a vehicle sales system for the endeavor. This system can show comprehensive
information about (product) such as vehicle name and manufacturing date,... as well as its
reviews. Furthermore, when experiencing a problem or issue with the web, users can submit a
complaint to the administrator for resolution. The method makes it easier for administrators
to handle goods, users, categories, and writers.


a. HTML, CSS, bootstrap 3 and PHP

Figure 1 HTML,CSS,PHP
b. Symfony 6

Figure 2 Symofony 6


c. Github

Figure 3 Github
d. MySQL

Figure 4 MySQL


e. PhpStorm

Figure 5 Php strom

2. Structure of symfony
2.1. Overview
Model-View-Controller (MVC) is an architectural design pattern that divides an application's
three key logical components—model, view, and controller—into discrete parts. Each of these
parts is designed to deal with a certain application development task. The industry standard
web development framework MVC is one of the most often utilized to produce scalable and
extendable projects. But with Symfony, the entity replaces and uses the model.

2.2.MVC Components
MVC is known to generally have three parts. Controllers, Views, and Models.
Model:
It contains all of its information and related logic.
View:
interacts with users or displays info to them.


Controller:
It links the Model and View components, making it the most crucial component of the model.

Figure 6 MVC
To complete this homework, I built a motorcycle sales website. The shoe (product)'s name,
category, category, picture, and description are just a few of the details that this system can
present. The website allows users to upload new shoes and provide in-depth reviews of the
shoes after successfully registering and logging in. Additionally, users may report issues with the
website to the administrator for a fix.


Figure 7. MVC ENTITY
MVC works:
Step 1: A user can use any web browser to send an HTTP request. Data to be processed by the
controller may be included with this request. that The Navigator Routing will establish the
Controller.
Step 2: The Controller assesses if it needs information from the Model before responding to the
request. If so, the Model classes and functions will be used, and the outcomes will then be
returned. After processing those values, the controller will return the view to the screen. The
controller will choose the necessary views and show them as necessary.
Step 3: Before sending Gui content to the Controller for results and display on the Browser
screen, the view will trust show components like as pictures, data information, and so forth
when it receives data from the Controller.
Step 4: The browser will build a display for the user to see the return value after getting it,
concluding the process.

3. System consumers
On this platform, I split people into two categories: admin and user. And now I'd like to go over
some of the specific duties of each individual.
3.1 Administrator qualifications
• They can post, examine details, and read product reviews.
• They can also delete, create, examine, and edit categories.
• They can delete, upload, examine, and edit photos.

3.2 User needs
• The user may log in and create an account.
• They may examine product evaluations from various reviewers
• They can add and evaluate goods.
• You can look up goods using categories.

4. Non-functional and Functional
4.1 Requirements for functionality
Admin:


•
•
•
•
•

Login
Logout
Register(Sign up)
You can add, update, review, and examine the merchandise.
Edit, delete, add, and examine the source and category.

User :
• User may log in by providing email and password. They will return to the main page after a
successful login.
• User registration requires the input of a password and email.
• Upload items and read reviews on them.

4.2 Non-Functional requirement:
Performance:
• Anyone can use the program.
• Anyone can simply use the program.

Security:
• Users must input their email address and password to establish an account.
• To evaluate or submit a product, users must create an account and register in.

Operational:
• The web registration will be available in multiple languages.
• A well-designed and functional website

5. Risk management plan


Risk

Probability of
the risk
occurring

Lack of time was High
the danger I had
to deal with.

The software is
flawed or fails
to satisfy the
requirements

set out by the
teacher.

High

lack of expertise
and inability to
fund the
project's
completion

High

Creating the
incorrect
database and
setting up
associations for
the incorrect
entities

High

Impact

Solution

High

Before producing, I must make a

detailed list of the steps I must do,
and I must also establish a deadline
for each. Prioritizing key activities
first, such as ERD development and
then entity construction, is
something I need to learn how to
do.
High
The criteria must be thoroughly
documented and examined closely.
I have to test the website
repeatedly once I've created it.
Along with that, I engage the
lecturers frequently and solicit
their feedback.
High
I must pay close attention during
lectures and continue to expand
my knowledge and abilities by
using the Internet, books, and
newspapers. Find out more from
your friends, and if feasible, enlist
their assistance.
High
We must draw the ERD before
(serious) beginning the project to restrict
and avoid this problem. In addition,
we must study and inquire of the
lecturer on the creation of entities
in a logical order when drawing the

ERD. After that, we must rely on
that ERD to construct the
appropriate entities.
Table 1 Risk arrangement

Risk
category
Time risk

Resource
risks

Resource
risks

Resource
risks


6. Models
6.1 Use case diagram

Figure 8 UCD USER


Figure 9 USC ADMIN
Use case description using a diagram.
a. Admin
Use Case Name

Customer diagram

Description

To access the website and carry out administrative
tasks, log in as an admin

Actor(s)

Email

Pre-Condition(s):

-Presently existing user accounts
- User account is approved

Post-Condition(s):

- The user is logged in when their device is already
connected to the internet
- The user has successfully signed in to the
application.
- The system logs successful logins into the
administrator's database.


Basic Flow

1. A person accesses the website.
2. The user logs in with the admin account

3. After choosing the login command, the user
logs into the Admin account.
4. After successfully verifying the user's
credentials, the system permits access to the
website.
5. The system logs a successful logging attempt in
the Activity Log.

Alternative Flow

6. Execute tasks as necessary
3.1. When you log in, you cannot use
administrator powers if your account is not an
admin account.
3.2.The homepage is now the website.
3.3. Execute typical user tasks
Table 2 USECASE ADMIN

b. User
Use Case Name
Description
Actor(s)
Pre-Condition(s):

Post-Condition(s):

Admin diagram
Users to access the website and do the user
tasks
Email

- User accounts are already set up
- User account has been approved.
- When signing in, the user's device is already
connected to the internet.
- User has successfully signed in to the
website


Basic Flow

- The system acknowledges the successful
login.
- The user logs onto the website.
- The user signs in using a personal account
- User selects login request after entering
personal account.
- Users can access the website when the
system successfully authenticates their login
details.
- The system logs successful access to the
archive page.

Alternative Flow

- Execute tasks as necessary
-If the account is not active or the person
does not have an account
-The user registers for an account on the
website.
- Website reroutes to the login page

-Log in using a user account (individual)
-Implementation of user-specific (individual)
functions
Table 3 USD USER

c.

Register

Use case name
Actor
Trigger

Register
User
The actor selects the Register button

Precondition
PostCondition

Go to back the login page


Standard flow/ process

Alternate flow/ process
System error
System state in an error situation

-The user hits the Register button.

-Enter your email and password
-Press the Join button.
-Changing the Login Page
3’. The mail existed
4’. Re-enter another email
Cannot connect to the server
Cannot register
Table 4 USD REGISTER

6.2 Schematic of the steps (2-3)

Figure 10 Login


Figure 11 Display a product's detail page.


6.3 . Activity flowchart

Figure 12 Login and register


Figure 13 Review and include the user's product.


Figure 14 Take a look at the product review's content.


Figure 15 ADD PRODUCT

Figure 16 EDIT PRODUCT


Figure 17 DELETE


6.4 ERD

Figure 18 ERD

No

Field name

Type

Constraint

Description

1

Importgoods_Id

Int (10)

Primary Key

The ID of the imported

goods

2

Supplier_id

Varchar (255)

3

Employee_id

Varchar (255)

Foreign Key

Id of the employee

4

Importgoodsnow

Varchar (255)

Foreign Key

Importgoodsnow

Id of the supplier

Table 5 IMPORTGOODS

No

Field name

Type

Constraint

Description

1

employee_ID

Int (10)

Primary Key

The ID of the employee

2

Employee name

Varchar (255)

Name of the employee