Cafeteria Ordering System SRS, Study Guides, Projects, Research of Food Science and Technology

Download Cafeteria Ordering System SRS and more Study Guides, Projects, Research Food Science and Technology in PDF only on Docsity!

Software Requirements

Specification

for

Cafeteria Ordering System,

Release 1.

Version 1.0 approved

Prepared by Ahsan Altaf

FURC

January 23, 2017

Table of Contents

Revision History Name Date Reason For Changes Version Software Requirements Specification for Cafeteria Ordering

• 1 Revision History.......................................................................................................
  • 1.1 Purpose
  • 1.2 Document Conventions..........................................................................................................
  • 1.3 Intended Audience and Reading Suggestions........................................................................
  • 1.4 Project Scope
  • 1.5 References..............................................................................................................................
  • 1.6 Product Perspective................................................................................................................
  • 1.7 Product Functions..................................................................................................................
  • 1.8 User Classes and Characteristics...........................................................................................
  • 1.9 Operating Environment..........................................................................................................
  • 1.10 Design and Implementation Constraints................................................................................
  • 1.11 User Documentation..............................................................................................................
  • 1.12 Assumptions and Dependencies............................................................................................
  • 1.13 User Interfaces.......................................................................................................................
  • 1.14 Hardware Interfaces...............................................................................................................
  • 1.15 Software Interfaces................................................................................................................
  • 1.16 Communications Interfaces...................................................................................................
  • 1.17 Order Meals...........................................................................................................................
• 1.17.
  • 1.18 Create, View, Modify, and Delete Meal Subscriptions..........................................................
  • 1.19 Register for Meal Payment Options.......................................................................................
  • 1.20 Request Meal Delivery..........................................................................................................
  • 1.21 Create, View, Modify, and Delete Cafeteria Menus..............................................................
  • 1.22 Use-Case Diagram for COS...................................................................................................
  • 1.23 Data Flow Diagram
    • 1.23.1 Level-0......................................................................................................................
    • 1.23.2 Level-1......................................................................................................................
  • 1.24 Class Diagram........................................................................................................................
  • 1.25 Performance Requirements....................................................................................................
  • 1.26 Safety Requirements..............................................................................................................
  • 1.27 Security Requirements...........................................................................................................
  • 1.28 Software Quality Attributes...................................................................................................
  • 1.29 Business Rules.......................................................................................................................
• 2 Appendix A: Data Dictionary and Data Model.....................................................
• 3 -------------------------..................................................................................................
• 4 Appendix B: Analysis Models.................................................................................
• 5 ----------------------------..............................................................................................
• 6 Appendix C: To Be Determined List......................................................................
• 7 -------------------------------..........................................................................................
• Page System

1. Introduction

1.1. Purpose

This SRS describes the software functional and nonfunctional requirements for release 1.0 of the Cafeteria Ordering System (COS) of Foundation University Rawalpindi Campus. Particularly this SRS describes the Part of a System which may have other sub-systems as well.

1.2. Document Conventions

FURC_Foundation University Rawalpindi Campus

COS_Cafeteria Ordering System SRS_Software Requirement Specification GUI_Graphical User Interface ERD_Entity Relationship Diagram DFD_Data Flow Diagram

1.3. Intended Audience and Reading Suggestions

This document is intended to be used by the members of the project team that will implement and verify the correct functioning of the system, Users including Software Engineers & non-Software Engineers and Documentation Writer as well.

1.4. Project Scope

The Cafeteria Ordering System will permit a Student to select desired meal from the Cafeteria

Screen in which every item included present in a Café. Receipt will be generated automatically having a unique number by which Student wait for their turn to receive packet from a serving person. The thing which is excluded is Payment system which you have to manually submit to a person (receptionist) whose concern to confirm packet with payments and stamp the Receipt. Goal of this System is to provide easy way to select desire food item without having trouble. It is more Discipline way to handle Students aggression.

1.5. References

1. https://en.wikipedia.org/wiki/Automated_
2. https://en.wikipedia.org/wiki/Automated_restaurant#Technology
3. https://en.wikipedia.org/wiki/Cafeteria
4. http://www.mealsplus.com/components
5. https://campuscafesoftware.com/products/
6. (^) https://www.shopify.com/pos/retail/cafe
7. Overall Description

1.6. Product Perspective

The Cafeteria Ordering System is a new system that replaces the current manual process for placing

order and picking up packets in the Process Impact cafeteria. The context diagram in Figure 1 illustrates the external entities and system interfaces for release 1.0.

1.7. Product Functions

COS (Cafeteria Ordering System) will have Functions like selecting a meal, deselecting Item, selecting quantity, calculating price & confirmation of order.

1.8. User Classes and Characteristics

