MITS5501

Software Quality, Change Management and Testing

Student Name:

Student Id:

1
Table of Contents

Executive summary.........................................................................................................................3

System description...........................................................................................................................3

Management....................................................................................................................................4

Documentation.................................................................................................................................5

Standard practices, convention and metrics.....................................................................................5

Peer reviews plan.............................................................................................................................7

Testing.............................................................................................................................................8

Problem reporting and corrective actions........................................................................................8

Tools, techniques and methods........................................................................................................9

Configuration management plan......................................................................................................9

References........................................................................................................................................9

Appendices....................................................................................................................................10

2
Executive summary

The software quality assurance plan is where the documentation of each and every step that has
to be followed to guarantee a high-quality end result for the customer can be found. The use of
this technique for ensuring the quality of software will result in the delivery to the customer of a
library management system that is not only completely functional but also has an easy-to-use
interface.

The purpose of the documentation is to guarantee the dependability of every feature and
configuration option inside the application. This is a heads-up estimate that will help us save
time and effort in the long run by enabling us to foresee future challenges and prepare
appropriately. In other words, it will give us a head start. The client will be able to ascertain,
based on the information included in this report, whether or not the work being performed meets
his expectations.

System description

Introduction

A library management system is a piece of software that is intended for use by library networks
that are on the smaller or medium-sized end of the spectrum. It serves as a computerized
framework that is used by librarians for the purpose of administering the library and keeping
track of various types of data. Maintenance on books, returns of books, addition of new books,
enrollment of new students, and other similar tasks. This framework also includes modules for
managing books and students. The module for managing books keeps track of how many
individuals are borrowing books from the module for managing students, and it lists all of the
students alphabetically.

3
Scope

Students and faculty at the university library will have access to books, information about book
viewing, and other services thanks to the library management system that will soon be deployed.
The proposed library management system should provide for the following features.

The primary objective of this approach is to assist users in keeping better time logs so that they
may better use their time and resources. The system also produces many different kinds of data
for many different applications.

The books and participant records that are needed for this computerized system will not be in
short supply, as is sometimes the case with systems that do not use computers. In addition, there
is a summary section accessible via the Library Management System.[5]

Reports, such as patron lists, book inventories, and checkout/return summaries, may be generated
by users who have administrative capabilities and are granted access to the system. The
librarians will be able to handle the library in a way that is both easier and more efficient than
they could if they had to do it manually thanks to both of these modules.

The main objectives of this system is:

 The publication of a book online.

 A section for librarians to suggest titles for purchase.
 Public library advocacy column.
 A login website where students may see what books they have been assigned and when
they are due back.
 A searchable bookshelf column.

Management

Clients and developers make up the group that is accountable for monitoring the quality of our
product, and the typical runtime of a library management system is being used by us as a
benchmark for comparison. [1]

4
  Joint review

It is the responsibility of every member of the team to take these, and they do so by accumulating
information from the customer, the developer, and the other members of the working people.
This will assist us in identifying any issues that may still be present in the application.

 Process review
 They are only accessible to the client and the coder. With your help, we will be able to
ensure that all of the features are operating as intended.
 Customer review

In order to accomplish this objective, both employees of the library and students will be
responsible for operating the system. This will give us an idea of how long it takes an individual
to get a handle on the framework that we have developed.

Documentation

These are the bare minimum of project documentation requirements.

 A Plan for Developing Software

 Plan for Testing
 Requirements Documentation for Software (SRS)

Standard practices, convention and metrics

User interface

 The first page was shown for logging either student or staff.
 After log in successfully users can use the system according to their privileges.
 Students can search, or publish the book.
 Staff can check update and edit the books and their details also they are check the
requested student is clear from library dues or not.

5
Design guidelines

 This module is used by the library's patrons, who are the librarians. To determine the
user's privileges, they must log in to the server using a unique identifier and password.
 When users log in, they'll be able to use a number of different features.
 Books may be tracked, along with searches, additions, and changes, using this module.
Furthermore, it may generate and print the book's barcode for the librarian to affix to the
book's cover.
 change or add a book's publisher with ease. The word "publisher" is used when a new
publication is being registered.
 The return module just requires the librarian to scan the book's barcode and double-check
the renter's information.
 The rental return process will be completed if all data is correct and no fees have been
assessed.

Figure 1: Working module for Librarian

6
 Figure 2 module for publish maintenance

Figure 3 student module

Peer reviews plan

Both the end user and the developer of the library management software will participate in an
analysis of the software's performance. The establishment of a basis for the timetable depends on
the completion of each system page. The system is constructed up of a wide variety of distinct
elements all working together. When a module is finished being developed, the customer and the
developer could meet together to evaluate whether or not the page works as it was supposed to.
In the event that it does not, they may decide to make any required adjustments.

7
Testing

Table 1 testing plan for library management system

Class Test plan Description

Class is related to The user will log into the The user will enter their ID and
logging. system. password.
The user edits the details of The user should be a staff member and
Edit the book details.
the book. edit the book details.
The user should be a staff member and
Add a new book User adds new book
add the new book.
The user should be a staff member and
Generate barcode User request for barcode
request the system generate a barcode.
User request for book User log in with their ID and request a
Book reservation
reservation book reservation.

Problem reporting and corrective actions

The library management system problems along with their corrective actions

Experts in their field:

In order to build a digital library, an organization has to employ knowledgeable people.

Investment for the Future:

To efficiently maintain digital materials and provide instant access to users, the digital library
needs substantial financial support.

Security of Ideas and Creations:

Respect for copyright and IP rights is a major barrier to institutional change.

8
Tools, techniques and methods

Tools are

 Python
 Internet

Techniques

Agile model can be used to develop a software.

Configuration management plan

This is the scheme:

 Planning and details

 Design and analysis
 Implementation
 Testing
 Launching
 Maintaining

References

[1]. Lewis, W. E. (2017). Software testing and continuous quality improvement. CRC press.

[2]. Kamble, V. T., & Raj, H. (2012). Open Source Library Management and Digital library
software.

[3]. Chucks, E., Sani, Y., & Moses, T. (2020). A review of information and communication
technology (ICT) facilities for the implementation of virtual library management
system. International Journal of Scientific and Engineering Research, 11, 448-460.

9
[4]. Shaw, J. N., & De Sarkar, T. (2021). A cloud-based approach to library management
solution for college libraries. Information Discovery and Delivery, 49(4), 308-318.

[5]. Satoglu, S. I., Ustundag, A., & Kilinc, M. S. (2012). Value of RFID in library management
system. In The value of RFID: Benefits vs. costs (pp. 155-167). London: Springer London.

[6]. Khan, S. A., & Ayesha, G. (2022). Key features of information management systems (IMSs)
for automation in university libraries: a view point of information professionals in
Pakistan. Library Hi Tech, 40(6), 1606-1626.

[7]. Randhawa, S. (2013). Open source library management softwares. E-Library Science
Research Journal, 1(7).

[8]. R. Earnshaw, “State of the Art in Digital Media and Application”, Springer Briefs in
Computer Science, (2017).

Appendices
Have hope that once the overhaul is
complete, the problems with the old
system will be addressed. The
"LIBRARY MANAGEMENT
SYSTEM" approach became
digital to cut down on human error
and boost output. Human labour
minimization is a primary objective
of this project.

10