In this report, library management system functionality of Globe Library will be discussed based on ER, relational model and sample screen diagram. The computerized library management system will adjust its design components based on the verification profile. The authenticated services are attached to its variation form for maintaining effective design operation. By allocating requirements from the case study, diagrams have been developed in this report. specification is the main aspect of these allocated requirements, which will be delivered as per specification.   

Entity relationship diagram

Figure 1: ER diagram

Entity relationship diagram represents the relationship of different entities based on a database. A detailed logical structure of the library management system database has been controlled by the database design. There are different attributes and entities, which are related to each other with specific conditions. Only generated activities based on the documentation are attached by the content management control. By maintaining functional activity, every attribute is adjusted by the event data. Entities mentioned in this diagram are:

Book

Since Globe library is related to community libraries, every genre of books should be present in the library section. Meeting rooms are also initiated by the computerized system, which accommodates every featured book. Rich collections of books are specified by the attributes mentioned in the diagram. Functional efficiency of this Computerized library management system can only be enhanced if the books are structured well within the database. These attributes of books are stored by a significant transaction element, which manages the entire structure. Soria et al. (2017, p.78) have stated that the format of the database development relies on the system adaptability of this computerized system.     

Verification

In case verification, only the authentication IDs is controlled by the design format of the database. A specific subject category is verified by the system related to the database. Registration number of books and users are also important for verifying each of the database mechanisms. In order to control the system requirement, there are specific transaction elements, which accommodate every design feature in system components. Verification profiles are important to check the authentication of users. Location of the exact database formats are installed within the design feature of suitable books. 

Staff 

Staff controls library members who track records of every activity. The staff members maintain reservation of transactions and conferences. Requirements of barcodes and specification controls are supported by this entity. Soria et al. (2017, p.78) have stated that attributes of this entity are controlled by systematic adjustments of collectable components. Copies of the books are preserved from the particular system information that is controlled by the staff entity. Only the main management modules are adjusted by the staff entity who controls the entire design feature.    

Readers 

By verifying the authorization, membership elements are attached by the control units that are adjusted by database developments. Only the data racks that are maintained by users attach the information about the membership elements. Not only the library functionality but also the information elements are controlled by the system. Every information about the attached profiles are controlled by the readers based on the availability.  Pham et al. (2019, p.224) have mentioned that reservation of the books are controlled by the categorical specification, which are attached by membership profile. Readers can access every detail of the book information by fetching out the information from datasets.     

Relational model

Figure 2: Relational model

System requirements of the database functionalities are related to the dataset models in a specific format. Only the maintenance department within the structural format adjusts the common control functions. In the case of functional attributes, every design component is featured by the authentication service elements. Moran and Morner (2017, p.545) have mentioned that relational models adjusted overall configurations that are maintained in specific format. Database functionalities within the data warehouse are maintained by the specific design format of specific channels. A fixed communication profile is adjusted by the information profile and is controlled by the design analysis. 

Library members can maintain physical components within the database feature. As a result, all the system elements are functioned by the design analysis components. Copy of the booking information is aligned by the control elements that are attached with the database developments. Only specific library control opportunities are maintained by the distribution format. Abdullah et al. (2019. p.298) have stated that database membership according to the system atmosphere relies upon the control elements that are maintained in a control channel operation. Searching control designs are accommodated by the unique barcode functionality, which is maintained by the databases. The development components are controlled by the authentication service profile. The system will automatically read the system elements that are part of the physical design profile. 

In case of every design profile, attached components are designed to form a specific channel. Mainly the network profiles are accommodated by the subject category that is part of distribution profiles. Only the authentication service profiles related to database functionalities are accommodated within the control units. Configurations are attached within the relational database in the membership elements. Elementary control functions are maintained by distributed profiles that accommodate every designed component. Not only the distributed profiles but also the relational databases are attached within the network features. Degott et al. (2019) have stated that every controlling element is featured within the authentication service profile. As a result, conferences related to the main rooms are allocated within the distributed profiles. Specific channels control library portal developments. 

