IS 497 Presentation

1
IS 497 Presentation

• IS 497 Final Project PresentationMonday
  5-6-2006
• Jury
• Dr. Mohemt Aksoy
• Dr. Ibrahim Fathy
• Done by
• Mazen
• Hisham

You are very welcome to contribute in any part of
the presentation
2
Objectives

• Introduction to HotMeal system .
• System benefits .
• System Actors .
• Summary of design .
• Implementation method .
• Future work .
• Conclusions .

3
Introduction to HotMeal system

• HotMeal is a web-based system that enables the
  customers to perform two main tasks 1)
  KNOWING about the restaurants 2) MAKING
  orders.
• The system plays the intermediation role between
  the customer and restaurant .
• The system is supposed to convert the typical way
  of ordering to an electronic effective way.

4
How it Works ?
Step 3 The Restaurant Employee determine
whether ( accept / reject ) the order .
Step 2 The HotMeal EMPLOYEE in the same region
for the customer receives the order , then
assigns a time and driver to it before he
forwards it to the restaurant .
Step 1 a CUSTOMER surfers the HotMeal website
and issues an order
5
Objectives

• Introduction to HotMeal system .
• System benefits .
• System Actors .
• Summary of design .
• Implementation method .
• Future work .
• Conclusions .

6
System Benefits

• HotMeal vs. Telephone Ordering
• Let us compare and see !
• Benefits for Customer
• Why someone be a member in the system !
• Benefits for The HotMeal company
• Do they make it for FREE really !
• Benefits for The Restaurants

7
Objectives

• Introduction to HotMeal system .
• System benefits .
• System Actors .
• Summary of design .
• Implementation method .
• Future work .
• Conclusions .

8
System Actors
I am the ADMIN
I am the HotMeal Employee

• I can do the following tasks
• Orders management .
• Customer management .

• I can do the following tasks
• Restaurants Management .
• Employees Management .
• Drivers Management .
• Cars Management .
• Users Creation .

I am the Restaurant Employee
I am the Customer

• I can do the following tasks
• Meals management .
• Accept / Reject Orders

• I can do the following tasks
• Search for meals .
• Make orders .

9
Objectives

• Introduction to HotMeal system .
• System benefits .
• System Actors .
• Summary of design .
• Implementation method .
• Future work .
• Conclusions .

10
Summary of design

• UML ( Logical design )
• Use Case , Scenario , and Class diagrams
• E-R diagram ( Physical design )
• Entity Relationship Diagram

11
Objectives

• Introduction to HotMeal system .
• System benefits .
• System Actors .
• Summary of design .
• Implementation method .
• Future work .
• Conclusions .

12
Implementation method

• Direct Access
• What does that mean ?
• Why ?
• Less work time .
• More Effective .
• Load balancing .

13
Implementation method
User Inputs
SQL server
User Frame takes the inputs , validate it (
client side validation ) then forward it to the
SQL server
Depending on the function , the input may be
stored directly OR be an input for a stored
procedures that will return an out put
14
Objectives

• Introduction to HotMeal system .
• System benefits .
• System Actors .
• Summary of design .
• Implementation method .
• Future work .
• Conclusions .

15
Future Work

• Electronic registration and payment
• Need more secure connection and online payment
  gateway .
• Expert System can handle it !
• the expert system agent can handle the employee
  role ( i.e. setting the time , selecting the most
  appropriate driver ) .
• Data Mining and Association analysis
• By analyzing the data we can generate a useful
  association rules for customers , restaurants and
  HotMeal head office .

16
Objectives

• Introduction to HotMeal system .
• System benefits .
• System Actors .
• Summary of design .
• Implementation method .
• Future work .
• Conclusions .

17
Conclusions

• Its not ready yet !
• More enhancements can be added .
• We learn new thing and revise many of our
  previous courses .