Sie sind auf Seite 1von 22

Data Flow Diagram

Context Diagram

Diagram 1 Context diagram of Waiter on Wheels delivery system

Data Flow Diagram Level 0

Diagram 2 Data flow diagram level 0 of Waiter on Wheels Delivery system

Data Dictionary External Entities of DFD Level 0 Name: Customer Description: The customer who order food using Waiter on Wheels Delivery System and they get registered in the system. Input data flow: Confirmation detail, Customer receipt Output Data flow: New order request, Order payment, and customer identity

Name: Restaurant Description: The food supplier in the system. They prepare the food after giving confirmation. Input data flow: Weekly statement, Order list Output data flow: Order confirmation, Statement confirmation

Name: Bank Description: Office sends the deposit slip to bank and bank provides bank statement every month. Input data flow: Deposit slip Output data flow: Bank statement

Processes in DFD level 0 Name: Process 1.0 Submit information of order Description: Customer submits the information of order via medium available of the Waiter on Wheels, such as, telephone, fax, and company websites account. The information included the name, address, order request. This process also involves registering the new customer and storing the information to customer file. Input data flows: New order request, Customer identity Output data flows: New customer detail, Customer order request Process description: GET New order request GET Customer identity GET Customer detail IF Customer identity confirm THEN proceed to new order request& save in customer file ELSE register new customer detail & send customer order request ENDIF END

Name: Process 2.0 Check and verify Description: This process is done after declaring the customer information to verifying the order of customer. If customer had change order, then precede another process to change order of customer and inform the restaurant. Then, restaurant will give a confirmation about the waiting time and food viability. After that office sends confirmation to customer. Input data flows: Order confirmation, Customer order request Output data flows: Order list, Order detail, Confirmation detail

Process description:

GET Customer order request GET Order confirmation

IF Customer order request verified THEN send order list to restaurant ELSE get customer order request IF restaurant confirmation verified THEN confirmation detail to customer ELSE get order confirmation ENDIF ENDIF END

Name: Process 3.0 Delivery Handling Description: This process is to giving information to the driver and get confirmation from driver that had accept this duty. After driver accept the delivery duty, office operator will record it in driver file. Then driver will get meal from restaurant and sends it to destination. Driver giving customer a customer receipt that had plus a service charge and tips. Then customer pays for the meal. Input data flows: Order detail, Current drivers status, Order payment Output data flows: Customer receipt, Record driver status, Payment of sales Process description: CHECK Current drivers status IF driver status is available THEN send order detail ELSE check driver status ENDIF GET Confirmation from driver DO record the status of driver in driver file

WHILE the driver is confirm the order ENDO GET Order payment IF customer verified the order, THEN give customer receipt ELSE handle customer problem SEND Payment of sales ENDIF END Name: Process 4.0 Calculate Payment Description: This process will accept the payment of sales and calculate the payment. Then save the order payment detail in to the payment file and sends the amount of sales to generate report. Input data flows: Payment of sales Output data flows: Order payment detail, Amount of sales Process description: GET Payment of sales IF Payment of sales is verified with zero error THEN record in to payment file ELSE solve the error IF Payment of sales is verified with zero error THEN send amount of sales ELSE solve the error ENDIF ENDIF END

Name: Process 5.0 Generate report Description: In this process, the operator will get payment amount from payment file and amount of sales to generate the report. Then provide weekly statement to restaurant and daily deposit slip to bank. Then the operator will save the report detail in to report file. Input data flows: Amount of sales, Payment amount, Statement confirmation, Bank statement Output data flows: Weekly statement, Report detail, Deposit slip Process description: GET Amount of sales IF Amount of sales verified with non error THEN send weekly statement to restaurant ELSE solve the error ENDIF SEND Deposit slip GET Bank Statement GET Payment amount IF Payment amount is verified with non error THEN send total sales and create report ELSE solve the error ENDIF IF Bank statement is verified with non error THEN create report ELSE solve the error SAVE report detail in Report File ENDIF END

Data stores in DFD level 0 Name: Customer file Description: This is the database that stores the information of customer. Input data flows: New customer detail Output data flows: Customer detail Data structure: customer name + Food ordered detail + Address+ Contact number+ Gender+ Date of Birth Name: Driver file Description: This storage which storing the information of driver that on duty. Allow the operator to check and change driver status. Input data flows: Record driver status Output data flows: Current drivers status Data structure: Driver name+ Driver duty time+ Driver status+ Driver contact number+ Driver working information+ Driver ID

Name: Payment file Description: This is the database which storing the order payment details from driver. Then operators verify the amount and store in the payment file. The purpose of this is providing information to generate report process. Input data flows: Order payment detail Output data flows: Payment amount Data structure: Order food price+ Service tax & tips+ Total Name: Report file Description: This storage stores the report that generated. Report content involves the sales, bank statement, restaurant statements. To provide the information to check whether the company whether making profit. Input data flows: Report Detail Output data flows: Data structure: Daily sales amount+ Deposit slip+ Monthly bank statement+ Restaurant statement+ Daily report

