KENDRIYA VIDYALAYA

ACADEMIC YEAR : 2025-26

PROJECT REPORT ON

BOOK STALL MANAGEMENT

ROLL NO :

NAME : ARCHITA MOHANTY

CLASS : XII – ‘A’

SUBJECT : COMPUTER SCIENCE

SUB CODE : 083

PROJECT GUIDE: Mr MANASH RANJAN SAHOO

PGT (CS)

KENDRIYA VIDYALAYA

ARC CHARBATIA

ODISHA

1
 KENDRIYA VIDYALAYA

CERTIFICATE

This is to certify that Cadet Archita Mohanty Roll No: has successfully

completed the project Work entitled BOOK STALL MANAGEMENT in the subject

Computer Science (083) laid down in the regulations of CBSE for the purpose of

Practical Examination in Class XII to be held in kendriya vidyalaya on ____________.

(manash ranjan sahoo)

PGT Comp Science
Master IC

Examiner:

Name: _______________

Signature:

2
 TABLE OF CONTENTS [ T O C ]

SL
DESCRIPTION PAGE NO
NO.

01 ACKNOWLEDGEMENT 04

02 INTRODUCTION 05

03 OBJECTIVES OF THE PROJECT 05

04 PROPOSED SYSTEM 06

05 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 07

06 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 08

07 SOURCE CODE 15

08 OUTPUT 21

09 TESTING 21

10 HARDWARE AND SOFTWARE REQUIREMENTS 24

11 BIBLIOGRAPHY 25

ACKNOWLEDGEMENT

3
 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, kendriya

vidyalaya who has been continuously motivating and extending their helping hand to
us.

I express my sincere thanks to the academician The Vice Principal, kendriya

vidyalaya, for constant encouragement and the guidance provided during this project

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 Mr. manash ranjan sahoo, 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.

PROJECT ON BOOK STALL MANAGEMENT

4
INTRODUCTION
This project is all about a software for Book Stalls. It helps the Book Stall Owner

to have a full-fledged control over his/her stall. It adds a new stock, updates an existing

stock and ofcourse prints a receipt to the customer. Besides it displays a graph of the

sales of the current month.

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

programming skills helps in developing a good software.

1. Write programs utilizing modern software tools.

2. Apply object oriented programming principles effectively when developing small

to medium sized projects.

3. Write effective procedural code to solve small to medium sized problems.

4. Students will demonstrate a breadth of knowledge in computer science, as

exemplified in the areas of systems, theory and software development.

5. Students will demonstrate ability to conduct a research or applied Computer

Science project, requiring writing and presentation skills which exemplify

scholarly style in computer science.

PROPOSED SYSTEM

5
 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

disk of the computer.

One has to use the data management software. Software has been an ascent

in atomization various organisations. Many software products working are now in

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 button.

Moreover, now it’s an age of computers of and automating such an organization gives

the better look.

SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

6
 The systems 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, and
planning phases. End users of the system under development should be involved in
reviewing the output of each phase to ensure the system is being built to deliver the
needed functionality.

7
 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE
INITIATION PHASE

The Initiation Phase begins when a business sponsor 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 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 initiation phase begins when an 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

8
The System Concept Development Phase begins after a business need or opportunity
is validated by the Agency/Organization Program Leadership and 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 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 a 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 products as opposed to developing custom software or reusing
software components, or the decision to use an incremental delivery versus a
complete, onetime deployment.
Construction of executable prototypes is encouraged to evaluate technology to
support the business process. The System Boundary Document serves as an
important reference document 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:

9
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 to coordinate activities and manage project risks
effectively. The depth and formality of 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, tools, tasks, resources, project schedules, and user input.
Personnel assignments, costs, project schedule, and target dates are established.
A Project Management Plan is created with components related to acquisition
planning, configuration management planning, quality assurance planning, concept of
operations, system security, verification and validation, and systems engineering
management planning.

10
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 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

11
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:

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.
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

12
 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.

INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance testing is

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 &

13
 Validation evaluation is performed and all documentation is 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 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.

OPERATIONS AND MAINTENANCE 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 continue to be satisfied.
Determine when the system needs to be modernized, replaced, or retired.

SOURCE CODE

14
================================================================

# PYTHON MODULE : [Link]

import pymysql as cntr , datetime as __dt , [Link] as plt

from random import shuffle
from tempfile import mktemp
from os import system , startfile

__db = [Link](host = 'localhost' , user = 'root' , passwd =

'manager' , database = 'book_shop')
__cur = __db.cursor()
__db.autocommit(True)

#Function to check is it leap year

is_leapyear = lambda year : year % 4 == 0

#Function to get last date of month

