ASSIGNMENT 2 FRONT SHEET

Qualification BTEC Level 5 HND Diploma in Business

Unit number and title Unit 30: Application Development

Submission date 9/7/2021 Date Received 1st submission

Re-submission Date Date Received 2nd submission

Student Name Nguyen Trung Hieu Student ID GCH190423

Class GCH0801 Assessor name Nguyen Dinh Tran Long

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

Grading grid

P4 P5 P6 M3 M4 M5 D2 D3
 Summative Feedback:  Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

Table of Contents
List of figures................................................................................................................................................................. 4
List of tables .................................................................................................................................................................. 5
I. Introduction ............................................................................................................................................................... 6
II. Review and feedback ................................................................................................................................................ 6
1. Formal questionnaire ........................................................................................................................................... 6
1.1. Interview question .................................................................................................................................... 6
1.2. Survey form ............................................................................................................................................... 6
2. Collect ................................................................................................................................................................... 7
2.1. Interview ........................................................................................................................................................ 7
2.2. Survey ............................................................................................................................................................ 8
3. Interpret .............................................................................................................................................................. 11
4. Evaluate .............................................................................................................................................................. 16
III. Application development....................................................................................................................................... 17
1. Folder structure .................................................................................................................................................. 17
2. Source code with explanation ............................................................................................................................ 19
3. Final screenshot .................................................................................................................................................. 22
4. Using GitHub ....................................................................................................................................................... 34
5. Sever ................................................................................................................................................................... 35
IV. Application evaluation ........................................................................................................................................... 37
1. Testing ................................................................................................................................................................ 37
2. Performance of the application .......................................................................................................................... 44
3. Function evaluation and future update .............................................................................................................. 44
4. Factor that affect the website ............................................................................................................................ 44
5. Strength and weekness of the website............................................................................................................... 45
5.1. Strength ....................................................................................................................................................... 45
5.2. Weakness ......................................................................................................................................................... 45
V. Team evaluation ..................................................................................................................................................... 45
1. Task breakdown .................................................................................................................................................. 45
2. Evaluating............................................................................................................................................................ 46
V. Conclusion .............................................................................................................................................................. 46
List of figures
Figure 1: Do you see the website run stable? ............................................................................................................ 11
Figure 2: Do you find the website convenient? .......................................................................................................... 12
Figure 3: Is the interface of the website appropriate and easy to use? ..................................................................... 13
Figure 4: Is the information correct? .......................................................................................................................... 14
Figure 5: Is the chatbox function useful to you? ........................................................................................................ 15
Figure 6: Do you find such functions enough? ........................................................................................................... 16
Figure 7: Folder structure ........................................................................................................................................... 17
Figure 8: Category folder inside SRC folder ................................................................................................................ 18
Figure 9: View folder ................................................................................................................................................... 19
Figure 10: Example code controller ............................................................................................................................ 20
Figure 11: Example code for service (provider) .......................................................................................................... 21
Figure 12: Example code module................................................................................................................................ 21
Figure 13: Login screen ............................................................................................................................................... 22
Figure 14: Chat screen ................................................................................................................................................ 23
Figure 15: Trainee list screen ...................................................................................................................................... 23
Figure 16: Trainee profile............................................................................................................................................ 24
Figure 17: Trainee add ................................................................................................................................................ 24
Figure 18: Trainer account .......................................................................................................................................... 25
Figure 19: Trainer add view ........................................................................................................................................ 25
Figure 20: Trainer edit view ........................................................................................................................................ 26
Figure 21: Category list ............................................................................................................................................... 27
Figure 22: Add and update category .......................................................................................................................... 27
Figure 23: Course list view .......................................................................................................................................... 28
Figure 24: Add course view ......................................................................................................................................... 28
Figure 25: Course update view ................................................................................................................................... 29
Figure 26: Course detail list view ................................................................................................................................ 29
Figure 27: Course detail add view............................................................................................................................... 30
Figure 28: Subject list view ......................................................................................................................................... 30
Figure 29: Subject update view .................................................................................................................................. 31
Figure 30: Registration list .......................................................................................................................................... 31
Figure 31: Registration add ......................................................................................................................................... 32
Figure 32: Trainer/ trainee view ................................................................................................................................. 33
Figure 33: Course view................................................................................................................................................ 33
Figure 34: Trainer list views ........................................................................................................................................ 34
Figure 35: Evidence of using GitHub ........................................................................................................................... 35
Figure 36: Server - Bitsive SSH Client .......................................................................................................................... 36
Figure 37: Cloud Bitsive Sterm .................................................................................................................................... 37
Figure 38: Error messenger for unauthorized account............................................................................................... 39
Figure 39: Messenge box for failed login .................................................................................................................... 40
Figure 40: Dashboard on 5/7/2021 version ................................................................................................................ 42
Figure 41: Dashboard on 7/7/2021 version ................................................................................................................ 42

