PROJECT

DETAIL
Title - Information Practices
Subject - Library Management
Name - Devanshi Dugaya
Class - 11th “B”
Roll No. - 4308
Name of teacher - Mrs. Alis Caleb
Name of school - St. Joseph’s Convent School
Itarsi
Session - 2023-24

PRINCIPAL SEAL EXTERNAL

AND SIGN SIGN
 INDEX
S NO. TOPIC PG NO.
1. OBJECTIVE
2. INTRODUCTION
3. EXISTING SYSTEM
4. PROPOSED SYSTEM
5. HARDWARE AND SOFTWARE
REQUIREMENT
6. SDLC
7. FLOW CHART
8. USERCASE
9. SOURCE CODE
10. OUTPUT
11. TESTING
12. BIBLOGRAPHY
13. VIVA VOCE
 OBJECTIVE
This project gives an overview about the aim ,
objectives ,background and operational environment of the
system of library management.

PROJECT AIMS AND OBJECTIVES

The project aims and objectives that will be achieved after
completion of this project are discussed in this subchapter.
The aims and objectives are as follows:

I. Online book issue

II. Request column for librarian for providing new books
III. A separate column for digital library
IV. Student login page where student can find books issued
by him/her and date of return.
V. A search column to search availability of books
VI. A teacher login page where teacher can add any events
being organized in the college and important suggestions
regarding books.
VII. Display the available books.
VIII. Check the availability.
IX. Delete or clear the entries made.
INTRODUCTION
Library management system is a project which aims in
developing a computerized system to maintain all
the daily work of library .This project has many features
which are generally not available in normal library
management systems like facility of user login and a facility
of teachers login .It also has a facility of admin login through
which the admin can monitor the whole system .It also has
facility of an online notice board where teachers can student
can put up information about workshops or seminars being
held in our colleges or nearby colleges and librarian after
proper verification from the concerned institution organizing
the seminar can add it to the notice board . It has also a
facility where student after logging in their accounts can see
list of books issued and its issue date and return date and also
the students can request the librarian to add new books by
filling the book request form. The librarian after logging into
his account i.e. admin account can generate various reports
such as student report , issue report, teacher report and book
report Overall this project of ours is being developed to help
the students as well as staff of library to maintain the library
in the best way possible and also reduce the human efforts
All these modules are able to help librarian to manage the
library with more convenience and in a more efficient way as
compared to library systems which are not computerized.
EXISTINGSYSTEM

Present system comprises all the information related to books

such as book name, author and edition. Current system also
contains information about the students and books. It contains
registrations option to users. Without registration nobody can
use this system.

Present system also contains various limitations and

drawbacks. Existing system is difficult to use. User interface
is not shown properly and is not really interactive. Fast report
generations is not possible. Tracing a book and its availability
is difficult. Security issues occur sometimes. Information
about issue or return of the books are not properly maintained
as they are all manual.
PROBLEM STATEMENT :
 File loss – when computerized system is not
implemented file is always lost because of human
environment . Some times due to some human error there
may be a loss of records.
File damage – loss due to some accident like spilling of watee
by some member on file accidentally can take place in the
manual management system. There may be the chances of
loss due to some natural disaster as well such as flood,
earthquake etc. and hence is risky.
 Difficult to search record – 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 for files and records
also increases and can get really hectic.
 Cost consuming – no computerisation of the system leads
to increase in the cost of management as then more
supplies will be required for it.
PROPOSED SYSTEM

 Improvement in control and performance-The

system is developed to cope up with the current
issues and problems of library.The system can
add user, validate user and is also bug free.
 Save cost- after computerized system is
implemented less human force will be required
tomaintain the library thus reducing the overall
cost.
 Save time- Librarian is able to search record by
using few clicks of mouse and
few searchkeywords thus saving his valuable
time.
 Option of online Notice board- Librarian will
be able to provide a detailed description.
 Lecture notes- Teachers can provide the lecture
notes by uploading it to the system in less than
10 MB.
HARDWARE AND
SOFTWARE
REQUIREMENTS
HARDWARE REQUIRMENT:
 Processor – Dual core
 Operating system – 32 bit
 Hard disk – 50 GB(minimum)
 Memory – 1 GB(minimum)

