REQUIREMENT ENGINEERING

GROUP PROJECT

1. INTRODUCTION
1.1. PROJECT BACKGROUND Customer calls for make the order, than all the order information will be record somewhere and get the right restaurant. And to check driver availability, to know who is free for delivery and driver have to call for their free time. Sometimes customers can change the order, so the first order has to be modified. The available driver has to drop the copy of the bill directly from the restaurant .The drivers collect the money plus a service charge. When the driver will finish making the report than, we add up the money and compare it to the system report. Than create a deposit slip for the bank for the days total receipts. Each week calculate the amount we owe to each restaurant at the agreed to wholesale price and send them a statement and check.

1.2. PROBLEM ANALYSIS The current system is manual, so that why the system is too slow. Every information is saving in a register, difficult to find easily some information when needed. Cannot find availability of the driver easily and make the report .The system has many customer but the bill and other report is manual and calculation of bank and restaurant money is calculate by hands, so that why take time and human energy.

1.3. PROBLEM SOLUTION The system helps customer who cannot come directly to buy food to order by call. Customers increase day after day and no way to save information and not enough drivers and how to check their availability, so the solution recommended for the current system is to computerize it. After computerized the system, it will be easy to make a report or calculate money for bank and restaurant. All the information can be finding easily because they are saved in one place.

1.4. SCOPE OF THE PROJECT Computerized system will allow a good agreement between all users. Allow to extend the system,

REQUIREMENT ENGINEERING

GROUP PROJECT

1.5. AIMS AND OBJECTIVES

different
The aims and the objectives are to develop a new system that will be based on computer usage. That can help the system to save all the information of customer and can calculate easily all the report by day or week. In which the system can easily make all the transaction needed and do all the report easily. Manage the staff availability and customer order.

2. REQUIREMENTS DEVELOPMENT
2.2 ANALYSIS
2.2.1 CONTEXT DIAGRA M

REQUIREMENT ENGINEERING

GROUP PROJECT

CUSTOMER

User Infromation

MANAGER

Menu Order Details Change / Cancel Order Order Status View Reports Update Price Order Details

RESTAURANT

Order Status Delivery Request Bill Details

MEAL DELIVERY SYSTEM

Delivery Status

Manage Notifications / Finance

Order Details, bill

STAFF

Check In / Check Out

DRIVER

Figure 1.0 context diagram The Figure 1.0 shows how the interactions happen in waiters on wheels meal delivery system. It shows the main entities and their interaction to the system. If the customer wants to place an order, he/she have to give the appropriate information about them and after that the system will provide the menu. Customer can change or cancel the order after placing the order. The order status will be provided to the customer. The restaurant will get the order information from the system with the bill. The restaurant then updates the system with order status. When the order gets ready, the restaurant will request the system to send the driver. The driver will deliver the order to the given address. Driver has to update the system by giving the order status to the system. The staff has to manage order notifications like, late orders, canceled orders and also financial statements. The manager can view all the reports and can update the price of meals.

2.2.2 USE CASE DIAGRAM

REQUIREMENT ENGINEERING
WAITERS ON WHEELS
Cancel Order extends Take Order

GROUP PROJECT

CUSTOMER

Order extends Money Deposit Update Order extends

STAFF

Deposit Slips

Oredered Items

Bill Select Restaurant

extends extends Driver Availability Checking

Deliver Order Create Reports

extends

View Reports

extends DRIVER

extends

MANAGER Report for Work Weekly Reports Daily Reports

Figure 2.0 use case diagram The figure 2.0 shows how the interactions happen between actors in the system. Customer can place order, change order, cancel order and track the order. Staff can take order, deposit money, select restaurant, check driver availability and create reports. Driver can report for work and deliver order. Manager can be able to view all the reports.

2.2.3 DATA DICTIONARY

Data Dictionary
Field Name Data types Size Constraints Description/Purpose Possible Values

REQUIREMENT ENGINEERING Login Username Password varchar varchar 15 15 Primary key Not Null Name of the User User Unique Password

GROUP PROJECT

Athlab adlabs2077

