Requirements and Specification Document
- Initial creation
- Update User Interface Requirements
- Delete the user stories because they are duplicated (The actual document is in the design document)
- Update use cases(UX changes are reflected)
- Update page naming
- Update feature change
- To move UAT from design document
- Update User Interface Requirements
- Project Abstract
- Customer
- Competitive Landscape
- Functional Requirements
- User Interface Requirements
In a world with meaningless 5-star restaurant ratings where restaurant recommendation apps are filled with advertisements, consumers have lost trust in reviews. However, people are willing to visit restaurants recommended by their friends. Fooriend recreates the experience of recommending restaurants to friends as a service. In Fooriend, users can check the reviews left by their friends on the map. Fooriend provides a quick summary of reviews about the restaurant by automatically dividing the reviews as positive or negative. Users can leave reviews of the restaurant they visited and can collect these reviews to create their own restaurant map. Also, when users leave reviews, they can add a photo of the receipt to certify that they have visited the restaurant. This authentication ensures the reliability of the review. Just by sharing maps of restaurants with each other, networking is possible through the daily act of recommending restaurants, and everyone can become famous restaurant-recommend influencers as in Foodinko. Fooriend wants to solve the problem of unreliable reviews caused by restaurant advertisements with the keyword “connection”.
Specific Customer
- People who are tired of existing recommendation services(e.g. Baedal Minjok, Mangoplate, etc.) and willing to receive trustworthy restaurant recommendations based on the certain location General Customer
- People who want to share restaurant reviews and photos with their peer group as a function of SNS
| service | Mangoplate | Foodinko | Kakaomap | Fooriend |
|---|---|---|---|---|
| Reliability of Reviews | △ | O | X | O |
| Own Map | △ | X | O | O |
| Writing/Sharing reviews | △ | X | △ | O |
| Goal | new account creation for user who does not have an account |
|---|---|
| Feature | Sign up |
| Actor | Who wants to see a reliable restaurant review of an acquaintance |
| Precondition | The user is not registered |
| Trigger | The user clicks on “Sign up” button |
| Scenario | 1. The user fills up 'name', ‘ID’, ‘password’, ‘password confirm’ fields and clicks on “Sign up” button |
| Exceptions | 1a. ID already exists 1a.1. show “account already exist” & deny create a new account 1b. Password and password confirm fields do not match 1b.1 show “password and password confirm do not match” & deny create a new account 1c. & 2b. The user clicks on “Sign up” button without filling all the fields 1c.1 & 2b.1 show “Fill in the required items” & deny create a new account |
| Acceptance Test | When the user fills all the fields correctly and clicks on “Sign up” button, the user is redirected to “Login page” |
| Goal | Login of a user with an account |
|---|---|
| Feature | Log in |
| Actor | Who wants to see a reliable restaurant review of an acquaintance |
| Precondition | The user is registered |
| Trigger | The user enters ID, password and clicks on “Login” button |
| Scenario | 1. The user fills in ID and password fields 2. The user clicks on “Login” button |
| Extensions(error scenarios) | 1a. The user enters an unregistered ID 1a.1. Show “Account is not registered” 1b. Password input does not match with the registered password of the input ID |
| Acceptance Test | When the user enters the correct ID, password and clicks on “Login” button, a toast message “login success” is displayed and the user is redirected to “Home page” |
| Goal | check out the restaurants reviewed by "fooriends(The people the user is following)" on the map |
|---|---|
| Feature | Map search |
| Actor | Who wants to move the area on the map and looks for restaurants |
| Precondition | The restaurant is on (Google) map and current location permission is accepted |
| Trigger | The user clicks on the Home tab on the bottom or is on the Home page and clicks the current location button at the top right |
| Scenario | 1. The user moves around and zoom into certain area near the user 2. Restaurants with a "fooriend" marker is viewed. Only restaurants with reviews from fooriend have "fooriend" markers. |
| Extensions(error scenarios) | 1a. The user clicks the marker of the place which is not classified as a restaurant by Google Place 1a.1 System shows a “음식점에 대한 정보만 볼 수 있습니다.” message to the user. 1b. The name of the restaurant is English or ambiguous 1b.1 Follow the api of the Google map |
| Acceptance Test | The marker is created first on the map and then the map moves so that the marker is placed on the center of the map |
| Goal | Move to restaurant detail page |
|---|---|
| Actor | Who wants to know the detail of the certain restaurant |
| Precondition | In the home page |
| Trigger | The user clicks on the restaurant name toggled above the marker. |
| Scenario | 1. When the user clicks the restaurant name above the fooreind marker, redirected to restaurant detail page. 2. If the restaurant is not the place where "fooriend" had left reviews, restaurant name will be above the simple marker |
| Extensions (error scenarios) | 1a. The user clicks the place where is not classified as a restaurant according to the Google Place, nothing will be displayed |
| Acceptance Test | When the user clicks the restaurant name above the marker, redirected to restaurant detail page. |
| Goal | See random reviews made by all users |
|---|---|
| Actor | Who wants to see a review. |
| Precondition | Reviews in the social page. |
| Trigger | The user clicks on “Social” tab on the bottom. |
| Scenario | 1. The representative photos of the reviews made by users are arranged randomly in the form of a checkerboard pattern. 2. When the user clicks a photo, the user is redirected to “Review detail page” of that review. |
| Extensions (error scenarios) | None |
| Acceptance Test | When the user clicks “Search” tab, he/she can see photos of randomized reviews made by users. |
| Goal | Search users |
|---|---|
| Actor | Who wants to see other’s profile. |
| Precondition | In the social page |
| Trigger | The user clicks on search bar at the top. |
| Scenario | 1. The user clicks on the search bar at the top and enters a name of a user. 2. When the user successfully finds the user and clicks his/her name, the user is redirected to “Fooriend page”. |
| Extensions (error scenarios) | 1a. The user enters the name of the user which is not registered. 1a.1. System shows a “please enter valid user name” message to the user. |
| Acceptance Test | When the user clicks on the search bar and enters the name of a fooriend correctly, the user can see the profile of that fooriend. |
| Goal | See detailed information about a restaurant |
|---|---|
| Actor | Who wants to see detailed information about a restaurant. |
| Precondition | The restaurant and its information is on the map. |
| Trigger | The user clicks the name of the restaurant on the “Review page” or clicks on a pin of a particular restaurant on the map. |
| Scenario | 1. The page displays the reviews of a restaurant containing photos. 2. Reviews are divided into positive and negative reviews about the restaurant, and by default, entire reviews are displayed on the screen. 3. The total number of reviews of each type is also displayed on the tab. 4. When the user clicks either a positive or a negative review tab, that type of reviews are displayed as a list. 6. When the user clicks the “리뷰 작성하러 가기" button, the user is redirected to “posting review page”. 7. When the user clicks on a profile of another user who wrote a review, the user is redirected to “Fooriend page”. |
| Extensions (error scenarios) | None |
| Acceptance Test | The user should see detailed information about the restaurant and see reviews which are divided into positive/negative reviews. |
| Goal | See detailed review |
|---|---|
| Actor | Who wants to see a review. |
| Precondition | There is a review. |
| Trigger | The user clicks the photo of a particular review on “Social page” or on “My page” or “Fooriend page”. |
| Scenario | 1. Photos of the review are displayed in the center. 2. Texts of the review are displayed at the bottom, with sentiment-analyzed mark and verifying mark if the review is verified. 3. When the user clicks the name of the restaurant, the user is redirected to the “Restaurant detail page”. 4. When the user clicks the left arrow button on the top-left, the user is redirected to the previous page. |
| Extensions (error scenarios) | None |
| Acceptance Test | The user should see photos, texts, sentiment-analyzed mark of the review and verifying mark if the review is verified. |
| Goal | Write a review |
|---|---|
| Actor | Who wants to write a review. |
| Precondition | - |
| Trigger | The user clicks on “리뷰등록” button. |
| Scenario | 1. The user can add photos of the food. 2. The user can enter the review text with a maximum of 200 characters. 3. If a user adds a photo of a receipt, he/she can receive a “Verified Review” badge. 4. The user can register a review by clicking the “리뷰등록" button. |
| Extensions (error scenarios) | 4a. The user clicks on “리뷰등록" button without entering the review text. 4a.1. System shows a “enter text” message to the user. |
| Acceptance Test | When the user fill the text field and click “리뷰등록" button, the review is registered. |
| Goal | See reviews of fooriends |
|---|---|
| Actor | Who wants to see reviews of a fooriend. |
| Precondition | The user has searched a fooriend by his/her id. |
| Trigger | The user clicks the profile of a fooriend. |
| Scenario | 1. The profile photo and short information(total number of follower/following) about a fooriend and a “follow” button are displayed at the top. 2. The representative photos of the review made by the fooriend are arranged in the order of recent uploads in a checkerboard pattern. 3. If the user is following the fooriend, the user can see "follow" button and if not, the user can see "following" button. 4. When the user clicks “follow/following” button, the fooriend is added/deleted to the fooriend list of the user. 5. When the user clicks a photo, the user is redirected to “Review page” of that review. |
| Extensions (error scenarios) | None |
| Acceptance Test | 1. The user should see representative photos of reviews made by the fooriend. |
| Goal | See my reviews |
|---|---|
| Actor | Who wants to see one’s reviews |
| Precondition | The user is logged in. |
| Trigger | The user clicks on "My" tab on the bottom. |
| Scenario | 1. The profile photo and short information(total number of follower/following) about the user is displayed at the top. 2. The representative photos of the reviews made by the user are arranged in the order of recent uploads in a checkerboard pattern. 3. When the user clicks a photo, the user is redirected to “Review page” of that review. |
| Extensions (error scenarios) | 1a. The login token has expired 1a.1 Redirect the user to the login page |
| Acceptance Test | 1. The user should see photos of all reviews made by oneself. |
| Goal | See my information |
|---|---|
| Actor | Who wants to see information about oneself. |
| Precondition | The user is logged in. |
| Trigger | The user clicks on setting icon on "My page". |
| Scenario | 1. The page displays the information of the user (name) 2. When the user clicks on "Log out" button, the user is logged out and redirected to login page |
| Extensions (error scenarios) | 1a. The login token has expired 1a.1 Redirect the user to the login page |
| Acceptance Test | 1. When the user clicks the logout button, the user should log out with login token expired and redirected to login page. |
- As an user looking for a nearby restaurant, I want to see a reliable restaurant, so the restaurant choice doesn't fail.
-
Acceptance Criteria
- Given I sign up the fooriend app,
- When I logged into the app,
- Then I should see pins representing my friends' reviewed restaurants.
- As a meticulous person, I want to check overall assessment from individuals about restaurant, so that I can ensure the quality.
-
Acceptance Criteria
- Given I am on a restaurant's page in the Fooriend,
- When I look at the review section,
- Then I should see a summarized view indicating the overall sentiment about the restaurant.
- As a food enthusiast, I want to share my opinions about restaurant, so that my friends can benefit from my experiences.
-
Acceptance Criteria
- Given that I have visited a restaurant, I decided to leave a post about my opinions in Fooriend,
- When other users 'follow' me and become my friends,
- Then my friends can check my opinions to see my recommendations.
- As a reviewer, I want to authenticate my reviews, so that they are seen as reliable and genuine by other users.
-
Acceptance Criteria
- Given I am writing a review for a restaurant in Fooriend,
- When I attach a photo of my receipt or other proof of my visit,
- Then my review should be posted with a verified badge indicating my authenticity.
- As a diner, I want to have a personal compilation of my restaurant reviews, so that I can easily recall and revisit my favorite dining moments.
-
Acceptance Criteria
- Given I am on Fooriend and have previously written multiple reviews,
- When I go to My Tab,
- Then I should see a list of all the restaurants I have reviewed, enabling me to reminisce and plan future visits.