게시판 만들기 (1) - user story, case

1. User Stories

1. As an uploader, I want uploading daily picture, so that I can accurately record the day.

2. As an uploader, I want a personal account, so that I can view and manage my posts that others can’t see.

3. As an uploader, I want to keep a special post among my posts in an important storage box, so that I can see them occasionally and remember them.

4. As an uploader, I want to receive a notification, so that I can write a diary once a day.

5. As an uploader, I want to have a one-line record page, so that I can briefly look back at the contents of the bullentin board.

6. As an uploader, I want to divide the posts by themes, so that I pick up and read easily later.

7. As an uploader, I want to apply for buying diary by selecting only what I want out of my post, so that I can get the contents of the bulletin board as a real diary.

2. Use cases

Name of Use case	Select post category
Date Created	May 14
Description	Users view posts by category.
Actor	Server, user
Precondition	1. The server is running 2. The user logs in to his/her account.
Post condition	1. Divide the categories of posts on the bulletin board and show them. 2. Posts are saved in the database by category
Flow	1. The user clicks the 'add post' button on his or her bulletin board. 2. The post category selection window is displayed on the user's web browser. 3. The user selects a category and presses the OK button. 4. The server receives the category information selected by the user. 5. After the user writes the post, he presses the 'save post' button. 6. The server sorts and stores posts by category in the browser with the category information. 7. The user can view the updated post page.
Exception	1. If the “add post” button does not work in step 1 - If an error message is displayed and the OK button is pressed, the user is redirected to the default page. 2. If the category is not saved after clicking the OK button in step 3 - The category reselection message is displayed in the web browser window, and the process goes back to step 2. 3. If the “save post” button does not work in step 5 - If you press the OK button with an error message displayed, you will be taken back to the post writing page.
Additional Requirements

Name of Use case	Summary bulletin board
Date Created	May 15
Description	Users view their writings at a glance through the summary bulletin board.
Actor	Server, user
Precondition	1. The server is running 2. The user logs in to his/her account.
Post condition	1. Summarized information using specific data is stored in the summary bulletin board. 2. The summary information is stored in the summary board database.
Flow	1. The user clicks the'add post' button on their bulletin board. 2. Select a post category. 3. Write a title in the post title box. 4. The user presses the ‘save post’ button after writing the entire post. 5. When saving a post on the server, all the information created is saved. 6. From all the information in the post on the server, only the contents of steps 2 and 3 are selected separately. 7. On the server, write the contents of step 3 on the calendar according to the date. 8. When the user goes to the summary page, he can see what's new.
Exception	1. If the “add post” button does not work in step 1 - If an error message is displayed and the OK button is pressed, the user is redirected to the default page. 2. If the “save post” button does not work in step 4 - If you press the OK button with an error message displayed, you will be taken back to the post writing page.
Additional Requirements	1. When filling out the contents of step 3 in step 7, if the category in step 2 falls under an important category, it is indicated in orange.

Name of Use case	Important bulletin board
Date Created	May 16
Description	A bulletin board page where users can view only important posts selected by the user.
Actor	Server, user
Precondition	1. The server is running 2. The user logs in to his/her account.
Post condition	1. Important posts are saved and displayed on the important bulletin board. 2. Important posts are saved in the database.
Flow	1. The user clicks the'add post' button on his or her bulletin board. 2. The post category selection window is displayed on the user's web browser. 3. Select whether the user is an important post or not and click the OK button. 4. The server receives information about whether or not the user has selected an important post. 5. The user presses the ‘save post’ button after writing the entire post. 6. If the user selects an important post, the server uploads the post to the important bulletin board as well as the general bulletin board. 8. Users can view updated postings on both general and important bulletin boards.
Exception	1. In case of failure in steps 1 and 5 -If an error message is displayed and the ok button is pressed, the user is redirected to the previous page. 2. If step 3 fails -The post category selection window is redisplayed in the user's web browser.
Additional Requirements

Name of Use case	Important bulletin board
Date Created	May 16
Description	A bulletin board page where users can view only important posts selected by the user.
Actor	Server, user
Precondition	1. The server is running 2. The user logs in to his/her account.
Post condition	1. Important posts are saved and displayed on the important bulletin board. 2. Important posts are saved in the database.
Flow	1. The user clicks the'add post' button on his or her bulletin board. 2. The post category selection window is displayed on the user's web browser. 3. Select whether the user is an important post or not and click the OK button. 4. The server receives information about whether or not the user has selected an important post. 5. The user presses the ‘save post’ button after writing the entire post. 6. If the user selects an important post, the server uploads the post to the important bulletin board as well as the general bulletin board. 8. Users can view updated postings on both general and important bulletin boards.
Exception	1. In case of failure in steps 1 and 5 -If an error message is displayed and the ok button is pressed, the user is redirected to the previous page. 2. If step 3 fails -The post category selection window is redisplayed in the user's web browser.
Additional Requirements

Name of Use case	Diary application and production
Date Created	May 18
Description	Make the desired post into a real diary.
Actor	Server, Administrator, User
Precondition	1. The server is running 2. The user logs in to his/her account.
Post condition	1. The user pays and the manager receives the money. 2. The manager makes a diary and ships it.
Flow	1. Select the diary order button on the general bulletin board webpage. 2. A screen where users can select 10 posts from among the posted posts is displayed. 3. The user selects 10 posts that the user wants to create a diary. 4. The user selects the type of diary. 5. The user presses the diary order. 6. User information, selected posts and diary types are stored on the server. 7. The user is directed to the page where the administrator's account number and money are displayed. 8. Update the order information on the admin page on the server. 9. The manager directly checks the payment details. 10. When payment is made, click the OK button on the admin page. 11. The administrator's OK sign is saved in the server. 12. Order details and order confirmation details are displayed on the order management page of the orderer. 13. Delivery after production. 14. Users are provided with a prepared diary.
Exception	1. Failure in steps 4 and 5 The RETRY message is displayed on the user's web browser window, and if you click OK, the page goes back to the page. 2. If you fail in step 10 The RETRY message is displayed in the administrator's web browser window, and if you click OK, the page goes back to the relevant page.
Additional Requirements	1. The manager checks the type of diary and, if it is out of stock, personally contact and handle it.