Software Requirements

Specification

For
Café Management System
Version 1.0 approved

Prepared by: ABC - #002,

Submitted to: Miss

University

14-May-2018

Copyright © 2024
Software Requirements Specification Page ii

Table of Contents
List of Tables...........................................................................................................................................iii
List of Figures..........................................................................................................................................iii
1 Introduction.................................................................................................................................4
1.1 Purpose................................................................................................................................................4
1.2 Product scope......................................................................................................................................4
1.3 Intended audience and document overview........................................................................................4
1.4 References...........................................................................................................................................4
2 Overall description......................................................................................................................4
2.1 Product perspective.............................................................................................................................4
2.2 Product function..................................................................................................................................4
2.3 User class and characteristics..............................................................................................................5
2.4 Operating environment........................................................................................................................5
2.5 Design and implementation constraints..............................................................................................5
2.7 User documentation............................................................................................................................5
2.8 Assumptions and Dependencies..........................................................................................................6
3 External interface requirements................................................................................................6
3.1 User interfaces.....................................................................................................................................6
3.2 Hardware interfaces............................................................................................................................6
3.3 Software interfaces..............................................................................................................................6
3.4 Communication interfaces..................................................................................................................6
4 System Features..........................................................................................................................6
4.1 Functional Requirements....................................................................................................................6
4.1.1 USECASE MODEL OF CAFÉ MANAGEMENT SYSTEM...........................................6
4.1.2 Scenarios of Use Case...........................................................................................................7
4.1.3 Sequence Diagrams.............................................................................................................15
4.1.4 Context Flow Diagram...................................................................................................................24
4.2 Behavior requirements......................................................................................................................24
4.2.1 Use case view:..........................................................................................................................24
5 Other Nonfunctional Requirements.....................................................................................25
5.1 Performance Requirements...............................................................................................................25
5.2 Safety and Security Requirements....................................................................................................25
6 Other Requirements.................................................................................................................26
Software Requirements Specification Page iii

List of Tables

Table 1: Café system login..............................................................................................................7

Table 2: Information of order food..................................................................................................8
Table 3: Information of checking the food order.............................................................................8
Table 4: Information about prepare.................................................................................................8
Table 5: Information about taking the food.....................................................................................9
Table 6: Information about the payment.........................................................................................9
Table 7: Debit/credit information..................................................................................................10
Table 8: Cash information.............................................................................................................10
Table 9: Request for raw material.................................................................................................10
Table 10: Order the raw material...................................................................................................11
Table 11: Supply raw material.......................................................................................................11
Table 12: Information of maintain the system...............................................................................12
Table 13: Take payment................................................................................................................12
Table 14: Generate report..............................................................................................................12
Table 15: Check the report...........................................................................................................13
Table 16: Get discount...................................................................................................................13
Table 17: Information about Membership.....................................................................................13
Table 18: System logout................................................................................................................14
Software Requirements Specification Page iv

List of Figures

Figure 1: Use case Model................................................................................................................7

Figure 2: cafe system login............................................................................................................15
Figure 3: Information of order food...............................................................................................15
Figure 4: Information of checking the food order.........................................................................16
Figure 5: Information of prepare the food................................................................................16
Figure 6: Information about taking the food..................................................................................17
Figure 7: Information about the payment.....................................................................................17
Figure 8: Debit/credit information.................................................................................................18
Figure 9: Cash information............................................................................................................18
Figure 10: Request for raw material..............................................................................................19
Figure 11: Order the raw material.................................................................................................19
Figure 12: Supply raw material.....................................................................................................20
Figure 13: Information of maintain the system.............................................................................20
Figure 14: Take payment...............................................................................................................21
Figure 15: Generate report.............................................................................................................21
Figure 16: Check the report..........................................................................................................22
Figure 17: Get discount.................................................................................................................22
Figure 18: Information about Membership....................................................................................23
Figure 19: System logout...............................................................................................................23
Figure 20: CFD of Cafe Management System..............................................................................24
Software Requirements Specification Page 5

1 Introduction
1.1 Purpose
The purpose of our system is to facilitate the student, faculty members of the university, by providing the
fresh, hygienic and cost efficient food.

1.2 Product scope

