HO CHI MINH NATIONAL UNIVERSITY

UNIVERSITY OF INFORMATION TECHNOLOGY

INFORMATION SYSTEM DEPARTMENT

FINAL REPORT
PROJECT MANAGEMENT

PROJECT
MOTOCYCLE ACCESSORIES WEBSITE

Lecturers: Ph.D Nguyễn Thanh Bình

Mr. Trần Vĩnh Khiêm
Student:
Nguyễn Thị Khánh Hà – 18520692

Ho Chi Minh City, June 2021

 THANK YOU

First of all, our team would like to express our sincere thanks to the lecturers of the
University of Information Technology - Vietnam National University, Ho Chi Minh
City, and the Department of Information Systems teachers for helping me have a basic
knowledge that underlies this thesis.

In particular, our group would like to express our deepest gratitude and gratitude to our
teacher - Ph.D Nguyen Thanh Binh and Mr. Tran Vinh Khiem, who guided me during
the project. The teacher and I directly guided, corrected, and provided many valuable
comments to help our group complete our subject report well. Once again, I sincerely
thank you and wish you good health.

During one semester of implementing the project, I applied the accumulated

background knowledge and combined it with learning and researching new knowledge
from teachers, friends, and many sources. references. From there, our team makes the
most of what has been collected to complete the best project report. However, because
of my limited professional knowledge and my lack of practical experience, the content
of the report cannot avoid shortcomings, I look forward to receiving further advice and
guidance from you to perfect our knowledge so that our group can use it as a luggage
to carry out other topics in the future as well as in future study and work.

Once again, I would like to send my sincere and best thanks to teachers and friends!

Ho Chi Minh City, June 2021

Student name
 TEACHER’s FEEDBACK
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………
…………………………………………………………………………………………

…………………………………………………………………………………………
 CONTENTS

THANK YOU...............................................................................................................2

TEACHER’s FEEDBACK..........................................................................................3

CONTENTS.................................................................................................................4

1. Executive Summary..............................................................................................6

2. Project Purpose/Justification...............................................................................7
2.1. Business Information..............................................................................................................7
2.2. Business Need/Case................................................................................................................8
2.2.1. Market Demand............................................................................................................8
2.2.2. Customer request..........................................................................................................8
2.2.3. Technological advance..................................................................................................8
2.3. Business Objectives................................................................................................................8
3. Project Description...............................................................................................9
3.1. Project Objectives and Success Criteria................................................................................10
3.2. Requirements........................................................................................................................10
3.2.1. Funtional Requirement.................................................................................................10
3.2.2. Non-Funtional Requirement.........................................................................................16
3.3. Constraints............................................................................................................................18
3.3.1. Milestones....................................................................................................................18
3.3.2. Project Budget.............................................................................................................19
3.3.3. Project Constraints.....................................................................................................19
3.3.4. Dependencies...............................................................................................................19
3.4. Assumptions.........................................................................................................................20
3.5. Preliminary Scope Statement................................................................................................20
4. General Technical solution.................................................................................21
4.1. General system architecture..................................................................................................21
4.2. Usecase.................................................................................................................................22
4.2.1. General usecase...........................................................................................................22
4.2.2. Order Usecase.............................................................................................................22
4.2.3. Mange Cart Usecase...................................................................................................23
4.2.4. Manage Category/Product Usecase...........................................................................23
5. WORK BREAKDOWN STRUCTURE (WBS)................................................23
6. Risks..................................................................................................................... 29

7. Project Deliverables............................................................................................31

8. Summary Milestone Schedule............................................................................32

9. Summary Budget.................................................................................................32

10. Project Approval Requirements........................................................................32

11. Project Manager & Stakehoder.........................................................................33

12. Authorization.......................................................................................................34
 EXECUTIVE SUMMARY

The COVID-19 pandemic continues to include many complex and unpredictable

developments that have significantly impacted every aspect of the economy. Shops
and business establishments are among the subjects directly affected. The difficulties
were aggravated when purchasing power and consumption of goods declined sharply,
significantly affecting revenues and profits.