List of tables
Table 1: Survey result ................................................................................................................................................... 8
Table 2: Survey after coded ........................................................................................................................................ 10
Table 3: Test result on 5/7/2021 ................................................................................................................................ 38
Table 4: Test result on 7/7/2021 ................................................................................................................................ 39
Table 5: Task breakdown structure ............................................................................................................................ 45
I. Introduction
Following the plan and development that has been reported in the first report, the second phase of the
application creation is started and the documentation of it is written on this report. In the first part, the
report showing the review and feedback of the user, by that way knowing if the user is satisfacted with
the website or not. On the second part, the code folder and example code of the back end is shown
together with the frontend view and evidence of using GitHub and deploying to the server during the
process of development. The third part evaluating the website based on its performance, facter that affect
its performance and the strength and weekness of the website at current state together with how can it
be improved in ther future. The last part of the report is about evaluating the contribution of each team
member and conclusion of the project.

Link GitHub: https://github.com/LuxuryFi/ASM2_DiscordLink

Screencast: https://www.youtube.com/watch?v=8mtuaaa1gR4&ab_channel=PhanV%C3%A2nPhong

Link Web: www.Ucen.net

II. Review and feedback

1. Formal questionnaire
To support the review and feedback of users, a survey and an interview is created to get the users feedback
on the webpage.

1.1. Interview question

The interview for user experience is based on 7 questions. These question support the developer
understanding the insight of user based on 2 main problem: “Is the system easy to use and is the system
make the user comfortable using it?”.
1. What is your experience of using the system? Is it easy or difficult to use?
2. Which function that you think that is difficult? And how does it make you have a bad using experience?
3. Are you satisfied with out system? Which function makes you satisfied?
4. How could we do to improve your experience with our system?

1.2. Survey form

For quanitative research on user experience, a survey with 9 questions about the system is created using
google form. These question based on 3 main problem: “Is the system run as intended, is the system easy
to use, and is the system useful for its users?”
2. Collect
2.1. Interview
The interview is taken on 2 user named “Bui Phuong Giang” and “Nguyen Thu Huyen”. Based on the
answer, while the 1st interviewee think the website is easy to use and satify with the website, the 2nd
interviewee think the website is difficult to use and need some improvement. Though both user think the
design of the website is good and it will be useful for the users.
Interviewee Answer
Interviewee 1: Bui Phuong Giang
1. What is your experience of using the system? Is it easy or difficult to use?
As for my first impression, the website is quite easy to use even for newbies like me.
2. Which function that you think that is difficult? And how does it make you have a bad using experience?
For me everything is great, so I do not think that have any function difficulty.
3. Are you satisfied with our system? Which function makes you satisfied?
Yes, I 100 percent satisfied with your system. The most satisfied function is the box chat. I can
communicate easily with orther people through this.
4. How could we do to improve your experience with our system?
My personal experience is quite complete and wonderful, so I have no complain.
Interviewee 2: Nguyen Thu Huyen
1. What is your experience of using the system? Is it easy or difficult to use?
For me, it is quite hard to use because I don’t use this technology before. But it help me to control our
business easier so I like to own it by myself.
2. Which function that you think that is difficult? And how does it make you have a bad using experience?
Function is difficult for me is the enrollment of trainee to a course. It takes a long time to add trainee to a
course because I just can add one by one trainee. If I have a course with 100 trainees, I need to do it 100
times.
3. Are you satisfied with out system? Which function makes you satisfied?
I qutie satisfied with your system. The design is quite beautiful and stunning. The function make me
satisfied is chat box.
4. How could we do to improve your experience with our system?
I think you need upgrade the feature of adding trainee to course. It will save our time.

