LIBRARY INFORMATION SYSTEM

6.2.1.3 USE CASE MODEL

View book category

Manage reservation

STUDENT Search ebooks

FACULTY

Login

Search book Return books

Feedback

ADMIN Issued book status

STAFF

Login

Book record maintenance

Place notification Issue books

Add/remove staff

Manage student record

Fine calculation

Manage books
 USE CASE: LOGIN
Brief Description:
This use case describes how a user logs into the System. The use case takes in the user name and
password to logon and checks for its validity.

Flow of events:

NORMAL FLOW:
step Actor Description Condition Location
1. Administrator/Staff/Use System generate login page ---------- -----------
r which request user enter
his/her name and password.
2. Administrator/Staff/Use The user enters Login id and ---------- -----------
r password
3. Administrator/Staff/Use The system validates the Invalid Alternate
r entered name and password userid/passwor flow
and logs the actor into the d
system.
4. Administrator/Staff/Use System generates required ---------- ------------
r page listing all the available
operations.
5. Administrator/Staff/Use Use Case Ends. ----------- ------------
r

ALTERNATE FLOW:
step Actor Description Conditio Locatio
n n
1. Administrator/Staff/Us The user enters an invalid Login Id and --------- ----------
er password. The System displays an error -
message.
2. Administrator/Staff/Us System request to re-enter user ID and ----------- ----------
er password. The actor can choose to either --
return to the main flow or cancel the login,
at which point the use case ends.

Precondition: User needs a valid user name and password to logon to the system.
Post condition: If the use case was successful, the actor is logged into the system.
Actor: Administrator/Staff/User
Special Requirements: The ID and password should be provided to the Administrator/Staff/User
for login purposes.

USE CASE: MAINTAIN BOOKS

Brief Description:
This use case maintains the information of the books and the book Ids. It adds, deletes and
updates books/book id information

<<include>>

Add Books

<<include>>

<<include>>
Manage Books
Update Books

delete books

Flow of Events:
NORMAL FLOW:
step Actor Description Condition Location
1. Staff System prompts the staff member to select the desired -------- --------
activity
2. Staff If the activity selected is ADD, the Add Book/Book Add new s-1
Id information Book/Book Id
Sub flow is performed. information
3. Staff If the activity selected is DELETE, the Delete Delete s-2
Book/Book Id information Book/Book Id
Sub flow is performed. information
4. Staff If the activity selected is UPDATE, the update Update s-3
Book/Book Id information Book/Book Id
 Sub flow is performed. information
5. Staff If the activity selected is Logout --------- --------
Use case ends.

SUB FLOW S-1

Step Actor Description Condition Location
1. Staff System generates Add Book/Book ID page, which --------- ---------
request that the Staff to enter the desired information.
2. Staff If the Staff enters information about the book name Invalid ALT-1
and clicks OK button then System adds the new book Information
to the Database of books
3. Staff If the Administrator enter information about the book --------- ----------
and clicks ok button then System Add
New Book to Database of book
4. Staff Staff Wants to Add more books/book ids then go to ---------- ----------
Step1 Or Use case ends

ALTERNATE FLOW ALT-1

Step Acto Description Condition Location
r
1. Staff If in the main flow , the staff enter an invalid information, --------- --------
the system displays an error message
2. Staff System request to re-enter Correct information .The Staff ---------- --------
can choose to either return to the main flow or cancel, at
which point use case ends.

SUB FLOW S-2

Step Actor Description Conditio Location

n
1. Staff System generates Delete book/book Id page, which request --------- ---------
that the Staff to enter book id to delete book id information
or the book name to delete book information.
2. Staff If Staff enters book id & click delete the System Deletes --------- ----------
Book Id info. from Database
3. Staff If Staff enters book name & click delete the System Deletes ---------- ----------
Book info. from Database
4. Staff Staff Wants to Delete more. Books/Book ids info then go to ---------- ----------
 Step1Or Use case ends.

SUB FLOW S-3

Step Actor Description Condition Location
1. Staff System generates Update Book page, which request ---------- ----------
that the Staff to enter book id to update Book Id
information or the Book Name to update Book
information.
2. Staff If the Staff enters book id information and clicks on Invalid ALT-2
update button, System updates Book Id information to Information
Database of books
3. Staff If the Staff enters book information and clicks on ------------ ---------
update button, System updates Book information to
Database of boo
4. Staff Staff Wants to update more books/book ids then go to --------- --------
Step1 Or Use case ends