def last_month(month , year):
if month in (1,3,5,7,8,10,12) :
return 31
elif month == 2 and is_leapyear(year) :
return 29
elif month == 2 :
return 28
else :
return 30

clrscreen = lambda : system("cls")

def view_stock() :
__cur.execute("select Book_No , Book_Name , Available_Stock from
stock")
data = __cur.fetchall()
print("Book Number\tBook Name\tStock")
for row in data : print(row[0] , '\t\t' , row[1] , '\t' ,
row[2])

def add_stock() :
print('Add Stock'.center(89 , '='))
bno = unique_book_no()
if bno :
print("Book Number : " , bno)
else :

15
 bno = int(input("Enter book number : "))
bname = input("Enter the Book\'s Name : ")
auth = input("Enter the Author of the Book : ")
publ = input("Enter the Publisher of the Book : ")
cost = eval(input("Enter the Cost per Book : "))
stock = int(input("Enter the Quantity purchased : "))
__cur.execute("insert into stock values ({} , '{}' , '{}' , '{}'
, {} , {} , {} , '{}')".format(bno , bname , auth , publ , cost ,
stock , 0, __dt.[Link]()))
print("Inserted Sucessfully !!!")

def add_user() :
user = input("Enter the user name : ")
passwd = input("Enter a Password : ")
passwd2 = input("Enter Password to confirm : ")
if passwd == passwd2 :
__cur.execute("insert into users values('{}' ,
'{}')".format(user , passwd))
print("Created Successfully!!!")
elif passwd != passwd2 :
print("You've entered different passwords")

