Requirements

Summary

This project aims to serve people to learn more about what they eat in terms of micro and macro nutrients.

Background

The main purpose of this application is ordering foods with exclusive information about the ingredients considering personal preferences and reliability standards with a wide interconnection availability between consumer and provider sides with all its openness to social media. This application will enable food servers to create a profile and description of the food they serve as well as individual users being able to create a profile and interact with the servers and the other users by all means. The nutritional properties for the food served will be determined from nutritional information given recipes. There will be basically two types of users: regular users and visitors. Visitors have access only to explore the website whereas regular users (including servers and institutionals) have also access to order foods, follow other users, comment and tag on foods and servers, post media or any other information in their comments, advanced search and filter etc. There will be also user-specific profiles that contains preferences, daily consumptions, history of previous meals and so on..

Glossary Of The Requirements

Registered User: Is a person who has an account with privileges such as ordering foods, searching/filtering based on some criterias and is able to comment/tag/share/post his opinions and follow other profiles.

Visitor: Is a person who uses the website to explore restaurants and foods. Server: Restaurants, cafeterias, canteens. Comment: Allows both the user and the server to interact with each other. Rating: Restaurants are rated by their speed, hygiene, taste and service quality. Notification: User is notified when a restaurant he follows has a special offer or a new restaurant of his preference is open nearby. Servers are also notified by emails about positive and negative feedbacks the users give. Image: Servers include images for food descriptions and users are able to post images in comments. User Profile: Each registered user has a user profile that contains personal preferences, history of orders, favourite foods. Stats: Servers take scheduled statistical reports of how many times of clicking,commenting,sharing occurred. Popularity: Based on periodically consumption of foods. Semantic Tag: Used for grouping restaurants and foods on different factors. (i.e. For restaurants, cuisine,diet information. For foods, allergen,diet,organic information.) Filter: Could be either on restaurants or foods. Restauants could be filtered by location and labels. Foods could be filtered by ingredients, cuisine type, regimes, organic or allergenic types. Sorting: Restaurants on alphabetical ordering, popularity and ratings, foods on total calorie amount and which cuisine they belong to. Payment: Payment options such as credit/debit card, cash, ticket.. Working hours: When the restaurants are open. Micronutrients: Nutrients that humans consume in small quantities throughout life such as vitamins Macronutrients: Chemical elements that humans consume in the largest quantities. Three primary macronutrients are carbohydrate, fat and protein. Restaurant Profile: Restaurants have their own profile including a section at the top of food list which contains quantitatively most consumed foods, contact info, location, ratings. Recommendations: Main page of registered users include a section which provides recommendations based on their consumption history History: Keeps track of what the user has ordered, what he searched for,what he has consumed. Location: Restaurants have detailed location information on their public pages. Menu: Restaurants have to provide their menus on their profiles. Privacy: Personal information is visible to users who follow each other. Label: Restaurants and foods are labeled such that if a restaurant is open it has an open label and if some food is organic it has organic label. Favourites: User profile has this favourite food/place section which he can share with others. Sharing: In accordance with other social networks such as Facebook, Twitter, Instagram.

1. User Requirements

2. System Requirements

2.1. Functional Requirements
2.2. Non-Functional Requirements
2.2.1. Security
2.2.1.1. Confidentiality, integrity, availability, accountability, privacy and authenticity shall be provided.
2.2.1.1.1. Privacy
2.2.1.1.1.1. The user’s information shall not be shared, copied or used without user’s permission.
2.2.1.1.2. Availability
2.2.1.1.2.1. Information shall be available to authorised users when they need them.
2.2.2. Usability
2.2.2.1. The system shall be user friendly.
2.2.2.1.1. Learnability
2.2.2.1.1.1. New users shall begin effective interaction.
2.2.2.1.1.2. Tutorial for the new users shall be provided.
2.2.2.1.1.3. Help document shall be provided.
2.2.2.1.2. Flexibility
2.2.2.1.2.1. Negotiable task allocation between the user and the system should be provided. (Task-Migratability)
2.2.2.1.2.2. The system shall be dialogue initiative.
2.2.2.1.3. Robustness
2.2.2.1.3.1. User shall be able to evaluate internal conditions of the system. (Observability)
2.2.2.1.3.2. The system shall provide support for undoing errors. (Recoverability)
2.2.2.1.3.3. The system functionality shall match common user tasks. (Task Conformance)
2.2.3. Portability
2.2.3.1. The system shall have Web and Mobile client.
2.2.3.1.1. The system shall be compatible with latest versions of Google Chrome, Mozilla Firefox and Safari available in 2016.
2.2.3.1.2. The system shall be compatible with Android.
2.2.4 Reliability
2.2.4.1. The system shall recover the last working state in case of crush.
2.2.5 Flexibility
2.2.5.1. The system shall be designed to add new features easily.
2.2.6. Accessibility
2.2.6.1. The interface shall be designed according to color-blindness.
2.2.6.1. The font size shall be changed for users who have eye discomforts.
2.2.7. Efficiency
2.2.7.1. The system shall be storage-friendly.
2.2.8. Maintainability
2.2.8.1. The system shall support previous version for 6 months.
2.2.9. Price
2.2.9.1. The system shall be free for all users.
2.2.10. Operability
2.2.10.1. The system shall be kept in safe and reliable functioning operation.
2.2.11. Performance
2.2.11.1. The maximum response time shall be 5 seconds for all tasks excluding problems regarding users such as network problems etc..