The system will help to manage, run and maintain the café management system. We will make such
system that the student and the staff can easily access the food and the owner of the café can easily
evaluate the whole system. Customers can also payment through debit and credit cards. To facilitate the
student and staff by getting discount of several deals that is access through the membership card.

1.3 Intended audience and document overview

This document is intended for different types of reader such as café owner, System designer, system
developer and tester. By reading this document, a reader can learn about what the project is implemented
for and how it will present its basic ideas.

1.4 References

(Usecase diagrams of custom software, 2018)

1. Usecase diagrams of custom software. (2018). Retrieved from Institute of Electrical and
Electronics Engineers: https://www.ieee.org/

2 Overall description

2.1 Product perspective

The café management system helps the café manager to manage the café more effective and efficiently by
computerized billing and inventory control. The system processes transaction and store resulting data.
Report will generate from these data which help the manager to make an appropriate business decisions
for the café. By knowing the number of customer for the particular time interval, manager can manage
properly.

2.2 Product function

Functionality of the product is as follow:

Software Requirements Specification Page 6

1. Customer information.
2. Food order.
3. Take order.
4. Serve order.
5. Payment.
6. Customer review.

2.3 User class and characteristics

Café management system has several active actors and one cooperating system. The customer can order
the food. Receptionist can enter the data or order of the customer in the computer and cook will prepare
the requested food. After that the customer will pay the bill to the cashier. The daily report of the daily
sale will be generated by the cashier.

2.4 Operating environment

Operating system: Minimum Windows XP or window VISTA. Better environment Windows 7, 8, and
8.1,10.

Language: JAVA

It is need to use smartphone to place food order in this system. Which, we are running an Android
Operating System. We will provide the android app to place order with the system. Whole system should
be covered by Wi-Fi connection.

To maintain whole system these requirement can be followed to provide best environment.

3-computers (owner, cashier, manager)

2-3 tablets with android operating system.

2.5 Design and implementation constraints

These are some constraints which costs more for the system. If those constraints can overcome then this
whole system will be perform best. These are follows:

1. IOS App and Windows App.

2. Information flow or data flow can be controlled and more effective.
3. Faster server system such as UNIX server.

2.7 User documentation

It will provide specific guidelines to a user for using the Restaurant management system. More slide
shows will be provided which will represent the whole system function and how it works.

Assumptions and Dependencies:

Software Requirements Specification Page 7

If this system have IOS and Windows app then customers who use such kind of smartphone will be more
benefited. If there are more Tablets for each tables the whole system performance will be better. For more
secure system it is beneficial to use CC camera and TV.

2.8 Assumptions and Dependencies

If this system have IOS and Windows app then customers who use such kind of smartphone will be more
benefited. If there are more Tablets for each tables the whole system performance will be better. For more
secure system it is beneficial to use CC camera and TV.

3 External interface requirements

There are many types of interfaces as such supported by this software system namely;

User interface, software interface and hardware interface.

3.1 User interfaces

The user interface will be implemented using any android smartphone app browser. The interface will be
user friendly. So, that customer can place the food order easily. Customers can also give feedback through
it easily with some demo comment or if they are keen to write their review by own they can do it.

3.2 Hardware interfaces

They shall be logical address of the system in IPv6 format.

3.3 Software interfaces

The system shall communicate with the configurator to identify all the available components to configure
the product.

The system shall communicate with the content manager to get the product specifications.

3.4 Communication interfaces

Communication function required the Internet protocol version 6 and it will follow HTTPS. It will use
FTP for whole system with local server and email communication to device to device of the system.

4 System Features
System features contains different functional requirements of the system
Software Requirements Specification Page 8

4.1 Functional Requirements

Write FR here

4.1.1 USECASE MODEL OF CAFÉ MANAGEMENT SYSTEM

Figure 1: Use case Model

4.1.2 Scenarios of Use Case

Table 1: Café system login

Use case: System Login

Actor: Customer
Software Requirements Specification Page 9

Pre-condition: Customer is an authorized person who must enter in the café system management.

Normal flow: Customer enters the data that is required by the system and then login. The record of
the recent enter customer is stored in database of the café.

Post-condition: Customer successfully enters his data in the café database.

