Chili Flax (Dish advisor) Web Site Analysis

Chili Flax (Dish advisor) Web Site Analysis1 IntroductionIn this department, documentation answer for purpose of organization, scope, and different possible fundamental interaction with system.1.1 PurposeThe purpose of this documentation is to give a detailed reading slightly Chili Flax (Dish advisor) electronic network site. In this documentation, we describe various interactions, interfaces and system constraints for this system. The main(prenominal) purpose of this documents is to give illusion to developer and subprogramr about system.1.2 ScopeThe Chili Flax (Dish Advisor) is a website, which helps exploiter to comp atomic number 18 foods serving all restaurants in the city. It compares based on price and customers review on particular food selected by user.It pull up stakes help user to find best food nearby his/her location. Main gain that it brings transparency in price and quality of food is serving in the city. restaurant owners will go forth data about its menu and other information about restaurants like establishment years, experience in this business, connected with another firm and schedule. Restaurant owner croup energize Owner panel to diversify menu whenever they want.The software get hold of GPS (location) permission for find nearby place feature which allow software to calculate minimum distance with user and provide best face declaration.1.3 Definitions, acronyms and abbreviationsTermDefinitionuserPerson who interact with websiteAdmin/AdministratorSystem administrator who suck rights to change and manage website informationRestaurant ownerWho have rights to change own restaurant menu and pricesDeveloperWho created this website and managed all informationGPSGlobal Positioning SystemGPS-Location ManagerLocation permission need when website is excessed through user device to improve explore optimizationData SourcePerson or referencing object who contributed data in this website1.4 OverviewIn this documentation, we have majo rly included three chapter which enable to give brief introduction of system and other interaction modules given by all whole system. In this document, in like manner describe different stakeholders and their respective roles. Another aspect is that what is constrains and supposition 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 implementation of requirement also mentioned.In the quaternary chapter prioritization of requirement is mention and also mentioned what basis developers are choose those requirement is first and all filtration process.The appendixes in the end include all results of requirement prioritized and institute plan of development.2. Overall descriptionThis section will provide associate summary of the entire system. The system will be explained in its con text to augur however the system interacts with alternative systems and introduce the essential practicality of it. It will 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 fleck is database. Web browser serve screening rogues which contains different pages to serve.GPS will be used by fluid operation to locate user. Distance surrounded by 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 somewhere. Mobile application as well as website both can rise to power to database. They will use database in different ways. Mobile application will use database to display those data whic h is required by user. Web portal will use database to store and transform those data needed by administration team of system. Internet will be used for this kind of communication.There are limited resources available for mobile application. The maximum amount of hard drive space required by application will be 20 MB.2.2 Product functionsUser can search restaurants using mobile application. The result will be displayed using inputs given by user. Administrator of system can change of add criteria. explore result will be displayed in either list view or in map view according 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 User characteristicsThe number of types of users is three which will interact with system User of mobile application, administr ators and restaurant owners. Each user carries different role, requirements and rights on system.The mobile application users can jar against data only. They can input criteria for search restaurants and gets directions to reach 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 practicable properly. Mobile devices with different GPS will use same interface.The application will also require cyberspace connection. Connectivity to database is established over internet so internet connection will be needed by application.Both 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 que ue incoming requests.2.5 Assumptions 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 release, witness Appendix 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. Thi s section provides basic prototypes of the user interface.3.1.1 User interfaces Login page will be displayed to first time user, see visit 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 databa se.3.1.4 Communications interfacesThe different parts of system are highly dependent on each other so communication among them is very important. Way of communication is doesnt concerned by whole system. So, communication will be handled by underlying processes of operation system on respective devices.3.2 Functional requirements3.2.1 User Class 1 The User3.2.1.1 Functional requirement 1.1ID FR1 human activity Download mobile applicationDESC Application should be transfered by user from application store and free of cost thieve So, user can download application.DEP None3.2.1.2 Functional requirement 1.2ID FR2 denomination Notification of new releasesDESC 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 LoginD ESC User should login in system 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 reverse Plan4.1 Choice of prioritization systemTop 10 most important requirements will be selected first. This will be done by simple number method in which higher(prenominal) number means high precedence. Number will be assigned base on decision of meting of stockholders. The highest s ummed number associated with requirement will 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. opposite requirements can be implemented in middle release,Gantt Chart