ALTERNATE FLOW ALT 2

Step Actor Description Condition Location
1. Staff If in the main flow , the Staff enter an invalid -------- -------
information, the system display an error message
2. Staff System request to re-enter Correct information -------- --------
The Staff can choose to either return to the main flow or
cancel, at which point use case ends.

Precondition: User needs a valid user name and password to logon to the system.
Post condition: If the use case was successful, the Staff maintains books/book id information
(i.e. add, delete, update).
Actor: Staff
Special Requirements: The details about the books such as the book id, book name, subject
department, edition etc. must be known.
.

USE CASE: VIEW BOOK INFO

Brief Description
This use case facilitates the members to view information about the books available in the library.
Flow of Events
NORMAL FLOW
Ste Actor Description Condition Location
p
1. Administrator/Staff/Use System generates View books page, ------ ------
r which request that the
administrator/user to enter book
name to view book information or
the book id to view book id
information.
2. Administrator/Staff/Use If the Administrator enters the book Invalid ALT-1
r name & click view button then the informatio
System Displays book details. n
3. Administrator/Staff/Use If the Administrator enters the book ------- --------
r id & click view button then the
System
Displays book id details.
4. Administrator/Staff/Use Administrator Wants to view more -------- --------
r books/book ids then go to Step1
Or Use case ends

ALTERNATE FLOW ALT 1

Ste Actor Description Condition Location
p
1. Administrator/Staff/Use If in the main flow , the administrator ------- --------
r enter an invalid information, the
system display an error message
2. Administrator/Staff/Use System request to re-enter Correct ------- --------
r information. The Administrator can
choose to either return to the main
flow or cancel, at which point use case
ends.
Precondition: None
Post condition: If the use case was successful, the book/book id details are displayed.
Actor: Administrator/Staff/User
Special Requirements: The name of the book or the book id must be known
.
USE CASE: ISSUE RECORDS
Brief Description
This use case maintains the information of the books issued to various members. It adds, deletes
and updates issued books information

add issue record

<<include>>

<<include>>

delete issue record

<<include>>

Issue record
<<include>>

update issue record

view issue record

Flow of Events
NORMAL FLOW
Step Actor Description Condition Location
1 Staff System prompts the Staff to select the desired ------- ------
activity
2 Staff If the activity selected is ADD, the Add issue record Add issue S-1
Sub flow is performed. record
3 Staff If the activity selected is DELETE, the Delete issue Delete issue s-2
 record Sub flow is performed record
4 Staff If the activity selected is UPDATE, the update issue Update issue s-3
record Sub flow is performed. record
5. Staff If the activity selected is VIEW, the view issue View issue s-4
record record
Sub flow is performed.
6. Staff If the activity selected is LOGOUT Use case ends ------- --------

SUB FLOW S-1

Step Actor Description Condition Location
1. Staff System generates Add issue record page, which ------ ------
requests the Staff to enter user id , book id, date of
issue, date of return etc.
2. Staff Staff enters above information Invalid ALT 1
information
3. Staff Click add button -------- --------
4. Staff System Add New issue record to the database -------- ---------
5. Staff Staff Wants to Add more issue records then go to Step1 ------- ----------
Or Use case ends

ALTERNATE FLOW ALT 1

Step Actor Description Condition Location
1. Staff If in the main flow , the Staff enter an invalid -------- -------
information, the system display an error message
2. Staff System request to re-enter Correct information -------- --------
The Staff can choose to either return to the main flow or
cancel, at which point use case ends.

SUB FLOW S-2

Step Actor Description Condition Location
1. Staff System generates Delete issue record page, which ------- --------
request that the Staff to enter user id and due return
2. Staff Staff enter above information & click delete ------- --------
3. Staff System Delete. Issue record. from Database -------- --------
4. Staff Staff Wants to Delete issue records then go to Step1 -------- --------
Or Use case ends

SUB FLOW S-3

Step Actor Description Condition Location
1. Staff System generates Update issue record page, which ------- --------
request that the Staff to enter user id and due return
date
2. Staff Staff enters the required information Invalid ALT-2
information
3. Staff Click update button -------- --------
4. Staff System updates issue record to Database -------- --------

