Use Case Review 1

Review 1 by Egemen

Hi, I made a list of things that came to my mind, they are by no means the last words and most of them should be considered by looking and/or modifying the diagram and the requirements simultaneously. Very good work :)

1. In the use case Enter credentials, do we know that these info are precisely what we want/need, nothing less nothing more? For example, do we need to require the birth date?
2. Display demo exercises use case should be detailed.
3. Do Verify suggested learning materials get done by the admins or users?
4. Grade assignments and Give feedback use cases look like they are the includes of another use case.
5. Add suggested tags may be a different use case on its own.
6. At See the progress for each language use case, does it matter that we show all the languages' progress or a single one's? Do we need to emphasize this?
7. Interact with another user use case can be demonstrated better if we use another stick figure for the other user so diagram shows an interaction between users, rather then simply reads.
8. We need to make sure that when we sayReach learning materials and Select ... materials, we are comfortable with the verbs of action here. These words are very sticky, do we convey the right info when we use them?
9. Do assignments use case needs to be under Writing use case. Again, we can use another stick figure on that part of the graph.
10. I cannot remember if we talked about Take exercises about the notes use case. Is there any exercise for the notes? Should there be?
11. After taking the proficiency exam, what happens? For example, at what point, the learning materials which were not accessible, become so?
12. Admin user should be able to interact with other users, should be able to learn a new language. In the UML Use Case Diagram Tutorial, there was a technique which looks like "OO inheritance". We can use that to differentiate between normal users and admins, all the while providing to the admins with every service we already provide to the users.