Sad

40
System analysis and design waiter on wheels WAITERS ON WHEELS : COMPUTERIZED DELIVERY TRACKING SYSTEM Waiters on Wheels is a restaurant meal-delivery service started in 1997 by Sue and Tom Bickford. The Bickfords both worked for restaurants while in college and always dreamed of opening their own restaurant. But unfortunately, the initial investment was always out of reach. The Bickfords noticed that many restaurants offer take out food, and some restaurants, primarily pizzerias, offer home delivery service. Many people they met, however, seemed to want home delivery service but with a more complete food selection. Waiter on Wheels was conceived as the best of both worlds for Sue and Tom – a restaurant service but without the high initial investment. The Bickfords contracted with a variety of well-known restaurants in town to accept orders from customers and to deliver the complete meals. After the restaurant prepares the meal to order, it charges Waiters on Wheels a wholesale price, and the customer pays retail plus a service charge and tip. Waiters on Wheels started modestly, with only two restaurants and one delivery driver working the dinner shift. Business rapidly expanded, and the Bickfords realized they needed a customer computer system to support their business operations. They hired your consultant firm to help them define what sort of a system they needed. Sue described the current system as such “When a customer calls in wanting to order, I need to record it and get the information to the right restaurant. I need to know which driver to ask to pick up the order, so I need drivers to call in and tell me when they are free. Sometimes customers call back wanting to change their orders, so I need to get my hands on the original order and notify the restaurant to make the change.” Tom continued, “The drivers get the copy of the bill directly from the restaurant when they pick up the meal, which should agree with our calculations. The drivers collect the amount plus a service charge. When drivers report in at closing, we add up the money they have and compare it to the records we have. After all drivers report in, we need to create a deposit slip for the bank for the day’s total receipts. At the end of each week, we calculate what we owe each UCTI-BMA

Transcript of Sad

Page 1: Sad

System analysis and design waiter on wheels

WAITERS ON WHEELS : COMPUTERIZED DELIVERY TRACKING SYSTEM

Waiters on Wheels is a restaurant meal-delivery service started in 1997 by Sue and Tom Bickford. The Bickfords both worked for restaurants while in college and always dreamed of opening their own restaurant. But unfortunately, the initial investment was always out of reach. The Bickfords noticed that many restaurants offer take out food, and some restaurants, primarily pizzerias, offer home delivery service. Many people they met, however, seemed to want home delivery service but with a more complete food selection.

Waiter on Wheels was conceived as the best of both worlds for Sue and Tom – a restaurant service but without the high initial investment. The Bickfords contracted with a variety of well-known restaurants in town to accept orders from customers and to deliver the complete meals. After the restaurant prepares the meal to order, it charges Waiters on Wheels a wholesale price, and the customer pays retail plus a service charge and tip. Waiters on Wheels started modestly, with only two restaurants and one delivery driver working the dinner shift. Business rapidly expanded, and the Bickfords realized they needed a customer computer system to support their business operations. They hired your consultant firm to help them define what sort of a system they needed.

Sue described the current system as such “When a customer calls in wanting to order, I need to record it and get the information to the right restaurant. I need to know which driver to ask to pick up the order, so I need drivers to call in and tell me when they are free. Sometimes customers call back wanting to change their orders, so I need to get my hands on the original order and notify the restaurant to make the change.”

Tom continued, “The drivers get the copy of the bill directly from the restaurant when they pick up the meal, which should agree with our calculations. The drivers collect the amount plus a service charge. When drivers report in at closing, we add up the money they have and compare it to the records we have. After all drivers report in, we need to create a deposit slip for the bank for the day’s total receipts. At the end of each week, we calculate what we owe each restaurant at the agreed-to-wholesale price and send them a statement and check.”

Basic requirements :

Design a system which does some processing when events such as these occur : a customer places an order either via telephone or via the company website. a driver is finished with a delivery a driver reports for work

The system should also produce information at some specific points in time – for example, when it is :

time to produce an end-of-day deposit slip time to produce end-of-week restaurant payments time to produce weekly sales reports

UCTI-BMA

Page 2: Sad

System analysis and design waiter on wheels

ABSTRACT

The main objective of the project is to identify the Methods or activities associated with

methodologies and of how the techniques are used together to develop a system. The project

