FINAL PROJECT PROPOSAL _ BATCH 93

LIBRARY MANAGEMENT SYSTEM

HND in Computing & Software Engineering

ICBT Campus
2021
pg. 1
 Acknowledgement

In performing our final proposal, we had to take the help and guideline of some
respected people, who deserve our greatest gratitude. The Completion of this
project gives us much pleasure. We would also like to expand our deepest
gratitude to all our lectures for giving us a good guideline for project throughout
numerous consultations. We would also like to expand our deepest gratitude to
all those who have directly and indirectly guided us in writing this project
proposal.

Many people, especially Team members of Int Elegance itself, have made
valuable comments, suggestions and innovative ideas on this proposal which
gave us an inspiration on to improve our project. We thank all the people for
their help to complete our project proposal.
 Table of Content

Acknowledgement................................................................................................................................ 2
Introduction......................................................................................................................................... 4
Organization Details............................................................................................................................ 5
Problem Statement.............................................................................................................................. 6
Proposed Solution................................................................................................................................ 8
Aim and Objective............................................................................................................................... 9
Justification to the Solution.............................................................................................................. 10
Scope of the system............................................................................................................................ 11
Limitation........................................................................................................................................... 12
Lack of user Involvement.............................................................................................................. 12
Limited time................................................................................................................................... 12
Multiple roles for a member......................................................................................................... 12
Other problems.............................................................................................................................. 12
Methodology....................................................................................................................................... 13
Literature Review.............................................................................................................................. 15
Functionalities of the proposed solution.......................................................................................... 16
Resource Requirement and allocation.............................................................................................. 18
Team Structure............................................................................................................................... 18
Roles and Responsibilities of the team......................................................................................... 19
Hardware Requirements............................................................................................................... 22
Software Requirements................................................................................................................. 22
Gantt chart......................................................................................................................................... 23
Technologies planned to use in the system........................................................................................ 24
Java................................................................................................................................................. 24
HTML............................................................................................................................................. 24
PHP................................................................................................................................................. 24
SQL Server..................................................................................................................................... 24
Risk Analysis...................................................................................................................................... 25
Referencing........................................................................................................................................ 26
 Introduction

A library may be a collection of sources of data and similar resources, made accessible to an
outlined community for reference or borrowing. It provides physical or digital access to
material and perhaps a physical building or room, or a virtual space, or both. A library's
collection can include books, periodicals, newspapers, manuscripts, films, maps, prints,
documents, microform, CDs, cassettes, videotapes, DVDs, Blu-ray Discs, e-books,
audiobooks, databases, and other formats. Libraries home in size from a couple of shelves of
books to many million items.

***To be the welcoming heart of us.

community where all come to
learn, discover, create, and connect. ***

Library Management System is an application which refers to library systems which are.
generally small or medium in size. It is used by librarian to manage the library using a
computerized system where he/she can record various transactions like issue of books, return of
books, addition of new books, addition of new students etc. Books and student maintenance
modules are also included in this system which would keep track.
of the students using the library and a detailed description about the books a library
contains. With this computerized system there will be no loss of book record or member record
which generally happens when a non-computerized system is used. In addition, report module is
also included in Library Management System. If user’s position is admin, the user can generate
different kinds of reports like lists of students registered, list of books, issue and return reports.
All these modules can help librarian to manage the library with more convenience and in a more
efficient way as compared to library systems which are not computerized.
 Organization Details

Organizational Logo:

Organizational Name: Global Technologies

Core values:
Being a warm and welcoming place for community members to gather.
Being actively engaged in the life of the community.

Vision:
To be the welcoming heart of our community where all come to learn, discover,
create, and connect.

Mission:
The Belleville Public Library is a strong community partner providing programs
and services that bring people together, foster creativity, and encourage lifelong
learning. We preserve our storied past, enrich present lives, and prepare for an
ever-changing future.
 Problem Statement

Proposed system is an automated Library Management System. Through our software user
can add members, add books, search members, search books, update information, edit
information, borrow, and return books in quick time. Our proposed system has the following
advantages.

 User friendly interface

 Fast access to database
 Less error
 More Storage Capacity
 Search facility
 Look and Feel Environment
 Quick transaction