Customer Full Name Age Full Address Contact-No Gender Email_ID varchar int varchar int char varchar 1 20 225 1,1 Primary key Not Null Not Null Not Null Not Null Not Null Unique Customer Identity Age of Customer. Full Address of the Customer Customer Contact Number Gender of the Customer Email_ID of Customer
naomie Naske

35 Bangalore-32 91900187285 Female

a@gmail.com

Online Customer Customer_ID Full Name Full Address Contact-No Gender Email_ID User Name Password varchar varchar varchar int char varchar varchar varchar 1 20 15 15 1,1 20 225 Foreign Key Not Null Not Null Not Null Not Null Not Null Not Null Not Null Unique Customer ID Customer Name Full Address of the Customer Customer Contact Number Gender of the online Customer Email_ID of online Customer Customer user name Customer unique password 345345
Athlab Mohamed

Bangalore-16 9900376287 Male

b@gmail.com

Athlab 5435646

Customer Order Order_ID Customer_ID int varchar 1,1 40 Primary key Not Null Unique Order ID Customer unique ID
564435

adlabs987

REQUIREMENT ENGINEERING Full Name Select Items Address Deliver_date Deliver_Time Employee_ID varchar char varchar varchar varchar int 20 20 225 20 20 Not Null Not Null Not Null Not Null Not Null Foreign Key Customer Name Select Items from the list Full Address of the Customer Customer deliver date Order delivered Time UniqueEmployee Identity

GROUP PROJECT
Athlab Mohamed

Biriyaani Bangalore-16 12/2/2013 12:35 PM 86354

Restaurant Restaurant_ID Name Location Type varchar varchar char varchar 1,1 20 1 20 Foreign Key Not Null Not Null Not Null Unique Restaurant ID Restaurant Name Restaurant location The type of the restaurant 345345
Kebab Majic

Doddannekundi Chinese

Recording Transaction Order_ID Customer_ID Order Details Total Amount Date Time int varchar varchar double varchar varchar 20 20 1,1 40 225 Primary key Not Null Not Null Not Null Not Null Not Null Unique Order ID Customer unique ID Details of the order Total Amount of the order Delivered Date Delivered Time
564435

adlabs987 2CD, 3DVD 300.5 12/2/2013 12:35 PM

Accounts

REQUIREMENT ENGINEERING Order_ID Customer_ID Order Details Total Amount Date Time int varchar varchar double varchar varchar 20 20 1,1 40 225 Primary key Not Null Not Null Not Null Not Null Not Null Unique Order ID Customer unique ID Details of the order Total Amount of the order Transaction Recorded Date Transaction Recorded Time

GROUP PROJECT
564435

adlabs987 Biriyaani/Paneer 300.5 12/2/2013 12:35 PM

Delivery Delivery_ID Order_ID Driver Name Address Deliver_date Deliver_Time int int varchar varchar varchar varchar 1,1 1,1 20 225 20 20 Primary key Not Null Not Null Not Null Not Null Not Null Unique Delivery ID Unique Order ID Customer Name Full Address of the Customer Customer Deliver date Order Deliver Time
564435 564435 Mike Nzuzi

Bangalore-16 12/2/2013 12:35 PM

Manager Manager_ID Full Name D.O.J Salary int varchar varchar double 1,1 20 20 Primary key Not Null Not Null Not Null Unique Manager ID Manager Name Manager Joined date Manager Salary
564435 Tanmay

3/7/2011 60000.4

Driver Manager_ID Full Name D.O.J int varchar varchar 1,1 20 20 Primary key Not Null Not Null Unique Driver ID Driver Name Manager Joined date
564435 Athlab

9/5/2012

REQUIREMENT ENGINEERING Salary double Not Null Manager Salary

GROUP PROJECT 80500.4

Order Employee_ID Order_ID Full Name Contact-No Order Details varchar int varchar int varchar 225 1,1 1,1 20 Foreign Key Not Null Not Null Not Null Not Null Unique Employee ID Unique Order ID Employee Name Driver Contact Number Details of the order 345345
564435 Naoimie

9864346565 Bread, chapati

