Chapter 2

Requirement Specification and Analysis

Requirement Specification

2.1. Functional Requirements

Table 2.1: Functional Requirements

S. No. Functional Requirement Type Status

1 Admin can login to system Core New
2 Admin can perform CRUD Core New
operations for employees.
3 Admin can perform CRUD Core New
operations for food categories.
4 Admin can perform CRUD Core New
operations for deals.
5 Admin can perform CRUD Core New
operations for menu.
6 Customer can login to system Core New
7 Customer can signup to system Core New
8 Customer can see all categories of Core New
food.
9 Customer can see the menu. Core New
10 Customer can see all the deals Core New
available
11 Customer can place order from Core New
deals and menu.
12 Customer can cancel order. Core New
13 Customer can see location of rider. Core New
14 Employee can login to system. Core New
15 Employee can assign order to riders. Core New
16 Riders will get location of customer Core New
through map.
17 Rider can tell the status of ride to Core New
restaurant and customer.
18 System will generate total amount Core New
that user had to pay.
19 System will give location of Core New
customer to restaurant
20 System will give shortest path to
rider.
2.2. Non-Functional Requirements

Table 2.2: Functional and Non-Functional Requirement

S. No. Non Functional Requirements Category

1

3…
2.3. Selected Functional Requirements
Given below is a list of selected functional requirements of Eventified.

Table 2.3: Selected Functional Requirements

S. No. Functional Requirement Type

1
2
3
4
5
6
7
8
9