WHAT IS WRONG The library does not have automated library

management system.

WHERE IT To control the current library

HAPPENED
WHEN IT OCCURED The library cannot be controlled.

TO WHAT EXTENT The library wants a properly working management

IT HAPPENED of the library using computer.

HOW DO WE DO IT After using the System, the library performs very

well.

Important problem statements

∙ File lost.
When computerized web application system is not implemented file is always lost
because of human environment. Sometimes due to some human error there may be a loss
of records.

∙ File damaged
When a computerized web application system is not their file is always lost due to some
accident like spilling of water by some member on file accidentally. Besides some natural
disaster like floods or fires may also damage the files.
∙ Difficult to search record.
When there is no computerized web application system there is always a difficulty in
searching of records if the records are large in number .
∙ Space consuming
After the number of records become large the space for physical storage of file and
records also increases if no computerized system is implemented.
∙ Cost consuming
as there is no computerized web application system the to add each record paper will be
needed which will increase the cost for the management of library.

Proposed Solution

The problem was that the library did not have an appropriate system, so handling the library was
difficult. The issue can therefore be solved by developing a system that manage this library .there
are some solutions for the problem.

It reduces the risk of paperwork such as file lost, file damaged and time consuming. It can help
user to manage the transaction or record more effectively and timesaving.

 There will provide login button on the system.

 System will be able to register new library members with the system.
 The system will eliminate every member of the library.
 The system will see the books in detail, and it is in the library.
 The system Will provide the option to see the part's subtleties.
 The system will provide the option to monitor the process of the books.
 The system will provide the option to monitor the return of the books.
 Book details like authors, number of copies totally maintained by library, present
available number of books, reference books, non-reference books etc. all this
information can be made handy.
 Time consuming is low, gives accurate results, reliability can be improved with the
help of security.

User Requirements
The User Requirements describes the business needs for what users require from the system.
User Requirements are written early in the validation process, typically before the system is
created. They are written by the system owner and end-users, with input from Quality
Assurance.

 The user wants to log in with a username and password.

 The user needs the automated system.
 ∙The consumer needs to borrow books.

System Requirements

System requirements are the configuration that a system must have for a hardware or software
application to run smoothly and efficiently. Failure to meet these requirements can result in
installation problems or performance problems.

 By title, author, subject category and date of publication, any member of the library
should be able to search for books.
 For however many books a member can check out, a regular restriction should be
enforced.
 A regular restriction should be issued for how many days a member should keep a book.
 The scheme should be able to recover fines on books returned after the due date.
 It should be possible to reserve books for members who are not currently eligible.
 Each book will have a unique identification number and other information.
 There might be more than one copy of a book online, and it should be possible for library
members to check out and reserve any copy.
 Aim and Objective.

The library management system is a software to manage manual functions of a library. The main
aim of this project is to provide an easy to handle and automated library management system.

This project also provides features and an interface for maintaining librarian’s records, student’s
history of issues, and fines. The owner can easily update, delete, and insert data in the database
with this project. The software helps to manage the entire library operations from maintaining
book records to issue a book. In addition, it allows streamlined management of fine details of
books such as author name, edition, and many other important details. So, it is easier to search
for books and find the right materials for students and the librarian.

The electronic management via the software is essential to track information like issue date, due
date, who has borrowed any material, etc. The system is developed and designed with an aim to
facilitate efficient management to the schools to manage a modern library with accurate data
management.

The objectives are as follows:

 Online book issue

 Request column for librarian for providing new books.
 A separate column for digital library
 Student login page where student can find books issued by him/her and date of return.
 A search column to search availability of books.
 A teacher login page where teacher can add any events being organized in the college and
important suggestions regarding books.
 Online notice board about the workshop.
 Justification to the Solution