Table 2: Information of order food

Use case: Order food

Actor: Customer

Pre-condition: Customer must request the food item that he wants to ordered.

Normal flow: After login the system, customer selects the food items from the given menu and
then orders the selected food items.

Post-condition: Customer successfully orders the food.

Table 3: Information of checking the food order

Use case: Check order

Actor: Chef

Pre-condition: Chef must check the order that is currently visible on the entire screen of the system.

Normal flow: Chef checks the order that is notified in the notification bar of the order list that is
running on the café system. He checks all the ingredients that is available and then
send the conformation message.

Post-condition: Chef successfully checking the order details.

Table 4: Information about prepare

Software Requirements Specification Page 10

Use case: Prepare food

Actor: Chef

Pre-condition: Chef must prepare the food that customer order.

Normal flow: After sending the conformation message and give the delivered time to the customer
that he ordered. Then chef starts preparing the food.

Post-condition: Chef successfully cook the food at the given time duration.

Table 5: Information about taking the food

Use case: Take food

Actor: Customer

Pre-condition: After completing the time period given by the chef, customer takes his order food.

Normal flow: Customer go to the counter, received his food by checking the order details.

Post-condition: Customer successfully took order from the counter.

Table 6: Information about the payment

Use case: Payment

Actor: Customer, Administration

Pre-condition: Customer must got the receipt and paid it.

Administration must paid supplier for supplying the raw material related for the café
kitchen.

Normal flow: After ordering the food, customer got the receipt from the cashier and checks the
mood of payment; he wants to pay and then paid the bill.
Software Requirements Specification Page 11

Administration check all the list that the supplier delivered, admin paid for this.

Supplier gets the payment from the admin for delivering the raw material.

Post-condition: Customer, administration successfully pays the bill for the desired parties.

Cashier, supplier successfully received the payment.

Table 7: Debit/credit information

Use case: Debit/credit

Actor: Customer, administration

Pre-condition: Customer and admin must check the mood of payment either it is debit/credit.

Normal flow: After receiving the receipt, both parties pay the bill via debit/credit.

Post-condition: Both are successfully pay the bill through debit/credit.

Table 8: Cash information

Use case: Cash

Actor: Customer, administration

Pre-condition: Customer and admin must check the mood of payment either it is cash.

Normal flow: After receiving the receipt, both parties pay the bill by cash.

Post-condition: Both are successfully pay the bill through cash.

Table 9: Request for raw material

Use case: Request for raw material

Actor: Chef
Software Requirements Specification Page 12

Pre-condition: Chef must create and provide the list of raw material that is required in the cooking
to the administration.

Normal flow: Chef check all the ingredients in the stock that is available for preparing the food, all
the missing and less product list is created and send it to the administration.

Post-condition: Chef successfully created the list of raw material.

Table 10: Order the raw material

Use case: Order raw material

Actor: Administration

Pre-condition: Admin must order the list of raw material to the supplier.

Normal flow: Admin check out the list of raw material that chef’s created of the missing and less
products of the entire list, admin send the list to the supplier and give the date for
delivered the products.

Post-condition: Admin successfully order the raw material.

Table 11: Supply raw material

Use case: Supply the raw material

Actor: Supplier

Pre-condition: Must be supplied the raw material.

Normal flow: After receiving the list of raw material and checking the delivery date of the list.
Supplier start gathered all the items that is mentioned in the list, pack all the items
and then delivered it with receipt.

Post-condition: Successfully supply all the raw material to the administration of the café.
Software Requirements Specification Page 13

Table 12: Information of maintain the system

Use case: Maintain the system

Actor: Administration

Pre-condition: Admin must maintain the café management system.

Normal flow: Admin look after the system of the café, he added, update and delete the records
from the database of the café management system according to their need.

Post-condition: Admin successfully maintaining the café system.

Table 13: Take payment

Use case: Take payment

Actor: Cashier

Pre-condition: Cashier must take the payment from the customers.

Normal flow: Cashier give the receipt to the customer and then take the payment from the
customer and then enter the record in the database of the café management system.

Post-condition: Cashier successfully takes the payment from the customers.

Table 14: Generate report

Use case: Generate report

Actor: Cashier