2.2. Survey
As the qualitative primary research on the user experience can’t be taken for all user of the system, a
survey is created to support the research on user experience as a quanitative method. After 1 week, the
survey have the following answer:

Table 1: Survey result

Is the
Do you interface of Is the Did you Do you want to
Can you see the the website chatbox Do you find encounter improve the
log in to website Do you find appropriate Is the function such any errors or website or give
the running the website and easy to information useful to functions problems us
system? stable? convenient? use? correct? you? enough? during use? suggestions?
Yes Yes 3 3 Yes Yes Yes No No
Yes Yes 2 5 Yes Maybe Yes No No
Yes Yes 5 4 Yes No Yes No No
Yes Yes 4 3 Yes Maybe Yes No No
need more
function on
notification of
Can't see change
Yes Yes 3 4 Yes Yes Yes the avatar activities
I have some
problems It should have a
when using message box
the login or notify for
Yes Yes 4 5 Yes Yes Yes function validation.
I want to
customize
Nothing at some fields in
Yes Yes 4 4 Yes Maybe Yes the moment the export file
I want to
customize
Nothing at some fields in
Yes Yes 4 4 Yes Maybe Yes the moment the export file
Upload multiple
Yes A little 3 5 Yes Yes Yes Font error items
Yes Yes 3 3 Yes Maybe Yes Nothing Nothing
The main
function is
good
enough, The web might
though have a view to
some watch all
additional trainers and
functions trainees
can be assigned to a
Yes Yes 4 4 Yes Maybe added. No. course.
Review
uploaded
Yes Yes 4 4 Yes Yes Yes Not any image
I'm
allowed
to log in No. The system
to the is good enough
trainer No problem at its current
Yes A little 3 3 Yes only. Yes appeared. state.
No problem
appeared on
the main
function for
staff, admin,
trainer, and
Yes Yes 4 5 Yes Yes Yes trainee. Not necessary.
For better evaluation, the result of the survey should be changed into numerical code like the following.
Can you log in to the system?
 Yes: 1
 No: 0
Do you see the website running stable?
 Yes: 2
 A little: 1
 No: 0
Is the information correct?
 Yes: 1
 No: 0
Is the chatbox useful:
 Yes: 2
 Maybe or unknown: 1
 No: 0
Do you find such functions enough?
 Yes: 2
 Can be improved: 1
 No: 0
Table 2: Survey after coded

Is the
Do you see chatbox
Can you log the website Do you find the Is the interface of the Is the function Do you find
in to the running website website appropriate information useful to such functions
system? stable? convenient? and easy to use? correct? you? enough?
1 2 3 3 1 2 2
1 2 2 5 1 1 2
1 2 5 4 1 0 2
1 2 4 3 1 1 2
1 2 3 4 1 2 2
1 2 4 5 1 2 2
1 2 4 4 1 1 2
1 2 4 4 1 1 2
1 1 3 5 1 2 2
1 2 3 3 1 1 2
1 2 4 4 1 1 1
1 2 4 4 1 2 2
1 1 3 3 1 1 2
1 2 4 5 1 2 2
3. Interpret
To make the information becomes easier to be followed, the data above can be transferred to historgram
form. The positive choice will be weighted with a larger number in the code in table 2. Which makes the
positive answer stay on the right of the histogram when the negative answer stays on the left.