Now world is digital era. so, we need to connect with technology and digital things.
 In this digital world very, important thing is time. So, we need to do our software.
 much easier way.
 By the connecting the digital technology we can solve some human related errors.
 Through our web application we can increase the member’s satisfaction
 Library Automation reduces the drudgery of repeated manual efforts in library routine.
 we assure this method will reduce the physical management cost.
 out web application focus enhances advanced search, access, and retrieval of
 information.
 Digital libraries have reduced the burden of librarians as well as students.
 Physical library staff cannot find some early types of the books. But our solution will
 take better way to them.
  Our system reduced the burden of librarians as well as students
 Scope of the system

 Create distinct product users based on their roles and permissions.

 Authenticate users at their login.

 Provide the list of books the users can borrow.

 Facility to reserve books that are available.

 A status page for all users to view books reserved by them.

 Facility to cancel the reservation for a book made earlier.

 A status page for all users to view books borrowed by them, their individual due dates,
and their individual penalties if any.

 An interface to view and edit the own profile.

 Provide method for adjusting account settings such as passwords.

 Mechanism to reset the password in case user forgets it.

 Providing interface to add or delete books to staffs.

 Limitation

During the development of the project for we will have to expect certain challenges and
limitations that we will have to overcome.

Lack of user Involvement

When we are developing a system, the user’s involvement is important. Without their
involvement we will not be able to complete the system successfully. For those developers
and the user should have good relationship and they must be involved from the beginning of
the project and throughout the development until the deployment. In this case the users of the
system will be customers of the restaurant and the employees of that restaurant. Mostly the
role of the customer will have to be taken by the analyst and developing team and stay in
touch with the restaurant to complete the project successfully.

Limited time
The system we are planning to implement is quite a big system for our standard. Moreover,
this field is somewhat challenging and new to us as students. Therefore, it will take some
time to learn new techniques and technologies we are about to use in the development of the
system.

Multiple roles for a member

One of the major limitations for the development of this system is lack of advanced
programming concepts and knowledge. Knowing the risks and the size of the project; for
designing and developing a system like ours is a difficult task. As each member is assigned
with multiple roles, sometimes it will be difficult to concentrate on a particular role.

Other problems
Sometimes during the development of the project, we can expect other problems other than
mentioned above such as financial problems: sometimes to purchase certain things needed for
the project, internal problems within the group also can be expected due to certain
misunderstandings and other issues.

We as a group, will try to overcome these expected problems and complete the project
successfully.
Methodology

We are selected a methodology according to some requirements in below.

• Functional Decomposition: The methodology should have stages according to the

interrelated activities which activities which can be grouped into functional areas.
• Requirement changes: If required, methodology provides scope to change the
requirement.
• Manage Risks: Determined the risk is an important activity to develop a project.
• Iterative approach: Iteration allows refinement of requirement as well as design.
• Documentation: Methodology provide support for large documentation.
• Analysis and Design Support: A well-defined structure of the methodology helps for
analysis and designing to development process.
• Implementation: The system should be implemented as per plan.
• Testing Support: More testing, more reliable the product is.
• Object Oriented Approach: Object oriented concept will be used in developing the
project as it supports component reusability.

According to our opinion, the most suitable model to this patient Information Management
System is spiral design. The reason is mentioned as follows; Spiral model has four stages.
Software project repeatedly passes through these stages’ repetitions called coils.

Identification: This phase starts with the business requirement gathering at the base of spiral.
In later spirals as a teenager, identifying system requirements, changing demands and
requirements of all units performed at this stage.

It also includes as understanding of the system requirements of continue communication

between the client and systems analyst. In the final product, it has been developed in spiral
identified.

Design: Design phase begins with the conceptual design of the base spiral and architectural
design, logical design of the module, the design of the physical product and the final design
and subsequent spirals.
Build or construct: Construction phase refers to the production of the actual software on any
spiral. At the base of snail when the product only think and design are, opening POC (proof
of concept) developed at this stage to get feedback from customers.

Therefore, in these spiral clarity on the requirement and design details of a working model of
accumulation program called extracted with a version number. These buildings are sent to the
client for feedback.

Evaluation and Risk Analysis: Risk analysis includes identification, estimation and risk
control and management technique, such as leaks and schedule overruns viability. After
checking the accumulation, at the end of the first iteration, customers evaluate the software
and provide feedback.