Data flow in DFD level 0 Name: New order request Description: The customer sends the information of new order, includes the customer identity information. It can be the change information from customer. Origin/Source: External Entities: Customer Destination link: Process 1.0 Submit information of order Data structure: Customer name + Food order detail+ Changed order detail+ Name: Customer identity Description: Customer giving own information for operator to verify. Origin/Source: External Entity: Customer Destination link: Process 1.0: Submit information of order Data structure: Customer name+ Contact Number+ Address+ Date of birth+ Gender+ Online username & password+ Email Address

Name: New customer detail Description: The data entries of new customer. Origin/Source: Process 1.0: Submit information of order Destination link: Data stores: Customer files Data structure: Customer name + Address+ Contact number+ Username & Password+ Gender+ Email Address+ Date of Birth

Name: Customer detail Description: The customer giving name and operator will gain information from customer file. Origin/Source: Data store: Customer file Destination link: Process 1.0 Submit information of order Data structure: Customer name + Food ordered detail+ Changed order detail+ Address+ Contact number+ Customer ID

Name: Customer order request Description: Operator checks and verifies the order type using customer order request information. Origin/Source: Process 1.0 Submit information of order Destination link: Process 2.0 Check and verify Data structure: New order list+ Change order list Name: Order list Description: After operator checks the food order, then operator will sends this data flow to restaurant that have this food. Origin/Source: Process 2.0: Check and verify Destination link: External Entity: Restaurant Data structure: food name+ Quantity+ Additional information Name: Order confirmation Description: Restaurant sends the information of confirmation of meal Origin/Source: External Entity: Restaurant Destination link: Process 2.0: Check and verify Data structure: Food name+ Waiting time+ Sales price

Name: Confirmation detail Description: Office sends the confirmation detail to customer about the price and waiting so on. Origin/Source: Process2.0: Check and verify Destination link: External Entity: Customer Data structure: Price of order+ Estimated reach time+ Confirmation of order

Name: Order detail Description: This giving information to driver about the detail of order from operator, telling the driver about the order food, restaurant destination, customer address. Origin/Source: Process 2.0: Check and verify Destination link: Process 3.0: Delivery Handling Data structure: Food order+ Restaurant to collect+ Collect time+ Delivery time+ Deliver price

Name: Record driver status Description: This data flow is to record the driver status in to driver file, to having more accuracy information of driver. Origin/Source: Process 3.0: Delivery Handling Destination link: Data stores: Driver file Data structure: Driver name and ID+ Driver duty time+ Driver status Name: Current drivers status Description: Operator gets information from driver file to know that driver status. Origin/Source: Data store: Driver file Destination link: Process 3.0: Delivery Handling Data structure: Driver name+ Driver duty time+ Driver status Name: Customer receipt Description: This data flow provide the customer receipt to customer from driver Origin/Source: Process 3.0: Delivery Handling Destination link: External Entity: Customer Data structure: Driver name+ Order meal+ Price of order+ Service tax

Name: Order payment Description: Customer pays the amount to driver after driver gave customer receipt. Origin/Source: External Entity: Customer Destination link: Process 3.0: Delivery Handling Data structure: Cash

Name: Payment of sales Description: Driver gets the payment from customer and sends it to office to calculate payment. Origin/Source: Process 3.0: Delivery Handling Destination link: Process 4.0: Calculate Payment Data structure: Payment from customer+ Customer receipt copy

Name: Amount of sales Description: This data flow sending the information of amount of sales to generate report. Origin/Source: Process 4.0: Calculate payment Destination link: Process 5.0: Generate report Data structure: Daily sales+ Amount owe restaurant+ Amount of deposit

Name: Order payment detail Description: Operator record the information to payment file Origin/Source: Process 4.0: Calculate payment Destination link: Data store: Payment file Data structure: Payment of customer+ Service tax amount

Name: Payment amount Description: Operator gets information from payment file to generate reports. Origin/Source: Data store: Payment file Destination link: Process 5.0: Generate report Data structure: Daily sales+ Total service tax amount

Name: Report detail Description: Operator stores the report in to report file Origin/Source: Process 5.0: Generate report Destination link: Data stores: Report file Data structure: Report of daily sales amount+ Report of bank statement+ Report of restaurant statement

Name: Deposit slip Description: The office sends the deposit slip in to bank Origin/Source: Process 5.0: Generate report Destination link: External Entity: Bank Data structure: Amount of daily sales+ Amount owe restaurant

Name: Bank statement Description: Bank provides statement to office as a receipt monthly. Origin/Source: External Entity: Bank Destination link: Process 5.0: Generate report Data structure: Amount of deposit+ Amount of transfer

Name: Weekly statement Description: Office sends statement to restaurant about the deposited amount and sales Origin/Source: Process 5.0: Generate report Destination link: External Entity: Restaurant Data structure: Amount of sales+ Deposit amount

Name: Statement confirmation Description: Restaurant giving confirmation that agree about the statement provided Origin/Source: External Entity: Restaurant Destination link: Process 5.0: Generate report Data structure: Total sales for Waiter on Wheels+ Amount received

Data Flow Diagram Level 1 Process 1.0

Diagram 3 DFD Level 1 Process 1.0

Data Flow Diagram Level 1 Process 2.0

Diagram 4 DFD Level 1 Process 2.0

Data Flow Diagram Level 1 Process 3.0

Diagram 5 DFD Level 1 Process 3.0

Data Flow Diagram Level 1 Process 5.0

Diagram 6 DFD Level 1 Process 5.0