FPT Restaurant Online Reservation and Delivery System

FPT – Aptech Computer Education eProject Document
FPT-APTECH 1
Tunga Restaurant
Documentation
C0710g – Group IV
Group Member
Nguyen Thanh Hieu - A03774 - 0308
Instructor Nguyen Tuan
- Hanoi, 8/2010 –
C0710g-Group IV Page 1 CONFIDENTIAL2/18/2015

1. Index
1.Index...........................................................................................................................2
2.Problem Definition....................................................................................................3
3.Requirements and Business Flow............................................................................6
4.Design.......................................................................................................................32
5.System Prototype.....................................................................................................56
6.Management and Project Planning.......................................................................57
7.Checklists.................................................................................................................58
8.Screenshots...............................................................................................................58
9.Other Concerns.......................................................................................................58
Appendix.....................................................................................................................59

2. Problem Definition
2.1. Problem Abstraction
FUN ‘N’ FOOD is a big name in the hospitality business (Hotels & Resorts)
and has a very successful independent chain of restaurants TUNGA in the
country. Booking Tables are known for their wide range of continental
cuisine and consummate style.
TUNGA provides range fully-equipped, private meeting rooms, and regal
banquet halls which offer the perfect combination of efficiency and
convenience. They are also popular among school & college students for
range of bakery & fast food products.
With increasing popularity and the customer base, organization has
decided to go techno savvy to meet customer expectations with respect to
its exclusive services in the market.
Organization has decided to reach out to its customers via online services
through a web site on the internet.
The web site talks about other business aspects of the firm and has online
reservation and home delivery service as one of its premium services.
However you are essentially required to focus on the online booking
and the home delivery aspect only and to design and build a site
which deals with the same.
2.2. The Current System
- Server :
Processor
• Itanium processor
Processor speed:
• Recommended: 1. 0 GHz
RAM:
• 1 GB
- Client :
Processor
• Pentium processor
Processor speed:
• Recommended: 1. 0 GHz
RAM:

• Minimum: 1 GB
2.3. The Proposed System
- Server :
Processor
• Itanium processor or faster
Processor speed:
• Recommended: 1. 0 GHz or faster
RAM:
• Recommended: 4 GB or more
• Maximum: Operating system maximum
- Client :
Processor
• Core Duo 2 or faster
Processor speed:
• Recommended: 1. 0 GHz or faster
RAM:
• Recommended: 4 GB or more
• Maximum: Operating system maximum
2.4. Boundaries of the System
< >
2.5. Development Environment
Computers with Windows OS installed
Microsoft Visual Studio 2005 Professional
Netbeans 6. 9
SQL Server 2005
Microsoft Office 2010
Microsoft Visio 2010

FPT-Aptech Project Management System (pms.aptech.ac.vn)

3. Requirements and Business Flow
3.1. Customer Requirement Specification
The site should allow customer to choose the services offered by the
restaurant.
1. Online Booking Table reservation in the restaurant for specific date and
time. This will
a. Provide the list of restaurants in the country so that the user can
choose accordingly.
b. Provide the list of Booking Tables available for online
reservation at different dining rooms in the restaurant.
c. Mention the number of guests that can be accommodated on
the particular Booking Table.
d. Accept the booking for Booking Tables.
e. Online Booking Table reservations are done 6hrs in advance for
the current date.
f. Booking Table reservation can be done up to one month in
advance.
g. Give a token number to the customer as an acknowledgement
of booking.
2. Online order for food under restaurant’s exclusive home delivery service.
a. This facility is valid for 24hrs. from the time of order.
b. Accept the customers order so that the nearest restaurant can
service the order in stipulated time (60 - 120 Minutes).
c. Record the customer’s name, residence address and contact
numbers and other vital details if required.
d. Facilitate with the choice of food keeping Vegetarian and non-
vegetarian customers in mind.
e. Provide the menu list with their price tags accordingly and also
mention the number of persons that can be served with one unit
of order. This will help the customer to decide the quantity to be
ordered.
f. Display the list items select from the menu and exact amount
(itemized bill) that the customer is supposed to pay (inclusive of
all taxes applicable).
g. Give a token number as an acknowledgement to the customer
that the order has been noted down by the restaurant.
h. Show the approximate time (in minutes) in which the ordered will
be delivered to the customer.
3. The site should have the appropriate look and feel suitable to the
restaurant’s reputation and status.

