MINISTRY OF EDUCATION AND TRAINING
DUY TAN UNIVERSITY
----------

APPLYING NODEJS AND VUE
TECHNOLOGY TO BUILD WEBSITE FOR
SUPPORTING WORLDWIDE TOURISM
Mentor:

M.r.Trinh Su Truong Thi

Team Members:
Văn Hồ Ngân Hà
Ngô Phan Thông
Đinh Quang Thi
Nguyễn Hà Bảo Việt

Da Nang, 2020

-2220125623
-2221174893
-2221439676
-2221123650


LIST OF DOCUMENTS
1. PROPOSAL DOCUMENT
2. PROJECT PLAN DOCUMENT
3. PRODUCT BACKLOG DOCUMENT
4. USER STORY DOCUMENT
5. DATABASE DESIGN DOCUMENT

6. USER INTERFACE DOCUMENT
7. TEST PLAN
8. TEST CASE
9. SPRINT BACKLOG
10. MEETING RECORD


DUY TÂN UNIVERSITY
DEPARTMENT OF INFORMATION TECHNOLOGY

APPLYING NODEJS AND VUE TECHNOLOGY TO
BUILD WEBSITE FOR SUPPORTING WORLDWIDE
TOURISM


PROPOSAL DOCUMENT
Students:
Văn Hồ Ngân Hà

- 2220125623

Ngô Phan Thông

- 2221174893

Đinh Quang Thi

- 2221439676

Nguyễn Hà Bảo Việt - 2221123650


DaNang, October 2020


PROJECT INFORMATION
Project Acronym
Applying nodejs and vue technology to build website for supporting

Project name

worldwide tourism.

Started day

Oct 2nd, 2020

Lead Institution

Department Of Information Technology, Duy Tan University

Cố vấn dự án

Thi S. T. TRINH
Email:
Tel: 0905.723.278

Product

Owner


& Contact Detail

Partner Organization

Dec 11th, 2020

End day

Thi S. T. TRINH
Email:
Phone: 0905723278

Duy Tan University

Ha H. N. Van
Scrum Master

Email:
Tel: 0901979408
Full name
Thi Q. Dinh

Team members

Thong P. Ngo

Viet H. B. Nguyen

Phone number


Email

0981863229



0382987085

phanthong.1106@gmal.
com


0905055436

om


DOCUMENT NAME

Proposal Document

Document Title
Author(s)

Ha H. N. Van

Role

Scrum master
Oct 4th, 2020


Date

Proposal-ver 1.0.docx

File name:

URL
Access

REVISION HISTORY

Version
1.0

Person

Date

Description

Oct 4th, 2020

Ha H. N. Van

Create proposal document

DOCUMENT APPROVAL

Mentor


Thi S. T. Trinh

Signature:
Date:

Product Owner

Thi S. T. Trinh

Signature:
Date:

Scrum Master

Ha H. N. Van

Signature:
Date:

Team Member(s)

Thong P. Ngo

Signature:
Date:

Viet H. B. Nguyen

Signature:

Date:

Thi Q. Dinh

Signature:
Date:


Table of contents
1. INTRODUCTION.................................................................................................................................................. 4
1.1.
1.2.

Scope ....................................................................................................................................................... 5

1.3.
2.

3.

Purpose.......................................................................................................................................................4

References ..................................................................................................................................................5

PROJECT OVERVIEW ..................................................................................................................................... 5
2.1

Project definition ........................................................................................................................................5

2.2.


Issue description.........................................................................................................................................6

2.4.

Project scope ..............................................................................................................................................8

2.5.

Other constraints .......................................................................................................................................8

MASTER PLAN ............................................................................................................................................... 8
3.1.

Scrum definition .........................................................................................................................................8

3.2.

Scrum description:......................................................................................................................................9

3.3.

Handling ...................................................................................................................................................13

3.4.

The rules need to be defined in scrum .....................................................................................................14

3.5.


Overall Plan: .............................................................................................................................................14

3.6.

Component manage ................................................................................................................................15

1. INTRODUCTION
1.1. Purpose


