Members:
Trần Huy Thường - 00467
Trần Mạnh Cường - 00416
Đào Anh Thư - 00362
Nguyễn Duy Tiến - 00256
Contents
e-Restaurant
1
Introduction add Title
2
Project management plan lick to add Title
3
Requirement Specifications
4
Design Description to add Title
5
Implementation Title
6
Testing
7
Demo & Q&A
3TC Company
1. Introduction
Background add Title
Literature Review
Our Proposal
e-Restaurant
3TC Company
2. Project management plan
Development Environment
Process Model
Project organization
Project Planning
e-Restaurant
3TC Company
2. Project management plan
Development Environment
 Hardware
 Operating system: Windows 7
 Configuration: 2 Gb of RAM, 100Gb of hard disk,
Core 2 Duo 2.0 GHz or higher.
 Software






e-Restaurant
Framework: .NET Framework 4.0
Visual Studio 2010
SQL Server 2008
Web Server: IIS 7
Office 2010
TortoiseSVN
3TC Company
2. Project management plan
Process Model
V-Model
e-Restaurant
3TC Company
2. Project management plan
Project organization
e-Restaurant
3TC Company
2. Project management plan
Project Planning
 Schedule Management
People risk
 Resource Management
Risk
 Communications
management
Management
 Risk management
Schedule risk
Technology risk
Requirement risk
e-Restaurant
3TC Company
3. Requirement Specifications
User Requirements
System Requirements
Non-functional requirements
e-Restaurant
3TC Company
3.1 User Requirements
Website :
 Customers :
View information on the website.
Example : News, Event, Menu, Albums…
• Make the reservation on the website
• Make a contact on website.
•
Applications:
 Customer :
• Make the reservation on the website or phone
 Administrators :
• Add edit delete information user
e-Restaurant
3TC Company
3.1 User Requirements
Applications:
 User:
• Manage Reservation (Add, edit, delete)
• Manage table’s information
• Manage menu’s information, menu details(Add,
edit, delete)
• Manage customer’s information(Add, edit, delete)
• Statistics menu lists dishes in a restaurant
• Statistics monthly bills
• Statistics client list has reservation
• Send SMS, Email to customers
• Manage Website’s information
e-Restaurant
3TC Company
3.2 Non-functional requirements
Usability
Availability
Reliability
Security
Security
Performance
Maintainability
e-Restaurant
3TC Company
3.3 System Requirements
 Document requirements as use-cases
 Each use case include:










Use case diagram
Actor
Summary
Goals
Triggers
Exceptions
Relationship
Description
Screen
Data field
www.themegallery.com
Company Logo
3.3 System Requirements
www.themegallery.com
Company Logo
4. Software Design Description
Architectural design
Detailed design
Database design
e-Restaurant
3TC Company
Architecture Design
Three Layers
e-Restaurant
3TC Company
Detail Design
Component Diagram
Sequence Diagram
Use Case Diagram
Business Model
www.themegallery.com
Company Logo
Detail Design
Business
Model
Component
Diagram
e-Restaurant
3TC Company
Database Design
Relationship
 Entity
Business
tables
 Every table has a primary key named Id which is of type: int not null
identity(1, 1)
 Every business table will have the trigger to save all the table changing
e-Restaurant
3TC Company
5. Implementation
Coding convention
Technologies
 DotNetBar
for Windows
forms conventions
(Devcomponent)
Follow
general
.NET coding
 GSM
Communication
Library
(GSMComm)
(e.g.
Pascal
Casing, Camel
Casing…)
Create specific conventions for our project
e-Restaurant
3TC Company
6. Testing
Test Model
Test plan
Test Phases
Bug control
Test report
e-Restaurant
3TC Company
6.1. Testing Model
Process Testing
e-Restaurant
3TC Company
6.2. Test Plan
Task Name
Test Cases Development
Test Cases Writing
Duration
21 days
14 days
Start
6/6/2011
6/6/2011
Finish
27/6/2011
20/6/2011
Comp
lete
(%)
0%
100
Test Cases Review & Update
6 days
21/6/2011
27/6/2011
100
ThuDA,
ThuongTH
Execute Test
Unit Test
Module Website
35 days
13 days
1 days
28/6/2011
28/6/2011
26/6/2011
2/8/2011
10/7/2011
27/6/2011
100
ThuongTH
0.5 days
1.5 days
17 days
2 days
27/6/2011
27/6/2011
11/7/2011
11/7/2011
27/6/2011
29/6/2011
28/7/2011
12/7/2011
100
100
CuongTM
TienND
100
ThuDA
2 days
30 days
3 days
13/7/2011
18/7/2011
18/7/2011
14/7/2011
18/8/2011
21/7/2011
100
ThuDA
100
ThuDA
3 days
8 days
21/7/2011
18/8/2011
24/7/2011
26/8/2011
100
ThuDA
User
Module Application_Đăng nhập
Module Application_Đặt chỗ
Integration Test
Module Website
Module Application_Đăng nhập
System Test
Module Website
Module Application_Đăng nhập
Acceptance Test
e-Restaurant
Resource Name
ThuDA
3TC Company
6.3. Testing Phases
Unit
Testing
Integration
Test
System
Test
Acceptant
Test
e-Restaurant
Unit Testing will be done by developers
(ThuongTH, CuongTM, TienND), is integrated
and approved by ThuDA, ThuongTH
Integration Test will be done by ThuDA
System Test will be done by ThuDA and
ThuongTH
Acceptent Test will be done by people who
use product with supported of team member
3TC Company
6.4. Bug control
e-Restaurant
3TC Company
6.5. Test Report
e-Restaurant
3TC Company
Demo & Q&A
e-Restaurant
3TC Company
e-Restaurant
LOGO