Pre-condition: Cashier must generate the report of daily sale.

Software Requirements Specification Page 14

Normal flow: After entered the daily record of sale in the system, he generate the daily report at the
end of each day.

Post-condition: Cashier successfully generates the report of daily sale.

Table 15: Check the report

Use case: Check the report

Actor: Administration

Pre-condition: Administration must check the report that is generated by the cashier on daily basis.

Normal flow: After generated the report, cashier send the report to the admin, then admin check it.

Post-condition: Administration successfully checks the report.

Table 16: Get discount

Use case: Get discount

Actor: Student

Pre-condition: Student must get discount by ordering some specific food.

Normal flow: Customer is classified into groups, so the student is one who get the discount by
fulfill some rules of café on some specific food that he ordered.

Post-condition: Student successfully get discount.

Table 17: Information about Membership

Use case: Membership

Actor: Faculty
Software Requirements Specification Page 15

Pre-condition: Faculty must get membership card from café.

Normal flow: Customer is another group is faculty, café facilitate faculty members to become a
part of café and get discount on different items that is available in café and enjoy it.
So, faculty member get the membership card.

Post-condition: Faculty successfully get membership card.

Table 18: System logout

Use case: System logout

Actor: Customer

Pre-condition: Customers are an authorized person who must exist in the system.

Normal flow: After getting the required items, customer leaves the café system and logout his
current account.

Post-condition: Customer successfully logout the system.

Software Requirements Specification Page 16

4.1.3 Sequence Diagrams

Sequence diagrams of café management system are as follows:

Figure 2: cafe system login

Figure 3: Information of order food

Software Requirements Specification Page 17

Figure 4: Information of checking the food order

Figure 5: Information of prepare the food

Software Requirements Specification Page 18

Figure 6: Information about taking the food

Figure 7: Information about the payment

Software Requirements Specification Page 19

Figure 8: Debit/credit information

Figure 9: Cash information

Software Requirements Specification Page 20

Figure 10: Request for raw material

Figure 11: Order the raw material

Software Requirements Specification Page 21

Figure 12: Supply raw material

Figure 13: Information of maintain the system

Software Requirements Specification Page 22

Figure 14: Take payment

Figure 15: Generate report

Software Requirements Specification Page 23

Figure 16: Check the report

Figure 17: Get discount

Software Requirements Specification Page 24

Figure 18: Information about Membership

Figure 19: System logout

Software Requirements Specification Page 25

4.1.4 Context Flow Diagram

Figure 20: CFD of Cafe Management System

4.1.5 Activity Diagram

Only one of entire system here

4.1.6 Class Diagram

Only one of entire system here

4.2 Behavior requirements

4.2.1 Use case view:

The use case for each of the actor is described below:

Customer Use Case:

Use case: Order Food.

Description:
Software Requirements Specification Page 26

The customer can order food and see their payment receipt and pay.

Chef Use Case:

Use Case: Prepare food.

Description:

The chef can see the orders of customers and checks whether this order can be taken or not and then
confirms the order and starts preparing the food. When the food is ready the chef alerts the waiter to
server the food. He can also edit what ingredients are available and what ingredients are demanded.

Cashier Use Case:

Use case: Take Payment

Description

The cashier can only take payment from the customer and save it into the system database with respect to
the food item and also check if the customer is eligible for discount. If yes then take the payment
accordingly.

Admin Use Case:

Use Case: Maintain System

Description

The admin has full access to the system. He maintains the whole system to ensure better and secure
service and solves any error appeared in the system.

5 Non-functional Requirements

5.1 Performance Requirements

 The product will be based on local server.

 The product will take initial load time.
 The performance will depend upon hardware components.
 Payment system will be fully secured through POS system.
 Different database for employee.

5.2 Safety and Security Requirements

 The source code developed for this system shall be maintained in configuration
management tool.
 The whole system is secured. Only admin can access all the data.
 The system will use HTTPS; because of this protocol this is more secure.
Software Requirements Specification Page 27

 The system will use secured POS system.

6 Other Requirements
Licensing Requirements

Not applicable.

Legal, Copyright and Other Notices

All rights reserved by our team.

Applicable Standards

It should be as per the industry standard