1. Purpose: Thisdocument presents an explanation of the features, objectives, application and userinterface of “UOG Smart Cafe”. It will describe that how under which conditionsthe system must operate. This SRS describes the software functional andnonfunctional requirements of the “UOG smart café”. This document is intendedto be used by the members of the project team that will implement and verifythe correct functioning of the system. All requirements specified here are highpriority requirements.
This UOG smart cafeis the system where the students/ workers/ faculty will order their food and receive their orders fromcafeteria without any delay, as they can directly go and collect what theyordered without waiting any time. The purpose of the system is to develop asimple Canteen Automation System and implement it by android mobile applicationand It will be applicable in the boundaries of UOG under certainconditions.2.1.2.Intended Audience and Reading SuggestionsThisdocument is intended for many kinds of readers. These readers are systemdevelopers, system designers, system tester and cafeteria owner.
By readingthis document they will get knowledge about the system and learn about what theproject is implemented for. So, if the reader will read this document he willget the clear idea about the system, what are the functionalities and features ofthe system.2.
1.3. Project Scope andProduct FeaturesThe system will runand manage the cafeteria business systematically.
In UOG smart café system, wewill provide a mobile application that can be used by the users to place theirorder. So, the owner of the cafeteria can evaluate the system and maintain propercheck and balance. This will lead the owner to hire less no.
of waiters andcreate an opportunity to provide a better place for customers and appoint morechefs. The customers can also make payment through their accounts which they openedin cafeteria. Users can see current deals and offers of the café. All theinformation of expenditures and profits of a working day will save in the system.The information of cafeteria employees saved in the system and cafeteria admin canaccess them.2.
1.4. ReferencesThe references are as follow: Writing a Software Requirements Specification Documentwww.
onedesk.com/writing-a-software-requirements-specification-document/ Zambito, Christine. Process Impact Business Rules Catalog,www.processimpact.com/corporate/policies/PI_business_rules.
doc SRS example documentshttps://www.cse.msu.edu/~cse435/Handouts/SRSExample-webapp.doc2.2. Overall Description2.2.
1. Product PerspectiveThe “UOG SmartCafé” is a new system that replaces the current manual and telephone processesfor ordering and picking up lunches in the cafeteria. The context diagram inFigure 1 illustrates the external entities and system interfaces. The system isexpected to evolve over several releases, ultimately connecting to the Internetordering services for several types of user’s and to credit charges onlineservices. 2.2.2.
Product FunctionsThe functions of this system will perform in this order. User Registration User Login Order Placement via application Payment through account Delivery at Spot for Faculty Sale and Purchase Reports Feedback for each individual Product2.2.3.
Operating EnvironmentThe Operatingenvironments are as follow: OE-1: Operating System: window 7 or above versionsfor admin web application.OE-2: Operating System: android jellybean 4.2 orabove versions for users of the systemOE-3: TheUOG Smart Cafe shall operate with the following Web browsers: MicrosoftInternet Explorer versions 8.0 and above, Google chrome version 50.
0 or above,Firefox 50.0 or above and Safari version 9.0 or above.OE-4: 3computers. (One for owner, one forcashier, one for manager) OE-5: TheUOG smart café shall permit user access from the corporate Intranet and, if auser is authorized for outside access through the corporate firewall, from anInternet connection.
2.2.4. Design and Implementation Constraints CO-1: Thesystem’s design, code, and maintenance documentation shall conform to the Intranet Development Standard.CO-2: Thesystem shall use the current corporate standard MySQL database.
CO-3: AllHTML code shall conform to the HTML 5 standard.CO-4: Allscripts shall be written in PHP.2.2.5. User DocumentationUD-1: Thesystem shall provide an online hierarchical help system in HTML that describesand illustrates all system functions.UD-2: Thefirst time a new user accesses the system and on user demand thereafter, thesystem shall provide an online tutorial to allow users to practice orderingmeals using a static tutorial menu. 2.
2.6. Assumptions and DependenciesAS-1: It isassumed that each user has proper working internet connection in order to userthis system.AS-1: Thecafeteria is open for breakfast and lunch from (8:30Am-4:30PM) every universityworking day in which users are expected to be on site.DE-1: Theoperation of the UOG Smart Cafe depends on changes being made in the CafeteriaInventory System to update the availability of food items as UOG smart cafeorders are accepted.
2.3. External Interface Requirements2.3.1. UserInterfacesUI-1: The UOG Smart Café screen displays shallconform to the Internet Application UserInterface Standard.UI-2: The system shall provide a helplink/activity from each HTML page/android activities to explain how to use thatpage.UI-3: The android application shall permitcomplete navigation and food item selection using the touch screen and embeddedkeyboard.
Hardware InterfacesNo hardware interfaces have been identified.2.3.3. Software InterfacesSI-1: CafeteriaInventory managementSI-1.1: The COS shall transmit the quantities offood items ordered to the Cafeteria Inventory System through a programmaticinterface.SI-1.
2: The UOG smart café system shall poll theCafeteria Inventory System to determine whether a requested food item isavailable. SI-2: Accounts management The COS shall communicate withthe Payroll System through a programmatic interface for the followingoperations:SI-2.1: To submit a payment request for apurchased meal.SI-2.2: To view previous purchased records.SI-2.
3: To deduct all or part of paid charges ifa user does not take his/her order.SI-2.4: To reverse all or part of a previouscharge because a user rejected a meal or wasn’t satisfied with it, or becausethe meal was not delivered per the confirmed delivery instructions.
SI-3: The system shall communicate with thecontent manager to get the product specifications. 2.3.
4. Communications InterfacesCI-1: The UOG Smart Café system shall send anotification message to the user to confirm acceptance of an order, orderprepared, price, and delivery instructions.CI-2: The UOG Smart Café system shall send amessage to the Patron to report any problems with the meal order or deliveryafter the order is accepted.2.4. System Features2.4.1.
PlaceOrder via ApplicationUser can order food with the application butit needs specific internet connection. 2.4.
2. TakeOrderThe chef will take the order and if it isavailable to make then he will confirm the order and start to prepare food. 2.4.3.
ServeFood When the food is ready to be served then thechef will alert the waiter/distributer/deliverer. After this waiter will insurethe order is served. 2.4.4. PaymentThe payment is done at the time of orderplacement from user account. So, the café staff will prevent from taking fakeorder requests.2.
4.5. Available/ Required GoodsThe Chef will add what goods are availableand the admin can see that data and the chef will add what goods are required. 2.4.6.
CustomerInformation The user will be get registered and be themember of special customer. 2.4.7. UserFeedback Customer can give overall review about thefood items and services provided by the café. 2.5. OtherNonfunctional Requirements2.
5.1. PerformanceRequirementsTheperformance requirement for this project are as follow:PE-1: Thesystem shall accommodate 400 users during the peak usage time window of 3:00pmto 4:30pm local time, with an estimated average session duration of 5-10minutes.PE-3: Responsesto queries shall take no longer than 9 seconds to load onto the screen afterthe user submits the query.
PE-4: Thesystem shall display confirmation messages to users within 5 seconds after theuser submits information to the system.2.5.
2. Safety RequirementsNo safetyrequirements have been identified.2.5.3. Security RequirementsSE-1: Allnetwork transactions that involve financial information or personallyidentifiable information shall be encrypted per BR-33.SE-2: Usersshall be required to log in to the Cafeteria Ordering System for all operationsexcept viewing a menu.
SE-3: Patronsshall log in according to the restricted computer system access policy perBR-35.SE-4: Thesystem shall permit only cafeteria staff members who are on the list ofauthorized Menu Managers to create or edit menus, per BR-24.SE-5: Onlyusers who have been authorized for home access to the corporate Intranet mayuse the COS from non-company locations.SE-6: Thesystem shall permit Patrons to view only their own previously placed orders,not orders placed by other Patrons.2.5.4.
Software Quality AttributesAvailability-1: TheCafeteria Ordering System shall be available to users on the corporate Intranetand to dial-in users 99.9% of the time between 5:00am and midnight local timeand 95% of the time between midnight and 5:00am local time.Robustness-1: Ifthe connection between the user and the system is broken prior to an orderbeing either confirmed or canceled, the Cafeteria Ordering System shall enablethe user to recover an incomplete order.