For the school assignment, we need to make a Usecase diagram. But the documentation that we have is not very expanded. It simply describes the components that make up the user system, and one example.
We need to make an expression about the library system. We found 11 usecases, but I will not bother you with all of them.
IIRC, usecase describes a typical use of the system, right? But what things relate to the Usecase diagram and how do they connect together?
Now we have four members (member, employee, manager and accountant). With most problems, we have a member and an employee.
The employee is the one who uses the system. Does the member stay here as an actor?
In some cases, we have:
- The user joins the library.
- User modifies his posts.
- The participant is borrowing a book.
- Parts of the library member (unsubscribing).
- The book of participants in the article.
- The user returns the book.
- Member pays (part) of fees and penalties.
Those become usecases on the chart. But should there be more cases, for example, an employee enters a member number, an employee enters a book number, etc. (Uses?).
Can anyone shed light on this?
Edit:
How are the steps described? I was told that you can see a usage association, such as a method call, to some routine that repeats itself? It is right? And how is the extension used?
source
share