Consequently, businesses and business owners also need solutions to modify their
operating practices, proactively address challenges, and quickly find new directions to
sustain the company's operations in difficult times to adapt to the complicated
developments of the COVID-19 pandemic, especially in the context of extended social
distancing, which has taken consumer behavior from offline to the Internet.

Selling through the website is no longer a strange form for consumers, selling through
the website is a very popular form of work, this form is chosen by any product
business. Website selling tool exchange of merchandise online between you (seller)
and your customer (buyer). Website selling you introduce products and services to the
needs of customers and make transactions without having to encounter them in person.
The project of building Motorcycle Accessories Website (MAW) was release to help
Quoc Hai - Motorcycle Accessories Distributor expand sales channels, improve
revenue, and help customers easily service vehicle maintenance requirements safety
and practicability.

Website selling motorcycle accessories online is a system to promote the branding of

the store as well as demonstrating the customer care at all times, everywhere. With this
website the customer does not need to stores or distributors that still reference works,
prices and information about each product and the assurance from the vendor, create
convenience, comfort customers when purchasing products.

Customer name QUOC HAI TRADING

Client Manager Nguyễn Thị Kim Chín
Project Name Motorcycle Accessories Website
Time Conventions 3 months
 Starting Date 1/07/2021
End Date 1/10/2020

1. PROJECT PURPOSE/JUSTIFICATION

1.1. Business Information

[1] Name: CÔNG TY TNHH TM - DV QUỐC HẢI

[2] English Name: QUOC HAI TRADING - SERVICE COMPANY
LIMITED
[3] Short name: QH Ltd
[4] Address: 327 Tieu La, Ha Lam, Thang Binh, Quang Nam
[5] Phone: (+84) 913 606 712 - (+84) 972 141 581
[6] Tax code: 4001177007

Figure 1.1 Quoc Hai’s Logo

Motorcycle Accessories Store - QUOC HAI specializes in providing motorcycle

parts, decorative accessories of all kinds. From the very beginning of its
establishment, Quoc Hai has determined for itself a clear direction: Bringing
good motorcycle spare parts products that meet assembly standards for the
 world's leading motorcycle manufacturers to Vietnamese consumers South with
the most reasonable price.

1.2. Business Need/Case

1.2.1. Market Demand

 Improve the company's professionalism.
 Increased competition in the parts market for motorcycles across Central.

1.2.2. Customer request

 Shopping for convenience merchandise.
 Get promotions, rebates more quickly.
 Seek out and compare products easily.
 Save time shopping
 Easily payable with various payment methods.
 Protect clients from the risk of becoming infected with COVID-19.

1.2.3. Technological advance

 An attractive, professional interface.
 Detailed product information.
 A shopping cart is easy to operate.
 Warehouse Management
 Integrate multiple payment methods.
 Online consultation assistance.
 Compatible with all devices
 Speedy loading of pages.
 The management system is easily usable.
 A business website with a standard SEO interface.

1.3. Business Objectives

 Figure 2.1 Business Objectives

 Expand customer find and reach, enhance customer interaction 50% next first
year
 Reduce the number of renting more premises and personnel by 50% in the first
year
 Sustain commercial activity during the COVID-19 pandemic, increase online
revenue by 25% in the next year.
 Enhancing opportunities for association and cooperation.
 Effective establishment of the branding
 Unlimited promotional activities.Unlimited promotional activities.

2. PROJECT DESCRIPTION

MAW is the project to build a website to sell motorcycle parts completely new,
providing users and store interactions with each other through a friendly website
interface and easy to use. The website will provide detailed information about
products, services, store locations so that customers can search, select, buy
replacement parts and pay online. In order to facilitate bulk buying, a shopping cart is
available to the user. The website will have a compelling user interface for visitors and
a user interface to manage the site. Moreover, the system is optimized for security and
 a strict security assessment before being put into service, in order to avoid interruption
of business activities or exposed customer data and important information.

2.1. Project Objectives and Success Criteria