def sell_book() :
print('Purchase')
cname = input("Enter the Customer Name : ")
phno = int(input("Enter the phone number : "))
bno = int(input("Enter book number : "))
bname = input("Enter the name of the book : ")
cost = eval(input("Enter the cost of the book : "))
__cur.execute("insert into purchased values({} ,
'{}')".format(bno , __dt.[Link]()))
__cur.execute("update stock set qty_purchased = qty_purchased +
1 where Book_No = {}".format(bno))
__cur.execute("update stock set Available_Stock =
Available_Stock - 1 where Book_No = {}".format(bno))
print("Bought Successfully")
q = '''Book Shop\nName : {}\nPhone No : {}\nBook Number :
{}\nBook Name : {}\nCost : {}\nDate Of Purchase : {}'''.format(cname
, phno , bno , bname , cost , __dt.[Link]())
filename = mktemp('.txt')
open(filename , 'w').write(q)
startfile(filename , 'print')
__cur.execute('select Book_Name , Book_No , Author from stock
where Available_Stock = 0')
if __cur.rowcount == 1 :
print("STOCK OF ")

16
 print("Book Name : " , __cur.fetchall()[0][0])
print("Book Number : " , __cur.fetchall()[0][1])
print("Author : " , __cur.fetchall()[0][2])
print("EXHAUSTED")
__cur.execute('delete from stock where Available_Stock = 0')

def unique_book_no () :
__cur.execute("select max(Book_No) from stock")
data = __cur.fetchall()
if bool(data[0][0]) :
L1 = [x for x in range((data[0][0] + 1) , (data[0][0] +
10000))]
shuffle(L1)
return [Link](0)
else :
return False

def view_sales () :
print('Overall Sales This Month')
__cur.execute("select distinct(s.Book_Name) , s.qty_purchased
from stock s , purchased p where s.Book_No = p.Book_No and
p.purchased_on between '{year}-{month}-01' and '{year}-{month}-
{date}'".format(year = __dt.[Link]().year , month =
__dt.[Link]().month , date = last_month(__dt.[Link]().month
, __dt.[Link]().year)))
data = __cur.fetchall()
L1 , L2 = [] , []
for row in data :
[Link](row[0])
[Link](row[1])
[Link](L1 , L2)
[Link]('Books')
[Link]('Sales')
[Link]('Sales')
[Link]()

def login():
user = input("Enter the username : ")
pwd = input("Enter the password : ")
__cur.execute("Select * from users where (username = '{}' and
password = '{}')".format(user , pwd))
if __cur.rowcount :
return True

17
def update_stock() :
bno = int(input("Enter the book number : "))
__cur.execute("select Book_Name , Available_Stock from stock
where Book_No = {}".format(bno))
data = __cur.fetchall()
print("Book Name : " , data[0][0])
print("Available Stock : " , data[0][1])
stock = int(input("Enter the new stock purchased : "))
__cur.execute("update stock set Available_Stock =
Available_Stock + {}".format(stock))
print("Updated Successfully")

====================================================================

# PYTHON MODULE : Tables_in_mysql

import pymysql as cntr

db = [Link](host = 'localhost' , user = 'root' , passwd =

'manager')
[Link](True)
cur = [Link]()
[Link]("create database if not exists book_shop")
[Link]("use book_shop")
[Link]("create table stock\
(Book_No bigint primary key,\
Book_Name varchar(255),\
Author varchar(255),\
Publisher varchar(255),\
Cost_per_Book float,\
Available_Stock bigint,\
qty_purchased bigint,\
purchased_on date)")
[Link]("create table users(username varchar(255) , password
varchar(255) , check (username <> 'ADMIN'))")
[Link]("create table purchased (Book_no bigint , purchased_on
date , foreign key(Book_no) references stock(Book_No))")
[Link]("create unique index Book_Index on stock(Book_No)")
[Link]("insert into users values('admin' , 'admin@123')")
print("Database and Tables created successfully")
c = input("Press any key to continue---->")
[Link]()
[Link]()

====================================================================

# PYTHON MODULE : main

import Book

18
c = 'y'
while [Link]() == 'y' :
print("Book Shop Management".center(89 , '='))
print('1. Register')
print('2. Login')
print('3. Exit')
choice4 = int(input("Enter the serial number of your choice :
"))
if choice4 == 1 :
[Link]()
Book.add_user()
elif choice4 == 2 :
[Link]()
if [Link]() :
[Link]
C = 'y'
while [Link]() == 'y' :
[Link]()
print("Book Shop Management".center(89 , '='))
print("1. Book Stock")
print("2. Book Selling")
print("3. Exit")
choice = int(input("Enter the serial number of your
choice : "))
if choice == 1 :
[Link]()
print("Book Book".center(89 , '='))
print("1. Add a new Stock")
print("2. View all Stock")
print("3. Update an existing Stock")
print("4. Exit")
choice2 = int(input("Enter the choice : "))
if choice2 == 1 :
[Link]()
Book.add_stock()
elif choice2 == 2 :
[Link]()
Book.view_stock()
elif choice2 == 3 :
[Link]()
Book.update_stock()
elif choice2 == 4 :
print("Good Bye")
break
else :
print("INVALID CHOICE")
elif choice == 2 :
[Link]()

19
 print('Book Selling'.center(89 , '='))
print('1. Sell a book')
print('2. View Sales this month')
print("3. Exit")
choice3 = int(input("Enter your choice : "))
if choice3 == 1 :
[Link]()
Book.sell_book()
elif choice3 == 2 :
[Link]()
Book.view_sales()
elif choice3 == 3 :
print("Good Bye")
break
else :
print("INVALID CHOICE")
elif choice == 3 :
print("Good Bye")
break
else :
print("INVALID CHOICE")
C = input("Do you want to continue (y/[n]) :
")
else :
print("Good Bye")
else :
print("Either your username or password is incorrect")
elif choice4 == 3 :
print("Good Bye")
break
else :
print("INVALID CHOICE")
c = input("Do you want to return to main menu (y/[n]) : ")
else :
print("Good Bye")

20
 OUTPUT

TESTING

Software Testing is an empirical investigation conducted to provide

stakeholders with information about the quality of the product or service under test[1]
, 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 employed, can be implemented at any time in the development

21
process, however the most test effort is employed after the requirements have been
defined and coding process has been completed.

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.

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, fuzz testing, model-based
testing, traceability matrix, exploratory testing and specification-based testing.

SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of software according

to the applicable requirements.[16] 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 for a given input, the output
value (or behaviour), either "is" or "is not" the same as the expected value 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 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

22
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

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 create 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 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.

Two common forms of code coverage are:

Function Coverage: Which reports on functions executed and
Statement Coverage: Which reports on the number of lines executed to
complete the test.
They both return coverage metric, measured as a percentage

23
 HARDWARE AND SOFTWARE REQUIREMENTS

[Link] SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUAL CORE)

III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R MSI

K9MM-V VIA K8M800+8237R PLUS

CHIPSET FOR AMD ATHALON

IV. RAM : 512MB+

V. Hard disk : SATA 40 GB OR ABOVE

VI. CD/DVD r/w multi drive combo: (If back up required)

VII. FLOPPY DRIVE 1.44 MB : (If Backup required)

VIII. MONITOR 14.1 or 15 -17 inch

IX. Key board and mouse

X. Printer : required

SOFTWARE REQUIREMENTS:

I. Windows OS

24
 BIBLIOGRAPHY

1. Computer science With Python - Class XI By : Sumita Arora

2. A Project Report On Space Invader Game and Gold Loan Shop
Management (GLSM)
By : [Link]
3. Website: [Link]

***

25