includes the standard methodology to develop the system and documenting of project as well.

All the requirement and specification for creating the system design are explained briefly.

Physical and logical designs are mapped accurately having clear and detailed documentation

of designing phase.

UCTI-BMA

Page 3: Sad

System analysis and design waiter on wheels

INTRODUCTION

The project will be about waiter on wheel which was conceived by Sue and tom bickford in 1997, both worked for restaurant while in college and always dreamed of opening their own restaurant, but the the initial investment was always out of reach.

Started as home delivery service with a poor selection, talking to people tom and Sue realized there is need for variety for their food selection. Contact two restaurants, a delivery boy.

Then became popular and orders started pouring in and it is impossible to provide a satisfying service for the customer. Therefore to provide a good and faster service they decided to implement a computerized delivery and sales processing system.

They hired our consultant firm to help them define what sort of a system they needed.

Our development team consists of 4 members

System Analyst-Kanange junior,

System Analyst,Logical designer-Tanmay Kamrani,

Physical Designer- Nseka Mina Naomi

Technical Architect ,asst. physical designer- Pooja Choubey

The methodology selected by our team is SSADM which stands for structured system analysis

and design. The selected methodology has been clearly justified and compared to other related

methodology.

We started working on the project in April 2012 and the following is the outcome of our project

UCTI-BMA

Page 4: Sad

System analysis and design waiter on wheels

Analysis of the system

Analyzing this system we understand that the system is about:The customer call the waiter to order the food and the waiter will first record the call and get to the right restaurant, then call the available driver which can take the order from the restaurant to the right address.

Logical Assumption

In the case study, some logical assumptions have been made. Among them are that there will be

8 drivers, 4 at non-peak hours and 4 at peak hours that will deliver food ordered. Operation hours

will be from 11.00 am to 3.00 pm and 4.00 pm to 10.00 pm daily. Total of 10 hours of work.

peak hours will be from 11.00 am to 3.00 pm and non-peak hours 4.00 pm to 10.00 pm. Driver

will be paid according to his work FULL time or PART time. Drivers should have a drivers

licence.

Besides that, there will be 4 operators taking orders during operation time. There will be caller

id’s so that a person can be traced incase of prank call.

Cell Phones will be provided for operators and drivers to ease communication.

Receipts will be given showing distance, price of order and service charges. Customers need to

sign the receipt upon delivery as acknowledgement of delivery.

Exiting System The existing system is manual. Using batch processing to update data , collecting data and grouping into.The following are the processes involved in the system.

1. Order

Waiter on wheel receive call form customer, records it, the address contact number and the necessary information of the customer and the order.

2. The Restaurant

Sue and tom should call the right restaurant to transfer the need of the customer and ask to that restaurant to make two bill one for the customer and one for wiater on wheel.

UCTI-BMA

Page 5: Sad

System analysis and design waiter on wheels

3. Driver

Waiter on wheel has to call the available driver to pick up the order and bring to the right address.

4. Updating Order

The customer can call back to update their order. In this case waiter on wheel should call the restaurant and inform about the change.

Problems Identification

1. Long distance orders- there are many places which are far from the head office delivering to which vehicle would require more fuel and time which may affect the other orders.

Solution- there would be a service charge for the long distance orders and a minimum order rate.eg if a order has to be delivered 25kms away from office, there would be a service charge (extra) and a minimum order value of lets say example Rs 300. So that if the others are missed , the present order can make a recovery.

2. Fake call- it is a common problem everywhere. For food delivery industry, a prank call is the situation where a person orders food for someone else without the receiver’s permission, and very often the receiver would refuse to accept the food and pay for it.

Solution- When a customer orders food for the first time, he is given a ID/order no manually and by SMS on the provided number. During the registration process, the customer will be prompted for his address. The address that he entered would be the address the food will be delivered. In other words, he is not able to order food for someone else. Caller ID’s will be there so that the customer can be traced easily incase he is providing the wrong number. The delivery boy will confirm the order if the customer shows his ID by word or the Company message.

3. Cancelling or changing order -

Customers might change their mind. If any customer cancels or change the order after the

meal is cooked. Refuse to pay money. Or is unavailable. This would waste the material,

time and money.

Solution: As the customer change the order via calling the operator, the operator will

convince to the customer that the food is already cook and the food will be on their door