This document will give you an overview, a purpose, and why this project was born. It
also gives you more detail about how the system works, resources, development models,
schedules, risks, solution for people and business need when using this system.

1.2. Scope
Besides giving you a detail of document, it will list all the members in developing team
in this project, the process, and the frameworks we will apply to.
This document provides a plan for each stage of the software development process based on
the Scrum process including: start time, end time and number of working days ... This is the
general plan and will be updated with detail of the software development process in the next
version of document. Proposal include the introduction of solutions, deciding the best approach
to software development with optimizing the cost, resources used and minimizing risks that
may occur during project implementation.

1.3. References
Table 1: Reference

No

Document


References

Information
1

Scrum Process

/>
2

Information

/>
3

Information

/>
2. PROJECT OVERVIEW
2.1

Project definition

Website is the place to connect the tourguide and the inviduals who want to book tourguide to
exploring special and mistery things in their destination.
This website will help the travelers to find perfect tourguides for them, ensurance to the travelers
it will be suitable about price, qualification, repuation and safety.



2.2.

Issue description

In modern life nowadays, there is a lot of pressure, a tight living space and many reasons why
we all want to travel. Travel not only to relax and reduce stress after stressful working, but also
to stimulate the need to exploring new things from the world of the surrounding things,
improve the value of spiritual life.
In order to meet the increasing travel demand of customers, website will help customers to
overview the flexible tours applied by specific tourdguides. Thanks to that, customers is able to
choose their perfect tour, suitable about time, price, qualification, repuation and safety.

2.3.

Proposes solution

Build a Website which is a connect place between customers and tourguide:

 Tour guide can post a tour (include informations about places, price, overview
about that tour).
 Visitors can find tours in places their want, see tours’ detail.
 Tourists can book tour guide, pay for tour online, connect to the tourguide by
show the QR code to tourguides to scan whenever the tour happen, to ensure
their safety.
2.3.1.

Project goal

Complete the development requirements and finish tasks on time.


2.3.2.

System overview

2.3.2.1. System Context


Figure 1:System Context

2.3.2.2. System context description
 Visitors has responsibilities to:
-

Search a tour suit with their demand.

-

View tour details.

 Tourists has responsibilites to:
-

Managing their information.

-

Search a tour suit with their demand.

-


View tour details

-

Booking tour and pay for it online.

-

View booking tour’s detail.

-

Rating and commenting tours after they had an experience about those tours.

-

Receive the notifications and the QR code when the tour they booked.

 Administrators has responsibilities to:
-

Customer Information Management

-

Posts management

-

Tour management



-

Tour category management

-

View statistical reports

2.3.3.

Technical constraints

2.3.3.1. Technical to develop the system
-

Programing language: Javascripts

-

Web Service: API

-

Single page: Nuxt

2.3.3.2. Environment
-


Operating system: Web Service

-

Develop tools: Visual Studio Code, Postman

-

Manage source code tools: GitHub

-

Job management tools: Trello

-

Internet Connection

2.4.

Project scope

When a tourguide or tourist resgister an account, they have to provide full information.
In case to book a tour successfully, the tourist will be supplied a ticket – it’s QR code. When
the tour will be happening, the tourguide will scan that QR of tourist to confirm that they will
have met each other already.

2.5.

Other constraints


-

Resource: 4 people

-

Budget: Limited

-

Time: The project must be completed within 2 months frame

-

Technology: Nodejs and vue

3. MASTER PLAN
3.1.

Scrum definition

Scrum is a subset of Agile and one of the most popular process frameworks for
implementing Agile. It is an iterative software development model used to manage complex


software and product development. Fixed-length iterations, called sprints lasting one to two
weeks long, allow the team to ship software on a regular cadence. At the end of each sprint,
stakeholders and team members meet to plan next steps.


3.2.

Scrum description:

Figure 2: Scrum Process
In order to make a good product, we need to know very well what products we have to
make, what quality requirements, or user friendliness. These request are written, constantly
updated in a priority list called the Product Backlog.
They are present in front of stakeholders in the development process, the person
assigned to perform creation and maintenance is Product Owner. Software construction work
is assigned to the Development Team include people who are qualified to make the product.
They sit together to Planning next “2 week” we need to do. To get some important function(s)
complete to “show” at the end of those 2 weeks. The team will choose the higher priority task
first, not the easy one. The workload is estimated to fit within the capacity of the team,
avoiding overloading.
The result of the planning meeting is a Detail Action Plan. Include goals and things to do in
the month. This plan is called Sprint Backlog. It can be updated continuously when working.


