Individual Report

COMP1640 - Enterprise Web Software Development

Subject Code: COMP1640

Subject Title: Enterprise Web Software Development
Student Name: Nguyen Thanh Nhan
Student ID: 001197129
Submission Date: 18/04/2022
Contents
1. Group Information...............................................................................................................................3
1.1 Team Members information........................................................................................................3
2. Evaluation of product and process......................................................................................................3
2.1 Evaluation of Product..................................................................................................................3
2.2 Evaluation of Process...................................................................................................................3
3. Evaluation of team...............................................................................................................................3
4. Self-evaluation.....................................................................................................................................5
 1. Group Information
Must include title page with a list of team members and roles, URL and password of group repository,
site and screencast.

Team Name Description

Group Repository Github: Vinhhoang-1312/COM1640: Heroku already deploy (github.com)
Group Board URL Trello: Idea Management System | Trello
Deployment URL http://comp1640app.herokuapp.com/
Front End Tech ReactJS (html, css, javaScript)
Back End Tech NodeJS (css, javaScript)
Database Tech MongoDB
Screen Cast URL https://youtu.be/aaIhYz3nZ0Y

1.1 Team Members information

Full Name Role
Phan Dinh Dat Backend Developer, Web Designer
Nguyen Duc Dung Scrum Master, Tester
Nguyen Thanh Nhan Backend Developer, Programmer
Nguyen Ngoc Hai Dang Technical Team Leader, Tester
Le Dinh Huy Frontend Developer, Tester
Tran Phan Vinh Hoang Product Owner, Programmer , Database Designer
Tran Van Quy Frontend Developer, Web Designer
Nguyen Ngoc Linh Frontend Developer, Web Designer

2. Evaluation of product and process

Appropriate screenshots and commentary, with cross-references to group documents, and on
 2.1 Evaluation of Product
This project is a project with functions such as login, delete, edit, create categories, ect. Here is a list of
the project's functional requirements:

Roles Functions
QA Manager  The University has a Quality Assurance
Manager to oversee the process.
 The QA Manager can add additional
categories at any time, and can delete
categories, but only if they have not been
used.
 The University QA Manager needs to be
able to download all the data after the
final closure date in a CSV file for transfer
out of the system. Any uploaded
documents need to be downloaded in a
ZIP file.
Staff  All staff (academic and support) have the
opportunity to submit one or more ideas.
 All staff must agree to Terms and
Conditions before they can submit.
 All staff can optionally upload documents
to support their ideas.
 All staff can see all submitted ideas and
can comment on any idea. They can also
give the Thumbs Up or Thumbs Down for
any idea, but only once for any idea
QA Coordinator  All Departments have a QA coordinator
who is responsible for managing the
process for their Department, and for
encouraging staff to contribute.
 Once an idea is submitted the system
emails a notification to the Department’s
QA Coordinator.
Anonymous  Ideas and comments can be posted
anonymously, although the author’s
details will be stored in the database so
any inappropriate ideas can be
investigated.
Admin  An administrator is needed to maintain
any system data, e.g. closure dates for
each academic year, staff details.
 Statistical analysis (e.g. number of ideas
per Department) needs to be available.
We have tried to develop and meet the listed functionalities of the web application. We have developed
some additional features to improve performance. Let's take a look at some of the app's interfaces.
Note, this is not their priority, we want to focus more deeply on the functions. I'm a back-end developer
so I wanted its functionality to be more efficient than the interface. But I will show everyone the user
interface that has functions like: create, edit and delete categories.

Here's what we got when I created it. As for the back-end, we used NodeJs in combination with
MongoDB to set up the functions. This is the function that I take care of, so I have tried my best to be
able to optimize it.
I used the JSON Site Token library for added security. Users need to verify their information before
logging in. If someone isn't a user, they won't be able to log in. As shown in the figure, the user's
password has been encrypted to a high degree, so those who want to gain unauthorized access will not
be able to break into the system.

2.2 Evaluation of Process

To evaluate the process, we used the software development process, specifically the Scrum model. This
is a suitable model for teamwork and it belongs to the Agile family of models. For the project to be
successful, there needs to be a process suitable for teamwork and the Scrum process has brought many
benefits. To see how our process works, I'll do a review of the stages the team went through:

Pros

 When applying the Scrum model, every member of the team is organized and purposeful.
 Each team member was in charge of each Sprint item effectively.
 Scrum team members got to know and work together, doing tasks together and helping each
other.
  Scrum master is the person who has helped the team develop a lot, especially helping the team
to overcome difficulties.

Cons

 The division and implementation of Print Backlog items are still difficult.
 During the process, members could not arrive on time, which hindered the Scrum team.
 The exchange between Scrum master and members is limited.
 There are many reports that have not been completed on schedule