3.2. Activity Diagram
3.2.1. Manage Restaurant

3.2.2. Manage Table

3.2.3. Manage Food

3.2.4. Manage Booking Table

3.2.5. Manage Order Food

3.2.6. View Bill

3.2.7. Manage Customer

3.2.8. Customer Activity

3.3. Use Case Diagram

3.4. Use Case Specification
3. 4. 1. Login
3. 1. 1. Brief Description:
This use case describes how a user logs into the Tunga
Restaurant System.
3. 1. 2. Flow of Events
3. 1. 2. 1. Basic Flow
 This use case starts when the actor wishes to Login to the
Tunga Restaurant System.
 The system requests that the actor enter his/her user name
and password.
 The actor enters his/her user name and password.
 The system validates the entered user name and password
and logs the actor into the system.
3. 1. 2. 2. Alternative Flows
3. 1. 2. 2. 1. Invalid Username/Password
If in the Basic Flow, the actor enters an invalid
user name and/or password, the system displays an
error message. The actor can choose to either return to
the beginning of the Basic Flow or cancel the login, at
which point the use case ends.
3. 1. 3. Special Requirements
None.
3. 1. 4. Pre-Conditions
None.
3. 1. 5. Post-Conditions
If the use case was successful, the actor is now logged
into the system. If not, the system state is unchanged.
3. 1. 6. Extension Points
None
3. 4. 2. Logout
This use case describes how a user logs out the Tunga
Restaurant System.
 This use case starts when the actor wishes to Logout to
the Tunga Restaurant System.
 The user(employee/Administrator/Manager) click Logout
button.
 The system remove user‘s session.
2. 2. 2. Alternative Flows
None.
None.

If the use case was successful, the user is now logged
out the system, user’s session is remove from the system. If
not, the system state is unchanged.
None
3. 4. 3. Manage Customer
 This use case allows the Tunga Restaurant
Administrator/Manager to manage customer information.
 This includes adding, search, changing, and deleting
customer information from the system.
 This use case starts when the Tunga Restaurant
Administrator/Manager wishes to add, search,
change, or delete customer information from the
system.
 The system requests that the Tunga Restaurant
Administrator/Manager specify the function he/she
would like to preform(either Add customer, Search
customer, Edit customer, or Delete customer)
 Once the Tunga Restaurant Administrator/Manager
provides the requested information, one of the sub-
flows is executed.
 If the Tunga Restaurant Administrator/Manager
selected “Add customer”, the Add customer sub-flow
is executed.
 If the Tunga Restaurant Administrator selected
“Search customer”, the Search customer sub-flow is
executed.
selected “Edit customer”, the Edit customer sub-flow
is executed.
selected “Delete customer”, the Delete customer
sub-flow is executed.
3.4. 2. 1. 1 Add customer
 The system requests that the Tunga
Restaurant Administrator/Manager enter the customer
information. This includes :
 Username
 Password
 Birthday
 Sex
 Address
 Email

 Phone
 The system validates the entered employee
information. The employee is added to the
system.
 The system provides the
Administrator/Manager with the new Employee
Id.
3. 4. 2. 1. 2. Search customer
 The Tunga Restaurant Administrator/Manager
enters the customer Id.
 The system retrieves and display the customer
information
3.4. 2. 1. 3. Edit customer
Restaurant Administrator/Manager enter the
customer Id.
 The system retrieves and display the customer
information
makes the desired change to the customer
information. This includes any of the
information specified in the Add customer
sub-flow.
 Once the Tunga Restaurant
Administrator/Manager updates the necessary
information, the system updates the customer
record with the updated information
3. 4. 2. 1. 4. Delete Employee
Customer Id.
 The system retrieves and display the employee
