logo

COVER PAGE Contents

14 Pages1811 Words354 Views
   

Added on  2020-04-21

About This Document

COVER PAGE Contents COVER PAGE 1 Introduction 3 2 Purpose 3 3 Scope 3 4 Acronyms 3 5 Constraints 3 6 Assumptions 3 7 Requirements 4 7.1 Functional requirements 4 7.2 Nonfunctional requirements 4 8 Stakeholders 5 9 Project schedule and deliverables 6 10 Project budget 6 11 Risk analysis 6 12 Quality assurance 6 13 Use case diagram 7 13.2 Use case scenarios 7 14 Class diagram 9 15 User interfaces 9 Bibliography 14 1 Introduction The Dining system is an information system that helps connect customers with their

COVER PAGE Contents

   Added on 2020-04-21

ShareRelated Documents
COVER PAGE
COVER PAGE Contents_1
ContentsCOVER PAGE................................................................................................................................................11 Introduction..............................................................................................................................................32 Purpose.....................................................................................................................................................33 Scope........................................................................................................................................................34 Acronyms..................................................................................................................................................35 Constraints...............................................................................................................................................36 Assumptions.............................................................................................................................................37 Requirements...........................................................................................................................................47.1 Functional requirements...................................................................................................................47.2 Nonfunctional requirements.............................................................................................................48 Stakeholders.............................................................................................................................................59 Project schedule and deliverables............................................................................................................610 Project budget........................................................................................................................................611 Risk analysis............................................................................................................................................612 Quality assurance...................................................................................................................................613 Use case diagram....................................................................................................................................713.2 Use case scenarios...........................................................................................................................714 Class diagram..........................................................................................................................................915 User interfaces.......................................................................................................................................9Bibliography...............................................................................................................................................14
COVER PAGE Contents_2
1 IntroductionThe Dining closely is an information system that helps connect customers with their preferred restaurants. The information system is made up of a number of collective systems that are integrated together to form the complete information system which can be used by either customers, restaurant owners or an administrator. The system uses a GPS to help customers find the closest restaurant to theircurrent location so that they can book a table specifying the number of seats, selecting the type of food they want and how long they might take before getting to the restaurant. The customers can also pay directly from the application. 2 PurposeThis report aims at modelling the system by identifying the functional and non-functional requirements that make up the system while modeling the structural and behavioral architecture using UML. For better illustrations prototyping using wireframes is done.3 ScopeThis report describes the functional and the nonfunctional requirements of the proposed system. TO model the requirements a use case diagram is used. The use case diagram shows which actors interact with the system and to which scope of the system they do it within. The use case diagram shows the behavioral aspect of the system. A class diagram is used to show the structural aspects of the system by showing the classes and objects making up the system. Finally, simple wireframes are used to describe a prototype of the system.4 AcronymsGPS- Global Positioning SystemUML- Unified Modelling Language5 ConstraintsThe constraints of the system are the conditions that should hold for the system to operate as it was designed to. The following are the constraints of the proposed system.The customer sub-system is accessed using a mobile phone only.The restaurant sub-system is accessed using a web browser as it is a web application thus any device capable of opening web application pages can open the restaurant subsystem.The administrator subsystem is accessed using a web browser as it a web application.The payment subsystem used by the customers to pay for orders should be secure.All the subsystems will share a central database to help control and coordinate the flow of information between all the subsystems making up the system.6 AssumptionsThe following assumptions are made to make the constraints more clear for the implementation of the system.
COVER PAGE Contents_3
The customer subsystem of the system can only be downloaded on specific application stores.The GPS coordinates fed to the system for every restaurant should be accurate and verified by the administrator.The payment system to be implemented for the system will be an external payment service like PayPal. This is done to avoid developing a payment service for the application from scratch but instead take advantage of the existing payment services which have been fully developed overtime and are more secure. This will ensure that the customer’s payment details are kept secure for any transaction happening in the system.For the customer subsystem to work efficiently the customer’s mobile device must be GPS enabled and at the time of launching the application, the customer must ensure that the mobile data is on or the device is connected to a wireless network with internet access.7 Requirements7.1 Functional requirementsFunctional requirements describe what the end user expects the application to do in order to achieve a certain goal using the system. Functional requirements are functions of the system from the end user’s point of view. The following are the functional requirements of the system.A customer should be able t register and log in to their account after successful registration.A customer should be able to check for availability of a restaurant that is closest to them using their mobile devices which are GPS enabled.The restaurant search is based on the current position of the customer, price, restaurant type, dish and more factors. The customer can specify all the factors except for the current position which is determined using GPS system on the mobile device.A customer can make an order after identifying a restaurant from the search results depending on the availability of the restaurantA customer can specify the approximate time of arrival after making an order.A customer can pay for an order using their mobile phone.A restaurant owner can register to the system and login after successful registration.A restaurant owner can provide restaurant information to the system.The administrator can verify restaurant owners informationThe administrator can manage user information.The administrator can add GPS information for a restaurant7.2 Nonfunctional requirementsNonfunctional requirements are requirements that the end user does not interact with but are needed to achieve the functional requirements. The following are the nonfunctional requirements of the system.Availability- The system should be available at all times to enable the customers to access it and use it at any time of the day.Performance- the system should have a good performance. The time it takes for the customer subsystem to search for a restaurant based on the search criteria should not be more than 5 seconds on a good internet connection.
COVER PAGE Contents_4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Software Engineering: GPS Application for Smart Phones
|24
|2574
|56

ITC560 - Software Validation for XYZ Car Park System - Assignment
|29
|4201
|108

Analysis of UML Diagrams for Wood Stocks Application
|7
|633
|48

ITAP2013 Software Engineering
|19
|2481
|1

Re-design of Guest Tracker Application Report 2022
|23
|4171
|40

iDine Information System for Vallée de Goût - Object Modelling
|14
|2664
|244