Based on that Plan, the Development Team tries to get everyone to do what they do,
voluntarily working closely with each other. Meeting at least 15 minutes a day (no more than).
To synchronize each other’s work, grasp progress and uncover difficulties, find ways to
overcome and promote work forward. If there is anything you need to do more, or less a few
do not need to do, then update always in Sprint Backlog. This is called adaptive planning
(Adaptive Planning). If there is a need for further discussion, the Development Team needs to
sit down to clarify before starting a new working day. Just like that until the end of the time
frame (2 weeks) this period of activity is called Sprint. In Sprint, when necessary,
Development Team with Product Owner may have to sit in meetings Refine the Product
Backlog (add, remove, reorganize, details…). End each Sprint, Development Team give out
THE HIGH QUALITY PRODUCT PACKAGE. End Sprint, Development Team with Product

Owner acceptance the result of Sprint, It’s very detailed and fun at the Sprint Review. Have to
sit down to see if the last time you worked was OK, could you do it better, try to find
something to improve for next month. This mandatory session is called Sprint Improvements.
Then REPEAT like that, repeating until the project development task is completed.

Figure 3:Three key positions in Scrum

-

There are positions in Scrum:

Product Owner: Product Owner responsible for maximizing the value of the Development
Team’s products and work.

 Determining product features
 Decide on the date and content for each release
 Responsible for product profit (ROI)


 Determining priority and function based on market data
 Change the priority and function after each iteration (if necessary)
 Accept or reject work result
Scrum Master responsible for making sure people understand and use Scrum. The Scrum
Master does this by ensuring the Scrum Team adheres to the Scrum’s theory, practical
techniques and rules.

 Project management representative
 Responsible for delivering the values and work of Scrum
 Solving problems
 Ensuring the group operates at full capacity and efficiency

 Create close cooperation between roles and functions
 Help the group avoid outside interference
What does the Scrum Master serve the Product Owner?

 Look for techniques to effectively manage the Product Backlog
 Communicate positively with the Development Team about the vision, goals and
items of the Product Backlog
 Teach the Development Team how to create Product Backlog items clearly and
simply
 Understand long-term product planning in an empirical environment
 Understand and practice agility
 Promote Scrum events on demand or as needed
Development Teams: includes experts working to produce releasable growth portions
(potentially releasable) the end of Sprint. Only members of the Development Team create these
growth portions.
The Development Team is structured and empowered to organize and manage their work.
Synergies will optimize the Development Team’s overall efforts and effectiveness. The
Development Team has the following characteristics:
Terminology


Figure 4: Object of Scrum (Artifacts)

-

Product Backlog is: A set of many item’s Product Backlog. One Item Product
Backlog may be described in any form, such as: User Story, Use Case, User
Scenario, …

-


Sprint: One phase of the project with a fixed time. The length of a Sprint will be
decided by the team and PO. Usually it is from 1 to 4 weeks.

-

Sprint Backlog: is a job board used by the Development Team to manage
development processes in one Sprint. The Sprint Backlog was created by the
Development Team during the Sprint Planning Session. Sprint Backlog contains
a list of items developed during the Sprint and the tasks to be done
corresponding to each item to complete it.

-

Estimation: In the Scrum, every member must choose tasks to work on, estimate
the time to complete, and when completed, update the product backlog.

-

Planning poker: the card records the numbers to give a rating on the features in
a sprint.

-

Velocity (Burn down chart): the chart shows the results the team has achieved
in a sprint.


Figure 5: The chart shows the result the team has achieved in a sprint


3.3.

Handling

 Sprint Planning
The Development Team meets with Product Owner to plan a sprint work (see also the sprint
section below). Planning involves selecting the needs of development, analyze and identify
tasks to be done with estimates of the time required to complete tasks. Scrum using partial and
incremental planning over time, whereby planning does not occur only once in the project’s
life cycle, but is repeated, adapted to Practical picture of the process of going to the product.

 Daily Scrum