SOFTWARE REQUIREMENT:
 Windows 8, Windows 10
 Python 3.7.3
 Anaconda Navigator
SYSTEM DEVELOPMENT LIFE
CYCLE
(SDLC)
The System Development Life Cycle
As used in the construction of the server appliance

The system development life cycle project

management technique that divides complex
projects into smaller, more easily managed
segments or phases. Segmenting projects allows
managers to verify the successful completion of
project phases before allocating resources to
subsequent phases.

Software development projects typically

include initiation, planning, designing,
development, testing, implementation, and
maintenance phases. However, the phases may be
divided differently depending in the organization
involved.

For example, initial project activities might be

designated as request, requirements-definition, and
planning phases, or initiation, concept-
development, and planning phases. End users of the
system under development should be involved in
viewing the output of each phase to ensure the
system is being built to deliver the needed
functionality.
PHASES OF SYSTEM
DEVELOPMENT LIFE
CYCLE
INITIAL PHASE

The initial phase begins when a business sponsor identifies a

need or an opportunity.

The purpose of the initial phase is to:

 Identify and validate an opportunity to improve business
accomplishments of the organization or a deficiency
related to a business need.
 Identify significant assumptions and constraints on
solutions to the need.
 Recommend the exploration of alternative concepts and
methods to satisfy the need including questioning
questioning the need of technology i.e. ,will a change in
the business process offer a solution?
 Assure executive business and executive technical
sponsorship. The sponsor designates a Project Manager
and the business need is documented in a concept
proposal. The concept proposal includes information
about the business process and the relationship to the
agency/organization.
 Infrastructure and the strategic plan. A successful concept
proposal results in a project management charter which
outlines the authority of the Project Manager to begin the
project.
Careful oversight is required to ensure projects support
strategic business objectives and resources are effectively
implemented into an organization’s enterprise
architecture. The initial phase begins with the
opportunity to add, improve, or correct a system is
identified and formally requested through the
presentation of a business case. The business case
should, at a minimum, describe a proposal’s purpose,
identify expected benefits, and explain how the proposed
system supports one of the organization’s business
strategies. The business case should also identify
alternative solutions and detail as many informational,
functional, and network requirements as possible.

SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a

business need or opportunity is validated by the
Agency/Organization CIO.

The purpose of the System Concept Development Phase

is to:

 Determine the feasibility and appropriateness of the

alternatives.
 Identify system interfaces.
 Identify basic functional and data requirements to
satisfy the business need.
 Establish system boundaries; identify goals,
objectives, critical success factors, and performance
measures.
 Evaluate costs and benefits of the alternative
approaches to satisfy the basic functional
requirements.
 Assess project risks.
 Identify and initiate risk mitigation actions, and
develop high level technical architecture, process
models, data models, and concept of operations.
This phase explores potential technical solutions
within the context of the business need.
 It may include several trade-off decisions such as
the decision to use COTS software or reusing
software components, or the decision to use an
incremental delivery versus a complete, onetime
deployment.
 Construction of the executable prototypes is
encouraged to evaluate technology to support the
business process. The System Boundary Document
serves as an important reference documents to
support the Information Technology Project
Request(ITPR) process.
 The ITPR must be approved by the State CIO
before the project can move forward.
 PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE

The planning phase is the most critical step in completing

development, acquisition, and maintenance projects. Careful
planning, particularly in the early stages of the project, is
necessary to coordinate activities and mange project risks
effectively. The depth and formality of the project plans
should be commensurate with the characteristics and risks of a
given project. Project plans refine the information gathered
during the initiation phase by further identifying the specific
activities and resources required to complete a project.

A critical part of a project manager’s job is to coordinate

discussions between user, audit, security,
design ,development, and network personnel to identify and
document as many functional, security, and network
requirements as possible. During this phase, a plan is
developed that documents the approach to be used and
includes a discussion of methods, tool, tasks, resources,
project schedules, and user input. Personnel assignments,
costs, project schedule, and target dates are established.

A Project Management Plan is created with cpmponents