The objectives that mutually support the milestones and deliverables of this project
have been established. To succeed in the MAW project, the following objectives
must be achieved on time and within planned budget allocations:

 The solution was completed and tabled with CEO Quoc Hai on September
1, 2021.
 The necessary equipment and licenses are delivered in their entirety.
 The website must be fully tested before being put into use.
 Critical bugs are to be resolved by October 30, 2021
 All staff must be trained prior to usage 100%
 The software is completely functional and stable.
 The core functions must be guaranteed not to cause errors losses 100%
 Design and test a new website within the next 60 days
 Complete implementation commercial website within the next 90 days

2.2. Requirements

2.2.1. Funtional Requirement

MENU
Homepage About Product Contact
Company Category

NO PAGE DESCRIPTION FUNCTIONS

1 Homepage  Website show promotion
banner/slide
Presenting an  Website show list best-seller
elegant, simple, products gentle form of
friendly movement
 Website allows admin edit
Color on the promotion’s slide by add image
 website tone of
the company
logo.
2 About Company  Display business information
Company Introduction including:
o Mission
Simple, formal o Vision
o Core values

 Website allows admin

customize posts: add, edit,
delete, hide, show posts.

 Website allows admin

customize text attributes: font,
size, type, highlight.

 Website allows admin add

images…

3 Product Category &  Website allows customer

Category Product search product by name, ID

 Website allows customer filter

product by category

 Display products by category.

 Website allows admin to add,

delete, edit, hide products on
categories and product details.
  Website allows admin to
manage keywords,
descriptions, tags for SEO,
friendly seo links (URLs) easy
to customize...

 Various product information

includes:
o Product's name
o Short description of the product
(if needed)
o Avatar
o Detailed photos
o Selling price by volume
o Purchase quantity (2 buttons -
+)
o Order Button
o Product details tab: single
content page
o Purchase Instructions tab:
single content page
o View product photos as a
popup when clicking on the
detail image.
4 Contact A form providing  The content of the form
contact includes:
information and
automatically o Full name
receive o Address
information/
 requirements o Email
from customers. o Contents
5 Manage  Allow customers to order
Cart products online.
Admin can view
order list statistics  Customers must log in to an
over time. account to order products
online.
Admin can
Delete, edit  Goods can be kept in the basket
orders. for later ordering.

Admin can view

order information.  Has the function of shopping
Admin can cart, order management:
change order Customers can
status Add/Remove/Edit/Delete
Admin can cancel Products in the cart.
the order

 Customers can track the status

Website send cart of their orders (processed,
information and unprocessed).
order information
to the website  Save the cart state at the time
administrator via of access.
email.

 The item is added to the cart,

the price of the item is
calculated on each item and the
total amount to be paid.
OTHERS REQUIREMENT
1 Register  Allows users to register for an
account.
 Register’s information:

o Full-name
o Email
o Phone Number
o Address

 Website automatically saves

customer information when
registering an account.

2 Login  Users who have an account can

then log in to the website.

 Logged-in users can buy

products online on the auto
parts trading website.

 Users must check their own

account information before
making a purchase.

 Users can reset password by

phone number
3 Intergrated  User can chat directly with
chatting online staff
 Admin can track all message
4 Report  Orders export features as
 Excel.
 Analyze number of customer
on day/week/month/
 Statistical access:
 Number of people accessing
the website to buy and sell
motorcycle parts
 Number of customers who are
online.
5 Payment  Allow admin to update
information about payment
methods including:
 Cash payment at the store
 Transfer payments
 Ship COD
 Customers choose a payment
method during the ordering
process, this information is
stored and the order is easily
collated by the admin when
needed.
6 Social  Allowing sharing via social
networks helps increase social
communication, resulting in
greater efficiency.
 Allows printing of product
information.
 Allow product link via email to
others.
 Display the posting date, article
views to attract more readers
 and the host to evaluate the
effectiveness of the website.

2.2.2. Non-Funtional Requirement

1. Operational

1.1 The MAW database should be restructured so that it can be searched by name,
gender, nickname, hometown, year of birth.

1.2 Website can be run on all browsers (including internet explorer)

