Professional Documents
Culture Documents
for
Library Automate
List of Figures
Figure No. Description Page
Figure 1.0 Login Class Diagram 52
Figure 2.0 Dashboard Class Diagram 52
Figure 3.0 Catalogue Class Diagram 53
Figure 4.0 Borrowers Class Diagram 53
Figure 5.0 Book Issuance Class Diagram 54
Figure 6.0 Return Book Class Diagram 54
Figure 7.0 Books Class Diagram 55
Figure 8.0 Report Class Diagram 55
Figure 9.0 Access Role Class Diagram 56
Figure 10.0 User Account Class Diagram 56
Figure 11.0 Authentication Class Diagram 57
Figure 12.0 Entity-Relationship Diagram 65
Figure 13.0 Login Sequence Diagram 66
Figure 14.0 Dashboard Sequence Diagram 66
Figure 15.0 Catalogue Sequence Diagram 67
Figure 16.0 Borrowers Sequence Diagram 68
Figure 17.0 Book Issuance Sequence Diagram 69
Figure 18.0 Return Book Sequence Diagram 70
Figure 19.0 Books Sequence Diagram 71
Figure 20.0 Reports Sequence Diagram 72
Figure 21.0 Access Role Sequence Diagram 73
Figure 22.0 User Accounts Sequence Diagram 74
Figure 23.0 Book Classification Sequence Diagram 75
Figure 24.0 Login Interface 76
Figure 25.0 Dashboard Interface 76
Figure 26.0 Catalogue Interface 77
Figure 27.0 Borrowers Interface 77
Figure 28.0 Borrowers Interface – Add New Borrower 78
Figure 29.0 Borrowers Interface – Deactivate Borrower 78
Borrowers Interface - Borrower's Information and Borrowing
Figure 30.0 79
History
Figure 31.0 Book Issuance Interface 79
Figure 32.0 Book Issuance Interface – Search Borrower 80
Figure 33.0 Book Issuance Interface – Search Books to Borrow 80
1. Introduction
1.1. Purpose
This document aims to present the design and progress of Library Automate for Trinidad
Municipal College project. This further explains the description of the software system design. The
general structural designs as well as the current project status are highlighted in this report.
1.2. Scope
This document describes the system design for the Library Automate for Trinidad Municipal
College. It describes how the application will be constructed, by specifying the components to be
used, how they will be organized in relation to each other, and the general principles of the
application's internal construction:
Page | 49
Software Design Description
Library Automate
Page | 50
Software Design Description
Library Automate
2. References
[1] Analee E. Mayo, Public High Schools Online Library System PHOLS, February 2016
[2] S. M.Mojapelo and D. Luyanda, “Information access in high school libraries in limpopo
province,south africa,” South African Journal of Libraries and Information Science, vol. 80, no. 2,
2015.
[4] By Hugh E. Williams, David Lane, Web Database Applications with PHP and MySQL:
https://www.computer.org/csdl/magazine/pc/2006/01/b1025/13rRUxlgxLD
[7] IEEE Std 1058-1998 (Revision and redesignation of IEEE Std 1058.1-1987, incorporating
Page | 51
Software Design Description
Library Automate
3. System Architecture
Page | 52
Software Design Description
Library Automate
3.1.3. Catalogue - A class diagram that depicts the structure of functions in retrieving books
specified by the user.
3.1.5. Book Issuance – A class diagram that depicts the structure of functions in processing
books to be borrowed.
Page | 54
Software Design Description
Library Automate
3.1.7. Books – A class diagram that depicts the structure of functions in managing books’
information.
Page | 55
Software Design Description
Library Automate
3.1.9. Access Role – A class diagram that depicts the structure of functions in managing different
access roles and its access rights.
Page | 56
Software Design Description
Library Automate
3.1.11. Authentication - A class diagram that depicts the structure of functions in authenticating
users who logs in to the system.
Page | 57
Software Design Description
Library Automate
4. Data Design
Page | 58
Software Design Description
Library Automate
Page | 59
Software Design Description
Library Automate
4.1.5. Books
Page | 60
Software Design Description
Library Automate
Page | 62
Software Design Description
Library Automate
Page | 63
Software Design Description
Library Automate
4.1.11. Users
Page | 64
Software Design Description
Library Automate
Page | 65
Software Design Description
Library Automate
5. Detailed Design
Page | 66
Software Design Description
Library Automate
Page | 67
Software Design Description
Library Automate
Page | 68
Software Design Description
Library Automate
Page | 69
Software Design Description
Library Automate
Page | 70
Software Design Description
Library Automate
Page | 71
Software Design Description
Library Automate
Page | 72
Software Design Description
Library Automate
Page | 73
Software Design Description
Library Automate
Page | 74
Software Design Description
Library Automate
Page | 75
Software Design Description
Library Automate
Page | 76
Software Design Description
Library Automate
Catalogue is the page where the users of the system including students and faculty can
search books throughout the Trinidad library. The user may select certain criteria in searching the
books they desire.
Borrowers’ page is intended for managing borrowers’ information. List of borrowers will be
loaded once the page displays.
Page | 77
Software Design Description
Library Automate
This is the part of borrower’s page where the authorized users can borrower’s information.
If the user wants to deactivate borrower’s information record, a message box will prompt as
confirmation for deactivation.
Page | 78
Software Design Description
Library Automate
Users can also view borrower’s entire information, including the books borrowed history
and library visit logs.
Book issuance page is used for processing books to borrowed inside the library.
Before the user selects books to borrow, user must search first for the borrower’s
information. Afterwards, click select button.
Page | 81
Software Design Description
Library Automate
Transaction number is needed for the user in order to process returned book. This is the
part where the user can look for the list of active borrowing transactions waiting to be processed.
Once transaction number is set, borrower’s information and books borrowed will be
displayed on the page. User must select books to be returned before processing
Page | 82
Software Design Description
Library Automate
Books page is where the user can manage books information. All active books are loaded
once books page is loaded.
To add new book information, the must click add and a form will appear where fields for
book’s data are to be filled-in.
Page | 83
Software Design Description
Library Automate
If the library personnel decide to deactivate book information record, the user must click
delete icon button. If the book is about to deactivate, the user must select reason for deactivation.
Library personnel/users can also view the entire book’s information and its list of borrowers.
Page | 84
Software Design Description
Library Automate
To generate reports, user must click report menu to redirect to report page. Report page
contains different reports: Borrowing Transactions, Library Visitors, Borrowers, Items, and
Inventory. For Borrowing Transactions report, the user can select unreturned and overdue status
for filtering.
To generate list of library visitors, user can select fiscal year and semester or display all
active library visitors for filtering.
To generate list of borrowers, user can select most issuing borrowers or borrowers without
issue options for filtering.
To generate list of items, user can select the following options for filtering: Frequently Used
Item, Less Issued Item, Items Not Issued, and Recently Added Items.
Page | 86
Software Design Description
Library Automate
To generate list of items, user can select the following options for filtering: Frequently Used
Item, Less Issued Item, Items Not Issued, and Recently Added Items.
Access role page is intended for managing different access roles and setting access rights
to each access role. Different access roles are loaded once the page is loaded.
Page | 87
Software Design Description
Library Automate
To add new access role, click add new button found on access role interface.
System also includes deactivation feature for unwanted access role record.
Page | 88
Software Design Description
Library Automate
Access rights page is intended for setting authorized access for each and every access
roles in the system.
User accounts are being managed under user accounts page. All active users are
displayed once user account page is loaded.
Page | 89
Software Design Description
Library Automate
To add new user account, click add new button on user account page and fill-in necessary
information in creating user account.
Page | 90
Software Design Description
Library Automate
Book classification page provides the list of classification to every book in library. Book
classification page can set new book classification and can also deactivate book classification
record.
The monitoring feature of “library automate” for every library visitors uses RFID technology.
Student’s id is built from rfid and must be tapped on the rfid reader to log its date and time of visit.
In the screen, student’s information and photo will appear including the status whether it’s IN or
OUT.
Page | 91