DUYTAN UNIVESITY
INTERNATIONAL SCHOOL
PROJECT PROPOSAL
KFC VIETNAM ORDER SYSTEM
Version: 1.3
Project team : HTC Team
Member
: Hung Phi Cao
Han Van Le
Chuong Hong Nguyen
Tan Nhat Tran Van
Hoang Phuc Tran
Mentor 1
: Son Van Phan
Mentor 2
: Toan Duc Vo
Project Proposal | HTC Team
Document Approvals: The following signatures are required for approval of this
document.
Mentor 1
Son V. Phan
Signal
Date
Signal
Date
Signal
Date
Signal
Date
Mentor 2
Toan D. Vo
Customer
KFC Vietnam Stores
Team leader
Hung P. Cao
P a g e 1 | 23
Project Proposal | HTC Team
Revision history
Date
Version
A, M, D (*)
Description
Author
10/03/2013
1.0
A
- The draft
Hung P. Cao
19/03/2013
1.1
M
- Section 3.3.1
Hung P. Cao
22/03/2013
1.2
A
- Section 3.3.2
Hung P. Cao
29/03/2013
1.3
M
- Section 3.1
A
- Section 1.3
Hung P. Cao
(*) A-added, M-modified, D-deleted
P a g e 2 | 23
Project Proposal | HTC Team
TABLE OF CONTENT
Definitions ...................................................................................................................... 5
1
2
3
Introduction ............................................................................................................. 6
1.1
Purpose .............................................................................................................. 6
1.2
Scope ................................................................................................................. 6
1.3
Documents referenced ....................................................................................... 6
Project overview...................................................................................................... 7
2.1
Business needs................................................................................................... 7
2.2
Proposed solution .............................................................................................. 7
2.3
Project goal ........................................................................................................ 8
Master plan .............................................................................................................. 9
3.1
Process description ............................................................................................ 9
3.2
Organization management ................................................................................ 9
3.2.1
Project team information ............................................................................ 9
3.2.2
Role and responsibility ............................................................................. 10
3.2.3
Communication, tracking and reporting plan ........................................... 12
3.2.4
Tool and techniques .................................................................................. 13
3.3
Schedule .......................................................................................................... 14
3.3.1
Milestones ................................................................................................. 14
3.3.2
Work breakdown structure ....................................................................... 14
3.4
Estimation........................................................................................................ 15
3.4.1
Risk management plan.............................................................................. 15
P a g e 3 | 23
Project Proposal | HTC Team
THE TABLE OF FIGURES
Figure 3.1: XP Process for systems................................................................................ 9
P a g e 4 | 23
Project Proposal | HTC Team
Definitions
Definitions/Acronyms/Abbreviations
Description
XP process
Extreme Programming process
P a g e 5 | 23
Project Proposal | HTC Team
1 Introduction
1.1 Purpose
KFC Vietnam Oder System proposal is to propose our ideas about the project.
Project description project will be developed. It includes overview of product,
process, and project team. It also shows solution for company and benefits that
you will get when the project completed.
In addition, it also provides a master plan of project include process
description, organization management, schedule and estimation.
1.2 Scope
This document provides an overview of project will be developed. It includes
overview of the product, overview of the process, and overview of the project
team.
The document provides a comprehensive master plan for each phase of
software development based on the processes that have been selected, including
start time, finish and the number of working days. This is the general plan and
will be updating the details during the process of developing website in the
version document.
Proposal is included in the document giving different ways to solve the
problem to decide the best solutions to develop software.
1.3 Documents referenced
[1]. Extreme Programing Process: http://www.extremeprogramming.org/
P a g e 6 | 23
Project Proposal | HTC Team
2 Project overview
2.1 Business needs
Customer: KFC Vietnam Stores
HEAD OFFICE
51/1 Bach Dang Street, Tan Binh District, Ho Chi Minh City, Vietnam
Phone: (84.8) 38 48 9828
(84.8) 38 48 9825
Email: lienhe@kfcvietnam.com.vn
KFC are known to at Vietnam with a name calling the chicken run Kentucky
- chain stores served of dishes from chicken, Bo-GO and Mon Floating known
first is a chicken bee run Kentucky is invented by Harland Sanders.
Six one series successfully of the system chain food restaurants Trademark
quick with KFC (above 10,000 restaurant has been a development in the entire
World), Vietnam at KFC have joined to the field once the first to 12/1997 at
Saigon Trade Center Super Bowl. Time here, the system food restaurants quick
is already lost in most of the route City the Philippines.
Nowadays, KFC Vietnam stores has many branches in many provinces and
cities. They, therefore, need a tool help their customers easily to search and order
food. In addition, this tool also support KFC Vietnam Stores manage their
customer easy and convenient. Especially, this tool must be effective to compete
against other company in the same business area, such as Lotteria or Burger
King.
2.2 Proposed solution
Our team decides to build a KFC Vietnam Order System with full features
for users based on management process and business needs of the KFC Vietnam
Stores:
P a g e 7 | 23
Project Proposal | HTC Team
-
This system will be developed based on web service and mobile devices
to ensure customers can order quickly and easily within a radius of 20km
and from 9am to 9pm.
-
KFC Vietnam Order System also helps restaurant managers manage their
stores (customers and food) more effective.
-
Customers, who use application through mobile devices in anywhere, will
connect to the nearest KFC Vietnam Stores with them to order food or use
function of system.
2.3 Project goal
The purpose of the project is to deliver KFC Vietnam Order System to KFC
Vietnam stores, which must satisfy following requirements:
-
The product must have all features, which KFC Vietnam Stores required
(refer to the user stories).
-
Administrators of the system can manage the system more effective about
foods and customers.
-
Customers can order foods or use function of application easily. They do
not spend more time going to KFC stores to buy foods.
P a g e 8 | 23
Project Proposal | HTC Team
3 Master plan
3.1 Process description
Figure 3.1: XP Process for systems [1]
3.2 Organization management
3.2.1 Project team information
Name
Address
[Mentor 1] Son Van Phan
sonpvs@duytan.edu.vn
[Mentor 2] Toan Duc Vo
voductoandtu@gmail.com
Hung Phi Cao
caophihung91@gmail.com
Han Van Le
vanhan91@gmail.com
Chuong Hong Nguyen
chuongk15cmuhttt@gmail.com
Hoang Phuoc Tran
phuochoangdtu@gmail.com
Tan Nhat Tran Van
vtnt411@gmail.com
P a g e 9 | 23
Project Proposal | HTC Team
3.2.2 Role and responsibility
Role
Team leader
Responsibilities
-
Motivate team members.
-
Run weekly team meeting.
-
Report weekly status.
-
Help team to allocate tasks.
-
Act as facilitator and timekeeper for
Participant(s)
- Hung P. Cao
team meetings.
-
Maintain the project notebook.
-
Lead team in producing developer
cycle report.
Interaction
designer
-
Write and clarify use cases and other - Hung P. Cao
requirements with the customer.
-
Lead usability tests, and analyze - Han V. Le
results, design database.
-
(low level)
(high level)
Define, design and refine the user - Chuong H. Nguyen
interface
(low level)
- Tan N. T. Van
(high level)
- Hoang P. Tran
(low level)
Programmer
-
Estimate tasks.
- Hung P. Cao
-
Detailed design
(low level)
-
Write code and tests.
-
Improve gradually the design.
- Han V. Le
(high level)
- Chuong H. Nguyen
(low level)
P a g e 10 | 23
Project Proposal | HTC Team
- Tan N. T. Van
(high level)
- Hoang P. Tran
(low level)
Customer/
Client
-
Writes user stories and specifies - KFC Vietnam Stores
functional tests.
-
Sets priorities, explains stories.
-
May or may not be an end-user.
-
Has authority to decide questions
about the stories.
Mentor/Coach
Tester
-
Confirmation documents.
-
Help the team during the doing this
project.
Create test case, test report.
- Hung P. Cao
-
Implements and runs functional tests
(not unit tests!).
-
Graphs results, and makes sure
- Son V. Phan
(low level)
- Han V. Le
(high level)
people know when test results - Chuong H. Nguyen
decline.
(high level)
- Tan N. T. Van
(high level)
- Hoang P. Tran
(high level)
Other roles
-
Write user’s guide.
- Hung P. Cao
-
Installation release.
(high level)
- Han V. Le
(low level)
- Chuong H. Nguyen
P a g e 11 | 23
Project Proposal | HTC Team
(low level)
- Tan N. T. Van
(low level)
- Hoang P. Tran
(low level)
3.2.3 Communication, tracking and reporting plan
Type of
Communication Communication
communication
Status report
Who
schedule
way
initiates
Every Friday
Team meeting
Project
Recipient
Project team.
manager.
Schedule and
Daily.
Google docs.
mentor.
report
Work report
Project team.
manager,
effort checking
Work review
Project
Daily.
At the end of
job.
Face to face,
Project
Email, Skype.
manager.
Email, yahoo,
Project team.
Member.
Project team.
Project
Project team,
Code.google,
Skype.
Project
Every
review, ask
Thursday. (May
problems
be change later.)
Team meeting
with mentor.
manager.
mentor.
P a g e 12 | 23
Project Proposal | HTC Team
Ask, review
Any time.
Face to face,
Member/
email, Skype.
problem
Project team,
individual. mentor.
3.2.4 Tool and techniques
Platform
Windows
Windows 7,8
PHP
5.2, 5.3
.NET Framework
4.0
Database
MySQL
5.1, 5.5
Web Server
Apache
2.0, 2.2
Applications
Microsoft Word
2007, 2010, 2013
Microsoft Excel
2007, 2010, 2013
Client (Browser)
Tool
Microsoft Visual Studio
2012
Eclipse
phpMyadmin
P a g e 13 | 23
Project Proposal | HTC Team
3.3 Schedule
3.3.1 Milestones
The project was implemented during the period from March 8th, 2013
to May 13th, 2013, through the stages and modules.
With a specific time, the project will be completed on cost limits and
time permit. Minimize the problem over budget and time specified.
Phase
Start day
End day
Human
Project initiation
08/03/2013
20/03/2013
HTC Team
Development 1
21/03/2013
09/04/2013
HTC Team
Development 2
10/04/2013
06/05/2013
HTC Team
Implementation
07/05/2013
13/05/2013
HTC Team
3.3.2 Work breakdown structure
 Project initiation:
 Create proposal document.
 Create project plan document.
 Gathering requirement
 Development 1:
 Risk assessment.
 Analysis user stories and create breaking stories.
 Design.
 Iteration.
 Acceptance test.
 Release.