Do you see the website running stable?

12

NO A LITTLE YES

Figure 1: Do you see the website run stable?

The result showing that out of 14 surveyed people, 12 think that the website is stable and 2 think that the
website is not always stable. This is an acceptable results as sometime the website won’t be stable due to
connection problem of the user, not the website itself. Though a deeper survey or interview taken on the
people who don’t see the website run stable can be taken to improve the performent of the website.
 Do you find the website convenient?

1 1

1 2 3 4 5

Figure 2: Do you find the website convenient?

The histogram show that most user think the website is convenient or very convenient to use. Only 1
person thinks the website is unconvinient and 5 people think that the website have a decent performent
based on the convenient rating.
 Is the interface of the website appropriate and easy
to use?

4 4

0 0

1 2 3 4 5

Figure 3: Is the interface of the website appropriate and easy to use?

Most surveyed user think that the website is appropriate and easy to use. There is no user think that the
websit is difficult to use according to the survey.
 Is the information correct?

14

0 1

Figure 4: Is the information correct?

Arcording to the survey, all use think the information is correct. This is an important factor for the
deployment of the website.
 Is the chatbox function useful to you?

NO MAYBE OR UNKNOWN YES

Figure 5: Is the chatbox function useful to you?

Out of 14 surveyed people, 6 people think the chatbox function is useful and only 1 thinks it is not useful,
this making the chatbox function become a useful function that should be implemented on the website.
 Do you find such functions enough?

13

0 1

NO YES, BUT CAN BE IMPROVED YES

Figure 6: Do you find such functions enough?

Arcording to the survey, 13 of 14 surveyed people think the website has already had enough function, only 1 person
think the website has already had enough function but can still be improved. This mean the function has already
met the requirement for the website.

4. Evaluate
According to the interview, the website has already had enough function and it has an appropriate layout
for the user. Though, the function is not really easy to use and only one of the 2 interviewed person thinks
that it is easy to use.
From the result of the survey, its shown that the website has all the required functions and can run
properly, most of the users think that the website is appropriate, comfortable and easy to use and the
additional functions are useful.
The result of the survey and interview show that the website has already had enough functions and is
ready to be deployed.
III. Application development
1. Folder structure
The folder structure of the website has 3 main folders. The public folder is used to store image and video
used for the website. The SRC folder is used to store back end code which use NestJS as framework and
TypeScript as the main programing language. The views folder is used to store frontend code which use
HTML under HBS extension.

Figure 7: Folder structure

Figure 8: Category folder inside SRC folder
 Figure 9: View folder

2. Source code with explanation

The controller is used to handling requests and return responses to the client. The sample code bellow including the
role that can perform the action and example code for viewing, creating and updating category function of the staff
and admin.
 Figure 10: Example code controller

The example code bellow show the service (or provider) code of the category. It can be injected as dependency
which can pass the information between database and the website through controllers’s contructor. Helping the
controller controlling the information flow. The code from top to bottom are create category, view one category,
view category list, update category, and delete category.
 Figure 11: Example code for service (provider)

The code below is the module of the catalgory, it act as a decorator that support to organize the structure of the
application, it also help the developer encapsulate the provider, making the providers is unable to be injected
without directly imported to the current module.

Figure 12: Example code module

3. Final screenshot
After using the hyperlink uncen.net, the user is moved to the login screen which allow the user to login to the
website.

Figure 13: Login screen

After logging in to the admin or staff account, the user will be moved to the chat screen which allow them
to chat to other admins or staffs.
 Figure 14: Chat screen

As a admin or staff, the user can press on Trainees, Trainee List to view the list of trainee those are available
on the system.

Figure 15: Trainee list screen

From the trainer list view, the admin or staff can press on the eye icon next to the user avatar to watch
the detailed profile of the related trainee.

