Use Cases
Simply put, a use case is a simple ellipse with a functionality written inside, as shown below.
Use cases indicate the actions that can be carried out by the system. A use case must be something that the system can do. That is, it must always be some verb (or verbal clause, for you grammar Nazis).
A use case is indicated by the action or functionality written inside an ellipse. Each separate action is shown as a separate ellipse.
That’s simple, right? However, before I talk more about use cases, I want to discuss the rest of the use case diagram first. I will come back to use cases later.
Use Cases should be written out as verbs. It is something that the system can do.
Users of the system should be able to create modules, add notices, update marks and view marks.
The diagram above shows each of the functionalities mentioned written in a separate ellipse. The use cases do not show how these functionalities are achieved, merely that they should exist within SPAMS.