Serving Person A Serving Person is a Process Impact employee at the FURC, who wishes to deliver the ordered meals from the cafeteria’s Kitchen to Customer. There may be more than 1 potential Person who will serve.

Chef Chef can be more than 1 person who will receive the Order from the System and

Prepare the Food according to the System information passes to Chef. His work is just to make sure that Meal is ready with in a Time expected.

Receptionist The Receptionist is a cafeteria employee, perhaps the cafeteria manager, who is responsible for establishing and maintaining daily menus of the food items available from the cafeteria and the times of day that each item is available. Some menu items may not be available for delivery. The Receptionist will also receive payments and Confirm the Package Delivery to a student by making a Stamp on a receipt.

Student As the Student is majority for the system has been Built. Student will simply place

his desire meal given in menu on screen and After Submit ion he will receive his package by a serving person and payment will be handover to the Receptionist before enjoying the Meal.

1.9. Operating Environment

It’s neither a Functional requirement nor non-functional.

OE-1: The Cafeteria Ordering System shall operate with like following Windows: Windows 2000, Windows XP server pack 3, Windows 7, Windows 8, 8.1 & Windows 10 as well.(32-bit & 64-bit both). OE-2: The Cafeteria Ordering System shall operate well on Linux and Mac systems. OE-3: The Cafeteria Ordering System should be user friendly.

1.10. Design and Implementation Constraints

CO-1: The system’s design, code, and maintenance documentation shall conform to the standards of our own Campus. CO-2: The system shall use the latest standard Oracle database system. CO-3: All code shall conform to the code standard respectively.

1.11. User Documentation

UD-1: The system shall provide a very simple interface which should be user friendly and easy for them to understand and operate better.

4.1.2 Stimulus/Response Sequences Stimulus: Student requests to place an order for one or more meals. Response: System will ask to confirm the order. Stimulus: Student requests to change a meal order. Response: If status is “Accepted,” system allows user to edit a previous meal order. Stimulus: Student requests to cancel a meal order. Response: If status is “Accepted, “system cancels a meal order. Sequence Diagram

---

4.1.3 Functional Requirements

Order.Place: The system shall let a Student to select & place an order for one or more meals. Order.Menu.Date: The system shall display a menu for the specified date. Order.Menu.Available: The menu for the current date shall display only those food items for which at least one unit is available in the cafeteria’s inventory. Order.Units.Food: The system shall allow the Student to indicate the number of units of each menu item that he wishes to order. Order.Units.Multiple: The system shall permit the user to order multiple identical meals, up to the fewest available units of any menu item in the order. Order.Units.TooMany: If the Student orders more units of a menu item than are presently in the cafeteria’s inventory, the system shall inform the Student of the maximum number of units of that food item that he can order. Order.Units.Change: If the available inventory cannot fulfill the number of units ordered, the Student may change the number of units ordered, change the number of identical meals being ordered, or cancel the meal order. Order.Confirm.Display: When the Student indicates that he does not wish to order any more food items, the system shall display the food items ordered, the individual food item prices, and the payment amount, calculated. Order.Confirm.Prompt:The system shall prompt the Student to confirm the meal order. Order.Confirm.Not: If the Student does not confirm the meal order, the Student may either edit or cancel the order. Order.Confirm.More: The system shall let the Student order additional meals after 1 meal deal.

Order.Reciept.Pickup: When the Student indicates that he is done placing orders, the system shall give him a receipt having order number. Order.Pay.Pickup: When the meal is to be picked up in the cafeteria, Student must pay cash at the time of pickup. Order.Pay.Details: The system shall display the food items ordered, payment amount, and delivery instructions. Order.Pay.Confirm: The Student shall either confirm the order, request to edit the order, or request to cancel the order. Order.Order.Confirm.OK: The system shall display a message confirming acceptance of the order. Order.Order.Confirm.NO: If the Confirm request is rejected, the system shall display a message with the reason for the rejection. The Student shall either cancel the order, or change the meal and request to pick up the order at the cafeteria. Order.Done.Times: Update the remaining available delivery times for the date of this order. Order.Done: Send an e-mail message to the Receptionist with the meal order and meal payment information. Order.Done.Cafeteria: Send an e-mail message to the Cafeteria Staff with the meal order information. Order.Done.Failure: If any step of Order.Done fails, the system shall roll back the current process and notify the user that the order was unsuccessful, along with the reason for failure.

4.2. Create, View, Modify, and Delete Meal Subscriptions

[details not provided in this example]

4.3. Register for Meal Payment Options

[details not provided in this example]

4.4. Request Meal Delivery

[details not provided in this example]

4.5. Create, View, Modify, and Delete Cafeteria Menus

[details not provided in this example]

4.6. Use-Case Diagram for COS

---

Appendix B: Analysis Models

---

Appendix C: To Be Determined List

---