Use Case Review 1 - bounswe/bounswe2019group9 GitHub Wiki
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 :)
- 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? Display demo exercisesuse case should be detailed.- Do
Verify suggested learning materialsget done by the admins or users? Grade assignmentsandGive feedbackuse cases look like they are theincludes of another use case.Add suggested tagsmay be a different use case on its own.- At
See the progress for each languageuse case, does it matter that we show all the languages' progress or a single one's? Do we need to emphasize this? Interact with another useruse 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.- We need to make sure that when we say
Reach learning materialsandSelect ... 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? Do assignmentsuse case needs to be underWritinguse case. Again, we can use another stick figure on that part of the graph.- I cannot remember if we talked about
Take exercises about the notesuse case. Is there any exercise for the notes? Should there be? - After taking the proficiency exam, what happens? For example, at what point, the learning materials which were not accessible, become so?
Admin usershould 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.