Reports Report_ID Report Description Report Type Date Time varchar varchar varchar varchar varchar 1,1 20 20 20 20 Foreign Key Not Null Not Null Not Null Not Null Unique Report ID Status of the Stock Type of the report Report generated Date Report generated Time 345345
Daily Order Daily

12/2/2013 12:35 PM

2.4.2.1. INSPECTION

http://sstc-online.org/2008/pdfs/RBV1954.pdf
2.4.2.2. REVIEW CHECKLIST

3. 4. SCHEDULE PLANNING
4.1. GANTT CHART

REQUIREMENT ENGINEERING

GROUP PROJECT

Jul 2013

Aug 2013 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

ID 1 2 3 4 5 6 7 8 9 10 11 12 Support Changes INTRODUCTION

Task Name

Start 7/1/2013 7/4/2013 7/4/2013 7/4/2013 7/4/2013 7/8/2013 7/9/2013 7/9/2013 7/10/2013 7/15/2013 7/17/2013 7/15/2013 7/22/2013 7/22/2013 7/24/2013 7/24/2013 7/29/2013 7/1/2013 7/31/2013 7/31/2013 8/6/2013 8/8/2013 8/14/2013 8/14/2013 8/14/2013 8/14/2013 8/14/2013 8/15/2013 8/16/2013

Finish 7/3/2013 7/4/2013 7/5/2013 7/5/2013 7/5/2013 7/10/2013 7/9/2013 7/11/2013 7/12/2013 7/16/2013 7/18/2013 7/18/2013 7/22/2013 7/24/2013 7/25/2013 7/29/2013 7/30/2013 8/19/2013 7/31/2013 8/2/2013 8/12/2013 8/13/2013 8/16/2013 8/16/2013 8/16/2013 8/19/2013 8/16/2013 8/19/2013 8/19/2013

Duration
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

3d 0d 2d 2d 2d 2d 4h 0d 2d 4h 2d 4h 2d 2d 4d 0d 2d 4h 1d 4h 3d 4h 2d 35d 0d 3d 5d 3d 4h 2d 4h 2d 4h 2d 4h 3d 4h 2d 4h 2d 4h 2d

REQUIREMENTS DEVELOPMENT Elicitation Analysis Specification Validation and Verification REQUIREMENTS MANAGEMENT Requirements Management Planning Requirement Identification Management of Requirements Traceability Requirement Management tool

13 SCHEDULE PLANNING 14 15 16 Gantt Chart Pert Chart Workload Matrix

17 PROGRESS REPORT 18 HARVARD REFERENCING 19 SPECIFICATION DOCUMENT (SRS) 20 21 22 23 24 25 26 27 28 29 Delivery External Interface Requirements Other Nonfunctional Requirements Analysis Model Introduction Overall Description System Features Order Meals Forward Order Generate Report Track driver and Assign Driver

Figure: 3.0 Gantt chart Above figure 3.0 shows the number of days spent to create this project. It shows the approximate time spent on each process of this project and their order of execution. It also defines the connectivity between two processes.

4.2. PERT CHART

REQUIREMENT ENGINEERING

GROUP PROJECT

4.3. WORKLOAD MATRIX NO TASK NAME

TANMAY BLR110813507
1 2 2.1 2.2 2.3 2.4 3 4 5 7 7.1 7.1.2 7.1.3 7.1.4 7.1.5 7.2

GROUP MEMBERS
ATHLAB BLR1108135013 NAOMIE BLR1108135010

INTRODUCTION REQUIREMENT DEVELOPMENT

ELICITATION ANALYSIS SPECIFICATION VALIDATION AND VERIFICATION

100

100 0 0 0 100 0 0

0 100 0 0 0 100 100

0 0 100 100 0 0 0

REQUIREMENT MANAGEMENT SCHEDULE PLANNING PROGRESS REPORT APPENDIX (SRS)

INTRODUCTION OVERALL DESCRIPTION SYSTEM FEATURES
EXTERNAL INTERFACE REQUIREMENTS
OTHER NON FUNCTIOONAL REQUIREMENTS

0 100 100 0 0 0