information
 The system prompts the Tunga Restaurant
Administrator/Manager to confirm the deletion
of the customer.
verifies the deletion.
 Remove the customer from the system.
3. 4. 2. 2. 1. customer not found
If in Search Customer sub-flow, an customer with
the specified id number does not exist, the system
displays an error message. The Tunga Restaurant
Administrator/Manager can then enter a different id
number.
3. 4. 2. 2. 2. Delete Cancelled

If in the Delete Customer sub-flow, the Tunga
Restaurant Administrator/Manager decides not to delete
the customer, the delete is cancelled and the Basic
Flow is re-started at the beginning.
None
The Tunga Restaurant Administrator/Manager must be logged
into system before this use case begins.
If the use case was successful, the customer information is
added, display, updated, or deleted form the system.
None
3. 4. 4. Manage Restaurant
This use case allows the Tunga Restaurant Administrator to
manage Restaurant .
This includes adding, search, changing, and deleting
Restaurant from the system.
3 . 5. 2. 1. Basic Flow
Administrator wishes to add, search, change, or delete
Restaurant information from the system.
Administrator specify the function he/she would like to
preform(either Add Restaurant, Search Restaurant, Edit
Restaurant, or Delete Restaurant)
 Once the Tunga Restaurant Administrator provides the
requested information, one of the sub-flows is executed.
 If the Tunga Restaurant Administrator selected “Add
Restaurant”, the Add Restaurant sub-flow is executed.
 If the Tunga Restaurant Administrator selected “Search
Restaurant”, the Search Restaurant sub-flow is
executed.
 If the Tunga Restaurant Administrator selected “Edit
Restaurant”, the Edit Restaurant sub-flow is executed.
 If the Tunga Restaurant Administrator selected “Delete
Restaurant”, the Delete Restaurant sub-flow is
executed.
3. 5. 2. 1. 1 Add Restaurant
Administrator enter the Restaurant information.
 This includes :
o Title

o Content
 The system validates the entered Restaurant
information. The Restaurant is added to the
system.
 The system provides the Administrator with the
new Restaurant Id, date post Restaurant is
current date. This date is auto-generate.
 The next time the Tunga Restaurant is run, the
system will display Restaurant that just added to
top Restaurant.
3. 5. 2. 1. 2. Search Restaurant
 The Tunga Restaurant Administrator enters the
Restaurant Id.
 The system retrieves and display the Restaurant
information
3. 5. 2. 1. 3. Edit Restaurant
Administrator enter the Restaurant Id.
information
 The Tunga Restaurant Administrator makes the
desired change to the Restaurant information.
This includes any of the information specified in
the Add Restaurant sub-flow.
 Once the Tunga Restaurant Administrator updates
the necessary information, the system updates
the Restaurant record with the updated information
3. 5. 2. 1. 4. Delete Restaurant
Administrator enter the Restaurant Id.
information
Administrator to confirm the deletion of the
Restaurant.
 The Tunga Restaurant Administrator verifies the
deletion.
 Remove the Restaurant from the system.
3. 5. 2. 2. 1. Restaurant not found
If in Search Restaurant sub-flow, an Restaurant
with the specified id number does not exist, the system
Administrator can then enter a different id number.
If in the Delete Restaurant sub-flow, the Tunga
Restaurant Administrator decides not to delete the

Restaurant, the delete is cancelled and the Basic Flow
is re-started at the beginning.
None
The Tunga Restaurant Administrator must be logged into
system before this use case begins.
If the use case was successful, the Restaurant information is
None
3. 4. 5. Manage Table
Administrator/Manager to manage Table information .
 This includes adding, search, changing, and deleting Table
information from the system.
Administrator/Manager wishes to add, search, change,
or delete Table information from the system.
Administrator/Manager specify the function he/she would
like to preform(either Add Table, Search Table, Edit
Table, or Delete Table)
provides the requested information, one of the sub-flows
is executed.
 If the Tunga Restaurant Administrator/Manager selected