step soon. However if the customer insists that he would like to cancel the food and

refuse to pay for it, the food will be return back to the restaurant. The restaurant would

UCTI-BMA

Page 6: Sad

System analysis and design waiter on wheels

keep the food for max 2 hours in refrigerator and wait if there is any same order been

registered by any customer in the restaurant. The food will be re processed and delivered

hot. It won’t spoil as kept preserved for a less time Besides, the delivery company would

black list the customer who is found to be misguiding, misbehaving or refusing order.

4. Driver updating-there might be a problem that there is no information of the driver

finished with delivery, or multiple orders of same area. Unable to find location

Solution-drivers will be provided with Cell phone with GPS. They will be tracked and

given the exact location. In case of multiple orders of same area a driver will be assigned

with it collectively. Driver should come and update to the call attender to enter his name

on driver available list.

LIMITATION OF THE SYSTEM

1. As the system is manual the human error can get in easily when doing report, bill or calculation

2. In assigning the delivery boy, all can be buzz and the order will take long time to reach the address

3. Bills can be lost easily Keeping it in a wall after 6 months or 1 year

4. The phone lign can be buzz for more than half hour, customer need to update the order will not have this opportunity

UCTI-BMA

Page 7: Sad

System analysis and design waiter on wheels

SUGGESTION FOR IMPROVEMENT

COMPUTER TRACKING SYSTEM

the delivery boy do not need to call the company and notify the status since the delivery is tracked by an automated computerized system(GPS)

COMPUTERIZED AND AUTOMATIC SYSTEM

Not human mind will be use for huge calculation or data verification. Updated order and cancellation will be notified to the restaurant and delivery boy in real time

Feasibility study

Is the process followed in making a determination.This type of study clearly specifies that, the project should be taken up or not.It does not solve any problems.Is aim is to find out the problem of the system and meet the end users requirements.

Feasibility report

Consist of: Technical feasibility Operational feasibility Schedule feasibility Economic feasibility

Technical FeasibilityA large part of determining resources has to do with assessing technical feasibility. It considers the technical requirements of the proposed project. The technical requirements are then compared to the technical capability of the organization. The systems project is considered technically feasible if the internal technical capability is sufficient to support the project requirement.To find out whether current technical resources can be upgraded or added to in manner that fulfills the request under consideration.To know, if the technology is good, mature enough to be be easily applied to the problem.Because some firms like the latest technology, but most like the good, mature and proven technology.Assuming that the technology used is practical and the organization has the capacity to use it.If not, then consider the possibilities to get from outside thinking about cost.

UCTI-BMA

Page 8: Sad

System analysis and design waiter on wheels

1.Hardware

In the system, there is a server and 5 desktop 4 for order taking and 1 for admisitrator (sue and

tom). The server contains the database for customer information and taransaction. An operator

operates the desktop and stores information into the server. If however a new customer calls, the

operator is required to fill in a form to store the customer’s details into the database. Below is the

optimal technical requirement to serve the system.

Software

Software requirements:

1. Operating System

All of computers must need Operating System. In this system, we use Windows7

Professional and home premium to manage all of data. We use this operating system

because it is very simple and smart, easy to use, nice interface and latest in market.

UCTI-BMA

Lenovo Desktop

(4)

HP Business

Desktop (1)

Intel core i5

processors

Intel core i7

processor

Windows7

professional Edition

Windows7 Home

premium

2GB DDR-3

SDRAM

4GB DDR PC5700

SDRAM

320GB SATA HDD 500GB HDD

Page 9: Sad

System analysis and design waiter on wheels

Specifications

Manufacturer Microsoft corporation

OS provided Microsoft Windows7 Professional and

Home premium

License type Complete package

Hard drive space Minimum 15 GB

Minimum processor Intel Pentium 1.83 GHz

RAM Minimum 2 GB

General License pricing standard

2. Microsoft Office2010

In order to complete our Operating System and for database storage, we need the

Microsoft Office. Microsoft Office 2010 is very completely useful for this system

because in the case of installing the Microsoft windows7. This Microsoft Office consists

of Word, Excel, PowerPoint, and Access. Our database is also using Microsoft access.

3. Antivirus

For this system we can use quick heal antivirus. antivirus are protection from viruses,

Trojans and worms, protection from spyware, adware and other potentially junk program,

