1.

SPECIFIC REQUIREMENTS

Software Product Features

1.1.1Login Use Case

officer Login
User

1.1.1.1Brief Description

This use case describes how a user logs into the Library System. The actors starting this use case
is officer.

1.1.1.2Flow of Events

The use case begins when the actor types his/her name and password on the login form.

1.1.1.3Basic Flow - Login

1. The user enters ID and password

2. The system validates the user password and logs him/her into the system.
3. The system displays the Main Form and the use case ends.

1.1.1.4Alternative Flows

1.1.1.4.1FORGET PASSWORD

1. The user tell it to administrator (maintenance)

3.1.1.4.2 Invalid Password

If user submits incorrect ID and password, the error message will be displayed. The user must re-
enter ID and password again.
1.1.1.5Special Requirements

The ID must begin by alphabet and contain number 0-9. The passwords at least 6 characters and
contain alphabet and number. Preconditions

The user must have an account.

1.1.1.6Postconditions

The user is logged in the system.

1.1.1.7Login Sequence Diagram

: Login Form : Login Ctl : User : User Form

: User
1.fill in login form()

2.get user info(integer,string)

3.is valid()

4.open()

Sequence Diagram:
Login/E--2:Forget
password

Sequence Diagram:
Login/E-1:Invalid
User Info

Figure 3 : Login Sequence Diagram

1.1.1.8Login Activity Diagram

Start Login Use Case

Fill in Login
Form

If a user forgot his/her

password, they must get
it first from the system by Select Submit
typing their e-mail.

Incorrect ID or Passward Display Error

Message

Open User Form

End Login Use Case

Figure 4 : Login Activity Diagram

1.1.2register Use Case

register
visitor

1.1.2.1Brief Description

This use case describes how a actor register to be a member of the Library. The actors starting
this use case is visitor.

1.1.2.2Flow of Events

The use case begins when the visitor want to borrow book(s) and should have a member ID.

1.1.2.3Basic Flow - register

1. Press register button

2. Press new member (open form register)
3. fill form register
4. submit
5. register has been submitted
6. view information member
7. press save button

1.1.2.4Alternative Flows

There is no alternative flow associated with this use case.

1.1.2.5Special Requirements

There are no special requirements associated with this use case.

1.1.2.6Preconditions

There are no preconditions associated with this use case.

1.1.2.7Postconditions

The visitor has been registered

1.1.2.8Register Sequence Diagram

Hehehe.. sequence diagram ak dk bisoooo

Figure 5 : Check out Customer Sequence Diagram