TABLE OF CONTENTS [ T O C ]

SER DESCRIPTION PAGE 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 FLOW CHART 15

08 SOURCE CODE 16

09 OUTPUT 19

10 TESTING 20

11 HARDWARE AND SOFTWARE REQUIREMENTS 23

12 BIBLIOGRAPHY 24

1
 PROJECT ON COMPUTING PI VALUE

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 of course 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 their programming

knowledge to a real-world situation/problem and exposed the students to how

programming skills help in developing 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 the ability to conduct research or applied Computer

Science projects, requiring writing and presentation skills that exemplify

scholarly style in computer science.

2
PROPOSED SYSTEM

Today one cannot afford to rely on the fallible human beings of be wants to

stand against today’s merciless competition where not to wise saying “to err is

human” is 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 to replace the unending heaps of flies with a much more sophisticated

computer hard disk.

One has to use data management software. The software has been an ascent

in the atomization of various organizations. Many software products working are now

in the markets, which has helped in making organizations work easier and more

efficiently. Data management initially had to maintain a lot of ledgers and a lot of

paperwork to be done but now software product in 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 and, adding such an organization

gives the better look.

3
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 the 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 its relationship to the Agency/Organization.
Infrastructure and the Strategic Plan. A successful Concept Proposal results
in a Project Management Charter which outline the authority of the project
manager to begin the project.

Careful oversight is required to ensure projects that 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
business case presentation. 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.

4
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 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 the 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, one time 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.

5
 SOURCE CODE

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

# PYTHON MODULE: BOOK.py

import pymysl.cntr, datetime by MySQL, cntrotlib.pyplot as plt from

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

__db=
cntr.connect(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: bno=int(input("Enter Book Number:"))
bname = input ("Enter the Book\'s Name:")
auth = input ("Enter the Author of the Name :")
publ = inpur("Enter the publisher of the Book:")
cost = eval(input("Enter the cost per book:"))
stock = int(input("Enter the Quantity purchased:"))

6
 __cur.execute("insert into the stock values ({},'{}','{}','{}',
{},{},{}, '{}')".format(bno, bname, auth, publ, cost,
stock,0,__dt.date.today()))
print ("Inserted successfully!!!!")

def add_user():
user=input("Enter the user name:")
passwd=inpur("Enter a Password:")
passwd2=input("Enter Password to confirm:")
if passwd == passwd2:
__cur.execute("insert into user
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 the 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.date.today())
__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.date.today())
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")
print("Book Name:",__cur.fetchall()[0][0])
print("Book Numer:",__cur.fetchall()[0][1])
print("Author:", __cur.fetchall()[0][2])
print("Exhausted")
__cur.execute('delect from stock where
Available_Stock=0')

7
 def uniqe_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 L1.pop(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.date.today().year,month=__dt.date.today().
month,date=last_month(__dt.date.today().month,__dt.date.today().year
)))
data=__cur.fetchall()
L1,L2=[],[]
for row in data:
L1.append(row[0])
L2.append(row[1])
plt.bar(L1,L2)
plt.xlabel('Books')
plt.ylabel('Sales')
plt.title('Sales')
plt.show()

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

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")

8
 import pymysql as cntr

db = cntr.connect(host = 'localhost' , user = 'root' , passwd =

'manager')
db.autocommit(True)
cur = db.cursor()
cur.execute("create database if not exists book_shop")
cur.execute("use book_shop")
cur.execute("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)")
cur.execute("create table users(username varchar(255) , password
varchar(255) , check (username <> 'ADMIN'))")
cur.execute("create table purchased (Book_no bigint , purchased_on
date , foreign key(Book_no) references stock(Book_No))")
cur.execute("create unique index Book_Index on stock(Book_No)")
cur.execute("insert into users values('admin' , 'admin@123')")
print("Database and Tables created successfully")
c = input("Press any key to continue---->")
cur.close()
db.close()

import Book

c = 'y'
while c.lower() == '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 :
Book.clrscreen()
Book.add_user()
elif choice4 == 2 :
Book.clrscreen()
if Book.login() :
Book.clrscreen

9
 C = 'y'
while C.lower() == 'y' :
Book.clrscreen()
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 :
Book.clrscreen()
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 :
Book.clrscreen()
Book.add_stock()
elif choice2 == 2 :
Book.clrscreen()
Book.view_stock()
elif choice2 == 3 :
Book.clrscreen()
Book.update_stock()
elif choice2 == 4 :
print("Good Bye")
break
else : print("INVALID CHOICE")
elif choice == 2 :
Book.clrscreen()
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 :
Book.clrscreen()
Book.sell_book()
elif choice3 == 2 :
Book.clrscreen()
Book.view_sales()
elif choice3 == 3 :
print("Good Bye")
break
else : print("INVALID CHOICE")
elif choice == 3 :
print("Good Bye")
break

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

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

11
 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
process, however the most test effort is employed after the requirements have been
defined and coding process has been completed.

TESTING METHODS

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

13
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 implements
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: This reports on functions executed and
Statement Coverage: This reports on the number of lines executed to
complete the test.
They both return coverage metrics, measured as a percentage

HARDWARE AND SOFTWARE REQUIREMENTS

14
I.OPERATING 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:

 Windows OS
 Python
 mySQL

15
16