“Add Table”, the Add Table sub-flow is executed.
“Search Table”, the Search Table sub-flow is executed.
“Edit Table”, the Edit Table sub-flow is executed.
“Delete Table”, the Delete Table sub-flow is executed.
3. 6. 2. 1. 1 Add Table.
Table information. This includes :
 Title
 Content
 Start Date
 End Date

 The system validates the entered Table
information. The Table is added to the system.
Administrator/Manager with the new Table Id,
date post Table is current date. This date is
auto-generate.
 The next time the Manage Table is run, the
system will display Table that just added to top
Table.
3. 6. 2. 1. 2. Search Table
enters the Table Id.
 The system retrieves and display the Table
information
3. 6. 2. 1. 3. Edit Table
Table Id.
information
makes the desired change to the Table
information specified in the Add Table sub-
flow.
information, the system updates the Table
3. 6. 2. 1. 4. Delete Table
Table Id.
information
of the Table.
 Remove the Table from the system.
3. 6. 2. 2. 1. Table not found
If in Search Table sub-flow, an Restaurant with

number.
If in the Delete Table sub-flow, the Tunga
the Restaurant, the delete is cancelled and the Basic
None
If the use case was successful, the Table information is added,
display, updated, or deleted form the system.
None
3. 4. 6. Manage Food
Administrator/Manager to manage Food information .
 This includes adding, search, changing, and deleting Food
Administrator/Manager wishes to add, search, change,
or delete Food information from the system.
Administrator/Manager specify the function he/she would
like to preform(either Add Food, Search Food, Edit
Food, or Delete Food)
provides the requested information, one of the sub-flows
is executed.
“Add Food”, the Add Food sub-flow is executed.
“Search Food”, the Search Food sub-flow is executed.
“Edit Food”, the Edit Food sub-flow is executed.
“Delete Food”, the Delete Food sub-flow is executed.
3. 7. 2. 1. 1 Add Food.

Food information. This includes :
 Title
 Content
 Start Date
 End Date
 The system validates the entered Food
information. The Food is added to the system.
Administrator/Manager with the new Food Id,
date post Food is current date. This date is
auto-generate.
 The next time the Manage Food is run, the
system will display Food that just added to top
Food.
3. 7. 2. 1. 2. Search Food
enters the Food Id.
 The system retrieves and display the Food
information
3. 7. 2. 1. 3. Edit Food
Food Id.
information
makes the desired change to the Food
information specified in the Add Food sub-
flow.
information, the system updates the Food
3. 7. 2. 1. 4. Delete Food
Food Id.
information
of the Food.

 Remove the Food from the system.
3. 7. 2. 2. 1. Food not found
If in Search Food sub-flow, an Restaurant with
number.
If in the Delete Food sub-flow, the Tunga
the Restaurant, the delete is cancelled and the Basic
None
If the use case was successful, the Food information is added,
None
3. 4. 7. Manage Booking Table
 This use case allows the Tunga Restaurant Administrator to
manage Booking Table information .
 This includes adding, search, changing, and deleting Booking
Table information from the system.
Booking Table information from the system.
preform(either Add Booking Table, Search Booking
Table, Edit Booking Table, or Delete Booking Table)
Booking Table”, the Add Booking Table sub-flow is
executed.
Booking Table”, the Search Booking Table sub-flow is
executed.

Booking Table”, the Edit Booking Table sub-flow is
executed.
Booking Table”, the Delete Booking Table sub-flow is
executed.
3. 8. 2. 1. 1 Add Booking Table.
Restaurant Administrator enter the Booking
Table information. This includes :
 Title
 Content
 Start Date
 End Date
 The system validates the entered Booking
Table information. The Booking Table is added
to the system.
new Booking Table Id, date post Booking
Table is current date. This date is auto-
generate.
system will display evect that just added to top
Booking Table.
3. 8. 2. 1. 2. Search Booking Table
Booking Table Id.
 The system retrieves and display the Booking