Figure 16: Trainee profile

The admin and staff can add a new trainee to the website by pressing on Trainees/Add Trainee, after filling in the
form and press submit, a new trainee can be added to the database and show on the website.

Figure 17: Trainee add

Trainer related views:

Similar to the trainee list, the trainer list view can be accessed by an admin or user account.
 Figure 18: Trainer account

As an admin or staff, the user can add an additional trainer or trainee to the website, bellow is the form
to be filled in to add a trainer to the website.

Figure 19: Trainer add view

The information of a trainer and trainee can be edited by a admin or staff, after pressing on the edit icon
next to the avatar of a trainer or trainee, the user is moved to the editing view which is automatically filled
with the information of the related account. The user can change the information and press on submit
button to update the information on the website.

Figure 20: Trainer edit view

Category related function:

An staff or admin can views the category list by pressing on the button Category/ Category List on navigation bar.
 Figure 21: Category list

Figure 22: Add and update category

Course related function:

The course view can be accessed by admin and staff via Course/ Course List button on navigation bar.
 Figure 23: Course list view

A staff can add a new course to the database by pressing on Course/ Add course, then fill in the form
bellow and press submit.

Figure 24: Add course view

The information of the course can be updated by the staff by pressing on the edit icon next to the course.
The form is automatically filled with the current information of the course which can be edited and
updated on the database after the user pressing submit.

Figure 25: Course update view

The course detail list can be viewed by the staff or admin which show the information of the course and
the trainer assigned to it.

Figure 26: Course detail list view

The course detail add view allow the staff to assign a new trainer to the course.

Figure 27: Course detail add view

As a admin and staff, the user can access the subject list by pressing on Subject/ Subject List on the navigation bar.

Figure 28: Subject list view

A staff can update the information of subject by accessing and editing information in the form bellow.

Figure 29: Subject update view

The staff and admin can view the registration list by accessing it throw the navigation bar which show
which trainee is assigned to which course.

Figure 30: Registration list

As a staff, the user can add a new registration which mean assigning a trainee to a course.

Figure 31: Registration add

Function related to trainer and trainee account:

After logged in to trainer or trainee account, the user is moved to the view which is created for the related
account.
 Figure 32: Trainer/ trainee view

As a trainer or trainee, the user can view or search for the course available on the website with the trainer
that has been assigned to the course.

Figure 33: Course view

The trainer list is also available to be viewed by a trainer or trainee which has already been logged into the
account.
 Figure 34: Trainer list views

4. Using GitHub
During the development process of the website, GitHub is used as a collaboration. Each programmer code
there own part and push it to the GitHub and pull a new code down when there is a new update. With the
changlog of the GitHub, the leader “Nguyen Thi Hoa An” can manage and reverse the code back to any
version if necessary. Bellow is the evidence of using GitHub during the development process.
 Figure 35: Evidence of using GitHub

5. Sever
The website is pushed on the internet using BitSive SSH Client as server.
Figure 36: Server - Bitsive SSH Client
 Figure 37: Cloud Bitsive Sterm

IV. Application evaluation

1. Testing
Table 3: Test result on 5/7/2021
 Table 4: Test result on 7/7/2021

Failed test cases from 6 to 9:

During the test on 5/7/2021, 4 test cases from 6 to 9 was failed as the unauthorized login will move the user to an error page.

Figure 38: Error messenger for unauthorized account

 Figure 39: Messenge box for failed login

This was fixed by creating a new HTML site for unauthorized login, which will be shown up when the user enters a wrong password
or unauthorized account. The test after the fixing is shown in Table 2.

Typo problem:
 In the version on 5/7/2021, there were typos on some web pages like Trainer become Trainer ID or some pages shown
Trainee as Student. This was fixed in the version on 7/7/2021.

Anonymous chat:

