Library Management System Use Cases 522u4g

Library Management System Description Introduction - The purpose of the system is to allow for storing details of a large number of books and allow for add, search, borrow, return facilities separately to , staff and students. Different privileges are given to different types of s. Using the OOSE (Object Oriented Software Engineering) we try to express the requirements as use cases consisting of actors and how they interact with the system. We define the objects and use cases as system objects. We define the functions and attributes within these system objects. Actors – 1. (Category ) 2. Staff (Category ) 3. Students (Category ) 4. Library (Category System) 5. Book (Category System) 6. Transaction (Category System) 7. Report (Category System) 8. Search (Category System) 9. Registration (Category System) Objects that define the system1. Book (Attributes: title, author, isbn, price: Functions: add book, remove book Extended Functions: , _failed, search_book, requisituion_ist) 2. Transaction (Attributes: student_id, book_id,staff_id Functions: borrow_book, return_book Extended functions: search_student, search_staff, search_book) 3. Registration (Attributes: student_name,student_rollno,student_id, Staff_name, staff_designation, staff_id) Functions: _student, staff Extended Function: , _failed, search_student, search_staff, search_unsuccessful) 4. Report (Attributes : book_id , student_id,date_of_return Functions: defaulters_list, borrower_list requisition_list Extended Functions: , _failed) 5. Search (Attributes: student_id,book_id,staff_id Functions: , _failed, search_book, search_student, search_staff, search_unsuccessful) 6. (Attributes: name, _id Extended Functions: , , search, transaction, report) 7. Staff (Attributes : name, staff_id Extended Functions: , , search, view) 8. Student (Attributes: name, student_id Functions: , search)

9.

10. View/Edit

(Attributes: student_id,_id,staff_id, , Functions: , _failed Extended Functions: _student, regisater_staff) (Attributes: student_id,staff_id,_id Functions: view_student, edit_student, view_book, edit_book, view_staff, edit_staff, Extended Functions: , _failed, search_student, search_book, search_staff, search_unsuccessful)

Use Cases1. Use Case #1 Registration Primary Actors: , Staff Pre- Condition: The student should have a valid college hip document which contains his name, date_of_birth, course, rollno to obtain library hip. The same criteria apply for registration of library and other staff including the . Main Scenario 1. To a student the or staff has to first . 2. After the or staff searches for the existing students. 3. If the student is already ed there is no need to him. 4. If the student is not already ed then his name, roll_no is to be entered for registration . 5. A student_id for library hip is generated and provided to the Student. 6. To a staff member the has to first . 7. After successful he searches among the existing staff . 8. If the staff member is already ed there is no need to him. 9. If the staff member is not already ed then his name , designation is Entered. 10. After successful registration the staff member is provided with a unique id. Alternate Scenarios 1. The or staff fails to . 2. or staff can search for his id among existing . 3. If he is already a member and unable to he should the otherwise he should get re-ed. Search for student/staff SITRATOR

Enter data to

STUDENT

Generate library id STAFF

Re- for failed

Send non-registration msg for found

2. Use Case #2 Search Primary Actors , Staff, Students Pre-Condition: The book or student to be searched should have been ed in the database of the library management system. Main Scenario 1. The student or staff or s to the system. 2. If the is successful. student or staff or enters the book name or ISBN or author name and presses search 3. If the search is successful then that book is displayed on the screen. 4. To search for a student the or staff s to the system. 5. If the is successful then it is possible to search for any student by entering his id. 6. To search for a staff member the enters his id. 7. If successful he can search for any of the staff . Alternative Scenario 1. The fails. 2. The student or staff or can re- themselves 3. If the search is unsuccessful then the should add that . 4. If the book search is unsuccessful then that book should be added.

Enter book-id SITRATOR View book details

Enter student or staffid View student or staff STAFF

Re- for failed

Add book/member if Search fails

STUDENT