5. Staff Staff Wants to update more issue records then go to

Step1 Or Use case ends

ALTERNATE FLOW ALT 2

Step Actor Description Condition Location
1 Staff If in the main flow , the Staff enter an invalid -------- ------
information, the system display an error message
2 Staff System request to re-enter Correct information --------- -------
The Staff can choose to either return to the main
flow or cancel, at which point use case ends.

SUB FLOW S-4

Step Actor Description Condition Location
1 Staff System generates View issue record page, which -------- --------
request that the Staff to enter user id and due return
date
2 Staff Staff enter above information Invalid ALT-3
information
3 Staff Click view button -------- --------
4 Staff The system displays the issue record details. -------- --------
5. Staff Staff Wants to view more issue records then go to -------- --------
Step1
Or Use case ends
ALTERNATE FLOW ALT 3

Step Actor Description Condition Location

1 Staff If in the main flow , the Staff enter an invalid -------- --------
information, the system display an error message
2 Staff System request to re-enter Correct information -------- --------
The Staff can choose to either return to the main
 flow or cancel, at which point use case ends.

Precondition: Staff needs a valid user name and password to logon to the system.
Post condition: If the use case was successful, the Staff maintains and views the records of
books issued to the various members (i.e. add, delete, update, and view).
Actor: Staff
Special Requirements: The details such as the user id, book id, date of issue, return date etc.
must be known.

USE CASE: STAFF MAINTAINENCE

Brief Description
This use case maintains the information of the staff that works in the library. The chief library
officer who is the administrator can add a new staff to the system and can also delete an existing
staff.

<<include>>

Add Staff
<<include>>

Manage Staff

Remove Staff

Flow of Events
NORMAL FLOW
Step Actor Description Condition Location
1 Admin System generates manage staff page --------- ------
2 Admin Add staff --------- S1
3 Admin Remove Staff --------- S2
SUBFLOW S1:
Step Actor Description Condition Location
1 Admin System generates add staff page --------- ------
2 Admin Admin feeds the new staff entry. Invalid entry ALT
3 Staff record gets entered in the staff Table. Use ---------
case ends

ALTERNATE FLOW:
Step Actor Description Condition Location
1 Admin In main flow if required mandatory fields are not --------- ------
fulfilled it display error message
2 Admin System requests to enter user information/ can ---------- ------
cancel in that case use case ends

SUBFLOW S2:
Step Actor Description Condition Location
1 Admin System generates remove staff page --------- ------
2 Admin Feeds the Staff ID of the staff to be removed. ---------- ------

3 Admin Staff data gets removed. Use case ends.

Precondition: Administrator should be logged in.

Post condition: If the use case was successful, the refreshed list of staff is displayed.
Actor: Administrator.

USE CASE : STUDENT RECORD MAINTAINENCE

Brief Description
This use case maintains the information of the student that use the library.
 <<include>>
Add Student

<<include>>

<<include>> Remove Student

Manage Student Record

Update Student Record

Flow of Events

NORMAL FLOW
Step Actor Description Condition Location
1 Admin/Staf System opens the page of the student record. --------- ------
f
2 Admin/Staf Add a new student record. ---------- S1
f
3 Admin/Staf Delete an existing student record ----------- S2
f
4 Admin/Staf Update an existing student record ----------- S3
f

SUBFLOW 1
Step Actor Description Condition Location
1 Admin/Staf System opens the page of the student entry --------- ------
f
2 Admin/Staf Actor fills in the form. Invalid Entry ALT1
f
3 Admin/Staf System updates the database. ----------- ------
f
4 Asks for more student entry ----------- ------
Use case ends

ALT1
Step Actor Description Condition Location
1 Admin/Staf System gives an error message. --------- ------
f System prompts for a valid entry.

SUBFLOW 2
Step Actor Description Condition Location
1 Admin/Staf System opens the page of the student record --------- ------
f deletion
2 Admin/Staf Actor gives the Student ID for deletion Invalid Entry ALT1
f
3 Admin/Staf System deletes from database. ----------- ------
f
4 Admin/Staf Asks for more deletion. ----------- ------
f Use case ends.

