SOFTWARE PROJECT MANAGEMENT PLAN
II. SOFTWARE PROJECT MANAGEMENT PLAN
1. Problem Definition
1.1 Name of this CapStone Project
Name of the project is “Using Felica card and Apriori algorithm in Restaurant management”.
1.2. Problem Abstract
Restaurants in Vietnam are growing in number and quality, diversity and richness of style,
type of services. It has become more and more complex to manage large restaurants with lots of
services. With the help of information technology, management in restaurants now is computerized.
The kind of management software is becoming professional to support all complicated restaurant
domains.
However, because different restaurants have a different management method, it’s hard to
develop a standard system which meets all customers’ need.
One of the most important things is until now all restaurant management software packages
don’t support the method to assess the business situation and predict sales in near future.
1.3. Project Overview
1.3.1.The current system
Already defined in the introduction document
1.3.2.The proposed system
The system under development will concentrate on three parts:

Developing a restaurant management system which includes all required domain functions:
Our proposed system is expected to be a system which offers the management and all
departments in a restaurant the tools to manage restaurant through software. Almost handy
tasks like creating accounting report, printing bill… will be computerized. The system also
eliminates all the guesswork and count out of tracking inventory. It’s helpful to inform of
the inventory status at all times.

Using Felica card as VIP card in discount management: The system will support VIP cards
as discount which encourages the customers for future come.

Applying Apriori algorithm to mining real data to find out relationship rules: Using
algorithm, data mining is executed basing on the real data of restaurant. The process
provides the development trends and relationship between entities within the restaurant.
From that, the managers have the base to think of some changes or strategy in the near
future.
1.3.3.The boundaries of the system
Scopes of the project will be as listed in the following table
Software Project Management Plan
Software Requirements Specification
+ User Requirement
+ Functional and non-functional requirement
+ Specific Requirements
Software Design Description
Software Testing Documentation
Source code package
User manual
1.3.4. Development Environment
 Supported Operating Systems: Windows XP, Windows Vista, Windows 7

. Net Framework 3.5

Microsoft SQL Server2008
2. Project organization
2.2.1. Software development model
We decided to choose V-model to develop our system.
2.2.1.1. The reason why V-model is chosen
Because of time constraint and specific characteristic for a capstone project, we need a process
model which helps our system finish on time and high quality. It needs to give equal weight to
coding and testing in software. As the result, the code testing documentation is written in tandem
with the development phases, for instance, the integration tests should be documented as and when
the high level design is finalized and the unit tests should be ready as and when the detailed
specifications are laid down. So, we choose v-model as our software development lifecycle.
2.2.1.2. V-model
The V-Model demonstrates the relationships between each phase of the development life cycle
and its associated phase of testing.
The idea of the V-model is to have a implementation plan for the software testing at each level
namely component, interface, system, acceptance and release of the software project which need to
be adhered to eliminate discrepancies in the software simultaneously rather than waiting for the
software development process to complete before handling it to the software testing professionals.
The specification stream:
The specification stream mainly consists of:

User Requirement Specifications

Functional Requirement Specifications

Design Specifications
The testing stream generally consists of:

Installation Qualification (IQ)

Operational Qualification (OQ)

Performance Qualification (PQ)
The development stream can consist (depending on the system type and the development scope) of
customization, configuration or coding.
2.2.1.3. Advantages of V-model
 Minimization of project risks

Improvement and guarantee of quality

Reduction of total cost over the entire project and system lifecycle