3. Use Case #3 Transaction Primary Actors , Staff Pre-Condition: To return or borrow any book it is important that the student or staff member is ed with the library and the book to be borrowed is available witj the library. To return the book the pre-condition is that the student and the staff member is ed and that book data is available with the library. Main Scenario 1. If a student wants to borrow or return a book the staff or should to the system. 2. If is successful the staff or should enter the student id to be searched. 3. If student search is successful the staff or should enter the book id. 4. If the book is available it can be borrowed. 5. If the book is available the staff and should check The report data for any pending fine. 6. If no fine is pending the book can be returned. Alternate Scenarios 1. If the fails the staff or should re- Themselves. 2. If the student search is unsuccessful and no data is found then the should re- the student. 3. If the book search is unsuccessful and book data is not found then must enter the book in requisition report.

Search for book SITRATOR Search for student

Add book if search fails Add student if search fails STAFF

Check pending fines for a student

Borrow or return book

STUDENT

4. Use Case #4 Book (Add/Remove) Primary Actors : , Staff Pre-Condition : To add any book that book should be part of the requisition list and to delete the book the book must be part of the library. Main Scenario 1. The staff or to the system. 2. If is successful then to add a book the staff or must search for the book. 3. If the book is not found then it is checked in the requisition list. 4. If the book is not currently available and is part of the requisition list it can be added to the book database. 5. To remove a book it is again searched in the library system. 6. If it is found it should be checked in borrower_list. 7. If it is not in the borrowed list it can be removed. Alternate Scenarios 1. If the is unsuccessful then staff should re- themselves. 2. If a book is to be added and on search it is already found it should not e added again. 3. If book is to be removed and on search it is not found and is also not part of borrowers_list then there is any need to remove it.



SITRATOR

Search book Check book in requisition

list Add book if in req-list STAFF

Remove book in rem-list Re- for failed

Do not add book if already in list

STUDENT

5. Use Case #5 Report Primary Actors , Staff Pre-Condition : To generate any report the staff or should be ed with the library and to generate report on any book or student they should be part of the library system Main Scenario 1. The staff or s to the system, 2. To generate report on defaulters the staff or should first search for that student. 3. If the student is found then he can be checked in the defaulters list. 4. To generate report on borrowed books the staff or must search for that book. 5. If found that book can be checked in the borrowed books list. 6. To generate report on requisition list of book the he staff or should first search for that book. 7. If book is not found then it should be checked in the requisition list. Alternate Scenarios 1. If the is not successful then staff or should go to the registration page. 2. If student is not found after search he should be re-ed. 3. If book is not found then that book should be added again before checking it in the borrowers list.



SITRATOR

Search student Generate defaulter report STUDENT Search for book Generate re-list report

STAFF Generate borrowed books report

Re- for failed

6. Use Case #6 Primary Actors: , Staff, Student Pre-Condition: If the student or staff or wants to then he should have been first ed. Main Scenario 1. To the student or staff or should first open the page. 2. They should then enter their ids and s. 3. Once the id and are verified they are moved to the options page where they can search, view and perform other operations. Alternate Scenario 1. The fails after entering and . 2. It is the responsibility of the to see that all staff and students are properly ed and can to the system

Open screen SITRATOR Enter id Enter STUDENT Choose options if successful STAFF

Re- if wrong data Re- for failed

7.

Use Case #7 View/Edit Primary Actors: , Staff Pre-Condition: To view the details of any book or edit book details that book should be part of the library database. To view or edit student or staff details that student or staff should be part of the library database. Whoever is viewing or editing should be ed with the library. Main Scenario 1. To view details or edit details of any book the or staff should first to the library system. 2. If successfully they must search for that book by putting book id or title or isbn. 3. If the book is found they should enter book id to view the details and also edit it. 4. To view details or edit details of any student or staff the or staff should first to the library system. 5. If successfully they must search for that student or staff by putting student id or staff id. 6. If the student or staff is found they should enter student id or staff id to view the details and also edit it. Alternate Scenarios 1. If fails the should re- that staff 2. If book search is unsuccessful then that book cannot be viewed or edited. 3. If staff search is unsuccessful then that staff member cannot be viewed or edited.



SITRATOR

Search student/staff View/edit student/staff

Search for a book STUDENT View/edit book details STAFF

Re- for failed

Add book/student/staff if search fails