0% found this document useful (0 votes)
159 views

Sample Requirements Doc 1

The document outlines requirements for an online restaurant information management system. It includes 4 types of users - admin, cashier, receptionist, and customer. It describes functional requirements like managing the menu, orders, and reservations. Non-functional requirements include security, interfaces, hardware needs, and compatibility. The system will require a database to store information and software like Chrome and Firefox to access it. Hardware requirements include a minimum of 100GB hard disk, 1.5GB RAM, and an Intel i3 or higher processor. System design documents like use case diagrams and EER diagrams will be created to guide implementation.

Uploaded by

Ahwera Atensa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
159 views

Sample Requirements Doc 1

The document outlines requirements for an online restaurant information management system. It includes 4 types of users - admin, cashier, receptionist, and customer. It describes functional requirements like managing the menu, orders, and reservations. Non-functional requirements include security, interfaces, hardware needs, and compatibility. The system will require a database to store information and software like Chrome and Firefox to access it. Hardware requirements include a minimum of 100GB hard disk, 1.5GB RAM, and an Intel i3 or higher processor. System design documents like use case diagrams and EER diagrams will be created to guide implementation.

Uploaded by

Ahwera Atensa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 10

ONLINE RESTAURANT INFORMATION MANAGEMENT SYSTEM

REQUIREMENTS DOCUMENT

By

August, 2021
Table of Contents
Introduction.......................................................................................................................................2

1.0 User Characteristics.....................................................................................................................2

(a). Admin.........................................................................................................................................2

(b). Cashier........................................................................................................................................3

(c). Receptionist.................................................................................................................................3

(d). Customer.....................................................................................................................................3

2.1 Requirements Specifications........................................................................................................4

2.1.1 User Requirements....................................................................................................................4

2.1.2 Functional Requirements..........................................................................................................4

2.1.3 Non-Functional Requirements..................................................................................................4

2.1.3.1 Security Requirements...........................................................................................................4

2.1.3.2 User Interface Requirements..................................................................................................4

2.1.3.3 Hardware Constraints............................................................................................................5

2.1.3.4 Updatability...........................................................................................................................5

2.1.3.5 Compatibility.........................................................................................................................5

2.1.3.6 Storage...................................................................................................................................5

2.1.3.7 Usability and Dependability...................................................................................................5

2.1.3.8 Performance with Database...................................................................................................5

2.1.4 System Requirements...............................................................................................................5

2.1.4.1 Software Requirements..........................................................................................................5

2.1.4.2 Hardware Requirements.........................................................................................................6

3.0 System Design.............................................................................................................................6

3.1 Use Case Diagram.......................................................................................................................6

3.2 Flow Chart Diagram....................................................................................................................7

3.3 Enhanced Entity Relationship Diagram.......................................................................................8


Introduction
In this requirements document, the researcher will detail various requirements including
functional, non-functional, system, hardware, and software requirements, user scope, use
case diagram, flow chart diagram and enhanced entity relationship diagram.

1.0 User Characteristics


The system users shall provide correct credentials to ensure authorised and authenticated
users gain access to the system and perform the correct operations.

(a). Admin
1. Login to the system
2. Add menu
3. Add menu categories
4. Add compliments
5. Add accommodation
6. Add tables
7. Add staff
8. View staff
9. Edit staff
10. Delete or Disable staff status
11. View menu
12. Edit menu
13. Activate or deactivate menu status
14. Add services
15. Manage services
16. Manage customer inquiries
17. Manage sales
18. View tables
19. Edit table
20. Activate or deactivate table status
21. View reports
22. Generate reports
23. Print reports
24. Logout
(b). Cashier
1. Login to the system
2. View orders
3. View reservations
4. View payments
5. Print receipts
6. Logout

(c). Receptionist
1. Login to the system
2. View orders
3. View reservations
4. Follow up orders and reservations
5. View tables
6. Activate or deactivate table status
7. View rooms
8. Activate or Deactivate room status
9. Manage and follow up arrivals and departures
10. Generate reports
11. Print reports
12. Logout

