Use Case for Login

Use case name Login

Participating actor Initiated by: Finance officer
Communicated by: None
Entry Condition 1. The Finance officer has logs in
Flow of events 1. Begins types his/her name and password on the login form.
2. The system validates the finance officer password and logs him/her into the
system.
3. The system displays the Main Form and the use case ends.
Exit Condition 4. The system redirects and logout page.
Special requirements . There are no special requirements associated with this use case.

use case refinement

Use case name Login

Participating actor Initiated by: Finance officer
Communicated by: None
Entry Condition 1. The Finance officer has logs in
Flow of events 1. Begins types his/her name and password on the login form.
2. The system validates the finance officer password and logs him/her into the
system.
3. The system displays the Main Form and the use case ends.
4. The system requests that the actor enter his/her name and password.
5. The actor enters his/her name and password.
6. The system validates the entered name and password and logs the actor
into the system.
Exit Condition 4. The system redirects and logout page.
Special requirements . There are no special requirements associated with this use case.
 Use Case for Relationship

Use case name Login

Participating actor Initiated by: Finance officer
Communicated by: None
Entry Condition 1. The Finance officer has logs in
Flow of events 1. Begins types his/her name and password on the login form.
2. The system validates the finance officer password and logs him/her into the
system and extends logout, includes login
3. The system displays the Main Form and the use case ends.
Exit Condition 4. The system redirects and logout page.
Special requirements There are no special requirements associated with this use case.
Alternative Flows Invalid Name / Password, the system displays an error message. The Finance
officer can choose to either return to the beginning of the Basic Flow or
cancel the login, at which point the use case ends.

Use Case for Identifying classes

Use case name Login

Participating actor Initiated by: Finance officer
Communicated by: None
Entry Condition 1. The Finance officer has logs in
Flow of events 1. Begins types his/her name and password on the login form.
2. The system validates the finance officer password and logs him/her into the
system and extends logout, includes login
3. The system displays the Main Form and the use case ends.
Exit Condition 4. The system redirects and logout page.
Special requirements There are no special requirements associated with this use case.
Alternative Flows Invalid Name / Password, the system displays an error message. The Finance
officer can choose to either return to the beginning of the Basic Flow or
cancel the login, at which point the use case ends.