1
SBBM GSV SHANKRACHARYA MARG
CIVIL LINES DELHI 110054
COMPUTER SCIENCE (083)
PROJECT
2024-2025
TOPIC:
LIBRARY MANAGEMENT SYSTEM
SUBMITTED BY : SHRISTI
CLASS AND SECTION : XII A
ROLL NUMBER : 04
2
TABLE OF CONTENTS
S. No. TOPIC PAGE NO.
1 ACKNOWLEGMENT 3
2 CERTIFICATE 4
3 SDLC 5-15
4 SYSTEM 16
REQUIREMENT
5 BACKEND DETAILS 17-20
6 FRONT END 21
DETAILS
7 PROGRAM CODE 22-26
8 MOTIVE 27
9 OUTPUT 28-32
10 LIMITATIONS 33
11 BIBLIOGRPAHY 34
3
ACKNOWLEDGEMENT
I would like to express my special thanks of gratitude to my
computer science teacher MD. BICKY SIR and other school staff,
for their vital support, guidance and encouragement which
helped me in doing a lot of research and I came to know about
so many new things I am thankful to them.
Secondly i would also like to thank my parents who helped me a
lot in finalizing this project within the limited time frame.
SHRISTI
Student name
4
CERTIFICATE
This is to certify that SHRISTI of class XII A, of SBBM
GSV SHANKRACHARYA MARG CIVIL LINES
DELHI 110054 has successfully completed her project in
Computer Science Practical for DSSCE as prescribed by
CBSE in the year 2024-2025.
Roll No: 04
Sign. of Internal teacher Sign. of External teacher
___________ _____________
5
SYSTEM DEVELOPMENT LIFE CYCLE
The system development life cycle is a 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,
design, development, testing, implementation and maintenance
phases However, the phases may be divided differently
depending on the organization involved for example initial
project activities might be designated as request requirements -
definition, and planning phases or initiation. concept -
development, planning phase. The end users’ system under
development should be involved in reviewing the system is being
built to deliver the needed functionality
6
PHASES OF SYSTEM DEVELOPMENT LIFE
CYCLE (INITIATION PHASE)
The initiation Phase begins rumen a business change identifies a
need or an opportunity.
The purpose of the initiation 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 that need.
➢ Recommend the exploration of alternative concepts and
methods to satisfy the need including questioning the need
for technology, i.e., will a change in the business process
after a solution.
➢ Assure executive business and executive technical
sponsorship. The Spenser designated 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
7
SYSTEM CONCEPT DEVELOPMENT PHASE
The system concept development Phase begins after a business
need or opportunity is validated by the Agency / Organization
Program Leadership and the Agency/ Organization C70.
The purpose of the system Count 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 alternative approaches to
satisfy the basic functional requirements.
➢ Identify and initiate risk mitigation actions, and develop
high-level technical architecture, process models, data
models and a concept of operations. This phase explores
potential technical solutions within the context of business
need.
➢ Identify and initiate risk mitigation actions, and develop
high-level technical architecture, process models, data
models and a concept of operations. This phase explores
potential technical solutions within the context of business
need.
8
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 a project, is necessary
activities and manage, project risks e and formality of "project"
plans Loor donate risks effectively. The dep the commensurate
with the characteristics and wishes of a given project. Project
plans within the information gathered during the initiation phase
by further identifying the specific activities and sources required
to complete a project.
A critical part of converting a project manager’s job discussions
between, is to audit submit design, development, and network
requirements as much as possible. During this phase, a plan is
developed that documents the to be used and includes a discussion
approach of methods, tools, tasks, resources, project schedule and
user Input Personnel assignments, to its project schedule and
target date are established.
9
REQUIREMENTS 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 this 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 be used to
determine acceptance of the system are captured in the Test and
Evaluation Master Plan.
The purposes of this phase are 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 goes, 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.
10
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 layouts, and system architectures. End users, designers,
developers, database managers, and network administrators
should review and refine the prototyped 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 very
expensive to solve in the later stage of software development, a
variety of elements are considered in the design to mitigate risk.
These include:
11
➢ Identifying potential risks and defining mitigating design
features.
➢ Performing a security risk assessment.
➢ Developing a conversion plan to migrate current data to the
new system.
➢ Determining the operating environment.
➢ Defining major subsystems 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 as 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. Concurrently 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.
12
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
involves 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.
13
INTEGRATION AND TEST PHASE
Subsystem integration, system, security, and user acceptance
testing are conducted during the integration and test phase. The
user, with those responsible for quality assurance, validates that
the functional requirements, as defined in 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 & Validation evaluation is
performed, and all documentation is reviewed and accepted
prior to acceptance of the system.
14
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 objectives established during the
planning phase. Implementation includes user notification, user
training, installation of hardware, installation of software onto
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.
15
OPERATIONS AND MAINTENANCE PHASE
The system operation is ongoing. The system is monitored for
continued performance in accordance with user requirements and
the system modifications needed are incorporated. Operations
continue if 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
16
SYSTEM REQUIREMENTS
HARDWARE REQUIREMENT:
• Printer- to print the required documents of the
project.
• Compact Drive
• Processor: Pentium III and above
• RAM: 256 MB (minimum)
• Hard Disk: 20 GB (minimum)
SOFTWARE REQUIREMENT:
• Windows 11 or higher
• My-SQL server 24.1.1 or higher (as backend)
• Python idle 3.12 or higher (as frontend).
• Microsoft Word 2010 or higher for
documentation.
17
BACKEND DETAIL
Database Name: LIBRARY
Code:
Create Database Library.
use library.
18
Table Name: BOOKS
Code:
Attributes:
19
Table Name: ISSUE
Code:
Attributes:
20
Table Name: SUBMIT
Code:
Attributes:
21
FRONT-END DETAILS
22
PROGRAM CODE
23
24
25
26
27
MOTIVE
1. Efficient Book Management
The system allows easy addition, deletion and updating of books,
simplifying inventory management and ensuring accurate records of
available books in the library.
2.Automated Book Issuing and Returning
It automates the processes of issuing and submitting books, keeping
track of borrowed and returned books and updating the inventory
automatically.
3.Data Integrity and Access Control
The system include basic password protection to restrict access to
authorized users, ensuring the integrity of the library’s data and
preventing unauthorized changes.
4.User-Friendly Interface
The code provides a menu-driven interface, marking it simple for
librarians to perform tasks without requiring indepth technical
knowledge or manual record-keeping.
28
OUTPUT
MAIN MANU
On Pressing 1
ADDING A NEW BOOK
29
On Pressing 2
ISSUE BOOK BY ENTER NAME
On Pressing 3
SUBMIT BOOK BY NAME
30
On Pressing 4
DELETE BOOK BY ENTER BOOK
CODE
31
On Pressing 5
DISPLAY BOOK
32
33
LIMITATIONS
⚫ Limiting Search Functionality
It lacks advanced search filters, making it difficult to find
books based on criteria like author, genre, or publication year.
⚫ No Notification or Alerts
The project does not have automated notifications for due
dates, overdue books, or book availability.
⚫ Console-Based Interface
The absence of a graphical user interface (GUI) makes it less
intuitive and user-friendly for non-technical users.
34
BIBLIOGRAPHY
BOOKS:
• COMPUTER SCIENCE WITH PYTHON-BY
PREETI ARORA
WEBSITES:
• https://docs.python.org/3/
• https://youtu.be/0GHft_BuYhs
• www.google.com
