1

UML Diagram

This is a use case diagram about the enrollment of students at a university. There are several flaws in it, and I have to find them.

I am wondering what is happening when you get to use case "Choose course". Yes, you will also have to "Enroll", but what happens if you choose a course that is not available? You will extend the use case, "Course not available", but will you still enroll the course that isn't available? It seems to me like you will.

It would have been different if the association between "Choose Course" and "Enroll" was an extend, because then you only sometimes would enroll in the course, most likely only when it is available.

I am assuming the same logic applies to the "Log-in" use case and the "Student not Identified" use case. You can choose a course without being identified as a student.

  • "Student not identified" and "course not available" are not really suitable for a use case diagram. Those things belong in some other diagram, like a flowchart. Red Beard's use case diagram below is much better. – Robert Harvey Nov 10 '18 at 15:21
  • are you sure you dont want another type of diagram e.g. activity maybe? you seem to be trying to show state transitions? – jk. Dec 10 '18 at 14:28
0

I am not really sure to understand your use case diagram. What do you want to express? I guess that a Student can "Enroll a Course". To do so, he needs to "Pay fees", "Choose a Course", and "Log-In" right? So the includes links are in the other ways as depicted below. enter image description here

Now to really need to express tha fact that a course is not available? Or a user is not logged? If yes what for?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.