Table information
3. 8. 2. 1. 3. Edit Booking Table
Table Id.
Table information
desired change to the Booking Table
information specified in the Add Booking
Table sub-flow.
 Once the Tunga Restaurant Administrator
updates the necessary information, the system
updates the Booking Table record with the
updated information
3. 8. 2. 1. 4. Delete Booking Table

Table Id.
Table information
Booking Table.
 The Tunga Restaurant Administrator verifies
the deletion.
 Remove the Booking Table from the system.
3. 8. 2. 2. 1. Booking Table not found
If in Search Booking Table sub-flow, an news
with the specified id number does not exist, the system
If in the Delete Booking Table sub-flow, the Tunga
Restaurant Administrator decides not to delete the news,
the delete is cancelled and the Basic Flow is re-started
at the beginning.
None
If the use case was successful, the Booking Table information
is added, display, updated, or deleted form the system.
None
3. 4. 8. Manage Order Food
manage Order Food information .
 This includes adding, search, changing, and deleting Order
Food information from the system.
Order Food information from the system.
preform(either Add Order Food, Search Order Food,
Edit Order Food, or Delete Order Food)

Order Food”, the Add Order Food sub-flow is executed.
Order Food”, the Search Order Food sub-flow is
executed.
Order Food”, the Edit Order Food sub-flow is executed.
Order Food”, the Delete Order Food sub-flow is
executed.
3. 9. 2. 1. 1 Add Order Food.
Restaurant Administrator enter the Order Food
 Title
 Content
 Start Date
 End Date
 The system validates the entered Order Food
information. The Order Food is added to the
system.
new Order Food Id, date post Order Food is
current date. This date is auto-generate.
Order Food.
3. 9. 2. 1. 2. Search Order Food
Order Food Id.
 The system retrieves and display the Order
Food information
3. 9. 2. 1. 3. Edit Order Food
Id.
Food information
desired change to the Order Food information.
This includes any of the information specified in
the Add Order Food sub-flow.

updates the Order Food record with the
updated information
3. 9. 2. 1. 4. Delete Order Food
Id.
Food information
Order Food.
the deletion.
 Remove the Order Food from the system.
3. 9. 2. 2. 1. Order Food not found
If in Search Order Food sub-flow, an news with
If in the Delete Order Food sub-flow, the Tunga
Restaurant Administrator decides not to delete the news,
the delete is cancelled and the Basic Flow is re-started
at the beginning.
None
If the use case was successful, the Order Food information is
None
3. 4. 9. Manage Bill
manage Bill information .
 This includes adding, search, changing, and deleting Bill
3. 10. 2. 1. Basic Flow
Bill information from the system.

preform(either Add Bill, Search Bill, Edit Bill, or Delete
Bill)
 If the Tunga Restaurant Administrator selected “Add Bill”,
the Add Bill sub-flow is executed.
Bill”, the Search Bill sub-flow is executed.
 If the Tunga Restaurant Administrator selected “Edit Bill”,
the Edit Bill sub-flow is executed.
Bill”, the Delete Bill sub-flow is executed.
3. 10. 2. 1. 1 Add Bill.
Restaurant Administrator enter the Bill
 Title
 Content
 Start Date
 End Date
 The system validates the entered Bill
information. The Bill is added to the system.
new Bill Id, date post Bill is current date. This
date is auto-generate.
Bill.
3. 10. 2. 1. 2. Search Bill
Bill Id.
 The system retrieves and display the Bill
information
3. 10. 2. 1. 3. Edit Bill
Restaurant Administrator enter the Bill Id.
information
desired change to the Bill information. This
includes any of the information specified in the
Add Bill sub-flow.
updates the Bill record with the updated
information
3. 10. 2. 1. 4. Delete Bill

Restaurant Administrator enter the Bill Id.
information
Administrator to confirm the deletion of the Bill.
the deletion.
 Remove the Bill from the system.
