February 3
2011
Final Project
Report
Group Members:
Farrukh Ali
Mustafa Khan
Muhammad Zeeshan
Project Supervisor
Sheikh Kashif Rifat
Head of Department
Asima Nisar
TABLE OF CONTENTS
Preface ----------------------------------------------------------------------------------------------6
Acknowledgments -------------------------------------------------------------------------------7
Introduction to Client Organization --------------------------------------------------------8
1.
2.
4.
5.
Testing ---------------------------------------------------------------------------------------29
5.1. The Test Plan
5.2. Test Cases
6.
7.
8.
Summary -----------------------------------------------------------------------------------34
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.
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!
Finally and most importantly, a heartfelt acknowledgment goes to our group
members team coordination which is supportive beyond words.
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.
10
Admin Home
11
Agent Home
12
ADD Complaints
13
14
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
MF-04
Admin can review the sales record of a single or all outlets and can add
more outlets and agents in the system.
15
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
Agent
Domino Pizza
Order Booking
System
Outlet User
Admin
17
Name
Agent
Outlet
Forward
Order
NIC
Phone#
View
Record
s
Booking
ID
ID
Name
Phone#
Location
Customer
NIC
Location
ID
Name
Phone#
Admin
Cell#
Name
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
Outlet User
Admin
Characteristics
OE-02
OE-03
20
Outlet User
Login
Outlet
Home
View
Order
View
Complaint
21
Admin
2.9.2.
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
Complaint
Forward
Complaint
23
2.10.2.
Login
Edit Order
Update Status of
Order
Update Status of
Complaints
Change Password
2.10.3.
Add,, Edit, Delete
Users, Outlets
View Order
Reports
View & Action
complaints
Sales Report
Agent Module
Login with a register account.
Agents can add & view complaints into the system.
They can also add order & view previous orders.
Agent can add customer information into the system
24
PR-02
SCR-02
SCR-03
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
RISK MANAGEMENT
4.
Risk Type
Probability
Impact
Technical
80%
Economical
60%
Project Management
70%
Operational
40%
60%
Business Risk
Impact Values
1.
2.
3.
4.
Catastrophic
Critical
Marginal
Negligible
27
Mitigation
Monitoring
Management
System failure
Make multiple
backup copies
The development
team should cease
work on that system
until it is stable
again.
System Cost
Monitor the
technology costs
regularly.
Conduct a meeting
with customer to
convenience him
about the extra
budget.
Lack of
Communication
between
Developers
Must be a strong
& well mature
team selected
who enjoyed
working together.
During meetings
formally or in formally
ask members about
their task.
Change any
developer or
conduct a meeting to
know their issues.
Human
Resource
Shortage
Should complete
analyze before
the project starts
about the
systems length
and the Man
power available.
Requirements
In-complete
Preferably a meeting
conducts between
customer &
developers to
discuss at length this
issue.
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:
Testing requirements (scope),
- Domino Pizza order booking system is tested to identify any
bugs that can be occurred during the application run after the
project is deliverable.
Testing approach,
- We assigned each group member a system to test which was
made by other member.
Testing tasks and deliverables,
- Task of this testing is to identify the bugs, program efficiency &
reliability.
Completion criteria,
- Completion of a test is based on the report of the group member
that the system is accurate.
Test environment and team roles and responsibilities.
- Environment of this testing is home based so a member can
easily check & focused on the system.
And we have didnt find any bug or serious issue which cause any major
problem for the system.
29
6.
30
7.
REPORTS
7.1. Orders Report
31
32
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.
About Our Experience
This project gives us a chance to technically learn the current trends in
software engineering & how to explore yourself when a professional project
assigned to you. The time analysis, designing, coding, testing and
implementation with a limited schedule are a milestone for us, which we
successfully achieved.
Thanks to our Supervisor and course teachers without them we are
nothing.
34