Documentation Of A Library System Back End

Project Planning

1.1. Gantt Chart

1.2. Trello Board

Task 2 – Requirements Documentation

The librarian late fine should be calculated automatically in the information system after entering the details off the user and a notification message should be popped up showing the amount that is due. The manual calculation of the late fine can cause error in the system and thus it is designed to automate the management process.

Task 3 – Use Case Diagram

Task 4 – Use case textual description

Name Reserve Book
Version UC_1
Goal The use case defines the process involved in borrowing a book.

Summary The user can select the reserve book option to borrow a book from the library. The reserve option is followed by many of the sub processes such as verification of the user, paying late fine for returning the book after the due date.

Actors The primary actor of the library management system are the user, librarian and the information system.

Pre-conditions For borrowing a book from the library the user should have a valid user account and should successfully pass the verification process. The book. The book searched by the user from the catalogue should also be available in the library and can be allocated to the user requesting for it.

Triggers The user needs to select a book for borrowing it from the library.

Basic course of Events The user logs in into the system and searched for the book and selects the book he/ she wants. The reserve book option is checked and on selection of the option the information system verification the details of the user. The user can cancel the reservation and reserve from remote location. For remote reservation the user needs to physically visit the library to pick up the book. The librarian allocated the book and assigns a due date for returning the book. The user needs to return the book within the due date or else a fine is charged. For the next borrow of book the user needs to pay the fine.

Alternative Paths The user can visit the library and if the book is not available he can put a hold and wait for the book to be released.
Post-Conditions After the book has been allocated the database of the information system is updated with the details of the book and the return date for maintaining a transparency on the system.

Business Rules If the late fine is greater than $25 then the account of the borrower needs to be suspended. The borrower account can be created by the librarian and the details of the borrower should be recorded.
Notes Before issuing the book the librarian should check the details of the other users putting a hold request on the book and it should be allocated to the allocated to the user first claimed for the book.

Task 5: Sequence diagram

Task 6: Class diagram of the library system

Task 7: Activity diagram

Task 8: User interface design

Login, logout, forgotten password and registration pages for library admin

Task 9: Test case generation

Number Test name Description Scenario Precondition Input Expected Output
1 Verification of login It is important to verify the authentication for maintaining the security of the information system. The user logs in the system for using the different service provided by the library information system. User have a valid username and password Username and password User able to login

2 Availability checking The database should be connected with the information system for checking the availability The user checks the books available in the library The librarian should have marked the status of the books The book name from the user The details of the book with the status of availability.

3 Validate member The books allocated to the user should be a validate member The details of the user should be verified before allocating the book such as fines, borrowing limits, etc. The user should be a member and have an active user account for passing the member validation test The user account should act as an input The user have no previous dues and has not reached the limit for successfully borrow a book.

Bourque, P. and Fairley, R.E., 2014. Guide to the software engineering body of knowledge (SWEBOK (R)): Version 3.0. IEEE Computer Society Press.

Braude, E.J. and Bernstein, M.E., 2016. Software engineering: modern approaches. Waveland Press.
Fitzgerald, B. and Stol, K.J., 2017. Continuous software engineering: A roadmap and agenda. Journal of Systems and Software, 123, pp.176-189.
Petersen, K., Vakkalanka, S. and Kuzniarz, L., 2015. Guidelines for conducting systematic mapping studies in software engineering: An update. Information and Software Technology, 64, pp.1-18.