(d). Customer
1. Access the website
2. View services
3. View daily menu
4. Places an order
5. Makes reservation
6. Make an inquiry
2.1 Requirements Specifications
The online restaurant information management system shall have various requirements
specifications ranging from user requirements, functional, non-functional, hardware and
software requirements.

2.1.1 User Requirements


1. The users shall have stable internet connection to access the system services.
2. The users shall have a computer or a smart phone to use the system services.
3. The users should have some computer knowledge about internet/website navigation.
4. The customer shall either use MTN or Airtel network for mobile money payments.

2.1.2 Functional Requirements


1. The system shall allow the administrator to add, edit, activate or deactivate the menu.
2. The system shall allow the administrator to add, edit, activate or deactivate tables.
3. The system shall allow the administrator to manage orders.
4. The system shall allow the administrator to manage reservations.
5. The system shall allow the administrator to generate and print reports.
6. The system shall allow the administrator to search a specific record.
7. The system shall enable the administrator to archive information electronically.
8. The system shall allow the customer to make an order.
9. The system shall allow the customer to make a reservation.
10. The system shall automatically send payment confirmation email to the customer
upon successful reservation of the required service.

2.1.3 Non-Functional Requirements


In this section, the system shall have or conform to the following specifications to fully
function.

2.1.3.1 Security Requirements


Unauthorized users shall not gain access to the system and perform any operation or
modification about the stored information. So security is provided.

2.1.3.2 User Interface Requirements


The online restaurant information management system shall be developed in a way that
instructions are given clearly to navigate through the System. Warnings and error messages
are provided throughout the system which guides the users as they interact with the system.
2.1.3.3 Hardware Constraints
The online restaurant information management system shall require a database in order to
store the information. The database should have backup capabilities for data recovery in case
of any failure.

2.1.3.4 Updatability
The online restaurant information management system shall be able to accommodate updates
and scalability as per the user requirements.

2.1.3.5 Compatibility
The online restaurant information management system shall be compatible with any
advanced web browser and operating system.

2.1.3.6 Storage
The online restaurant information management system shall store all the restaurant
information for future use, decision making and auditing.

2.1.3.7 Usability and Dependability


The online restaurant information management system shall be usable since it enables its
stakeholders to meet their specific requirements.

2.1.3.8 Performance with Database


The online restaurant information management system shall perform well with the database
for easy data creation, processing, storage, and retrieval.

2.1.4 System Requirements


This section describes the hardware components and software requirements needed for
effective and efficient running of the online restaurant information management system.

2.1.4.1 Software Requirements


REQUIREMENT SPECIFICATION
Google Chrome 4.3 and higher
Mozilla Firefox 4.5.1 and later
Operating system Windows 8 and higher
Document readers Adobe reader, PDF reader, MS Excel
2.1.4.2 Hardware Requirements
REQUIREMENTS SPECIFICATION
Hard Disk Minimum 100 GB
RAM Minimum 1.5 GB
Processor Intel core i3, i5 and higher with 1.9 GHZ speed
Keyboard/Touch screen ISO standard
Mouse/Touch Pad ISO standard
Printer Inkjet, LaserJet or any

3.0 System Design


After interpretation and analysis of the collected data, process models of the collected data
shall be designed and developed to guide the researcher in the implementation stage of this
project.

The tools, which shall be employed during this methodology stage include flow chart
diagram, use case diagram, and Enhanced Entity Relationship Diagrams (EERDs).

3.1 Use Case Diagram


This figure below shows various user roles and their scope of use with the online restaurant
information management system.
3.2 Flow Chart Diagram
This figure below shows the flow chart of the online restaurant information management
system.

Start

Login

If

Perform task Perform task

Logout

End
3.3 Enhanced Entity Relationship Diagram
This diagram below shows the database tables, their attributes, constraints, values, and
relationships.

You might also like