Scribd
Upload
34 views5 pages

Milestone2 V4

This document contains the requirements specification for the Grab-n-Go Campus mobile application. It outlines the functional and non-functional requirements, including requirements for customers and restaurant staff to login, view menus, place and manage orders. Non-functional requirements address usability, performance, size, dependability, environmental impact, and adherence to regulations and ethics. A use case diagram is also included. The document was submitted on October 17, 2023 by students Manal Mkamel, Mohamed Amine Ghafil, and Othmane Chadi for their Software Engineering 1 milestone 2, supervised by Dr. Bouchaib Falah.

Uploaded by

Othmane Chadi
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
34 views5 pages

Milestone2 V4

This document contains the requirements specification for the Grab-n-Go Campus mobile application. It outlines the functional and non-functional requirements, including requirements for customers and restaurant staff to login, view menus, place and manage orders. Non-functional requirements address usability, performance, size, dependability, environmental impact, and adherence to regulations and ethics. A use case diagram is also included. The document was submitted on October 17, 2023 by students Manal Mkamel, Mohamed Amine Ghafil, and Othmane Chadi for their Software Engineering 1 milestone 2, supervised by Dr. Bouchaib Falah.

Uploaded by

Othmane Chadi
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/ 5

Fall 2023

Software Engineering 1
CSC3324 – Section 03

Milestone 2

Students’ Name: Manal Mkamel-


Mohamed Amine Ghafil – Othmane
Chadi

Supervised by: Dr. Bouchaib Falah

Submission Date:10/17/2023
1. d

2. Requirement Specification

2.1. Functional Requirements

2.1.1. Customer

2.1.1.1. Customer shall access the Login page.


2.1.1.2. Customer shall sign in their Grab-n-Go Campus account.
2.1.1.3. Customer shall register for a new account if they do not have an existing one.
2.1.1.4. Customer shall access one of the restaurants displayed after Sign In, which are
Cossa, El Piccollo, and ProxyRest.
2.1.1.5. Customer should go back to the previous page.
2.1.1.6. Customer should browse the restaurants’ food items.
2.1.1.7. Customer should add an item to their cart from the menu of the restaurant.
2.1.1.8. Customer should remove items from their cart.
2.1.1.9. Customer shall confirm the order from his cart.
2.1.1.10. Customer should access the history of their purchases.
2.1.1.11. Customer should access contact support.
2.1.1.12. Customer should exit the application.
2.1.1.13. Customer should sign out from their account.

2.1.2. Restaurant Staff

2.1.2.1. Staff shall access the Login page.


2.1.2.2. Staff shall sign in their Grab-n-Go Campus account.
2.1.2.3. Staff shall register for a new account if they do not have an existing one.
2.1.2.4. Staff shall confirm or deny an order.
2.1.2.5. Staff should edit the menu items’ availability.
2.1.2.6. Staff shall notify the customer when their food is available for pick up.
2.1.2.7. Staff should access contact support.
2.1.2.8. Staff should exit the application.
2.1.2.9. Staff should sign out from their account.

2.2. Non-Functional Requirements

2.2.1. Product Requirements

2.2.1.1. Usability Requirements


2.2.1.1.1. The application shall be quick and easy to use and navigate.
2.2.1.1.2. The application shall have a simple user interface.

2.2.1.2. Efficiency Requirements


2.2.1.2.1. Performance Requirements
2.2.1.2.1.1. The application shall take less than 2.5 seconds to react.
2.2.1.2.1.2. The application shall upload the order’s request in 10 seconds
under good connection conditions.

2.2.1.2.2. Space Requirements


2.2.1.2.2.1. The application shall not exceed 100 Megabytes in total size.

2.2.1.3. Dependability Requirements


2.2.1.3.1. The application shall be easily fixable in the case of a system
emergency.
2.2.1.3.2. The application shall deliver its services as promised to its users.

2.2.2. Organizational Requirements


2.2.2.1. Environmental Requirements
2.2.2.1.1. The application shall reduce the paper waste used in receipts.

2.2.2.2. Operational Requirements


2.2.2.2.1. The application shall run on the latest version of Android.
2.2.2.3. Development Requirements
2.2.2.3.1. The application shall be delivered in increments based on priority.

2.2.3. External Requirements


2.2.3.1. Regulatory Requirements
2.2.3.1.1. The application shall adhere to Moroccan regulations and to AUI
rules.
2.2.3.1.2. The application shall follow the specifications given by the client.

2.2.3.2. Ethical Requirements


2.2.3.2.1. The application shall adhere to the ACM or IEEE code of ethics.

2.2.3.3. Legislative Requirements


2.2.3.3.1. Accounting Requirements
2.2.3.3.1.1. The application shall not go over the allocated budget.

2.2.3.3.2. Safety Requirements


2.2.3.3.2.1. The application shall not cause harm to the user’s device or the
user.

2.2.3.3.3. Security Requirements


2.2.3.3.3.1. The application shall keep the user’s information secure.
2.2.3.3.3.2. The application shall not be vulnerable to outside attacks.

2.3. Use Case Diagram

You might also like