MODERN SCHOLAR’S ACADEMY

SENIOR SECONDARY SCHOOL

CHAMBA,TEHRI GARHWAL

SESSION–2023-24
PROJECT FILE

NAME : PRIYANSHU KAINTURA

ROLL NO :
CLASS : XII
SUBJECT : Computer Science with python
SUB CODE : 083

SUBMITTED TO : Er. Abhishek Dangwal

 Certificate

This is to certify that Priyanshu Kaintura

of class XII has completed his Computer
Science practical file under the guidance of
Er.Abhishek Dangwal for the academic
year 2023-24. The certified student has been
dedicated throughout his research and
completed his work before the given
deadline without missing any important
details from the practical file. It is also
certified that these practicals is the
individual work of the student and can be
submitted for evaluation.

Teacher’s sign Principal’s Sign Examiner’s Sign

 ACKNOWLEDGEMENT
I am really grateful for the opportunity of
these practicals and sincerely thank my
computer teacher Er. Abhishek Dangwal.
He will remain one of my favorite teachers for
contributing his valuable time and effort to
help me with these practicals. Their
suggestions and feedback helped me a lot to
improve the practical quality from the
implementation.

Secondly, I would like to thank my parents,

family member and friends who have always
been there whenever needed.

Lastly, I thank them all from my heart and

wish that they will continue to support me
like this.
 Index
S.no DESCRIPTION PAGE
NO
01 INTRODUCTION 01

02 OBJECTIVES OF THE PROJECT 02

03 PROPOSED SYSTEM

04 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

05 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

06 FLOW CHART

07 NEED OF COMPUTERIZATION

08 ADVANTAGES OF THE PROJECT

09 SOURCE CODE

10 PYTHON CODE

11 OUTPUT SCREEN

12 TESTING

13 HARDWARE AND SOFTWARE REQUIREMENT

14 BIBLIOGRAPHY
 INTRODUCTION
The main objective of the python project on
Food ordering is to manage the details of
booking, menu payments, and order.

The project is totally built at administrative

end and only administrator is guaranteed
the access.

The purpose of the project is to build an

application program to reduce the manual
work for managing the booking, discounts,
. and payments.

It tracks all the details about menu,

discount, and payments; it also prints
various reports as per input given by the
user.
 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.

 Write programs utilizing modern software tools.

 Apply object oriented programming principles

effectively when developing small to medium sized
projects.

 Write effective procedural code to solve small to

medium sized problems.

 Students will demonstrate a breadth of knowledge in

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

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

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.
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 andthe
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
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, andDevelop 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:

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' sjob 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.
 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 scriptprograms during the development phase. Program designs
are constructed 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:
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 byAgency 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 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 & Validation evaluation is performed
and all documentation is reviewedand 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 userrequirements.

OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is 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.
FLOW CHART
INPUT DATA AND VALIDATION OF PROJECT

1. All the fields such as order payments

discounts are validated and does not take invalid values.
2. Each form of sales, discounts, bookings cannot accept
the blank values.
3. Avoiding errors in data.
4. Controlling amount of input.

SOFTWARE AND HARDWARE REQUIREMENTS:

Data file handling:

has been effectively used in the program. The database is
a collection of interrelated data to serve multiple
applications. That is database programs create files of
information. So we see that files are worked with most,
inside the program.

DBMS:

The software required for the management of data is

called as DBMS. It has 3 models:
• Relation model
• Hierarchical model
• Network model

RELATIONAL MODEL:
It's based on the concept on relation. Relation is the table
that consists of rows and columns. The rows of the table
are called tuple and the columns of the table are called
attribute. Numbers of rows in the table is called as
cardinality. Number of columns in the table is called as
degree.

HIERARCHICAL MODEL:
In this type of model, we have multiple records for each
record. A particular record has one parent record. No
chide record can exist without parent record. In this, the
records are organized in tree.