In case 33, even though the dashboard work as intended, the version on 5/7/2021 allows the user to enter their name for the
dashboard, making anonymous messenger become possible. This was changed in the version on 7/7/2021 which will show the user
name as the name in the dashboard instead of an entered name.
 Figure 40: Dashboard on 5/7/2021 version

Figure 41: Dashboard on 7/7/2021 version

Detailed explanation for test case:

Test case 1:
The login link run properly on the test case.
Test case 2, 3:
The login for admin and staff is successfully deployed. The login move user to admin or staff’s view
depending on the account.
Test case 4, 5:
The login for user is successfully deployed. The login move user to trainer or trainee’s view depending on
the account.
Test case 8, 9, 10, 11:
The website allow user to use the function those are restricted to logged in account via hyperlink on
5/7/2021, though after the quick fix on 6/7/2021, the error pop up when the user try to enter these view
and using function with out logging in. This quick fix also remove the problem where user can login again
after already login to an account. At current version, the user have to log out of there account before login
another account.
Test case from 10 to 13:
These test case showing that the admin’s functions like view, add, delete, update, and search for user runs
properly on the current version of the website.
Test case from 14 to 24:
The test cases from 14 to 24 showing that the function to control category and course of staff’s account
run properly on the current version of the website. Those function are add, remove, edit, and search
category and course. The test case from 22 to 24 also show that the staff can also assign trainer to trainee
to a course properly.
Test case 25:
The test case show that the user can edit the information on there accounts properly.
Test case 26:
The test case show that the user can view and search for course from the website.
Test case 27 to 31:
The document of these test case showing that the other test case run the same on many type of operating
system and browser. This making user that the website supporting the operating system like Window,
MacOS, Android and webbrowser like: Safari, Firefox, Google Chrome, IE11.
Test case 32, 33:
These test case make sure the dashboard function of the website run as intended.
Test case 34:
These test case showing that the Authentication and its related button shown up on the naviation bar,
though it shouldn’t be there. This button is changed to a button to control the privacy of the account on
later version.
Test case 35:
This test case showing that the Darkmode don’t run properly on the version on 5/7/2021, this was later
fixed on the version on 7/7/2021.
Evaluating:
The test case has already cover all the main functions of the website and some additional function that is
created to support the user. The test case has cover many bug and glitch of the website, helping the
developer repair them on the later version on 7/7/2021. It is also perfomed on both laptop and
smartphone, showing that the website can run on many operating system and web browser.
Though only doing black box test making it become more difficult for the developer who has to fix the
buges and glitches performing their task as they have to test the functions on the failed test case
themselves.
The test can also be improved by perfoming it on some additional famous operating system like Linux and
Ubuntu or web browser like Opera, Microsoft Edge, etc.
2. Performance of the application
After the fix on 6/7/2021, the application run properly with all required functions. All 4 main roles which
are admin, staff, trainer, and trainee are created and there related function are divided properly, that
allow a function can only be used by the suitable role. The website have average load time for each view
under 5 secconds with proper internet connection and can be accessed by up to 20 accounts at the same
time as tested. According to theory, more people can access the website at the same time, though its
haven’t been tested.

3. Function evaluation and future update

The website has already had all the function those are required by the stakeholders. It also have additional
function which are chatbox to help the admin and staff connect to each other easier. Though, during the
development process, the team realize there are some function which isn’t required but can be created as
an improvement for the future version, which are:
 The Registration and Course List can be updated, which mean the team can creating one view that
allow the staff or admin view all the detail of a course, including its IT, name, trainer and trainee
assigned to it. This will help the user have easier time knowing which trainer and trainee are
assigned to the course instead of browsing through the current registration list.
 A view to watch all the course which is assigned to the logged in account for the trainer and trainee
account can be created, this can support the trainer and trainee view the course those are assigned
for them easier.

4. Factor that affect the website