Improvement of communication between all stakeholders
2.2.2. Roles and Responsibilities
Member’s name
NhuNHB00071
Role
Project Manager
LongDT00030
Technical Leader
AnhLTM00021
HoaiNT0008
Developer
Tester
NamNV00284
Developer
Responsibilities
Managing project tasks, reviewing code,
document control
Designing, coding, solving technical
problems
Designing, Coding
Writing test cases, executing test cases,
document control
Designing, coding
2.2.3. Tools and Techniques
2.2.3.1. Tools
In order to have a smooth run throughout the project development period, the following items
must be well prepared and efficiently used.
Item
Development
Environment
Target Environment
Subversion Control
Description
Windows XP,
Windows 7
Windows XP,
Windows 7
Microsoft Visual
Studio
. Net Framework 3.5
Microsoft Server
SQL 2008
Tortoise SVN
Hosting Server
Google code
IDE
Framework
DBMS
Project Management Microsoft Word,
Microsoft Excel,
Microsoft Project
Microsoft Visio
Diagraming
2.2.3.2. Techniques
Reading Felica card
Apriori algorithm
Note
A powerful IDE that ensures quality code
throughout the entire application lifecycle.
Version 1.6.12
Subversion library: 1.6.15
The repository for source codes and all
project documents such as reference, QA
sheet, issues tracking list, etc.
Simplifies the complexity in creating visual
diagrams
2.3. Project Management Plan
2.3.1. Task List
No.
Task
Name
1
Study
existing
system
2
Product
Evaluation
3
Defining
risks
4
Defining
project
scope
5
Defining
working
environment
6
Creating
Introduction
Document
Creating
project plan
7
8
Analyzing
use cases
9
Defining
user
requirement
Description
Deliverables
Resource
Needed
Study the two most
important aspects
(business process and
architecture) in order to
identify shortcomings and
issues with the current
system.
Study the feasibility, pros
and cons of the proposed
system
Define risks and
difficulties that may occur
during project execution
Define project scopes,
work that need to be
accomplished in order to
deliver product
Consider tools and
working environment
needed
Setup hosting and
working environment
Introduction about project
to be executed
System
analysis result
All team
Feasibility
Study
NhuNHB,
LongDT
Risk
management
plan
Project Scope
sheet
NhuNHB,
LongDT
Tool and
Working
Environment
Sheet
All team
Report 1:
Introduction
NhuNHB,
HoaiNT
Create project plan with
master schedule and
assignment timetable
Analyze use cases
Create use case diagrams
in order to present a
graphical overview of the
functionality provided by
a system in terms of
actors, their goals
(represented as use cases),
and any dependencies
between those use cases.
Report 2:
Software
Project Plan
Use case
diagrams
NhuNHB
Summarize user
User
requirements of product in Requirement
the compact form
NhuNHB,
HoaiNT
Dependencies
and
Constraint
All team
All team
All previous
tasks must be
completed
R
is
k
10
11
12
Defining
nonfunctional
requirement
Defining
functional
requirement
Creating
ERD
13
Creating
SRS
document
14
Creating
SDD
15
Creating
Prototype
16
Studying
Felica,
Apriori
Creating
Test Cases
Creating
STD
17
18
19
Developing
system
20
Creating
user manual
Inspecting
product
Delivering
product
21
21
Define non-functional
requirements of the
product
Software
System
Attribute
Document
Define functional
System
requirements of the
Requirement
product
Specification
Provide ERD (Entity
EntityRelationship Diagram) for Relationship
the system
Diagram
Create Software
Report 3: SRS
Requirement Specification Document
document composed of
functional, non-functional
requirements and user
requirements
Creating system
Report 4:
architectural design,
Software
component diagram,
Design
detailed description of
Description
components, sequence
diagram, user interface
design, database design
Create user interface
Software
prototype of the product
Prototype
NhuNHB,
HoaiNT
NhuNHB,
HoaiNT
NamNV,
LongDT
NhuNHB,
HoaiNT
Task 9, 10, 11,
12 must be
done
All team
LongDT,
NamNV,
AnhLTM
LongDT,
NamNV
Study Felica, Apriori
algorithm
Record
Create test case based on
SRS document
Create software test
documentation (test plan,
test case, test result)
Develop functions defined
in SRS and fix bugs found
when executing test cases
Create user manual with
installation guide
Execute final inspection
Test cases
HoaiNT
Report 5: STD
NhuNHB,
HoaiNT
Task 17 must
be done
Source code
package
Task 13 must
be done
Report 6: User
manual
FI Report
LongDT,
NamNV,
AnhLTM
NhuNHB,
HoaiNT
NhuNHB
Deliver product packed
with source codes,
documents, user manual
and all required.
Final product
NhuNHB
All the above
tasks must be
done
2.3.2. Task sheet (Assignments and Timetable/ Master Schedule)
Be detailed in the master plan.mpp included.
2.3.3. Meeting minutes
Meeting Minutes
Meeting with the potential customer and
Subject
decide topic for Capstone Project
Facilitator
Date
08/01/2011
Time
Location
Long Vi Restaurant
Attendees
Scribe
Mr. Le Thanh Quang
Supervisor
Ms. Le Thuy Hoa
Customer
Nguyen Hoang Bao Nhu
PM
Duong Thanh Long
PTL
Nguyen Vinh Nam
Developer
Le Thi Mai Anh
Developer
Nguyen Thi Hoai
Tester
Key Points Discussed
No.
1.
Topic
Introduction
Highlights
All team met with Ms. Hoa, the manager of Long Vi Restaurant. She gave
us some overview of the restaurant and introduced us staff who we can
ask information for the project.
At the present time, the restaurant is using purchased software to manage
the operations of accounting, inventory and sale. Ms. Hoa gave us the
user guide document for the current system.
2.
Customer’s opinions about
Ms. Hoa mentioned some problems when using the current system. In
current restaurant
general, it has the following drawbacks:
management system
-
It is not compatible with the operations of the restaurant. Therefore,
only some functions are useful.
-
There is no feature to help manager in decision making and
forecasting trends of customers.
She want to have a system that is less complex but still have the useful
fuctions.
3.
Topic for capstone project
All team approved to develop a new system that can overcome the
disadvantages of current system. Mr Quang suggested us to use Apriori
algorithm in data mining to use sale data for supporting decision making
of managers in the restaurant. Besides, Long suggested using Felica card
in managing VIP customers’ discount. All team also want to learn more
Key Points Discussed
No.
Topic
Highlights
about this kind of smart card too. Therefore, the project’s name will be
“Using
Felica
card
and
Apriori
algorithm
in
restaurant
management”.
4.
Plan
The next meeting will discuss about the requirement and scope of the
project
To prepare for the meeting, we should do the following work in next week
-
Study in detail about the current system. Read the user guide
taken from Ms Hoa and if there is any question, prepare Q&A file
and go to the restaurant to ask Ms Hoa directly.
-
Meet with managers of Long Vi restaurant to define specific
requirements.
-
We need a lot of data for testing, thus, ask for the data in the
restaurant’s current database.
-
Research about apriori algorithm.
Action Plan
No.
Action Item(s)
Owner
Target Date
1.
Research current system, Q&A file preparation
AnhLTM, NamNV
13/01/2011
2.
Meet with Long Vi’s managers
HoaiNT, NamNV,
15/01/2011
3.
Get the database of current system
LongDT
18/01/2011
4.
Research about apriori algorithm
LongDT
19/01/2011
Meeting Minutes
Subject
Define scope statement, development
model
Facilitator
Location
Attendees
Date
19/01/2011
Time
Room 107 – FPT University
Scribe
Nguyen Hoang Bao Nhu
PM
Duong Thanh Long
PTL
Nguyen Vinh Nam
Developer
Le Thi Mai Anh
Developer
Nguyen Thi Hoai
Tester
Key Points Discussed
No.
1.
Topic
Introduction
Highlights
Hoai and Nam showed Q&A file with the answer of people in Long
Vi’s restaurant.
Mai Anh and Nam reported about the current system. The problem
about time was mentioned because there will be a lot of work to
complete a full-function restaurant management software.
2.
Scope of the project
Because we do not have much time, we all agree that the project
develops only the basic functions in managing a restaurant. The
extend functions and online modules will be developed in the
future.
The new system includes 2 main functions:
-
Restaurant’s operation management: 3 modules

Accounting management module.

Inventory management module

Sale and reservation management process: using Felica
card for manage VIP customers
3.
Development model
Using Apriori algorithm in data mining
We only have more than 10 weeks for this project and have to
submit the report in specific time. Therefore, we chose V model for
developing it.
4.
Tools for development
-
Google svn
-
Visual Studio 2008
-
Sql Server 2008
Key Points Discussed
No.
Topic
Highlights
5.
Action Plan
No.
Action Item(s)
Owner
Target Date
1.
Set up SVN server
NhuNHB
21/01/2011
2.
Check out, set up in personal computer
All team
23/01/2011