-
Notifications
You must be signed in to change notification settings - Fork 1
Requirements and Specification
This service is intended for users who want to obtain, compare, or share their survey results. There are some existing services similar to ours, but they do not serve integrated service for both making survey and sharing survey results.
SurBing is designed to make/deploy survey&view survey results. Thus, it is possible to satisfy both those who want to do survey and those who want to see the survey results.
If users want to see the survey results, users need a point. For getting point, users should respond to ongoing surveys. This point system encourages more survey participations by the users.
When we look for survey data, we often want to search for similar surveys too. SurBing calculates text similarity among all surveys using machine learning and recommends context -based similar surveys to users.
Rev. 1.0 2019-10-05 - initial version
Rev. 2.0 2019-11-13 - revised version after mid demo
Rev. 2.1 2019-12-16 - revised version after poster session
Survey results are required in broad fields from marketing to academic researches in order to analyze the public and society. So anyone who wants to obtain the survey results easily would be our main customer. If they can't get survey results which they want, they can do survey in this service. This service is targeting both those who want to do survey and those who want to see the survey results.
- Survey monkey is a site where users can create survey sheets conveniently because this site has many types of items and users can modify design according to their preference. On the other hand, not only can users make a survey, but surBing can also collect opened survey results and provide them to those who want to conduct the same survey. Our site is specialized in the function of searching system and selecting and displaying survey items which has similar contents.
- KOSIS has a wide range of public survey, such as census and occupational surveys. In contrast, SurBing can do survey about various topic and collect the results. In other words, users can gather survey results about a narrow range of subjects, such as surveys for needs of university students in 2019s. Using Surbing, if there are existing survey results on the same topic, users can get them without redoing the survey.
- Actors: All site user
- Precondition: The user has to be registered
- Trigger: User is at the login/signup page
- Scenario:
- The page displays a form with two fields "ID" and "Password". Below the form, there is "Log In" button
- The User fills out the two fields with his/her login information
- Exceptions & Required Behaviors:
- The user does not fill out all fields to log in
- Pop up an alert "Please fill in the missing fields."
- The user fills inappropriate ID or Password
- Pop up an alert "Incorrect ID or Password." and empty the filled text
- The user does not fill out all fields to log in
- Acceptance Test:
Given the user has filled out appropriate login information
When the user clicks on the "Log in" Button
Then the user should see "Successfully Logged In!"
- Actors: All site user
- Precondition: The user has to be not registered yet
- Trigger: User is at the login/signup page
- Scenario:
- The page displays a form with four fields "E-mail", "ID", "Password" and "Password Confirmation". Below the form, there is "Sign up" button
- The User fills out the six fields with his/her E-mail, ID, preferred password, age and gender.
- Exceptions & Required Behaviors:
- The user does not fill out all fields to Sign up
- Pop up an alert "Please fill in the missing fields."
- There is a duplicated E-mail or ID in previously registered accounts
- Pop up an alert "There is duplicated E-mail or ID." and empty the filled text
- The user fills out the password Confirmation and password differently
- Pop up an alert "Incorrect Password confirmation." and empty the filled text
- The user does not fill out all fields to Sign up
- Acceptance Test:
Given the user has filled out appropriate Sign up information.
When the user clicks on the "Sign in" Button
Then the user should see "Successfully Registered!"
- Actors: Site users logged in
- Precondition: The user has to be logged in
- Trigger: User clicks the log out button on the my ID
- Scenario:
- Pop up the message “Do you really want to log out?”
- The user clicks yes, then be logged out
- Exceptions & Required Behaviors:
- If the user is doing some work when clicking the button, that work will be quit
- Acceptance Test:
When the user clicks on the “log out” button
then the user should see pop up message
Click yes, then the user will be logged out
- Actors: All site user
- Precondition: The user has to be registered
- Trigger: User clicks the Profile button at the right top
- Scenario:
- Below the button, "My Page" and "Log Out" buttons appears
- The User Clicks "My Page" button
- Exceptions & Required Behaviors:
- no expected exceptions
- Acceptance Test:
When the user clicks on the "My Page" button
Then the user should see "My Page" page
- Actors: Site user who has opened a survey
- Precondition: The user has already opened a survey.
- Trigger: User enters the mypage
- Scenario:
- On the fraction of the page, a section of ongoing survey appears.
- The User can see the ongoing survey's brief information, and respondant counts.
- If user clicks particular survey tab, go to detail page of that ongoing survey.
- Exceptions & Required Behaviors:
- no expected exceptions
- Acceptance Test:
The user opens a new survey. The other user writes and submits a response for that survey. The user should see the ongoing survey with one response on mypage.
- Actors: Site user that navigated other pages in the site
- Precondition: The user has to be registered
- Trigger: User is at the other page(ex: search for survey, cart, survey information tab, Home... )
- Scenario:
- On top left corner of pages, there is a logo for going home
- The User clicks the logo
- Exceptions & Required Behaviors: The operations that were going on stop and the page moves to Home
- Acceptance Test:
Given the user is at page excluding login/signup page
When the user clicks on the Button to home, then the user should see page ‘Home’
- Actors: All site user
- Precondition: The user has searched for survey
- Trigger: User is at Search result page
- Scenario:
- At the left column of the page, there are two text forms for each filtering criteria (Response number, etc...)
- User fills out the range value for each criteria (leave empty for unlimited)
- User clicks the "Apply" button at the bottom
- Exceptions & Required Behaviors:
- The start value is bigger than end value in certain criteria
- Shows up a red message "Please check the range of the value" under corresponding criteria
- Acceptance Test:
Given that the user filled out some of (can be none/all of) the range value for filtering criteria
When the user clicks on the "Apply" Button
Then the user should see all the search results matching with the criteria
And should not see any search results not matching with the criteria
- Actors: site users who wants to delete ongoing survey he uploaded.
- Precondition: user has to be at his mypage.
- Trigger: user clicks delete button of ongoing survey.
- Scenario:
- User wants to delete a single ongoing survey.
- User clicks on the delete button.
- Exceptions & Required Behaviors:
- user presses the delete button.
- The popup comes out asking if you are going to delete this survey.
- If the user clicks yes, the survey must be deleted at the database.
- user can't delete opened survey.
- Acceptance Test:
On myPage, we can click on the delete button and check if the survey is deleted when pressing yes, and not deleted when pressing no.
- Actors: Site users who wants to see survey details and items
- Precondition: The user has to be at searched survey list page & user has points
- Trigger: User clicks the survey block
- Scenario:
- The user moves to the information tab about clicking survey
- User points are deducted
- Show the each of item results and details about the survey(subjective -> responses, selection -> numbers of responses, block chart, pie chart)
- Exceptions & Required Behaviors:
- No Exceptions
- Acceptance Test:
When the user clicks on the survey block
then the user should see information tab consisting of details and items
If user has no point, user can't see detail information(some items blinded)
- Actors: site users who wants to add surveys to cart
- Precondition: user has to be at searched survey list page
- Trigger: user clicks add to cart button
- Scenario:
- User wants to add survey into his/her own cart.
- User clicks the button on the right side of the survey block.
- Exceptions & Required Behaviors:
- The item is added to cart with an alert message which informs that the item is successfully added.
- If the survey is already in the cart, the alert message pops up to inform that.
- User can move to his own cart by clicking the button on the right top corner of the website.
- Acceptance Test:
On search result page, we can click on many survey’s add-to-cart button and finally go to the personal cart page and check if surveys are successfully added.
- Actors: Site users who wants to delete surveys
- Precondition: The user has to be at “Cart” page
- Trigger: User checks one or more boxes, then clicks delete button
- Scenario:
- User selects surveys which wants to delete by checking the boxes
- Checking boxes, user clicks delete button
- The surveys disappear from the cart list
- Pop up the message “Done!”
- Exceptions & Required Behaviors:
- If user doesn’t select any checkboxes and clicks the delete button, then pop up “Please select surveys which you want to delete”
- Acceptance Test:
When the user clicks on delete button
then the user should see surveys deleted
- Actors: site user who wants to upload the survey he made.
- Precondition: user has to be at page excepts survey making page or responding page.
- Trigger: user clicks the 'Create Survey' button in 'utilbar' at upper side of the page.
- Scenario:
- User wants to upload survey here and get a survey result from this homepage.
- User writes the survey's title, content, questions, and their options.
- User inputs survey period, open date and goal personnel.
- User inputs survey items(subjective, radio, multi-selections).
- User presses the send button.
- Acceptance Test:
User clicks 'Create Survey' button and writes the survey's informations and questions and presses submit button. It saved in database and will be shown to other users who clicks the participating page.
- Actors: site user who wants to response on other's ongoing survey for download.
- Precondition: user has to be at participating page.
- Trigger: user has to click specific ongoing survey.
- Scenario:
- User wants to see others' survey results.(need points)
- Ongoing surveys based gender and age appear on the participating list.
- User click specific survey.
- Response all items of survey.
- Clikcing submit button, user can get point.
- Acceptance test:
If user responses on survey, the results should be stored in backend.
The number of responses exceeds a certain number(according to user settings), then that survey is treated ad a completed survey and people can't response on that.
- Actors: site users who wants to download a single survey result
- Precondition: user has to be at some survey’s detail page
- Trigger: user clicks download button
- Scenario:
- User wants to download a single survey result.
- User clicks on the download button
- Exceptions & Required Behaviors:
- The survey’s download starts with no alert.
- Acceptance Test:
On survey detail page, we can click on the survey download button and check if the download starts.