Further improvements

3. Evaluation of team
Nguyen Duc Dung (Scrum Master, Tester)
Attendance Dung is an exemplary leader, he always arrives on
time or earlier.
Task Dung holds the role of leader as well as Scrum
Master, he always completes the tasks assigned
to him well, and even he helps other members in
their tasks.
Communication Dung is a very polite communicator and is willing
to share anything with other team members.
That is also the reason that he is the leader and is
assigned with many important tasks.
Technical level Although he is a leader, not everyone is a
developer. He has 1 year experience in JavaScript
language and he also guides the members a lot
even though he is not proficient in this.
Discipline Dung is a much disciplined person in the group,
when he is elected as the leader, in all meetings,
he always makes rules for the group. His self-
discipline is very high, he even scolded some
members because they did many things wrong.
Creation Dung is a talented leader, he is always creative in
all circumstances. He helped all members find
their own strengths and paths. He is creative in
all his work.

Nguyen Thanh Nhan (Backend Developer, Programmer)

Attendance Dung is an exemplary leader, he always arrives on
time or earlier.
Task
Initiative
Communication
Technical level
Discipline
Creation
 Le Dinh Huy (Frontend Developer, Tester)
Attendance Huy is a very important person about punctuality.
He is always annoyed when a member is late.
Task Huy has always been a person who prioritizes his
duties. He always completes the mission even
though there are a few mistakes but it's
insignificant.
Communication Huy is a very good communicator. He is always
enthusiastic with all the team members and he is
always open and chatty with everyone.
Technical level Huy is a front-end developer. He has 1 year of
experience working with ReactJS. Although he
doesn't seem to be proficient with the JavaScript
language, he did a great job with the assignment.
Discipline Huy is a disciplined person. In particular, he
always reminds his team members to respect
their leader.
Creation On a creative level, Huy doesn't stand out yet,
but we respect his ability. Sometimes he will have
great ideas

Phan Dinh Dat (Backend Developer, Web Designer)

Attendance Dung is an exemplary leader, he always arrives on
time or earlier.
Task
Initiative
Communication
Technical level
Discipline
Creation

Nguyen Duc Dung (Scrum Master, Product Owner, Tester)

Attendance Dung is an exemplary leader, he always arrives on
time or earlier.
Task
Initiative
Communication
Technical level
Discipline
Creation
 Nguyen Duc Dung (Scrum Master, Product Owner, Tester)
Attendance Dung is an exemplary leader, he always arrives on
time or earlier.
Task
Initiative
Communication
Technical level
Discipline
Creation

Nguyen Duc Dung (Scrum Master, Product Owner, Tester)

Attendance Dung is an exemplary leader, he always arrives on
time or earlier.
Task
Initiative
Communication
Technical level
Discipline
Creation
FACTOR WEIGH Nguyen Nguyen Le Phan Tran Tran Nguyen Nguyen
T Duc Thanh Dinh Dinh Van Phan Ngoc Ngoc
Dung Nhan Huy Dat Quy Vinh Hai Linh
Hoang Dang
Attendance 6 9 9 9 8 9 9 8 8
Task 9 8 7 8 7 8 8 8 7
Communication 6 8 8 8 7 7 8 8 7
Technical level 10 7 8 7 8 7.5 9 8 7
Discipline 7 8.5 8 8 8.5 8 9.5 9 8
Creation 7 8 7.5 7 7 7.5 8 8 8
TOTAL 45 8 7.9 7.8 7.6 7.8 8.5 8.2 7.5

Factor Comparison
10
9
8
7
6
5
4
3
2
1
0
Nguyen Duc Nguyen Le Dinh Huy Phan Dinh Tran Van Tran Phan Nguyen Nguyen
Dung Thanh Nhan Dat Quy Vinh Hoang Ngoc Hai Ngoc Linh
Dang

Attendance Task Communication

Technical level Discipline Creation

PERSON TOTAL
Nguyen Duc Dung 8
Nguyen Thanh Nhan 7.9
Le Dinh Huy 7.8
Phan Dinh Dat 7.6
 Tran Van Quy 7.8
Tran Phan Vinh Hoang 8.5
Nguyen Ngoc Hai Dang 8.2
Nguyen Ngoc Linh 7.5

Overall Team Contribution

10
9
8
7
6
5
4
3
2
1
0
Nguyen Duc Nguyen Le Dinh Huy Phan Dinh Tran Van Tran Phan Nguyen Nguyen
Dung Thanh Nhan Dat Quy Vinh Hoang Ngoc Hai Ngoc Linh
Dang

Total

4. Self-evaluation
Honest description of own contribution, and reflection on own performance and any lessons learnt