0 0 0 100 0 100

100 0 0 0 100 0

ANALYSIS MODEL

SIGNATURE:
Figure: 4.0 Workload Matrix The above figure 4.0 shows a table of how the tasks have being assigned to individual members. It defines the percentage of each members contribution to entire project.

5. PROGRESS REPORT
WAITERS ON WHEELS.
MEETING MINUTES

REQUIREMENT ENGINEERING

GROUP PROJECT

Date: Meeting was held on 01/07/ 2013. Time: Meeting was started at 11am. Venue: Meeting was held at BMA Collage library.

Attendees Present: Tanmay (Overall incharge) Athlab Mohamed Naomie

Attendees Absent: Topics that are discussed: This meeting was our first group meeting of this project. So we all decided to discuss about what exactly we are going to do/make in this project. The main objective of this meeting was to know more about the project and to categorize the main topics that we are going to explore. Therefore: We have discussed about the project and categorized the leading areas such as the customers point of view, Drivers point of view, and staffs point of view of the system. We have discussed about individual roles in the project.

Individual roles / tasks: We all agreed that: 1- Tanmay will be the overall in charge of this project and he will be leading and guiding other members through the end of the project. We all agreed and assigned him: a. Requirement Development / Elicitation b. Requirement Management c. Specification Document (SRS) / Overall Description and System Features.

REQUIREMENT ENGINEERING

GROUP PROJECT

2- Athlab Mohamed will do the minutes meeting of this project. We all agreed and assigned him: a. Requirements Development / Analysis b. Schedule Planning c. Progress Report d. Specification Document (SRS) / External Interface Requirements and Analysis Model. 3- Naomie will be doing the following tasks that we all agreed and assigned to her a. Introduction b. Requirements Development / Specification, Validation and Verification c. Specification Document (SRS) / Introduction and Other non-functional Requirements. Difficulties: Everyone was present, so we didnt find any difficulties of explaining the project among us. End Time: 4:15pm

Conclusion of the meeting: In this meeting we have decided that we will be communicating with each other and to clear our doubts and difficulties. And also we have decided that we will be finalizing our documents before 17th of August 2013.

7.1.4 EXTERNAL INTERFACE REQUIREMENTS The External Interface Requirement defines the interaction between the user interface, software interface and the hardware interface of a system. It is to ensure that the external components and the system will communicate properly among them.

7.1.4.1 USER INTERFACE User interface defines the characteristics of the interface design which the user will interact to the system. In this system, the Graphical User Interface (GUI) will be designed in such a way that any kind of user can access to the system easily by giving some basic inputs to the system.

REQUIREMENT ENGINEERING

GROUP PROJECT

Standard icons, fonts, colors, button labels and test fields will be used to make the system user friendly. Some important text fields like date and time will be made mandatory for the user to fill in order to complete the task.

Figure 0.0 Order Form The above figure 0.0 shows the GUI of the order form where user can place the order using the waiters on wheels website. It has dropdown boxes and check lists for the user to choose food items easily from the list.

REQUIREMENT ENGINEERING

GROUP PROJECT

7.1.4.2 SOFTWARE INTERFACE This section will have more detailed information at a later date, however, NovaSoft Laboratories so far will be using databases to hold user login information and the NovaSoft staff information as well. In addition, there will be a Java testing system used to ensure the modules that are loaded will work correctly on the platform. Also, JBuilder Java programming environment will be user to help develop the modules and interfaces that drive the game platform system. Communication between all users and customer support will be through email providers like the Villanova mail system or even Microsoft outlook depending on the users personal emailing capabilities. The Villanova campus web server will be used to publish the NovaSoft Laboratories website and allow all of the game platform components to be available to users.

7.1.4.3 COMMUNICATION INTERFACE This section will be determined at a later date. The section relies on the future work of the Front End and Integration Team and possible the Module and Support Team as well.

7.2 ANALYSIS MODEL 7.2.1 CUSTOMER ORDERING 7.2.2 RESTAURANT PREPARE MEAL 7.2.3 DRIVER DELIVERY THE MEAL 7.2.4 USE CASE DIAGRAM