Applying NODEJS and VUE technology to build website for supporting worldwide tourism

End Sprint, Development Team with Product Owner acceptance the result of Sprint, It’s very detailed and fun at the Sprint Review..  Project management representative  Responsible for d

MINISTRY OF EDUCATION AND TRAINING

DUY TAN UNIVERSITY

- -

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

Team Members:

Da Nang, 2020

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

Đinh Quang Thi - 2221439676

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

DaNang, October 2020

Scrum Master

Ha H N Van Email: vanha2808@gmail.comTel: 0901979408

Viet H B Nguyen 0905055436 vietnguyendn198@gmail.c

om

DOCUMENT NAME

URL

Access

REVISION HISTORY

1.0 Ha H N Van Oct 4th, 2020 Create proposal document

Table of contents

1 INTRODUCTION 4

1.1 Purpose 4

1.2 Scope 5

1.3 References 5

2 PROJECT OVERVIEW 5

2.1 Project definition 5

2.2 Issue description 6

2.4 Project scope 8

2.5 Other constraints 8

3 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

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.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

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

- Resource: 4 people

- Budget: Limited

- Time: The project must be completed within 2 months frame

- Technology: Nodejs and vue

3 MASTER PLAN

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

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

 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

- 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

Table 2: Overall Plan board

Retrospective

Meeting

3.6 Component manage

Table 3:Human Resource board

Mentor  Guide on the process

 Monitoring all activities of team

 Code and Test the application

 Install and implement the functions of system

 Deploy the product

Thong P Ngo Viet H B Nguyen Thi Q Dinh

Scrum

Master

 Define and analyze the application

 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

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

Đinh Quang Thi - 2221439676

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

Da Nang, October 2020

DOCUMENT NAME

URL

Access

REVISION HISTORY

1.0 Ha H N Van Oct 6th, 2020 Create project

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

2.1 Scrum team information

Table 1: Scrum team information

Ha H N Van 0901979408 Vanha2808@gmail.com

Scrum master

Thi S T Trinh 0905.723.278 trinhsutruongthi@gmail.com

Product Owner Thong N Phan 0382987085 Phanthong.1106@gmail.com Member

VietH B Nguyen 0905055436 vietnguyendn198@gmail.com Member Thi Q Dinh 0981863229 dinhquangthi195@gmail.com Member

2.2 Role and responsibility

Table 2: Role and reponsibility

Mentor

 Guide on the process

 Supporting team management skills, writing, technical and more

 Responsible for increasing productivity

 Using the Scrum framework

 Facilitates and coaches the team

 Owns the impediment backlog

Ha H N Van

Development

Team

 Responsible for quality

 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

Weekly Meeting, Email,

Weekly Meeting, Conference

Meeting

Product Owner,

Manager and Team

leader

Explicit Requirement Occasionally Email, Skype

Team Leader and

Team Member

Review Project progress and Daily Meeting

Daily Trello, Email,

Facebook

2.4 Communication and report

Table 4: Commmunication and report

Type of

communication

Methods, tools

Communication in group

Facebook

or email

Everyday Information about what

was done in the last 24 hours, working on plans for today, the difficulties encountered and the

Project team

solutions required

Meeting duration is about 20-30 minutes

Task Planning

Meeting

Meet face

to face

15-20 days All members in team

together to analyze the requirements, functions, work on the sprint going

to do, plan and design for the sprint

Project team, Product Owner

Task Review

Meeting

Meet face to face

15-20 days Completed

documentation

For each stage, sharing materials, given the strengths and weaknesses for each member, period of tasks and the solution

calculated measurement project

Project team, Product Owner

External communication and reporting

Task

Management

Trello Every day A web based task

tracking system is used for managing or

assigning task, reporting bugs/issues

Project team

3.1 Detailed schedule

Table 5: Detailed schedule

No Task Name Start Finish Effort Resource

2-Oct-2020 4-Oct-2020 5 hours

document for

10-Oct-2020 10-Oct-2020

5 hours Viet

3.2.8.1

Fix bugs of

Book tour 4-Dec-2020 4-Dec-2020 3 hours

Thi + Thong