Scrum Master hold a production team meeting for about 15 minutes for the Development Team
to share the progress of the work as well as share the difficulties encountered during the
software development process during a Sprint.

 Sprint Review
End Sprint, Development Team with Product Owner will review the completed work (DONE)
in the last Sprint and suggest necessary modification or.
Sprint Retrospective


With the help of the Scrum Master, the Development team will comprehensively review the
recently-completed Sprint and find ways to improve the workflow and the product itself.

3.4.

The rules need to be defined in scrum

- Enough to start: do not focus on documenting process, how to produce a product soonest.

- Definition of done: Give the definition of team 1 task, how a feature is considered complete.
- Time box: limit sprint time, meetings must comply with the time give. To ensure the scrum
team works stably.

3.5.

Overall Plan:
Table 2: Overall Plan board

No.

Task Name

Duration

Start

Finish

1

Initial

3 days

28 - Sep -2020

1 - Oct -2020

1.1


Gathering

2 days

28 - Sep -2020

29 - Sep - 2020

1 day

4-Oct-2020

4- Oct -2020

Requirement
1.2

Create
Proposal
Document

2

Start Up

6 days

5- Oct -2020


7- Oct -2020

2.1

Project Kick-

1 day

5- Oct -2020

5- Oct -2020

2 days

6- Oct -2020

7- Oct -2020

off Meeting
2.2

Create
Document

3

Development

62 days


8- Oct -2020

10-Dec-2020

3.1

Sprint 1

28 days

8-Oct-2020

4-Nov-2020

3.2

Sprint 2

34 days

6- Nov -2020

10- Dec -2020

5

Project’s

1 day


11- Dec -2020

11- Dec -2020

1 day

11- Dec -2020

11- Dec -2020

Retrospective
Meeting
6

Final Release


3.6.

Component manage
Table 3:Human Resource board

Roles
Mentor

Responsibilities
 Guide on the process.

Participant
Thi S. T. Trinh


 Monitoring all activities of team.
Team

 Estimate time to finish task.

Thong P. Ngo

Members

 Analyze requirements.

Viet H. B. Nguyen

 Design and gradually improve the

Thi Q. Dinh

design.
 Code and Test the application.
 Install and implement the functions of
system.
 Deploy the product.
Scrum

 Define and analyze the application.

Master

 Assign work for team members.

 Control and manage team members.
 Orientate for team members.
 Make sure that the task is completed on
time.
 Manage risk.
 Provide solutions to solve problems.

Ha H. N. Van


3.6.1

Non-human resources
Table 4:Non-human resources

ID

Item

Purpose

Critical

Quantity

(Yes/No)
1

Laptop


Development

Yes

4

2

Visual Code

Development

Yes

2

Development

Yes

1

Studio
3

NoSQL Booter
for MongoDB

Detail



DUY TÂN UNIVERSITY
DEPARTMENT OF INFORMATION TECHNOLOGY

APPLYING NODEJS AND VUE TECHNOLOGY TO BUILD WEBSITE
FOR SUPPORTING WORLDWIDE TOURISM


PROJECT PLAN DOCUMENT
Students:
Văn Hồ Ngân Hà

- 2220125623

Ngô Phan Thông

- 2221174893

Đinh Quang Thi

- 2221439676

Nguyễn Hà Bảo Việt - 2221123650

Da Nang, October 2020


PROJECT INFORMATION
Project
Acronym

Project

Applying nodejs and vue technology to build website for

name

supporting worldwide tourism.

Started day

Oct 2nd, 2020

Lead

Department Of Information Technology, Duy Tan University

Institution
Project
Mentor
Product
Owner &
Contact

Dec 10th, 2020

End day

Thi S. T. TRINH
Email:
Tel: 0905.723.278

Thi S. T. TRINH
Email:
Phone: 0905723278

Detail
Partner
Organization

Scrum
Master

Duy Tan University

Ha H. N. Van
Email:
Tel: 0901979408
Full name
Thi Q. Dinh