NETWORK MODEL:
In this, the data is represented by collection of records
and relationship is represented by (ink or association.

CHARACTERISTICS OF DBMS:
• It reduces the redundancy
• Reduction of data in inconsistency
• Data sharing
• Data standardization
DIFFERENT TYPES OF FILES: -BASED ON ACCESS:
• Sequential file
• Serial file
• Random (direct access) file BASED ON STORAGE:-
• Text file
• Binary File
 NEED OF COMPUTERISATION
Over the decades computers and food bookings have
developed gradually, changed with time. But nobody
knew that a time will come when both these fields will
complement each other so well. Today food booking has
reached new heights by computer aided of design. As a
result of which, computer industry has got its new
customer. Computer technology is making waves in the
food booking zone. Computers are a vital component of
the food booking counters. Computer aided design (CAD)
programs reduce the demand for manual sketches. New
software.
Programs continue to replace old manual skills. Those
who lag in math can now breathe a little easier. Manually
figuring of food insists that knowledge. Software
programs constantly evolve. A program used today may
be obsolete within several years. Being trained on today's
software does not guarantee it will be used when you are
ready to go out into the field. Understanding calculations
is timeless, as is computer competency. Software,
however, shifts rapidly.
 ADVANTAGES
1. it generates the report on sales, discounts and menu.

2. Provides filter report on payments and food booking.

3. We can easily export PDF on sales, products and stocks

4. Applications can also provide excel export for bookings

and discounts

5. It deals with monitoring the information and

transaction of food bookings.

6. It increases the efficiency of food booking and

discount.

7. It has higher efficiency of editing, adding and updating

of records.

8. Provides the searching facilities on various factors.

 SOURCE CODE SCREEN
DBMS: MySQL
Host: local host
User: root
Password: 123@123#
Database: Food
Table Structure: (Image below)
 PYTHON CODE
import os
import platform
import mysql.connector

mydb = mysql.connector.connect(host="localhost",
user="root", password="123@123#")

#creating DB

mycursor = mydb.cursor()
mycursor.execute("create database if not exists food1")
mycursor.execute("use food1")

#creating Tables

# Define the Employee table

mycursor.execute("""
CREATE TABLE IF NOT EXISTS Employee (
Emp_id INT AUTO_INCREMENT PRIMARY KEY,
ename VARCHAR(255) NOT NULL,
emp_g VARCHAR(10),
eage INT,
emp_phone BIGINT,
pwd VARCHAR(255)
)
""")
# Define the Customer table
mycursor.execute("""
CREATE TABLE IF NOT EXISTS Customer (
c_id INT AUTO_INCREMENT PRIMARY KEY,
name VARCHAR(255) NOT NULL,
cphone BIGINT,
payment INT,
pstatus VARCHAR(20),
email VARCHAR(255),
orderid INT,
date DATE
)
""")

# Define the Food table

mycursor.execute("""
CREATE TABLE IF NOT EXISTS Food (
Food_id INT AUTO_INCREMENT PRIMARY KEY,
Foodname VARCHAR(255) NOT NULL,
Food_size VARCHAR(20),
prize INT
)
""")

# Define the OrderFood table

mycursor.execute("""
CREATE TABLE IF NOT EXISTS OrderFood (
Orderf_id INT AUTO_INCREMENT PRIMARY KEY,
C_id INT,
 Emp_id INT,
Food_id INT,
Food_qty INT,
Total_price INT
)
""")

# Define the fee table

mycursor.execute("""
CREATE TABLE IF NOT EXISTS fee (
roll INT AUTO_INCREMENT PRIMARY KEY,
feedeposit INT,
month VARCHAR(10)
)
""")

# main COde

def Customer():
L = []
c_id = int(input("Enter the customer ID number: "))
L.append(c_id)
name = input("Enter the Customer Name: ")
L.append(name)
cphone = int(input("Enter customer phone number: "))
L.append(cphone)
payment = int(input("Enter payment method (1 for credit
card, 2 for Debit Card): "))
 L.append(payment)
pstatus = input("Enter the payment status: ")
L.append(pstatus)
email = input("Enter the email id: ")
L.append(email)
orderid = input("Enter orderid: ")
L.append(orderid)
date = input("Enter the Date: ")
L.append(date)
cust = (L,)
sql = "INSERT INTO customer (c_id, name, cphone, payment,
pstatus, email, orderid, date) VALUES (%s, %s, %s, %s, %s, %s,
%s, %s)"
mycursor.execute(sql, cust)
mydb.commit()

def Employee():
L = []
Emp_id = int(input("Enter the Employee id: "))
L.append(Emp_id)
ename = input("Enter the Employee Name: ")
L.append(ename)
emp_g = input("Enter Employee Gender: ")
L.append(emp_g)
eage = int(input("Enter Employee age: "))
L.append(eage)
emp_phone = int(input("Enter employee phone number: "))
L.append(emp_phone)
pwd = input("Enter the password: ")
 L.append(pwd)
EMP = tuple(L) # Convert the list to a tuple
sql = "INSERT INTO Employee (Emp_id, ename, emp_g, eage,
emp_phone, pwd) VALUES (%s, %s, %s, %s, %s, %s)"
mycursor.execute(sql, EMP)
mydb.commit()