P a g e 14 | 23
Project Proposal | HTC Team
 Development 2:
 Risk assessment.
 Analysis user stories and create breaking stories.
 Design.
 Iteration.
 Acceptance test.
 Release.
 Implementation
 User guide
 Review and maintain.
3.4 Estimation
3.4.1 Risk management plan
The Project Management will generate a separate Risk Management
Plan document. Risks will be identified at the beginning of each phase and
the Project Management will assemble them into a prioritized risks list.
During the weekly status meeting, the team members will raise risks and
reassess the prioritized risks and if necessary, revise the list. The team will
use a “Risk Statement.” Team members will determine mitigation plans for
all identified risks and tasks that need to be completed and then these risks
and tasks will be assigned as action items. The team will monitor high
priority risks every week. All risks will be documented by the team.
P a g e 15 | 23
Project Proposal | HTC Team
Factor
Scope definition
Description
Likeli
hood
Impacts Grade
Scope changes may
Mitigation
Strategy
Analysis
arise during project.
and evaluate
Redundant scope
scope.
may be discovered.
H
H
A
Reduce
marginal
requirement.
Requirements
definition
Internal
Unifying
inconsistencies may
requirements
exist within
before
requirements.
proceeding
Key requirements
analysis. In
may be missing from
case if the
formal requirement
specification.
H
H
A
group does
not agree,
then meeting
with
instructors to
have the
conclusion.
P a g e 16 | 23
Project Proposal | HTC Team
Technical
processes
Standard processes
Analysis
may not meet
requirement
requirements of
and process
specific solution.
to ensure
New processes may
suitable
be required.
level.
Processes may be
improved and made
If the new
L
M
D
more effective.
process is
required we
need meeting
to evaluate
this one has
improve
more old
process.
Technology
Access to the
Share
supporting tools can
lead to extending the
time to learn and get
Technical
interfaces
experience in
M
M
C
using tools to
reduce
familiar with the
research time
tool.
and study.
Data
Advantage
inconsistencies
across interfaces
may require rework.
of iterative
M
M
C
processes to
overcome
this problem.
P a g e 17 | 23
Project Proposal | HTC Team
Design
It may prove
Will be
impossible to meet
some requirements
Project
management
update and
M
H
B
edit in
within design
version 2 of
documents.
project.
Project
Discuss
management systems
with our
may not be adequate
team to have
to support project
accurate and
requirements.
L
M
D
suitable
decision.
Poor decisionmaking may result in
inappropriate task
allocation.
Organization
Reorganization
Training for
may negatively
new member
impact project
to ensure that
organizational.
Changes in team
M
M
C
this member
understand
structure may
our project
negative affect
and the rules.
project.
Resourcing
Key resources may
be unavailable when
Training for
M
H
B
all members
required. Specific
skills may not be
P a g e 18 | 23
Project Proposal | HTC Team
available when
required.
Communication
The client’s
Having
requirement may be
analyzed the
misunderstood.
request and
Project reporting
recommende
needs may change
d customers
during project.
signed
Key stakeholder
M
H
B
certification
interests may change
to ensure that
(positively or
customer
negatively).
requirements
are not
misunderstoo
d.
Information
Client may fail to
During get
provide required
requirement
information on time.
process from
Client-supplied
customer we
information may be
inadequate to
support project.
M
L
D
should speak
again and
make
requirement
clearly with
customer.
P a g e 19 | 23
Project Proposal | HTC Team
Health
Health may change
The project
during the project.
plan has
An accident or
backup time
incident may occur
to ensure that
delaying the project.
M
M
C
if there are
any health
risks, they
will not
interrupt the
project.
Time
Time for project
Reduce
implementation is
offline
too short, so our
meeting time,
team couldn’t finish
make the
this project on time.
most of free
time, and
During project
implementation
process, our team
has to learn and has
many things to do,
our team can’t focus
increase our
H
M
B
work
overtime on
Saturday and
Sunday.
whole their time to
implement this
project.
P a g e 20 | 23
Project Proposal | HTC Team
Rating for Likelihood and Seriousness for each risk
L
Rated as Low
E
Rated as Extreme (Used for
Seriousness only)
M
Rated as Medium
H
Rated as High
NA Not Assessed
Grade: Combined effect of Likelihood/Seriousness
Likelihood
Seriousness
low
medium
high
EXTREME
low
E
D
C
A
medium
D
C
B
A
high
C
B
A
A
Recommended actions for grades of risk
Grade
A
Risk mitigation actions
Mitigation actions to reduce the likelihood and seriousness to be
identified and implemented as soon as the project commences.
B
Mitigation actions to reduce the likelihood and seriousness to be
identified and appropriate actions implemented during project
execution.
P a g e 21 | 23
Project Proposal | HTC Team
C
Mitigation actions to reduce the likelihood and seriousness to be
identified and cost for possible action if funds permit.
D
To be noted - no action is needed unless grading increases over time.
E
To be noted - no action is needed unless grading increases over time.
P a g e 22 | 23