3. 10. 2. 2. 1. Bill not found
If in Search Bill sub-flow, an news with the
specified id number does not exist, the system displays
an error message. The Tunga Restaurant Administrator
can then enter a different id number.
If in the Delete Bill sub-flow, the Tunga Restaurant
Administrator decides not to delete the news, the delete
is cancelled and the Basic Flow is re-started at the
beginning.
None
If the use case was successful, the Bill information is added,
None
3.5. Other Diagrams <Optional>

4. Design
4.1. System Architecture

4.2. Class Diagram
4.3. Class Diagram Explanation
4.3.1. Restaurant Management
RestaurantManagement
<Attributes>
private int id;
private int citytid;
private String username;
private String password;
private String managername;
private String phone;
private String address;
private String picture;
private String descr;
private boolean status;
<Operations>
public RestaurantManagement()
public void createRestaurant()
public void getAllRestaurant ()

public void getRestaurantByID ()
4.3.2. Table Management
TableManagement
<Attributes>
<Attributes>
private int id;
private int restaurantid;
private int tabletypeid;
<Operations>
public TableManagement()
public void createTable()
public void getAllTable ()
public void getTableByID ()
4.3.3. Food Management
FoodManagement
<Attributes>
private int id;
private int foodtypeid;
private String name;
private float price;
private int person;
private String picture;
<Operations>
public FoodManagement()
public void createFood()
public void getAllFood ()
public void getFoodByID ()
4.3.4. Booking Table Management
BookingTableManagement
<Attributes>
private int id;
private int customer;
private Date orderdate;
private Date ordertime;
private String email;

<Operations>
public BookingTableManagement()
public void createBookingTable ()
public void getAllBookingTable ()
public void getBookingTableByID ()
4.3.5. Order Food Management
OrderFoodManagement
<Attributes>
private int id;
private int customer;
private Date orderdate;
private Date ordertime;
<Operations>
public OderFoodManagement()
public void createOrderFood()
public void getAllOrderFood ()
public void getOrderFoodByID ()
4.3.6. Customer Management
CustomerManagement
<Attributes>
private int id;
private String username;
private String password;
private String fullname;
private Date dob;
private Boolean gender;
private int count;
<Operations>
public CustomerManagement()
public void createCustomer()
public void getAllCustomer ()
public void getCustomerByID ()

4.4. Sequence Diagram (Optional)

4.5. Collaboration Diagram (Optional)
4.6. State Diagram (Optional)
4.7. Entity Relationship Diagram
4.8. Database Design
4.8.1. Table: Restaurant
Table : Restaurant
Field Name Data Type Description
id int Specify id of Restaurant
cityid int Specify id of City

name nvarchar(100) Name of Restaurant
username nvarchar(100) Username of Account
Restaurant
Manager
password nvarchar(100) Password of Restaurant
Account
Manager
managername nvarchar(100) Name of Manager
phone nvarchar(100) Phone
address nvarchar(100) Address
picture nvarchar(100) Image url of Restaurant
descr nvarchar(500) description of Restaurant
status bit status of Restaurant
4.8.2. Table: Table
Table : Table
id int Specify id of table
tabletypeid int(100) Specify id of table type
id
4.8.3. Table:TableType
Table : TableType
id int Specify id of Table type
typename nvarchar(100) Name of Table Type
position Bit Position of Table
capacity int Number of persons can
be served

price float Price of Table Type
picture nvarchar(500) URL Image of Table
Type
descr nvarchar(500) Description of Table
Type
status bit Status of Table type
4.8.4. Table: Food
Table : Food
id int Specify id of Food
foodtypeid int Specify id of Food Type
name nvarchar(100) Name of food
price float Price of food
persons int Number of persons can
be served
picture nvarchar(500) Image url of food
descr nvarchar(500) Description of food
status bit Status of food
4.8.5. Table: FoodType
Table : FoodType
typename bit Name of Food Type
4.8.6. Table: BookingTable
Table : BookingTable