2. Performance

2.1 All data input and output screens need to be ready to be displayed to the user within
3 seconds, provided that loading and connecting between client/server is normal,
specifically:

A. For input screen: up to 30 data fields, no complex data calculations, no interaction

with external systems, can store data directly to the DB, and no internal files are stored
large content such as: images, videos, files over 3MB.

B. For the output screen: data is queried directly from the DB, limiting complex
queries, queries from external systems.

Displays up to 50 rows of data, up to 10 columns each, and each data is less than 100
characters in length.

C. Normal load condition: 30 CCUs (concurrent user) when load balancing is not in
use.

D. Minimum server conditions: Intel Core i5, 4GB RAM, 500GB hard disk.

E. Client/ Server Connection: 500KB/s

2.2 The site can handle 500 requests at the same time

3. Security
 3.1 User information must be kept strictly confidential.

3.2 Payment information will be encrypted and secure.

3.4 The system will deactivate for 30 minutes if the user enters the wrong password 5
times in a row.

3.5 User password must be hashed with b-crypt, s-crypt or argon2.

3.6 When the user makes an online payment, the system is not allowed to store the
user's credit/debit card information.

4. Usability

4.1 Minimize new user actions on the screen.

4.3 The system must make the user proficient within 5 minutes.

4.4 Error Tolerance is extremely low, check the data type right on each field, and
immediately warn if there is an error, do not force the user to enter it again and again.

5. User Interface

5.1 The system must ask for confirmation (Y/N) for data deletion operations.

5.2 Must be vertical scrolling, minimize horizontal scrolling.

5.3 The entire drop-down-list must be arranged in order of A to Z and ascending

number.

6. Available

7.1 The system must ensure 24/7 operation, maximum upgrade 1 time within 3 months,
downtime per year not exceeding 1 hour.

2.3. Constraints

2.3.1. Milestones

TIMELINE DUE DATE

 Starting Date 01/07/2021
Complete design solutions 30/07/2021
Develop and complete demo 15/8/2021
Complete testing 30/8/2021
Complete user training 30/8/2021
Deployed in a real business’s environment 15/09/2021
Complete the project 01/10/2021

2.3.2. Project Budget

PROJECT COMPONENT COST
Human Resources 5,000,000
Hardware & device 10,000,000
Software Licensing 19,000,000
Other costs incurred 5,000,000
Total 39,000,000

2.3.3. Project Constraints

The following constraints pertain to the MAW project:

 All security hardware and software must be compatible with our current IT
platforms
 All hardware and software must be purchased in accordance with the allocated
budget and timeline
 The project team need to analyze how the past stages of the project performed,
noting trends and impacts on future plans, and communicating these findings to
all relevant stakeholders.
 Having a contingency plan to identify all risks that the course of action to be
taken if they materialize.
 One IT specialists will be provided as resources for this project
 All project members must use Asana to track project progress
  Direct meetings are held once a week on Friday

2.3.4. Dependencies
Some depend on the project MAW is:

 Design solution must be agreed by business owners before deployment

 The business process must be agreed before deployment
 Software and hardware must be purchased before implementing testing
 Users must be made before the project training run

2.4. Assumptions

The following are a list of assumptions. Upon agreement and signature of this
document, all parties acknowledge that these assumptions are true and correct:

 Personnel costs will not change during the project cycle.

 The overall cost of day-to-day operations will not increase.
 The scope of the project will not change throughout the life cycle.
 This project has the full support of the project sponsor, stakeholders, and all
departments
 The purpose of this project will be communicated throughout the company
before deployment
 The IT manager will provide additional resources if necessary
 The remaining costs related to materials and resources will remain constant
throughout the project.
 Project team members will be provided with the resources they need to
perform their individual tasks promptly, from specialized equipment and
software to electricity during working hours.
 The people involved in the project might not be in their best condition or
health throughout the project life-cycle because sickness and fatigue might
result in a lack of efficiency when carrying out the project. This may violate
the assumption that all of the people involved will be doing their work
efficiently throughout the project.
2.5. Preliminary Scope Statement