In terms of maintenance, every user features reservations of the books. The design formats are adjusted by the membership profiles that are available within the staff membership. Searching of the book categories are part of the library functionality that are allocated with the limitation profiles. Pham et al. (2019, p.224) have mentioned that based on the profile elements, distributed service properties are attached with the identification services. Advanced booking system is adjusted by the searching facility that is related to the configuration profiles. Communication channels are distributed by the library management functions. In case of distributing the database feature, requirements are allocated to the portal itself. Categorical functionality maintains the control elements that are distributed by the authentication service profile. 

Sample screen

Figure 3: Sample screen

The sample screen provides detailed information about the System Specification that identifies the categorical specification. Only the categorical specifications are allocated within the specified program based on the relational database. There is a case study that provides a library functionally, which manages different attributes into the same controlling units. Only related information about the System Specification configurations are attached within the user information. Reiss et al. (2018, p. 554) have commented that System Specification capability holds specific information related to the physical system. There are different attributes present in the design profile, which accommodates every design feature in the user interface. The interface will adjust every design component based on the development features.

In the reservation profile, design components will adjust the requirements based on the system profile. The record of the transactional profile is attached by the functional dependency. Only the improved services are designed in the user interface. Only the improved services are controlled by the application format, which has redesigned the file format. Soria et al. (2017, p.78) have stated that based on the common user profile registration process has been adjusted by the systematic elements. Only the relational tables are adjusted within the design feature. By default the System Specification ambience accommodates the interface components that are controlled in a different format. By considering all of the library associated factors, main design components are controlled by the identification requirements. Data modelling and database designs are featured by the same service profile that is controlled by the control units.      

System information related to the desired profile components that are controlled by the transaction profile. Portal development features are maintained by specific formats that are installed in a control channel. Only the mainframe application format is installed within the design components. Therefore only the user interface related to system adjustment are controlled by the design format in this context.  Library functionality attributes are maintained by specific design components (scirp.org, 2021). There are different transactional profiles, which are managed by design opportunities within the database developments. Categorical specifications are maintained by the occupancy level requirements. Based on the searching category each copy of the user interface designs are attached by the application format.  

Not only the copy of the book items but payment and refund statuses are also featured in the UI. Configuration profiles are linked directly to the database server that is related to the specific library functionality. In terms of identification profile, common channelling profiles are distributed by the detailed UI functionality. Based on the membership profile, only control elements are featured by rack number elements.     

Conclusion

In terms of this modelling report, the diagrams adjust a detailed structure of library management functionality. ER diagram, relational model and sample screen is designed for providing a better overview of the library management functions. Only the main accessibility components are adjusted within these diagrams. Based on the identification number, specific conference rooms are attached by the design elements. Only the available design opportunities are accommodated within the interface control elements. Membership processes are controlled by the functional elements with a searching mechanism.

References

Book

Moran, B. B., & Morner, C. J. (2017). Library and information center management. ABC-CLIO.

Journals

Abdullah, A., Nasir, N. E., Mei, L. C., & Lee, K. M. (2021, March). Automating secondary school libraries: a web-based library management system. In IASL Annual Conference Proceedings (pp. 193-202). 

Degott, C., Borges Jr, N. P., & Zeller, A. (2019, July). Learning user interface element interactions. In Proceedings of the 28th ACM SIGSOFT International Symposium on Software Testing and Analysis (pp. 296-306). [Online] 

Pham, Q., Graham, G., Carrion, C., Morita, P. P., Seto, E., Stinson, J. N., & Cafazzo, J. A. (2019). A library of analytic indicators to evaluate effective engagement with consumer mHealth apps for chronic conditions: scoping review. JMIR mHealth and uHealth, 7(1), e11941. [Online] 

Reiss, S. P., Miao, Y., & Xin, Q. (2018). Seeking the user interface. Automated Software Engineering, 25(1), 157-193. 

Soria, K. M., Fransen, J., & Nackerud, S. (2017). Beyond books: The extended academic benefits of library use for first-year college students. College & Research Libraries, 78(1), 8.