Project SAMPLE Document
Project SAMPLE Document
CERTIFICATE
This is to certify that the project entitled “PROJECT NAME” is a bonafied record of work carried out
by ..........................submitted in partial fulfillment of All India Senior Secondary Certificate
Examination 2023-2024
EXTERNAL EXAMINER
ACKNOWLEDGEMENT
Apart from the efforts of me, the success of any project depends largely on
the encouragement and guidelines of many others. I take this opportunity to express
my gratitude to the people who have been instrumental in the successful completion
of this project.
I express deep sense of gratitude to almighty God for giving me strength for
the successful completion of the project.
I express my heartfelt gratitude to my parents for constant encouragement
while carrying out this project.
I gratefully acknowledge the contribution of the individuals who contributed in
bringing this project up to this level, who continues to look after me despite my flaws,
I express my deep sense of gratitude to the luminary The Principal I/C, who has
been continuously motivating and extending their helping hand to us.
I am overwhelmed to express my thanks to The Administrative Officer for
providing me an infrastructure and moral support while carrying out this project in the
school.
My sincere thanks to Mrs. Chattumala Saranya, Master In-charge, A guide,
Mentor all the above a friend, who critically reviewed my project and helped in
solving each and every problem, occurred during implementation of the project
The guidance and support received from all the members who contributed
and who are contributing to this project, was vital for the success of the project. I am
grateful for their constant support and help.
Sincerely,
TABLE OF CONTENTS
1 INTRODUCTION
3 PROPOSED SYSTEM
4 REQUIREMENTS
5 SYSTEM DEVELOPMENT
CYCLE
6 PHASES OF SDLC
7 TESTING
8 SOURCE CODE
9 OUTPUT
10 REFERENCES
1. INTRODUCTION
A Library Book Record management system uses to maintain the record of the library. This project
helps to maintain a database that is useful to insert, delete, update and display records . Moreover, it
also reduces the manual record burden of the librarian. Library management system allows the
librarian to maintain library resources in a more operative manner that will help to save their time.
2. OBJECTIVES OF THE PROJECT
The objective of this project is to let the students apply the programming
knowledge into a real- world situation/problem and exposed the students how
3. PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings of be really
wants to stand against today’s merciless competition where not to wise saying “to
err is human” no longer valid, it’s outdated to rationalize your mistake. So, to keep
pace with time, to bring about the best result without malfunctioning and greater
efficiency so to replace the unending heaps of flies with a much sophisticated hard
One has to use the data management software. Software has been an ascent
markets, which have helped in making the organizations work easier and efficiently.
Data management initially had to maintain a lot of ledgers and a lot of paper work
has to be done but now software product on this organization has made their work
faster and easier. Now only this software has to be loaded on the computer and work
can be done.
This prevents a lot of time and money. The work becomes fully automated
and any information regarding the organization can be obtained by clicking the
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
III. mysql
5. SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
INITIATION PHASE
the need including questioning the need for technology, i.e., will a change in
the business process offer a solution?
● Identify basic functional and data requirements to satisfy the business need.
functional requirements
● It may include several trade-off decisions such as the decision to use COTS
forward.
PLANNING 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 alevel 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 MasterPlan.
● Further define and refine the functional and data requirements and document
(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
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 scriptprograms during the development
phase. Program designs are c onstructed in various ways. Using a top-down
approach, designers first identify and link majorprogram 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 the software
development, a variety of elements are considered in the design to mitigate risk.
These include:
● 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.
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.
by end users
● Testing as a deployed system with end users working together with contract
personnel
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 userrequirements.
7. Testing
TESTING METHODS
Software testing methods are traditionally divided into black box testing and
white box testing. These two approaches are used to describe the point of view that
a test engineer takes when designing test cases.
SPECIFICATION-BASED TESTING
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 how the software being tested was
actually constructed.
That's why there are situations when (1) a black box tester writes many test
cases to check something that can be tested by only one test case, and/or (2) some
parts of the back end are not tested at all. Therefore, black box testing has the
advantage of "an unaffiliated opinion," on the one hand, and the disadvantage of
"blind exploring," on the other.
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)
● api testing - Testing of the application using Public and Private APIs.
coverage.
For example, the test designer can create tests to cause all statements in the
program to be executed at least once.
White box testing methods can also be used to evaluate the completeness of
a test suite 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 function points have been tested.
8. SOURCE CODE
# Code for creating table - book in the database- library [Must be executed only ONCE]
mycur=mycon.cursor()
mycur.execute("CREATE TABLE book(bno integer primary key, bname varchar(50), bauth
varchar(50), bprice integer, bqty integer)")
print("Table created successfully")
'''
if mycon.is_connected():
print("Connected to MYSQL database successfully")
mycur= mycon.cursor()
else:
print("\t\t\t Record NOT found..!!!")
if count!=0:
print("\t\t Book Records found.........:\n")
for (bno,bname,bauth,bprice,bqty) in data:
print("Book Code:\t",bno)
print("Book Name:\t",bname)
print("Book Author:\t",bauth)
print("Book Price:\t",bprice)
print("Book Quantity:\t",bqty)
print(".................................")
else:
print("\t\t\t Record NOT found..!!!")
# function to update book record
def updatebook():
bno=int(input("Enter book number to be updated...:"))
qry="SELECT * FROM book WHERE bno=%s"
rec=(bno,)
mycur.execute(qry,rec)
data=mycur.fetchall()
count=mycur.rowcount
if count!=0:a
print("\t\t Book Records found.........:\n")
for (bno,bname,bauth,bprice,bqty) in data:
print("Book Code:\t",bno)
print("Book Name:\t",bname)
print("Book Author:\t",bauth)
print("Book Price:\t",bprice)
print("Book Quantity:\t",bqty)
print(".................................")
else:
print("\t\t\t Record NOT found..!!!")
Database Creation
runfile('D:/cs/project/library record management/database_creation.py', wdir='D:/cs/project/library
record management')
databse connected successfully
Database created successfully
Table Creation
runfile('D:/cs/project/library record management/table_creation.py', wdir='D:/cs/project/library
record management')
Table created successfully
Operations:
INSERT
runfile('D:/cs/project/library record management/operations.py', wdir='D:/cs/project/library record
management')
Connected to MYSQL database successfully
==================================
1. Add New Book record
2. Display Book record
3. Search Book record
4. Delete Book record
5. Update Book record
6. EXIT
==================================
Enter choice 1-6:1
==================================
1. Add New Book record
2. Display Book record
3. Search Book record
4. Delete Book record
5. Update Book record
6. EXIT
==================================
==================================
1. Add New Book record
2. Display Book record
3. Search Book record
4. Delete Book record
5. Update Book record
6. EXIT
==================================
==================================
1. Add New Book record
2. Display Book record
3. Search Book record
4. Delete Book record
5. Update Book record
6. EXIT
==================================
==================================
1. Add New Book record
2. Display Book record
3. Search Book record
4. Delete Book record
5. Update Book record
6. EXIT
==================================
UPDATE
==================================
1. Add New Book record
2. Display Book record
3. Search Book record
4. Delete Book record
5. Update Book record
6. EXIT
==================================
==================================
1. Add New Book record
2. Display Book record
3. Search Book record
4. Delete Book record
5. Update Book record
6. EXIT
==================================
DISPLAY
==================================
1. Add New Book record
2. Display Book record
3. Search Book record
4. Delete Book record
5. Update Book record
6. EXIT
==================================
==================================
1. Add New Book record
2. Display Book record
3. Search Book record
4. Delete Book record
5. Update Book record
6. EXIT
==================================
DELETE
==================================
1. Add New Book record
2. Display Book record
3. Search Book record
4. Delete Book record
5. Update Book record
6. EXIT
==================================
Enter choice 1-6:4
==================================
1. Add New Book record
2. Display Book record
3. Search Book record
4. Delete Book record
5. Update Book record
6. EXIT
==================================
2. Website: https://www.w3resource.com