customerid nvarchar(100) Specify id of Customer
restaurantid int Specify id of Restaurant
bookingdate datetime Booking date
bookingtime datetime Booking time
email nvarchar(100) Email of customer
phone nvarchar(100) Phone of customer
descr nvarchar(500) Description of booking
table
status bit Status of Booking table
4.8.7. Table: BookingTableDetail
Table : BookingTableDetail
id int Specify id of food
bookingtableid int Specify id of Booking
table detail
tableid int Specify id of Table
quantity int Quantity of Booking
table detail
4.8.8. Table: OrderFood
Table : OrderFood
id int Specify id of Order food
customerid int Specify id of Customer
restaurantid int Specify id of Restaurant
orderdate datetime Booking date
ordertime datetime Booking time

address nvarchar(100) Address of Order food
email nvarchar(100) Email of customer
phone nvarchar(100) Phone of customer
descr nvarchar(500) Description of Booking
Table
status bit Status of Order food
4.8.9. Table: OrderFoodDetail
Table : OrderFoodDetail
id int Specify id of Order
Detail Food
orderfoodid int Specify id of Order Food
foodid int Specify id of food
quantity int Quantity of order food
detail
4.8.10. Table: Admin
Table : Admin
id int Specify id of Admin
username nvarchar(100) Username of Admin
password nvarchar(100) Password of Admin
4.8.11. Table: Customer
Table : Customer
id int Specify id of Customer
username nvarchar(100) Userame of Customer

password nvarchar(100) Password of Customer
fullname nvarchar(100) Full Name of Customer
dob datetime Birthday of Customer
gender bit Sex of Customer
phone nvarchar(100) Phone of Customer
address nvarchar(100) Address of Customer
email nvarchar(100) Email of Customer
count int Number of Order
4.8.12. Table: City
Table : City
id int Specify id of City
name nvarchar(100) Name of City
4.8.13. Table: Events
Table : Events
id int Specify id of Events
title nvarchar(100) Name of Event
datepost datetime Date of Event Launch
descr nvarchar(500) Content of Events
4.9. Algorithms (optional)

5. System Prototype

6. Management and Project Planning
6.1. Management Approach
< Briefly describe the management approach that your team selected. Is your
team self-managed or managed by one leader?>
6.2. Project Plan
<The detailed project plan is put here. You can use WBS Excel sheet, Sprint
Backlog, Task sheet, Gantt chart, etc. to present your team’s plan >
6.3. Task Sheet
Project Ref. No.:
Project
Title:
Activi
ty
Plan
Prepar
ed By:
Date of Preparation of Activity Plan:
No
Task
Actual
Start Date
Actual
Days
T e a m
M e m b e r
Names
Status
1 Analyzing
Tunga
Restaurant
Website
HieuNT 26-7-2010 2 Completed
2
Design of the
project
HieuNT 28-7-2010 1 Completed
3 Use Case Diagram HieuNT 29-7-2010 1 Completed
4 Class Diagram HieuNT 30-7-2010 1 Completed
5 Sequence Diagram HieuNT 31-7-2010 1 Completed
6 Activity diagram HieuNT 1-7-2010 1 Completed
7 Design Database HieuNT 2-7-2010 1 Completed
8 Snapshot HieuNT 4-7-2010 1 Completed
9
Write code of
module Data
Manager
10
Write code of
module Admin
manager
11
Write code of
Employee
Manager
12 Testing &
Correcting
6.4. Meeting Minutes (Optional)
<Put all minutes of your team meetings here>

7. Checklists
7.1. Check List of Validation
< >
7.2. Submission Checklist
< >
8. Screenshots
9. Other Concerns
<If you have any other information you want to add to this document, place it
here. This could include thoughts on the eProject, improvements, etc.>

Appendix
Glossary [Optional]
<Place all definitions used in this document >
References [Optional]
<Place all referenced materials used in this document >
Others

FPT Restaurant Online Reservation and Delivery System

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Similar to FPT Restaurant Online Reservation and Delivery System

Similar to FPT Restaurant Online Reservation and Delivery System (20)

Recently uploaded

Recently uploaded (20)

FPT Restaurant Online Reservation and Delivery System