related to acquisition planning, configuration management
planning, quality assurance planning, concept of operations,
system security, verification and validation, and systems
engineering management planning.

REQUIREMENT ANALYSIS PHASE

This phase formally defines the detailed functional user

requirements using high-level requirements identified in the
initiation, system concept, and planning phases. It also
delineates the requirements in terms of data, system
performance, security, and maintainability requirements for
the system. The requirements are defined in the phase to a
level of detail sufficient for systems design to proceed. They
need to be measurable, testable, and relate to the business
need or opportunity identified in the Initiation Phase. The
requirements that will ne used to determine acceptance of the
system are captured in the Test and Evaluation Master Plan.
The purpose of this phase is to:
 Further define and refine the functional and data
requirements and document them in the Requirements
Document.
 Complete business process reengineering of the functions
to be supported (i.e., verify what information drives the
business process, what information is generated, who
generates it, where does the information go, and who
processes it).
 Develop detailed data and process models (system
inputs, outputs, and the process.
 Develop the test and evaluation requirements that will be
used to determine acceptable system performance.

DESIGN PHASE

The design phase involves converting the informational,

functional and network requirements identified during
the initiation and planning phases into unified design
specifications that developers use to script programs
during the development phase. Program designs are
constructed in various ways. Using a top-down approach,
designers first identify and link major program
components and interfaces, then expand design layouts
as they identify and link smaller subsystems and
connections. Using a bottom-up approach, designers first
identify and link minor program components and
interfaces, then expand design layouts as they identify
and link larger systems and connections. Contemporary
design techniques often use prototyping tools that build
mock-up designs of items such as application screens,
database layout, and system architectures. End users,
designers, developers, database managers, and network
administrators should review and refine the prototype
designs in an iterative process until they agree on an
acceptable design. Audit, security, and quality assurance
personnel should be involved in the review and approval
process. During this phase, the system is designed to
satisfy the functional requirements identified in the
previous phase. Since problems in the design phase could
be every expensive to solve in the later stage of the
software development, a variety of elements are
considered in the design to mitigate risk. These include:

 Identifying potential risks and defining

mitigating design features.
 Performing a security risk assessment.
 Developing a conversion plan to migrate
current data to new system.
 Determining the operating environment.
 Defining major subsystem and their inputs and
outputs.
 Allocating processes to resources.
 Preparing detailed logic specifications for each
software module. The result is a draft System
 Design Document which captures the
preliminary design for the system.
 Everything requiring user input or approval is
documented and reviewed by the user. Once
these documents have been approved by the
Agency CIO and Business Sponsor, the final
System Design Document is created to serve
the Critical/Detailed Design for the system.
 This document receives a rigorous review by
Agency technical and functional
representatives to ensure that it satisfies the
business requirements. Concurrent with the
development of the system design, the Agency
Project Manager begins development of the
Implementation Plan, Operations and
Maintenance Manual, and the Training Plan.

DEVELOPMENT PHASE

The development phase involves converting design

specifications into executable programs. Effective
development standards include requirements that
programmers and other project participants discuss design
specifications before programming begins. The procedures
help ensure programmers clearly understand program designs
and functional requirements. Programmers use various
techniques to develop computer programs. The large
transaction oriented programs associated with financial
institutions have traditionally been developed using
procedural programming techniques. Procedural programming
involoves the line-by-line scripting of logical instructions that
are combined to form a program. Effective completion of the
previous stages is a key factor in the success of the
Development phase. The Development phase consists of:
 Translating the detailed requirements and design into
system components.
 Testing individual elements(units) for usability
 Preparing for integration and testing of the IT system.

INTEGRATION PHASE

Subsystem integration, system, security, and user

acceptance testing in conducted during the integration
and test phase. The user, with those responsible for
quality assurance, validates that the functional
requirements document, are satisfied by the developed or
modified system. OIT Security staff assess the system
security and issue a security certification and
accreditation prior to installation/implementation.

Multiple levels of testing are performed, including:

 Testing at the development facility by the contractor

and possibly supported by end users.
  Testing as a deployed system with end users
working together with contract personnel.
 Operational testing by the end user alone
performing all functions. Requirements are traced
throughout testing, a final Independent Verification
and Validation evaluation is performed and all
documentation reviewed and accepted prior to
acceptance of the system.

IMPLEMENTATION PHASE

This phase is initiated after the system has been tested

and accepted by the user. In this phase, the system is
installed to support the intended business functions.
System performance is compared to performance
b=objectives established during the planning phase.
Implementation includes user notification, user training,
installation of hardware, installation of software into
production computers, and integration of the system into
daily work processes. This phase continues until the
system is operating in production in accordance with the
defined user requirements.

OPERATIONS AND MAINTANANCE PHASE

The system operation is ongoing. The system is monitored for
continued performance in accordance with user requirements
and needed system modifications are incorporated. Operations
continue as long as the system can be effectively adapted to
respond to the organization’s needs. When modifications or
changes are identified, the system may reenter the planning
phase

The purpose of this phase is to:

 Operate, maintain, and enhance the system.

 Certify that the system can process sensitive
information.
 Conduct periodic assessments of the system to
ensure the functional requirements to continue to be
satisfied.
 Determine when the system needs to be
modernized, replaced, or retired.
TESTING
Software Testing is an empirical investigation
conducted to provide stakeholders with information
about the quality of the product or service under
test, with respect to the context in which it is
intended to operate. Software Testing also provides
an objective, independent view of the software to
allow the business to appreciate and understand the
risks at implementation of the software. Test
techniques include, but are not limited to, the
process of executing a program or application with
the intent of finding software bugs.

It can also be stated as the process of validating and

verifying that a software
program/application/product meets the business and
technical requirements that guided its design and
development, so that it works as expected and can
be implemented with the same characteristics.
Software Testing, depending on the testing method
process, however the most test effort is employed
after the requirements have been defined and coding
process has been completed.

TESTING METHODS
Software testing method are traditionally divided
into black box and white box testing. These two
approaches are used to describe the point of view
that a test engineer takes when designing test cases.
BLACK BOX TESTING
Black box testing treats the software as a “black
box”, without any knowledge of internal
implementation. Black box testing methods include:
equivalence partitioning, boundary value analysis,
all-pairs testing, fizz testing, model-based testing,
traceability matrix, exploratory testing and
specification-based testing.

SPECIFICATION-BASED TESTING
Specification-based testing aims to test the
functionality software according to the applicable
requirements. Thus, the tester inputs data into, and
only sees the output from, the test object. This level
of testing usually requires thorough test cases to be
provided to the tester, who then can simply verify
that fir a given input, the output value (or
behaviour), either “is” or “is not” the same as the
expected values specified in the test case.
Specification-based testing is necessary, but it is
insufficient to guard against certain risks.

ADVANTAGES AND DISADVANTAGES

The black box tester has no “bonds” with the code,

and a tester’s perception is very simple: a code must
have bugs. Using the principle, “Ask and you shall
receive”, black box testers find bugs where
programmers don’t. But, on the other hand, black
box testing has been said to be “like a walk in a dark
labyrinth without a flashlight”, because the tester
doesn’t know the software being tested was actually
constructed.

That’s why there are suitable situations (1) when a

black box tester writes many test cases to check
something that can be tested by only one test, and/or
(2) some parts of the back end are not tested at all.
Therefore, black box testing has advantage of “an
unaffiliated opinion”, on one hand, and the
disadvantage of “blind exploring,” on the other.

WHITE BOX TESTING

White box testing, by contrast to black box testing,

is when the tester has access to the internal data
structures and algorithms (and the code that
implement these)

Types of white box testing:-

The following types of white box testing exist:

 api testing- testing of the application using

public and private APIs.
 Code coverage- creating tests to satisfy some
criteria of code coverage.
 For example, the test designer can crete tests to
cause all statements in the program to be
executed at least once.
 Fault injection methods.
 Mutation testing methods.
 Static testing- white box testing includes
all static testing.

CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the

completeness of a test suit that was created with black box
testing methods. This allows the software team to examine
parts of a system that are rarely tested and ensures that the
most important points have been tested.
Two common forms of coverage are:
 Function coverage: which reports on functions executed
and
 Statement coverage: which reports on the number of
lines executed to complete the test.