Spiral Model Application

 Spiral Model is very widely used in the software industry as it is in synch with the
natural development process of any product i.e., learning with maturity and involves
minimum risk for the customers as well as development firms. Following are the
typical uses of Spiral model:

 When costs there is a budget constraint and risk evaluation is important

 For medium to high-risk projects
 Long-term project commitment because of potential changes to economic priorities as
the requirements change with time.
 Customer is not sure of their requirements which is usually the case.
 Requirements are complex and need evaluation to get clarity.
 New product line which should be released in phases to get enough customer
feedback.
 Significant changes are expected in the product during the development cycle.
 Literature Review

Our proposed solution is something new but similar systems are used in some countries. But
in Sri Lanka there are no ay specific system like this. At the time Sri Lankan government
trying to do this project. But it was a failure project, so that they are trying to renew the
project. So, our one is something new for here.

Our proposed system differs from this because our solution contains any devices. So, if
anyone need it, they can view, and use it. But instead from now they can access this web app
and save their time. Same time the process will be quick, thus they will get the response from
librarians as soon as possible.
 Functionalities of the proposed solution

In here we are having 3 interfaces,

i. User Interface
ii. Organization Interface (KCC)
iii. Workers Interface

User Interface

Users want to install our app.

User must get registered through their contact number, User will get a validation code
(including 4 digits)
After the validation they will enter to create their profile.

The data entry operator’s duty is to register the users to the system using user’s details such
as,
Username

User will be able to select required place.

• House
• Flats
• Schools/Institutes
• Office
• Regional places
Location share
If they share location user will get the confirmation message

User will be able to select the category of the dust bin which they want.
Organizational Interface

KCC member will get a message /alert from users, and they will send a message to workers.

Workers Interface

Workers will get a message /alert from KCC members.

KCC members will share the location to the workers.

Workers will reach the destinations.

After reaching the destination the worker will scan the barcode which is in the bin.

User can view the movement status of the workers through GPS.

User and KCC members will get the amount and the weight.

They must pay after 5 times.

Users can rate the workers.

Users can view DIY videos.

 Resource Requirement and allocation

Team Structure

Mr. Surendran
( Project Manager)

Mr. Infath Mr. Haisham Mr. Rifkhan Mr. Divagaran

(System Analyst & (Database Engineer) (Software Engineer) (QA Engineer)
DB Engineer)
Roles and Responsibilities of the team

Project Manager

 Identify and review program, space, and scope with end user for approval.
 Communicate budget, schedule, program assumptions and constraints to users.
 Ensure user program needs and requirements are being met.
 Ensure the needs of hospitals are being met.
 Determine project process, establish project team, and ensure understanding of roles and
responsibilities.
 Oversee agenda and documentation of project team meetings.
 Set-up and lead a series of meeting to review design drawings with department, users,
 Stanford entities, and landlords as necessary for approvals at schematic design, design
documents, and construction documents and coordinate any responses back to the
architect.
 Monitor team performance and intervene when necessary to ensure successful.
 delivery.
 Establish and monitor project schedule and ensure routine updates and reporting.
 Lead mitigation planning efforts for critical path items.

Database & Software Engineer

 Installing and upgrading the database server and application tools.

 Allocating system storage and planning future storage requirements for the database
system.
 Modifying the database structure, as necessary, form information given by application
developers.
 Enrolling users and maintaining system security.
 Ensuring compliance with database vendor license agreement.
 Controlling and monitoring user access to the database.
 Monitoring and optimizing the performance of the database.
 Planning for backup and recovery of database information.
 Maintaining archived data.
 Backing up and restoring databases.
 Contacting database vendor for technical support.
 Generating various reports by querying from database as per need.
 Managing and monitoring data replication.
 Determines operational feasibility by evaluating analysis, problem definition,
requirements solution development, and proposed solutions.
 Prepares and installs solutions by determining and designing system specifications,
standards, and programming.
 Improves operations by conducting systems analysis, recommending changes in