def Food():
L = []
Food_id = int(input("Enter the Food id: "))
L.append(Food_id)
Foodname = input("Enter the Food Name: ")
L.append(Foodname)
Food_size = input("Enter Food size: ")
L.append(Food_size)
prize = int(input("Enter Prize of Food: "))
L.append(prize)
Food = (L,)
sql = "INSERT INTO Food (Food_id, Foodname, Food_size,
prize) VALUES (%s, %s, %s, %s)"
mycursor.execute(sql, Food)
mydb.commit()

def OrderFood():
L = []
Orderf_id = int(input("Enter the Food Order id: "))
 L.append(Orderf_id)
C_id = int(input("Enter the Customer id: "))
L.append(C_id)
Emp_id = int(input("Enter Employee id: "))
L.append(Emp_id)
Food_id = int(input("Enter Food id: "))
L.append(Food_id)
Food_qty = int(input("Enter Qty: "))
L.append(Food_qty)
Total_price = int(input("Enter Total_price: "))
L.append(Total_price)
OrderFood = tuple(L) # Convert the list to a tuple
sql = "INSERT INTO OrderFood (Orderf_id, C_id, Emp_id,
Food_id, Food_qty, Total_price) VALUES (%s, %s, %s, %s, %s,
%s)"
mycursor.execute(sql, OrderFood)
mydb.commit()

def View():
print("Select the search criteria: ")
print("1. Employee")
print("2. Customer")
print("3. Food")
print("4. Order Food")
ch = int(input("Enter the choice 1 to 4: "))

if ch == 1:
Emp_id = int(input("Enter Employee ID: "))
 sql = "SELECT * FROM Employee WHERE Emp_id = %s"
mycursor.execute(sql, (Emp_id,))
res = mycursor.fetchall()
for x in res:
print(x)
elif ch == 2:
c_name = input("Enter Customer Name: ")
sql = "SELECT * FROM Customer WHERE name = %s"
mycursor.execute(sql, (c_name,))
res = mycursor.fetchall()
for x in res:
print(x)
elif ch == 3:
sql = "SELECT * FROM Food"
mycursor.execute(sql)
res = mycursor.fetchall()
for x in res:
print(x)
elif ch == 4:
food_id = int(input("Enter Food ID: "))
sql = "SELECT * FROM OrderFood WHERE Food_id = %s"
mycursor.execute(sql, (food_id,))
res = mycursor.fetchall()
for x in res:
print(x)

def MenuSet():
print("Enter 1 to Add Employee")
 print("Enter 2 to Add Customer details")
print("Enter 3 to Add Food Details")
print("Enter 4 for Food Order")
print("Enter 5 to view Food booking")

try:
userInput = int(input("Please Select an above option: "))
except ValueError:
exit("\nHey! That's Not A Number")
else:
print("\n")

if userInput == 1:
Employee()
elif userInput == 2:
Customer()
elif userInput == 3:
Food()
elif userInput == 4:
OrderFood()
elif userInput == 5:
View()
else:
print("Enter correct choice. . .")

def runAgain():
runAgn = input("\nWant to run again? (Y/N): ")
while runAgn.lower() == 'y':
if platform.system() == "Windows":
 os.system("cls")
else:
os.system("clear")
MenuSet()
runAgn = input("\nWant to run again? (Y/N): ")

MenuSet()
runAgain()
print("Good Bye... HAVE A NICE DAY")
OUTPUT SCREEN
 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
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 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

 HARDWARE AND SOFTWARE
REQUIREMENTS
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 OR MSI
K9MM-V VIA K8M800+8237R
PLUS
CHIPSET FOR AMD ATHALON

IV. RAM : 2GB+

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 : (if print is required - [Hard copy])

SOFTWARE REQUIREMENTS:
 Windows OS
 Python
 BIBLIOGRAPHY
1. http://www.google.com/
2. http://en.wikipedia.org
3. http://computerscience.com
4. http://www.w3resource.com
5. http://www.slideshare.com
6. Computer Science with python by Sumita Arora