The CSMW project will include the design, testing, and delivery of an improved
intranet website system throughout the organization.

All personnel, hardware, and software resources will be managed by the project team.
All project work will be independent of daily and ongoing operations and all required
testing will be done in the IT laboratory.

All project funding will be managed by the project manager up to and including the
allocated amounts in this document. Any additional funding requires approval from the
project sponsor.

This project will conclude when the final report is submitted within 30 days after the
intranet website solution is tested and deployed throughout the organization, all
technical documentation is complete and distributed to the appropriate personnel, and
a list of future website optimize considerations is complete and submitted to the VP of
Technology.

3. GENERAL TECHNICAL SOLUTION

3.1. General system architecture

 Figure 4.1 General system architecture

3.2. Usecase

3.2.1. General usecase

 Figure 4.2 General use case diagram

3.2.2. Order Usecase

Figure 4.3 Product ordering use case diagram

3.2.3. Mange Cart Usecase

 Figure 4.4 Manage shopping cart use case diagram

3.2.4. Manage Category/Product Usecase

Figure 4.4 Manage category/product use case diagram

4. WORK BREAKDOWN STRUCTURE (WBS)

Task Name Duration Start Finish

QUOC HAI - Motorcycle Accessories Thu Fri
90 days
Website 7/1/21 10/1/21
A. Collect and analyze requirement 15 days Thu Thu
 7/1/21 7/15/21
Thu Sat
Collect functional requirement 10 days
7/1/21 7/10/21
Thu Sun
Collect Product Category requirement 3 day
7/1/21 7/4/21
Sun Tue
Collect Homepage requirement 2 day
7/4/21 7/6/21
Tue Thu
Collect About Company requirement 2 day
7/6/21 7/8/21
Thu Sat
Collect Contact requirement 2 day
7/8/21 7/10/21
Sat Sun
Collect another functional requirement 1 day
7/10/21 7/11/21
Sun Fri
Collect non-functional requirement 5 day
7/11/21 7/16/21
Sun Mon
Collect Operation requirement 1 day
7/11/21 7/12/21
Mon Tue
Collect Performance requirement 1 day
7/12/21 7/13/21
Tue Wed
Collect Security requirement 1 day
7/13/21 7/14/21
Wed Thu
Collect Usability requirement 1 day
7/14/21 7/15/21
Thu Thu
Collect User Interface requirement 0,5 day
7/15/21 7/15/21
Collect another non-functional Thu Fri
0,5 day
requirement 7/15/21 7/16/21
Fri Fri
B. Write analysis documentation 7 days
7/16/21 7/23/21
Fri Sat
Write a functional description document 1 day
7/16/21 7/17/21
Sat Sun
Draw interface model forms (wireframe) 1 day
7/17/21 7/18/21
Complete requirements collection and Sun Mon
1 day
analysis 7/18/21 7/19/21
Mon Tue
Solution design 1 day
7/19/21 7/20/21
 Tue Wed
Architecture document 1 day
7/20/21 7/21/21
Wed Thu
General design 1 day
7/21/21 7/22/21
Thu Fri
Details design 1 day
7/22/21 7/23/21
Fri Mon
C. Buy license (hardware/software) 3 days
7/23/21 7/26/21
Collect quotation of license Fri Sat
1 day
(Domain/Hosting/Devices) 7/23/21 7/24/21
Sat Sat
Make a buying decision 0,5 day
7/24/21 7/24/21
Sat Sun
Sign contract 0,5 day
7/24/21 7/25/21
Sun Sun
Sign up and paid 0,5 day
7/25/21 7/25/21
Website develope and write test case Sun Mon
0,5 day
7/25/21 7/26/21
Mon Sat
D. Website develop 40 days
7/26/21 9/4/21
Mon Thu
Back-end develop 25 days
7/26/21 8/19/21
Mon Wed
Develop Login functions 3 days
7/26/21 7/29/21
Wed Sat
Develop Register functions 3 days
7/29/21 8/1/21
Sat Tue
Develop Menu 3 days
8/1/21 8/4/21
Tue Sat
Develop Homepage functions 3 days
8/4/21 8/7/21
Sat Tue
Develop About Company Page functions 3 days
8/7/21 8/10/21
Develop Category product Page Tue Sat
3 days
functions 8/10/21 8/13/21
Sat Mon
Develop Contact Page functions 2 days
8/13/21 8/15/21
Develop Order functions 2 days Mon Wed
 8/15/21 8/17/21