scanning for archived files and removable data storage device, instant database updates,

simple and easy to use.

UCTI-BMA

Page 10: Sad

System analysis and design waiter on wheels

Operational feasibility

Operational feasibility is dependent on human resources available for the project and involves projecting whether the system will be used if it is developed and implemented.

Operational feasibility is a measure of how well a proposed system solves the problems, and takes advantage of the opportunities identified during scope definition an how it satisfies the requirement analysis phase of system development.

Operational feasibility reviews the willingness of the organization to support the proposed system. This is probably the most difficult of the feasibilities to gauge. In order to determine this feasibility, it is important of us to understand the management, it is likely that there is management; it is likely that there is management commitment to the proposed project. If the request was initiated by management, it is likely that there is management support and the system will be accepted and used. However, it is also important that the employee base will be accepting to change.

There are two aspects of operational feasibility which should be considered,

Is the problem worth solving, or will the solution to the problem work What do the end users, and the management feels about the problem

PIECES FRAMEWORK

Information : How the information flows for waiter on wheel to restaurants and to drivers.

Customers can choose from the variety of food menu and place their order by call menu containing the full list of food the restaurant caters This system of ordering is tailored to be user friendly placing the needs, wants and demands of customers as their primary concern Upon careful selection of their desired food, simple step by step instructions are given to customers on phone directing them which kind of food they desire. After placing their order, information regarding the method of payment and various details of charges billed on them will be conveyed to the customer.

Performance : Order from customer till delivery.

The performance of the system is expected to have a higher respond time relatively compared

to a customer personally travel to a restaurant and order food. It is measured from the

moment the consumer steps out of his house door till the time when the food appears at the

table is estimated to be not more than 30 minutes. However if the distance or delivery point is

UCTI-BMA

Page 11: Sad

System analysis and design waiter on wheels

more than 25km, it may take 45km at max. The respond time here refers to the moment the

customer call the "Waiters On Wheels" center until the food arrive to his door.

Control : should have password, install antivirus

The system will be used by two types of users.

The first type is administrator(sue and tom) who has absolute power to see the "contents" of the

program. It includes editing the menu such as deleting or adding a new food to the list, rates and

other items The second type will be the waiters. Their responsibility is to receive orders from the

customers directing them the location for them to collect the requested deliveries and the

respective destination the food has to be sent to. Enter the updation of drivers and send ORDER

MESSAGE to customers. Upon completion of their deliveries to their clients, they will send a

response back to the call center informing them that they have completed their task successfully.

They will be able to track the driver by GPS.

Economy : it is cost beneficial

economy status is that the sue and tom realize the demand from customers and as they contracted

with a lot of well known restaurant, the income is stabilized. However, they can increase their

revenue by giving discount on bulk orders, or not throwing the cancelled order for 2 hours.

Assigning all orders of same area to same driver and additional charge for long distant orders to

cover fuel charges. They can also use fuel efficient cheap 125cc vehicles. 125cc engine has good

pickup so time will be saved and no delay in orders will be there.

Efficiency

"Waiters On Wheels" will be utilizing 4 waiters. Among the 4 of them, 2 waiters will undertake

the role of full time workers while the other two will be expected to fill in lunch and dinner

hours. Each waiter will be assigned a desktop computer to operate the system. Through the use

of this system, the operators will then be able to trace where the call is coming from and assign

available waiters to collect and deliver the food. Along the way of delivering food to the

customers, the waiters will be communicating with the drivers through the use of cellphones.

UCTI-BMA

Page 12: Sad

System analysis and design waiter on wheels

 

Service

The reliability of the system can be demonstrated through the use of unique identity for every

user to log in to the system. Every user will be provided a password to log into his account or

partition on the server or desktop. Therefore the owner of "Waiter On Wheels" will be able to

track any mistake that done by any user. In other words, the users would not be able to doing any

mistake to the system or misuse it .

The content of the system can be edited from time to time by administrator. This is specially

designed by the developers of the system to make sure the system is flexible and expandable.

UCTI-BMA

Page 13: Sad

System analysis and design waiter on wheels

Schedule Feasibility: is an analyzing the time for a project to be completed

Consists of

Work Load Matrix

Tasks Naomie Pooja Junior Tanmay

Identifying the system * * * *

Analysis of the system * *