ALT1
Step Actor Description Condition Location
1 Admin/Staf System gives an error message. --------- ------
f System prompts for a valid entry.

SUBFLOW 3
Step Actor Description Condition Location
1 Admin/Staf System opens the page of the student record --------- ------
f updation.
2 Admin/Staf Actor gives the Student ID for update. Invalid Entry ALT1
f
3 Admin/Staf System updates the database. ----------- ------
f
4 Admin/Staf Asks for more updation. ----------- ------
f Use case ends.
ALT1
Step Actor Description Condition Location
1 Admin/Staf System gives an error message. --------- ------
f System prompts for a valid entry.

Precondition: Administrator should be logged in.

Post condition: If the use case is successful, the refreshed list of student is displayed.
Actor: Administrator.

USE CASE: FEEDBACK

Brief Description
This use case maintains the feedback of the student that use the library to the administrator.

Flow of Events

NORMAL FLOW

Step Actor Description Condition Location

1 User Opens the page for feedback. --------- ------
2 User Feeds in the feedback. --------- ------

3 Admin Can read the feedback. ----------- ------

Precondition: Administrator should be logged in.

Post condition: If the use case was successful, the administrator gets to know the feedback of the
users of the library..
Actor: Administrator, User.
USE CASE: NOTIFICATION

Brief Description
This use case maintains the notifications published by the administrator.
Flow of Events

NORMAL FLOW

Step Actor Description Condition Location

1 Admin System opens the page for placing notification --------- ------
2 Admin Writes notification and publishes it. --------- ------

3 Admin View previous notification. ----------- ------

Use case ends.

Precondition: Administrator should be logged in.

Post condition: If the use case was successful, the administrator can post notifications on the
website.
Actor: Administrator.

USE CASE: BOOK RESERVATION

Brief Description:
This notification tells us about how a book is reserved by a user.

<<include>>

Make Reservation
<<include>>

Reservation

Cancel Reservation

NORMAL FLOW:
Step Actor Description Condition Location
1 User System generates the page for reserving ---------- ----------
the books.
2 User Can make reservations. ---------- Sub 1
3 User Cancellation of reservation. ---------- Sub 2
SUB FLOW 1:

Step Actor Description Condition Location

1 User System checks if the book is available. Not available Alt 1
2 User System checks the database. Already Alt 2
reserved
3 User Reserves in the database. ---------- ----------
Use case ends.

ALTERNATE FLOW ALT 1:

Step Actor Description Condition Location
1 User System prompt for non availability of ---------- ----------
books.
2 User System request for another book & ---------- ----------
redirects to the home page.
Use case ends.

ALTERNATE FLOW 2:
Step Actor Description Condition Location
1 User System gives an error message of already ---------- ----------
reserved books.
2 User System request for another book & ---------- ----------
redirects to home page.

SUB FLOW 2:
Step Actor Description Condition Location
1 User System opens the cancellation page. ---------- ----------
2 User System takes the reserve ID/book ID of Invalid id Alt 1
the books to be cancelled.
3 User System removes the entry from the ---------- ----------
database
Use case ends.

ALT ERNATE FLOW 1:

Step Actor Description Condition Location
1 User System prompts an error message. ---------- ----------
 2 User System prompts for an valid id or redirects ---------- ----------
to home.

Precondition: User should be logged in.

Post condition: If the use case was successful, the user reserves the book and collect it when he
goes to the library within a given timeframe.
Actor: User

USE CASE: FINE

Brief Description: This use case maintains the fine paid by student due to the late
submission of book.
FLOW OF EVENTS:
NORMAL FLOW:
Step Actor Description Condition Location
1 Staff System opens the page for returning ---------- ----------
books.
2 Staff Actor enters the book id Invalid entry Alt 1
3 Staff System calculates the fine and display it. ---------- ----------
4 Staff System asks for more entry. ---------- ----------
Use case ends.

ALTERNATE FLOW 1:
Step Actor Description Condition Location
1 Staff System displays an error message &
request for the correct entry

Precondition: Staff member should be logged in.

Post condition: If the use case was successful, the staff will be able to impose fine on the late
book returns.
Actor: Staff.

6.2.2 Conceptual Level Class Diagram

6.2.3 Conceptual Level Sequence Diagram