Wed Fri
Develop Admin functions 2 days
8/17/21 8/19/21
Fri Sat
Develop Addition functions 1 days
8/19/21 8/20/21
Sat Fri
Front-end develop 15 days
8/20/21 4/16/21
Sat Sat
Develop Login functions 3 days
8/20/21 8/20/21
Sat Sat
Develop Register functions 2 days
8/20/21 8/20/21
Sat Sat
Develop Menu 2 days
8/20/21 8/20/21
Sat Sat
Develop Homepage functions 1 day
8/20/21 8/20/21
Sat Sat
Develop About Company Page functions 1 day
8/20/21 8/20/21
Develop Category product Page Sat Sat
1 day
functions 8/20/21 8/20/21
Sat Sat
Develop Contact Page functions 1 day
8/20/21 8/20/21
Fri Fri
Develop Order functions 1 day
4/23/21 4/23/21
Sat Sat
Develop Admin functions 1 day
4/24/21 4/24/21
Sat Sat
Develop Addition functions 1 day
8/20/21 8/20/21
Fri Fri
E. Write test case 5 days
4/23/21 4/23/21
Sat Sat
Write Login test case 1 day
4/24/21 4/24/21
Sat Sat
Write Register test case 1 day
8/20/21 8/20/21
Fri Fri
Write Order module test case 1 day
4/23/21 4/23/21
Sat Sat
Write Manage test case 1 day
4/24/21 4/24/21
 Sun Sun
Complete develop and demo 1 day
4/25/21 4/25/21
Mon Mon
F. Testing 7 days
4/26/21 4/26/21
Tue Tue
Test Login functions 1 day
4/27/21 4/27/21
Sat Sat
Test Register functions 1 day
8/20/21 8/20/21
Fri Fri
Test Homepage functions 1 day
4/23/21 4/23/21
Sat Sat
Test About Company Page functions 1 day
8/20/21 8/20/21
Fri Fri
Test Category product Page functions 0,5 day
4/23/21 4/23/21
Sat Sat
Test Contact Page functions 0,5 day
4/24/21 4/24/21
Sat Sat
Test Order functions 0,5 day
8/20/21 8/20/21
Fri Fri
Test Admin functions 0,5 day
4/23/21 4/23/21
Sat Sat
Test user-interface 0,5 day
4/24/21 4/24/21
Wed Wed
Acceptance testing 0,5 day
4/28/21 4/28/21
Thu Thu
G. Operate 5 days
4/29/21 4/29/21
Sun Tue
Writing handover documents 1 day
5/2/21 5/4/21
Sun Mon
User training 1 day
5/2/21 5/3/21
Tue Tue
Project Audit 1 day
5/4/21 5/4/21
Wed
Project handover 1 day Fri 5/7/21
5/5/21
Wed Thu
Project summary report 1 day
5/5/21 5/6/21
H. Launch 2 days Sat Sat
 8/20/21 8/20/21
Data entry and configuration on real Fri Fri
2 days
environment 4/23/21 4/23/21
Mon Mon
I. Deleverable 5 days
5/10/21 5/10/21
Tue Tue
Release documentatio 2 days
5/11/21 5/11/21
Wed Wed
End-user documentation 2 days
5/12/21 5/12/21
Thu Thu
Website administration documentation 1 day
5/13/21 5/13/21
Thu Thu
J. Go Live 1 day
5/13/21 5/13/21

5. RISKS
No probabilit
Name of risk rate Signs identify ways of dealing
. y

1 Conflicts 30% 1 The lack of Create group