Problems in existing system * * *

Feasibility report * *

Work load matrix * *

Gantt chart * *

Technical feasibility * *

Selection of methodology * *

Justification *

Logical design *

Physical design * *

conclusion * * * *

UCTI-BMA

Page 14: Sad

System analysis and design waiter on wheels

Gantt Chart-

UCTI-BMA

Page 15: Sad

System analysis and design waiter on wheels

Economic Feasibility

Economic analysis could also be referred to as cost/benefit analysis. It is the most frequently used method for evaluating the effectiveness of a new system. In economic analysis the procedure is to determine the benefits and savings that are expected from a candidate system and compare them with costs. If benefits outweigh costs, then the decision is made to design and implement the system The system we are going to design will cost effectively, the hardware, the time of building which the system will need are flexible less expensive.Which will provide immediate acess to records that are periodically updated?

Selecting of methodology

SSADM (Structured Systems Analysis and Design Method )SSADM is a methodology developed originally by UK consultants learnmonth. And the central computing and telecommunication agency (CCTA) which is responsible for computer training and some procurement for the UK civil service ( Activison & Fitzgerald,2006) the main reason of this was to improve government service to public.The main target for SSADM is produced computer System, that fit the acquired purpose, by putting framework, carry out given task and also support organization IT Strategy according to the timeline

SSADM will be use for this project because since this methodology was developed, the main reason was improvement as we need the same for this project.

Object-oriented analysis

Object-oriented analysis (OOA) is the process of analyzing a task (also known as a problem domain), to develop a conceptual model that can then be used to complete the task. A typical OOA model would describe computer software that could be used to satisfy a set of customer-defined requirements. During the analysis phase of problem-solving, the analyst might consider a written requirements statement, a formal vision document, or interviews with stakeholders or other interested parties. The task to be addressed might be divided into several subtasks (or domains), each representing a different business, technological, or other areas of interest. Each subtask would be analyzed separately. Implementation constraints, (e.g., concurrency, distribution, persistence, or how the system is to be built) are not considered during the analysis phase; rather, they are addressed during object-oriented design (OOD).

The conceptual model that results from OOA will typically consist of a set of use cases, one or more UML class diagrams, and a number of interaction diagrams. It may also include some kind of user interface mock-up.

UCTI-BMA

Page 16: Sad

System analysis and design waiter on wheels

Reasons for selecting this methodology(SSADM)

It provides measurable, reviewable and definable product specification..

It increases involvement and communication between system and users.

A great impact of this methodology is that the total time and cost are greatly reduced, if

system developed by this methodology is implemented in the organization.

Stages that should be followed SSADM

Analysis of the current system

Detailed business specification

Logical data design

Logical process design

Physical design.

business specification

Customer calls to place the order. Waiter takes the order and sends SMS to customer with

order code. Waiter on wheels then informs to the related restaurants for the order. Waiter

on wheels then checks the availability of the driver and informs driver to pick the order

from the restaurants then restaurants will give the order to the driver along with the

customer code.

The driver will take the order and deliver it to customer, driver will check the code and

verify. after delivering the order driver will come back and give the bill, money and

attendance to waiter on wheels.

waiter on wheels keeps the record of each and every restaurant, what are the orders taken

from them and on which date and time. Weekly or monthly waiter on wheels will pay the

bill payment as per the wholesale price or the deal what they have done.

UCTI-BMA

Page 17: Sad

System analysis and design waiter on wheels

Flowchart

UCTI-BMA

PaymentTo driver

Customer

Driver

STOP

Restaurant

Detail of order

Detail of customer

Waiter On wheels

Customer Oder

START

Page 18: Sad

System analysis and design waiter on wheels

Context diagram.

Payment(food & service charge)

Cancel order

Send driver

Make order

Customer profile inform restaurant

Monthly receipt

Food pickup

Food Delivery

Check customer code

Send bill

UCTI-BMA

O

Waiter on wheels

Customers Restaurant

Page 19: Sad

System analysis and design waiter on wheels

Data flow diagram level 0

It shows relationship between following business processes:

External systems,

External organizations,

Customers

Other business processes.

UCTI-BMA

Page 20: Sad

System analysis and design waiter on wheels

Data flow diagram level 1

UCTI-BMA

Page 21: Sad

