Use Cade Model

Use cases represent the functionality of the system. If focuses on the behavior of the system
from an external point of view; that is, they describe a function provided by the system that
yields a visible result for an actor.

Use Case Diagram

The following diagram is used to capture the dynamic aspect of the system. It’s representation
of a user’s interaction with the system that shows the relationship between the user and the
different use cases in which the user is involved.
Use case name Amend defendant
Participating Actor  Investigator
Entry condition  The Investigator login to the system.
Flow of events  The system displays the investigator page.
 The Investigator click on view menu and select view
defendant submenu.
 The system displays the view defendant page and then the
investigator click on update button.
 The system displays the defendant register form and the
investigator edit information that he want to update.
 The investigator clicks on the save button.
 The system saves the updated information.
 The system will send the conformation and close the page.
Alternative flows  System will display message and prompt the user to
inform record is not present if there is no record in the
database.
 The user click on ‘’Close’’ button to close the printing
page if he or she does not want to print the report.
Exit condition  The record that had been updated will be stored on the
database.
Use case name Amend Investigator
Participating Actor  Administrator
Entry condition  The Administrator login to the system.
Flow of events  The system displays the Administrator page.
 The Administrator click on view menu and select view
investigator submenu.
 The system displays the view investigator page and then the
Administrator click on update button.
 The system displays the investigator register form and the
Administrator edit information that he want to update.
 The Administrator clicks on the save button.
 The system saves the updated information.
 The system will send the conformation and close the page.
Alternative flows  System will display message and prompt the user to
inform record is not present if there is no record in the
database.
 The user click on ‘’Close’’ button to close the printing
page if he or she does not want to print the report.
Exit condition  The record that had been updated will be stored on the
database.
Use case name Send feedback
Participating Actor  Public user
Flow of events  The system displays the home page.
 The public user click on send feedback menu.
 The system displays the send feedback page.
 The public user fill the feedback form and click on send
button.
 The system sends the full fill information.
 The system will send the conformation and close the page.

Special requirements  The form must be complete.

 Must full fill system validation.
Alternative flows
Exit condition 1. The record on send feedback form will be stored on the
database.
Use case name Amend Plaintiff
Participating Actor  Investigator
Entry condition  The Investigator login to the system.
Flow of events  The system displays the investigator page.
 The Investigator click on view menu and select view
Plaintiff submenu.
 The system displays the view plaintiff page and then the
investigator click on update button.
 The system displays the plaintiff register form and the
investigator edit information that he want to update.
 The investigator clicks on the save button.
 The system saves the updated information.
 The system will send the conformation and close the page.
Alternative flows  System will display message and prompt the user to
inform record is not present if there is no record in the
database.
 The user click on ‘’Close’’ button to close the printing
page if he or she does not want to print the report.
Exit condition  The record that had been updated will be stored on the
database.
Use case name Amend Witness
Participating Actor  Investigator
Entry condition  The Investigator login to the system.
Flow of events  The system displays the investigator page.
 The Investigator click on view menu and select view
witness submenu.
 The system displays the view witness page and then the
investigator click on update button.
 The system displays the witness register form and the
investigator edit information that he want to update.
 The investigator clicks on the save button.
 The system saves the updated information.
 The system will send the conformation and close the page.
Alternative flows  System will display message and prompt the user to
inform record is not present if there is no record in the
database.
 The user click on ‘’Close’’ button to close the printing
page if he or she does not want to print the report.
Exit condition  The record that had been updated will be stored on the
database.
Use case name Forget Password
Use case Description  The system informs the user that the user
name or password invalid.
Participating Actor  All user
Entry condition  Users entered invalid username or password.
Flow of events  The user writes the correct username and the
incorrect password.
 The system shows the error of username or
password.
 The users clicks on forgot password button.
 The system displays the page where he/she
needs to answer the security questions they
had set during account creation.
 The user’s answers the asked question and
click on submit.
 The system will send the conformation and
close the page.
Alternative flows
Exit condition  None
Use case name Amend Most Wanted Person
Participating Actor  Administrator
Entry condition  The Administrator login to the system.
Flow of events  The system displays the Administrator page.
 The Administrator click on view menu and select view most
wanted person submenu.
 The system displays the view most wanted person page and
then the Administrator click on update button.
 The system displays the most wanted person register form
and the Administrator edit information that he want to
update.
 The Administrator clicks on the save button.
 The system saves the updated information.
 The system will send the conformation and close the page.
Alternative flows  System will display message and prompt the user to
inform record is not present if there is no record in the
database.
 The user click on ‘’Close’’ button to close the printing
page if he or she does not want to print the report.
Exit condition  The record that had been updated will be stored on the
database.