Chili Flax (Dish advisor) Web Site Analysis

Chili Flax (Dish advisor) Web Site Analysis1 IntroductionIn this section, documentation withdraw utilisation of scheme, scope, and divergent possible interaction with system.1.1 PurposeThe purpose of this documentation is to give a expound t for each oneing near Chili Flax (Dish advisor) web site. In this documentation, we describe various interactions, interfaces and system constraints for this system. The main purpose of this documents is to give illusion to developer and user about system.1.2 ScopeThe Chili Flax (Dish Advisor) is a website, which helps user to comp atomic bout 18 foods serve exclusively eating places in the city. It comp ares based on price and customers review on particular food selected by user.It allow for help user to find best food nearby his/her location. Main advantage that it brings foil in price and quality of food is serving in the city.Restaurant owners ordain provide learning about its calling card and other information about restaur ants like establishment years, experience in this business, machine-accessible with a nonher firm and schedule. Restaurant owner rat have Owner panel to modify menu whenever they want.The software need GPS (location) permission for find nearby place feature which allow software to amount minimum distance with user and provide best search result.1.3 Definitions, acronyms and abbreviationsTermDefinitionuser psyche who interact with websiteAdmin/Administrator governing body administrator who have rights to change and have it away website informationRestaurant ownerWho have rights to change own restaurant menu and pricesDeveloperWho piddled this website and managed all informationGPSGlobal Positioning SystemGPS-Location ManagerLocation permission need when website is excessed through user device to improve search optimisationData SourcePerson or referencing object who contributed data in this website1.4 OverviewIn this documentation, we have majorly include three chapter which en able to give brief introduction of system and other interaction modules devoted by all whole system. In this document, also describe diverse stakeholders and their respective roles. Another aspect is that what is constrains and presumptuousness need to mention in system that every individual should make is also describe in this documentation.Requirement specification and detailed terms and definitions of the different interfaces mansion in third chapter of documentation. Technologies used during execution of instrument of requirement also mentioned.In the Fourth chapter prioritization of requirement is mention and also mentioned what basis developers are make out those requirement is beginning(a) and all filtration process.The appendixes in the end include all results of requirement prioritized and launch political program of development.2. Overall descriptionThis section forget provide associate summary of the entire system. The system result be explained in its context to indicate however the system interacts with alternative systems and introduce the essential practicality of it. It exit additionally describe what kind of stakeholders which will use the system and what practicality is obtainable for every kind. At last, the constraints and assumptions for the system will be given.2.1 Product perspectiveThis system mainly contain two parts first one is web browser and second is database. Web browser serve act pages which contains different pages to serve.GPS will be used by mobile application to locate user. Distance between user and restaurant will be displayed by GPS and also da of application will be displayed by GPS. user can use function of GPS seamlessly manner.This application contains centralized database so it requires to store data somew present. prompt application as well as website two can access to database. They will use database in different ways. Mobile application will use database to display those data which is required by use r. Web gate will use database to store and modify those data mandatory by administration team of system. mesh will be used for this kind of communication.There are limited resources available for mobile application. The utmost amount of hard drive space required by application will be 20 MB.2.2 Product functions user can search restaurants use mobile application. The result will be displayed using inputs given by user. Administrator of system can change of add criteria. Search result will be displayed in either list view or in map view check to the requirements of user. The list view will have one list item for each restaurant. Location of each restaurants will be displayed in map view. In both views user, can view information about restaurants. The web portal will be used for data population and administration purpose.2.3 drug user characteristicsThe fare of types of users is three which will interact with system User of mobile application, administrators and restaurant owne rs. Each user carries different role, requirements and rights on system.The mobile application users can take to data only. They can input criteria for search restaurants and gets directions to pass by there.The restaurant owners will use web portal to populate date. The can manage their menu and information about restaurants.The administrators will use web portal to system. They will have maximum rights on system. They are responsible for removing uncourts data and harmful contents.2.4 ConstraintsMobile application needs GPS system to be functional properly. Mobile devices with different GPS will use same interface.The application will also require internet connection. Connectivity to database is effected over internet so internet connection will be needed by application. twain the application and web portal will have limited size of database. Database is shared between both application and web portal so it can happen that they can be forced to line up incoming requests.2.5 Ass umptions and dependenciesWe can assume that application will be installed on capable devices. If device does not have enough space, then application will not be installed.Another assumption is that all mobile devices in which application is installed, have working GPS with same interface. If the phones have different interfaces to the GPS, the requirements for GPS will needed to be changed.2.6 Apportioning of requirementsIf project is about to be delayed, there are some requirements that will be implemented in the next versions of application. Those requirements are to be implemented in the next sac, see adjunct IV.3. Specific requirements The functional and quality requirements are contained by this section. Detailed description of system and interface is given in this section.3.1 External interface RequirementsThis section describes all inputs and outputs of system. It also describes the software, hardware and the communication interfaces. This section provides prefatorial prot otypes of the user interface.3.1.1 User interfaces Login page will be displayed to first time user, see Figure 2. User can navigate registration page from login page.Search page will be displayed to user if user is not first time user, see Figure 3. User will select search criteria here and able to get list of required restaurants.User will have profile page to manage personal and contact information, see Figure 4. Also, the user can change its preferred language.3.1.2 Hardware interfacesApplications are installed on fully built systems so they dont need any external hardware. The GPS and database will be handled by underlying processes of operating system of respected devices.3.1.3 Software interfacesThe mobile application will use GPS to get location of user and will use database to fetch data about restaurants which is required by user, see Figure 1. Mobile application can only read data from database. Web portal will have all rights on data of database.3.1.4 Communications inter facesThe different parts of system are highly dependent on each other so communication among them is very important. Way of communication is doesnt bear on by whole system. So, communication will be handled by underlying processes of operation system on respective devices.3.2 operating(a) requirements3.2.1 User Class 1 The User3.2.1.1 working(a) requirement 1.1ID FR1TITLE transfer mobile applicationDESC Application should be downloaded by user from application store and free of hail tail So, user can download application.DEP no(prenominal)3.2.1.2 Functional requirement 1.2ID FR2TITLE Notification of refreshed cedesDESC When new release of application comes, user will get notification about it.RAT So, user can download new version of application.DEP FR13.2.1.3 Functional requirement 1.3ID FR3TITLE RegistrationDESC User should create an account on system.RAT So, user can create an account.DEP FR23.2.1.4 Functional requirement 1.4ID FR4TITLE LoginDESC User should login in syst em in order to user features of system.RAT So, user can access its profile.DEP FR1, FR33.2.1.5 Functional requirement 1.5ID FR5TITLE Get passwordDESC User can get password by email.RAT Recovery of password.DEP FR13.2.1.6 Functional requirement 1.6ID FR6TITLE User ratingsDESC User should rate restaurants.RAT Improved feedback.DEP FR43.2.1.7 Functional requirement 1.7ID FR7TITLE Search restaurantsDESC User should search restaurants by food, price, distance and rating.RAT Search for a restaurant.DEP FR63.2.1.8 Functional requirement 1.8ID FR8TITLE Admin panelDESC Administrators should be able to manage database of system.RAT System management.DEP None4. Prioritization and Release devise4.1 Choice of prioritization methodTop 10 most important requirements will be selected first. This will be done by simple reduce method in which higher number means high priority. Number will be assigned base on decision of meting of stockholders. The highest summed number associated with requirement w ill decide priority of requirement. The results will be red marked and others will be left as are they before. These requirements were prioritized according to the points they got and the results can be viewed under Appendix II.4.2 Release PlanThe requirements were divided in three groups and each group will be implements in each release of application. Each release will be work as complete working system.The first release will contain essential requirements. The last release will contains most advanced requirements. Other requirements can be implemented in middle release,Gantt Chart