Professional Documents
Culture Documents
Domino Pizza Order Booking System-BS-2010 PDF
Domino Pizza Order Booking System-BS-2010 PDF
Group Members:
Farrukh Ali
Mustafa Khan
Muhammad Zeeshan
2
Federal Urdu University of Arts Science & Technology
CERTIFICATE
1. Farrukh Ali
2. Mustafa Khan
3. Muhammad Zeeshan
3
TABLE OF CONTENTS
Preface ----------------------------------------------------------------------------------------------6
Acknowledgments -------------------------------------------------------------------------------7
Introduction to Client Organization --------------------------------------------------------8
4
2.9.1. Outlet User -----------------------------------------------------------------------21
2.9.2. Admin -----------------------------------------------------------------------------22
2.9.3. Agent ------------------------------------------------------------------------------23
2.10. Functional Requirements -----------------------------------------------------------24
2.10.1. User Module
2.10.2. Agent Module
2.10.3. Admin Module
2.11. Non-Functional Requirements ----------------------------------------------------25
2.11.1. Performance Requirements
2.11.2. Security and Control Requirements
2.11.3. Software Quality Attributes
5. Testing ---------------------------------------------------------------------------------------29
5.1. The Test Plan
5.2. Test Cases
8. Summary -----------------------------------------------------------------------------------34
5
PREFACE
Objectives.
This document attempts to provide a unified detail of a final project of Domino Pizza
Order Booking System. The organization of this document reflects an attempt to
break this system into comprehensible parts and to build, piece by piece, and
technical details of the whole system. The document emphasizes technically & user
manually to provide a brief description of the online system.
In addition, the document includes some other information about the Tools &
Technology, Future Advancements, Summary and References about the project.
6
ACKNOWLEDGMENTS
First and foremost thanks to Almighty ALLAH for giving us the opportunity, courage
and strength to successfully complete this project within the specific time duration.
Huge thanks are in order to our project supervisor, Sir Sheikh Kashif Rifat. Far
beyond pointing out our mistakes & appreciate our work, Sir had a number of great
suggestions to clarify and refine our initial design & code samples. Thanks Sir!
7
INTRODUCTION TO CLIENT ORGANIZATION
The Client Representative for this project is Mr. Ahsan Saeed. He is the
incharge of Domino and McDonald Campaigns in Pakistan. The older system has not
full fill the requirements of current age. The old system was not enough for the
current orders. Mr. Ahsan Saeed felt that there was a need application which could
make "Order Taking" process more fast so that agents could log more orders in less
time.
The old system has build on Java, but now the age of Graphics. The Old system
not has much security and the old system not for online user this time organization
want to develop an on-line system for booking.
8
1. FEASIBILITY ANALYSIS
1.1 Technical Feasibility
Currently Domino Pakistan is running their online system on Dotnet
frame work 2.0 with classical ASP with P4 range PCs.
They want to upgrade this system on Dotnet frame work 3.5 and
Dynamic ASP.Net based website compatible with same PCs or above.
9
SCREEN SHOTS OF DOMINO PIZZA ORDER BOOKING
SYSTEM
Login Page
10
Admin Home
11
Agent Home
12
ADD Complaints
13
2. SOFTWARE REQUIREMENTS SPECIFICATION
2.1. Business Requirements
2.1.1 Background
Domino Pizza International was founded in 1960s. Currently, Each day, more
than 1 million customers enjoy hot, delicious Dominos Pizza products on every
inhabited continent on Earth. Around the world, Dominos Pizza is dedicated to a
single-minded focus of providing great-tasting pizza delivered directly to customers
door.
On September 12th 2004 Pakistans first Dominos Pizza Store opened in
Karachi. Domino Pakistan is looking for an online order booking system for its
Outlets Nationwide for delivering the Pizza orders to customers door step.
14
2.2. Vision of the Solution
MF-01 Register users can place their orders directly via web by their account
ids.
MF-02 The system automatically calculates the value of the whole order place.
MF-03 Users can lodge complaints online.
MF-04 Admin can review the sales record of a single or all outlets and can add
more outlets and agents in the system.
Assumptions
Client will provide all necessary requirements.
All group members worked according to their task assigned in the
discussion meeting & complete their task within the time schedule.
Constraints
Database Server MS SQL 2005
Dependencies
Microsoft .Net framework 2008 or greater is installed & configured
correctly.
The system is running Windows XP (SP2 or greater).
15
2.3. Scope and Limitations
2.3.1 Scope
The Order booking system is an online web application that permits new
users to place their orders online. Also the outlets agent had done the same job
when a user calls to them to place an order; the agents can also view complaints
& edit orders. The administration of the can add agents & outlets in system & can
view sales reports of an outlet.
16
2.4. Data Flow Diagram
Agent
Domino Pizza
Order Booking
System
17
2.5. Entity Relationship Diagram
ID Location
Name
ID Name
NIC Phone#
View
Booking
Record
s
ID
ID
Phone#
Name
Location
Customer Admin
18
2.6. Tables
The following sets of tables are made in SQL database from where we get,
send, update & delete data with respect to our demand.
City
- All cities nationwide where Domino Outlets are opened mention
& can add in this table.
Complains
- Any complaint regarding to outlet/order delivery will be
handover to this table.
Complain Status
- It mentions the current status of a complaint, weather it is
solved or not.
Customer Information
- All information related to customer will get & send in this table.
Customer Order Status
- Shows status like in Process/Delivered.
Locations
- Outlets Location area wise in different cities.
Meals
- Meals information
Meal Type
- Deal/single
Order Detail
- Detail of an order with special instructions
Orders
- Order Information place by customer
Order Status
- All Orders status weather it was open, punched or closed.
Outlet Information
- Outlets information with respected IDs placed in it.
Temporary Order
-
Users Group
- Admin/outlet user/agent
Users
19
2.7. User Classes and Characteristics
20
2.9. Use Cases
Login
Outlet
Home
View
View Complaint
Order
21
2.9.2. Admin
Log in
Admin
Home
View Order
View
Complaints
Generate
Reports
Add/ Remove
User/Agents
22
2.9.3. Agent
Login
Agent Home
Add Order
Add Forward
Complaint Complaint
23
2.10. Functional Requirements
The system features/functional requirements have been divided into three main
modules:
Agent
Outlet User
Admin
Add,, Edit, Delete Admin can add user, agent & outlet into the system & can edit
Users, Outlets their information & locations plus delete them from the system
as well.
View Order Admin can view orders of any Outlet in a form of a report.
Reports
View & Action Admin can also view & take actions against the Outlet / Agent
complaints about which the complaint lodge.
Sales Report Admin can view the sales record of any or all outlets.
24
2.11. Non Functional Requirements
25
3. PROCESS MODEL
3.1. Process Model Selection
For this system we used 2 Process Models.
1. Prototype
2. Linear Sequential Model - LSM (Flexible)
With the help of prototype model we create prototype. In Prototype Model we
create a prototype then test this prototype. This Prototype approximate as final
product. With the help of this model we get a overview about our system.
With the help of LSM the software life cycle is developed in a sequential order
i.e. analyzing, designing, coding and then implementation. First we analyze the
system that how the data flow after we design the system. This LSM model is
flexible. In classic LSM we dont reverse our work but with the help of flexible LSM
we were able to reversely go to any phase.
In analysis phase we break our system into 3 parts.
Admin Panel
Agent Panel
Outlet Panel
First we analysis about admin panel then create its prototype. 2nd we analysis agent
panel then create its prototype 3rd we analysis outlet panel then create prototype of
outlet.
26
4. RISK MANAGEMENT
4.1. Risk Identification
Impact Values
1. Catastrophic
2. Critical
3. Marginal
4. Negligible
27
4.2. RMMM Table
28
5. TESTING
5.1. The Test Plan
Software test planning is the process whereby the following are established
for the testing of a project deliverable:
29
6. TOOLS AND TECNNOLOGY
The following tools, technology programming languages have been used in the
development of this project and its documentation:
30
7. REPORTS
7.1. Orders Report
31
7.2. Complaints Report
32
7.3. Outlet User Orders Report
33
8. SUMMARY
About Project
This new system of DOMINO PIZZA ORDER BOOKING is more
efficient, reliable and secure to the previous one. Development using
Microsoft tools made it more commendable to the user.
Using its compatibility it can handle up to 100 outlets data of Domino
Pakistan. For future enhancement it is also supported by using Microsoft
platform.
34