Team
members

Thong P. Ngo

Phone

Email

number
0981863229




0382987085



Viet H. B. Nguyen 090505543
6




DOCUMENT NAME
Project Plan Document

Document Title
Author(s)

Ha H. N. Van

Role

Scrum master
Oct 6th, 2020

Date

File name:


ProjectPlan-ver 1.0.docx

URL
Access

REVISION HISTORY
Version
1.0

Person

Date

Description

Oct 6th, 2020

Ha H. N. Van

Create project
plan document

DOCUMENT APPROVAL
Mentor

Thi S. T. Trinh

Signature:
Date:


Product Owner

Thi S. T. Trinh

Signature:
Date:

Scrum Master

Ha H. N. Van

Signature:
Date:

Team Member(s)

Thong P. Ngo

Signature:
Date:

Viet H. B. Nguyen

Signature:
Date:

Thi Q. Dinh

Signature:
Date:



1. INTRODUCTION
1.1. Purpose
This document provides a summary of the project’s goal, work assignment,
milestones, necessary resources, time and overall schedule and budget allocation used
and based on document proposals to build cost management applications on time, on
demand and on schedule.
1.2. Project overview
Reference to Proposal Document.
1.3. Project delivererable
Project will be implemented for Renting Helper application.
2. TEAM ORGANIZATION
2.1. Scrum team information
Table 1: Scrum team information
Full name

Phone

Email

Position
Scrum

Ha H. N. Van

0901979408




Thi S. T. Trinh

0905.723.278



Thong N. Phan

0382987085



Member

VietH. B. Nguyen

0905055436



Member

Thi Q. Dinh

0981863229



Member


master
Product
Owner


2.2. Role and responsibility
Table 2: Role and reponsibility
Role

Responsibility

Participant(s)

 Guide on the process
Mentor

Product Owner

 Supporting team management skills, writing,
technical and more
 Providing vision and direction to the Agile
development team and stakeholders
throughout the project and create
requirements
 Ensure that the team always has an adequate
amount of prior prepared tasks to work on

Thi S. T. Trinh

Thi S. T. Trinh


 Define product vision, road-map and growth
opportunities
 Provide backlog management, iteration
planning, and elaboration of the user stories
 Responsible for increasing productivity
Scrum Master

 Using the Scrum framework
 Facilitates and coaches the team

Ha H. N. Van

 Owns the impediment backlog
 Responsible for quality
Development
Team

 Responsible for delivering the potentially
shippable product of the application each
sprint
 Report progress based on remaining time
 Self-organized
 Owns the Sprint backlog

All members


2.3. Communication methodology
Table 3: Communication methodology

Audience/

Topic/ Deliverable

Frequency

Method

Weekly

Meeting, Email,

Attendees
Manager, Mentor

Project Progress

and Team member

Review

Product Owner,

Project Progress

Manager and Team

Review

Trello


Weekly

Meeting, Conference
Meeting

Leader
Product Owner,

Explicit Requirement

Occasionally

Email, Skype

Team Leader and

Review Project

Daily

Trello, Email,

Team Member

progress and Daily

Manager and Team
leader


Facebook

Meeting

2.4. Communication and report
Table 4: Commmunication and report
Type of

Methods,

Frequency

Information

People

communication

tools

Everyday

Information about what

Project

Facebook

was done in the last 24


team

or email

hours, working on plans

Communication in group
Daily Meetings

Trello,

for today, the difficulties
encountered and the


solutions required.
Meeting duration is
about 20-30 minutes.
Task Planning

Meet face

Meeting

to face

15-20 days

All members in team


Project

together to analyze the

team,

requirements, functions,

Product

work on the sprint going

Owner

to do, plan and design
for the sprint.
Task Review

Meet

Meeting

15-20 days

Completed

Project

face to


documentation.

team,

face

For each stage, sharing

Product

materials, given the

Owner

strengths and
weaknesses for each
member, period of tasks
and the solution
calculated measurement
project.
External communication and reporting
Task
Management

Trello

Every day

A web based task


Project

tracking system is used

team

for managing or
assigning task, reporting
bugs/issues.