There are multiple facter that can affect the performent of the website. One is the user’s internet
connection. As the website only load the page when all the information on database is loaded (usage of
await function), the user without a proper internet connection may be unable to connect to the website.
Tested on smartphone using 3G is success showing that the minimal requirement for internet connection
is not high.
Another factor that affect the website is the company which provide the technology used for the website.
Some major update on TypeScript, NodeJS, NestJS, HTML, MySQL might require a quick fix on the code of
the website. The server Bitsive SSH’s status also affect the status of the website as if the server is down,
the website will also be down. Also the other factor like the bankruptcy of the company that providing
those technology will also cause a major trouble for the website. Though, those company are large
company which mean the risk mentioned above is not likely to happen.
5. Strength and weekness of the website
5.1. Strength
Good layout: The survey and interview show that most people are satify with the layout and decoration
of the website. It is easy to be tracked with a navigation bar on the left for admin and staff and on the top
of the website for trainer and trainee. The website also have enough space for the information to be shown
up and it is compatible with both wide screen like laptop, tablet or narrow screen like smartphone. The
padding also following some designing rule making the layout become good for user to watch. Additionally,
a darkmode is also added to support user using the website at night time.
Functionality: All the function that are required by the stakeholder are run properly on many operating
systems and web browsers on the current version of the website.
Easy to use: The website is considered easy to use by the majority of the test user. It is developed based
on the 3 click rules on developing a website, making the user being able to reach their destination within
3 clicks on the website.
Security: The website has a properly divided roles and log in system that prevent unauthorized access to
the website. From the version on 7/7/2021, the password is encrypted as a requirement from the
stakeholders.

5.2. Weakness
Forgot password is not implemented: The forgot password haven’t been implemented on the system,
making the user who has forgotten their password having to contact the admin or staff that assigned them
to the system to retrieve their password.
Login by third party: Some function allow user to login via google or facebook which is normally appeared
on many website isn’t implemented, making the website lack of convenient to some user.
Session based login: Eventhough the session based login has an increased security comparing to cookie
based login, it is inconvenient for user that if they close their webbrowser and enter the website again,
they will have to login again. In the future, a “Remember Password” check box can be used to help the
user feel more convenient.
Space for improvement: Eventhough not required by the stakeholders, some improvement can still be
applied like mentioned on the 3 section of the Application Evaluation.

V. Team evaluation
1. Task breakdown
Table 5: Task breakdown structure
 Task breakdown table
Nguyễn Thị Hòa An  Team leader
 Merge code
 Database creation
 Interview and survey creation
 Design back-end about registation and tester
 Design front-end
Nguyễn Trung Hiếu  Design back-end about category, course and course
detail
 Tester

Hoàng Văn Tùng  Design almost front-end

 Screen capture for the report
 Create interface
Lê Khôi Nguyên  Design back-end about four roles who use system
 Video screen cast for the report
 Take part in interview creation
 Take part in designing security system

2. Evaluating
All of the member has finished their part intime, making the deployment on the deadline on 7/7/2021
possible. The team has hosted weekly meeting and a meeting with the stakeholder before the deployment
on 5/7/2021 to discuss further about the detail of the website.
The website has run properly showing that all member has done their work correctly.

V. Conclusion
The website is successfully deployed with all the required function. It has 4 roles for user which is admin,
staff, trainer, trainee.

The function which are divided to each role are:

 Admin: View, add, edit, delete staff, trainer, and trainee.
 Staff: View, add, edit, delete trainer, trainee, course category, course, subject. Add a trainer or
trainee to a course.
 Trainer: Edit profile, view category, course, subject, trainer.
 Trainee: Edit profile, view category, course, subject, trainer, registration into a course.
Additionally, some functions which isn’t required is added as an improvement like chatbox for admin, staff,
darkmode. Though the website still have place for improvement. Some additional update can be added
for the future version of the website like:
 Chat function for trainer and trainee.
 Course view that show all information of a specific course.
In conclusion, the website is ready to be used but can still be improved in the future.