between communication between activities (team
group members, attitude, and building activities)
members gestures are not happy. such as eating
together, happy
lunch every month,
birthday parties,
outside activities...
to create close
relationships
between members.

2 Collecting 25% 2 After collecting Ask the staff

functional collected information, member in charge to
requirement s write documents, will consider additional
missing  send down to corrections.
departments for
confirmation.

The departments have

not or not confirmed.

3 Staff CoV19 by 30% 4 Employees have up medical report,

isolated expressed fatigue, dry requested disinfect
infections prolonged fever the entire school,
implement hygiene
measures such as
wearing a mask,
washing hands often
with antibacterial
solution, avoiding
close contact.

4 Employees 50% 1 or alienating attitude. Will inquire about

leave Arrive late and come the reason for
home early. Do not leaving to adjust.
focus on work.  Arrange backup
personnel when
replacement is
needed. Priority is
given to people who
are working in the
company. If there is
no available staff,
recruit.

5 Software 5% 5 Few progress reports, Report to

 supplier deliberate avoidance, management
company ambiguous behavior propose a plan to
suspended by find another
police for software supplier to
investigation replace

7 Software 50% 2 Periodic reports do not Quickly contact the

companies meet requirements supplier Request for
develop immediate
functions that correction
are not as
required

8 Not 25% 1 The departments have Inform the

providing many projects and the management and
enough staff employees are all too departments about
to work as busy. the project in
planned advance.

Requiring
management and
departments to
commit and plan to
provide enough
staff.

9 Buying a 50% 1 There is unfavorable Ask the partner to

Server is late information when check and commit to
compared to contacting the partner. the server delivery
the plan time. Regularly
check in with your
partner.

Ask the partner to

temporarily lend
another server if
needed.

10 Equipment 40% 3 The USD exchange rate Investigate the

purchased is is increasing against reason and contact
more VND, the inflation rate the person in charge
expensive is increasing, leading to to request an
than expected an increase in prices, explanation.
especially imported
goods.

6. PROJECT DELIVERABLES

 Solution selling motorcycle accesories website is fully functional deployment

 Ensuring information security access solutions
  Equipment and license must be fully handed over
 Technical documentation and support
 Instruction document

7. SUMMARY MILESTONE SCHEDULE

Summary Milestone Schedule – List key project milestones relative to

project start.
Project Milestone Target Date
(mm/dd/yyyy)
 Project Start 01/07/2021
 Complete analyze requirement 20/07/2021
 Complete Develop 20/08/2021
 Complete Testing 1/09/2021
 Complete Training 15/09/2021
 Complete Lauch 25/09/2021
 Complete Deleverable 30/9/2021
 Project Complete 01/10/2021

8. SUMMARY BUDGET

Summary Budget – List component project costs

Project Component Component
Cost
 Personnel Resources 10,000,000
 Hardware 10,000,000
 Software and Licensing 5,000,000
 IT Preparation 30,000,000
Total 55,000,000

9. PROJECT APPROVAL REQUIREMENTS

Success for the MAW project will be achieved when a fully tested intranet security
solution, and all technical documentation, is fully deployed throughout the company
within the time and cost constraints indicated in this charter. Additionally, this
measure of success must include a recommendation list for future function
considerations as we fully need the necessity of this solution. Success will be
determined by the Project Sponsor, Mrs. Khanh Ha, who will also authorize
completion of the project.

10. PROJECT MANAGER & STAKEHODER

Nguyen Thi Khanh Ha – 0918.333.444 – khanhha@gmail.com

Nguyen Thi Khanh Ha acted as the Project Manager for the duration of the HSM
Project. She will manage all HSM project tasks, planning and communication efforts.
Her team, consisting of two IT specialists and one security specialist, will receive
support from the IT department. Ms. Ha is authorized to approve all budget
expenditures up to and including allotted budget amounts. Any additional funding
must be requested through the Project Sponsor, Ms. Nguyen Thi Kim Chin. Ms. Ha
will provide weekly updates to the Project Sponsor.
11. AUTHORIZATION

Approved by the Project Sponsor:

Khanh Ha
_______________________________________ Date: 26/06/2021