Use Case Descriptions

Library System
Use Cases
for
<Library System>
Version 1.0 approved
Prepared by <author>
<organization>
<date created>
Use Cases for Library System Page 1
1. Use Case Identification
1.1. Use Case ID
 Adminstratror-1
 Staff-2
 Student-3
 Guest-4
 Book-5
1.2. Use Case Name
 Administrator- Record users, integrate systems, print reports
 Staff- Issue book, accept returned books, process fines
 Student- Borrow books, provide identification, pay fines.
2. Use Case Definition
Actor
1. Administrator (Category User)
2. Staff (Category User)
3. Students (Category User)
4. Library Account (Category System)
5. Book (Category System)
6. Transaction (Category System)

7. Reports (Category System)
8. Search (Category System)
9. User Registration (Category System)
2.1. Description
1. Book (Attributes: Book title, Book author, isbn, price: Functions: adding book, removing
book Other Functions: login, login failed, search book, requisituion ist)
2. Transaction (Attributes: students id, books id, staff id Functions: borrow book, return
book Other Functions: search student, search staff, search book)
3. Registration (Attributes:student_name,student_rollno,student_id,Staff_name,
staff_designation, staff_id)Functions: register_student, register staff Extended Function: login,
login_failed,search_student, search_staff, search_unsuccessful)
4. Report (Attributes: books_id , students_id, date_of_return Functions: defaulters_list,
borrower_listrequisition_listExtended Functions: login, login_failed)
5. Search (Attributes: student_id,book_id,staff_idFunctions: login, login_failed,
search_book,search_student, search_staff, search_unsuccessful)
6. Administrator (Attributes: Admin_name, admini_id Other Functions: login, register, search ,
transaction, report)
7. Staff (Attributes: Staf_name, id. Other Functions: login, register, search, view)
8. Student (Attributes: Student_name, Id Functions: login, search)
9.
Login (Attributes: student_id or administrator_i or, staff_id and Password,Functions: login,
login_failed Other Functions: register_student,regisater_staff)
10.
View/Edit (Attributes: student_id,staff_id,administrator_idFunctions: view_student,
edit_student,view_book, edit_book, view_staff, edit_staff,Extended Functions: login,
login_failed,search_student, search_book, search_staff,search_unsuccessful)
ase.
2.2. Preconditions
1. The system administrator should ensure the entry of all student records and integration of the
library system with the students' database, staff database and faculty database
2. Each user must be authenticated before access. The system should record who has borrowed
which books he or she must show a valid ID card, which is checked against the student
database maintained by the registrar's office (for student borrowers).
3. When it comes to borrowing books, the system must check to ensure that the borrower does
not have any overdue books or unpaid fines before he or she can borrow another book.
3.1. Postconditions
The faculty/staff database maintained by the personnel office (for faculty/staff borrowers), or
against the library's own guest data base (for individuals issued a guest card by the library) to
ensure that it is still valid.
3.2. Normal Course of Events
A borrower comes to the library to borrow a book. The library staff log into the system Puts the
borrower’s id in the system and conducts a search to see if he or she has pending books he has
not submitted yet. If the borrower is clear, the staff checks the availability of the book the
borrower wants. If the book is available the library makes entries of the book details, borrower
details and the time span in which the book will be in the hands of the borrower.
If a borrower returns the book, the staff logs into the system, goes to the allocated books category
and locates the book that has been returned. The borrower is cleared hence can be able to borrow
another book.
3.3. Alternative Courses
In case a student has delayed in returning a book the system calculates fines payable in respect to
the length of delay.
The system administrator has elevated privileges and can log into the system to add or remove
users. He also responsible for the integration of the system with other systems.
3.4. Exceptions
In case a staff logs in with the wrong password an exception will be produced, “Invalid
password”
In case a staff tries to log into the administrator account, an error message will show up,
“Unauthorized access.
3.5. Special Requirements
The system will exist on a network hence the institution must at least have a local area network.
3.6. Assumptions
1. All library staff are computer literate.
2. All students have student’s ID
3. Library books are detailed in terms of titles, authors and date of publication.
4. Other systems meant for integration with the Library system were created to allow that kind
of flexibility
Use Case Diagram

Register
users
Provide id
Admin
Print student
reports
Login> user_id
+ Student
Password
Enter book Borrow/Re
details turn book
Check for
fines in case
of delay Pay fine in
case of
delay
Staff
Call student Guest
in case of
delay Enter/Updat
e student Provide
Information Guest id
Process
issuing of
books

Use Case Descriptions

Uploaded by

Copyright:

Available Formats

Use Case Descriptions

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Use Case Descriptions

Uploaded by

Copyright:

Available Formats

Library System

Version 1.0 approved

1. Use Case Identification

1.1. Use Case ID

1.2. Use Case Name

 Administrator- Record users, integrate systems, print reports

 Staff- Issue book, accept returned books, process fines

 Student- Borrow books, provide identification, pay fines.

2. Use Case Definition

6. Transaction (Category System)

3.2. Normal Course of Events

3.3. Alternative Courses

3.5. Special Requirements

1. All library staff are computer literate.

2. All students have student’s ID

Use Case Diagram

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.