policies and procedures.
 Update job knowledge by studying state-of-the-art development tools, programming
techniques, and computing equipment; participating in educational opportunities.
 reading professional publications; maintaining personal network; participating in
professional organizations.
 Provides information by collecting, analyzing, and summarizing development and
 service issues.
 Develops software solutions by studying information needs; conferring with users;
studying system flow, data usage, and work processes; investigating problem areas;
following the software development lifecycle.

Quality Assurance

 Review requirements, specification, and technical design document to

provide timely and meaningful feedback.
 Create detailed, comprehensive, and well-structured test plans and test cases.
 Estimate, prioritize, plan and coordinate testing activities.
 Design, develop and execute automation script using open-source tools.
 Identify, record, document thoroughly and track bugs.
 Perform thorough regression testing when bugs are resolved.
 Develop and apply testing processes for new and existing products to meet
client needs.
 Liaise with internal teams (e.g., developers and products managers) to
identify system requirements.
  Monitor debugging process results.
 Investigate the cause of non-conforming software and train users to implement
solutions.
 Track quality assurance metrics, like defect densities and open defect counts.
 Stay up to date with new testing tools and test strategies.

System Analyst

 Defines application problem by conferring with clients, evaluating procedures and

processes.
 Develops solution by preparing and evaluating alternative workflow solutions.
 Controls solution by establishing specifications; coordinating production with
programmers.
 Validates results by testing programs.
 Ensures operation by training client personnel, providing support.
 Provides reference by writing documentation.
 Updates job knowledge by participating in educational opportunities; reading.
 professional publications; maintaining personal networks; participating in
professional organizations.
 Accomplishes information systems and organization mission by completing related.
 results as needed.

System Designer

 Designer solve business problems using information technology.

 Serve as change agents who identify the organizational improvements needed, design
systems to implement those changes and train and motivate others to use the systems.
 Specializes in designing and implementing information systems.
 Help programmers during system development, e.g., provide use cases, flowcharts, and
UML diagrams.
 Interact with software architect to understand software limitations.
 Plan a system flow from the ground up.
Hardware Requirements

Core i3 processor

4GB Ram

Software Requirements

Windows 10 or above operating system

Adobe Dreamweaver

SQL server
Gantt chart
 Technologies planned to use in the system.

Java
JAVA programming language used to develop Android applications. We are familiar with
some programming language such as HTML, C#, C++, to become comfortable working with
JAVA programming language and dive into Android app development.

To develop android application, we need a development environment to write and build

application.

HTML

HTML is the standard markup language for creating Web pages. It describes the structure of
Web pages using markup.HTML elements are the building blocks of HTML pages and
represented by tags.

PHP
PHP is a server-side scripted language designed for web development but also used as a
general-purpose programming language. PHP code may be embedded into HTML code, or it
can be used in combination with various web template system, web content management
systems, and web framework. PHP code is usually processed by a PHP
interpreter implemented as a module in the web server or as a Common Gateway Interface
(CGI) executable. The web server combines the results of the interpreted and executed PHP
code, which may be any type of data, including images, with the generated web page. PHP
code may also be executed with a command-line interface (CLI) and can be used to
implement standalone graphical applications.

SQL Server
We are using SQL Server,

• To crate database
• To maintain database
• To analyze the data through SQL Server Analysis Service (SSAD)
• To generate reports through SQL Server Reporting Service (SSRS)
• To carry out ETL operations through SQL Server Integration Services (SSIS)
 Risk Analysis

Risk Analyze

• Plan risk Management-The process of defining how to conduct risk management

activities for a project.
• Identify Risks- The process of determining which risk may affect the project and
documenting their characteristics.
• Perform Qualitative Risk Analysis-The process of prioritizing risks for further.
analysis or actions by assessing and combining their probability of occurrence and
impact.
• Perform quantitative Risk Analysis- The process of numerically analyzing the effect.
of identified risks on overall project objectives.
• Plan Risk Responses- The process of developing options and actions to enhance
opportunities and to monitoring residual risks, identifying new risks, and evaluating
risk process effectiveness throughout the project