Use Case - WordWiseProject/WordWise GitHub Wiki

| Log in | |
| User Case ID: | WW01 | 
| Actor | User, Google OAuth | 
| Description User will add a new word to a new WordDeck | |
| Basic Flow | |
| 
1. User clicks on the login button 2. System display login form (Template from Google) 3. User clicks the email which wants to Log in 4. System connect to Google OAuth 5. Database confirm 6. System Display message  | 
|
| Add a word to new WordDeck | |
| User Case ID: | WW02 | 
| Actor | User, WordDeck representative | 
| Description User will add a new word to a new WordDeck | |
| Basic Flow | |
| 
1. User clicks login on the home page  2. System shows user’s WordDeck page 3. User clocks create new WordDeck page 4. User names a WordDeck page 5. User clicks to create a new WordDeck button 6. System shows empty WordDeck 7. User clicks to add new word 8. System shows a page for adding word 9. User adds Word, and description of that word 10. User clicks add new word button 11. System shows a WordDeck with one new word  | 
|
| Create WordDeck, and add a word to new WordDeck | |
| Stakeholders | User, WORDAPI | 
| Precondition | User must be logged in | 
| Success Guarantee | Definition of a new word must be existed | 
| Main Success Scenario | |
| 
            1. The user clicks to create a new WordDeck. 2. System shows create a new WordDeck page. 3. User puts in name and description of WordDeck. 4. System creates a new WordDeck. 5. System shows a new empty WordDeck. 6. User clicks to add a new word. 7. System shows a page for adding words. 8. User put in a wanted word. 9. System fetches word information from WORDAPI. 10. System shows a list of definitions of that word. 11. User selects a wanted definition and click add. 12. System add it to user's WordDeck. 13. System shows user's WordDeck with a newly added word.  | 
    |
| Extension | |
| 
            * Word Does not exist: If the word does not exist, system report back to
            user that word does not exist, and user must input a new word * User is not logged in: System redirect user to the login page.  | 
    |
| Special requirements | |
| Functionality | WORDAPI must be able to respond to the request. | 
| Usability | Create a new WordDeck, and add a new word button should be able to see clearly. | 
| Reliability | WORDAPI is must be able to receive requests at all time. | 
| Performance | The system should be able to handle a growing number of users a significant degradation in performance. | 
| Supportability | Regularly update and maintain the system, if any issues are found. |