System analysis and design waiter on wheels

Entity Realationship Diagram-

Waiters

Customer

report/code

restaurant

invoice management

Order

Driver

calls

cre

ate

Ord

er

pay

delivered to

prin

t

Sent to

completed

taken by

Deliver

ord

er

given to

received by

Pass to

got by

Buy SmartDraw!- purchased copies print this document without a watermark .

Visit www.smartdraw.com or call 1-800-768-3729.

DATA DICTIONARY

UCTI-BMA

Page 22: Sad

System analysis and design waiter on wheels

Customer Information

S.No

Customer name address Time/date Order details

invoice driver code

123

Driver Information

S.No

Driver name reporting leaving Order availability Vehicle No

Phone

123

Driver Tracking-

Driver Name Order Code Location(GPS) Vehicle No Phone

Daily Report

S.no Component amount1 Total customers2 Fuel Charges3 Driver Charges4 Service charges Total-

Physical Design:

UCTI-BMA

Page 23: Sad

System analysis and design waiter on wheels

Physical design is related to logical design and produces the program specifications or database

and user interface for a specific entity. This will fulfill the logical design.

The design is based upon

Easy navigability

End user requirements

All Information

The screen includes

1.Customer information-

Date-

Time-

Customer name and phone-Phone verified on caller ID

Customer address-Re confimed

Customer code-order code also sent by message on number provided above.

2.Invoice-

date and time

customer name and code-

details of order with price-

3.Driver information-

Driver name-

Vehicle no-vehicle used by particular driver

Phone no-provided by company with gps activated

Order code-of the customer to be delivered

Availability-available or on delivery

4.Driver location-GPS location

UCTI-BMA

Page 24: Sad

System analysis and design waiter on wheels

Driver name

Order code- order in active position

Location- area according to satellite

Vehicle no- provided by company

Phone- GPS included.

5.Daily transaction-

Order code-all inclusive listed

Charge-each order charge according to code

Driver and service charge-in case of distant orders and daily pay of driver.

Total-orders and wholesome.

6.Weekly transaction-

Total orders- per day in a week

Collection-per day in a week

Total-total of 7 days with no of orders and whole total (service charge etc)

UCTI-BMA

Page 25: Sad

System analysis and design waiter on wheels

Screen-1 Customer Information

Screen-3 Driver Information

UCTI-BMA

CUSTOMER INFORMATION

Waiter on wheels

Customer Name:

Customer Phone:

Date :

Customer Code:

Time :

Customer Address:

Waiter on wheels

Page 26: Sad

System analysis and design waiter on wheels

Screen-2 Bill/Invoice

UCTI-BMA

Driver Information

Driver Name:

Contact Number:

Order code:

Availability:

Reporting time:

Closing time:

Vehicle no:

Page 27: Sad

System analysis and design waiter on wheels

UCTI-BMA

Total:

Invoice

Order Details

Items Quantity Price

Waiter on wheels

Date: Time:

Customer Name:

Customer ID:

Customer Phone:

Customer Address:Order code:

Page 28: Sad

System analysis and design waiter on wheels

Screen-4 Driver location

UCTI-BMA

Driver Location [GPS]

Details

Driver name order code location Vehicle no Phone no

Waiter on wheels

Page 29: Sad

System analysis and design waiter on wheels

Screen-5 Daily transaction

UCTI-BMA

Daily Transaction

Details

Order code charge Driver charge service charge Total

Waiter on wheels

Total Order:

Total collection:

Page 30: Sad

System analysis and design waiter on wheels

Screen-6 Weekly transaction

References:

UCTI-BMA

Weekly Transaction

Details

Total orders collection Driver charges service charges Total

Waiter on wheels

Total Orders:

Total collection:(inclusive all)

Page 31: Sad

System analysis and design waiter on wheels

System Analysis and Design, Kenneth E .Kendall, Julie E. Kendall, Saji K. Mathew .sixth

edition.

Smart draw tool tutorials available at: http://www.smartdraw.com/specials/diagram.asp[accessed

28may 2012]

Articles on Feasibility studies available at:

http://www.businessdictionary.com/definition/feasibility-study.html [accessed 15 may2012]

http://www.waterfall-model.com/sdlc/ [accessed 4 may 2012]

Appendices- Minutes of meeting

UCTI-BMA