TABLE OF CONTENTS

SER DESCRIPTION PAGE NO

01 ACKNOWLEDGEMENT 07

02 INTRODUCTION 09

03 OBJECTIVES OF THE PROJECT 09

04 PROPOSED SYSTEM 11

05 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 13

06 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 15

07 FLOW CHART 31

08 SOURCE CODE 33

09 OUTPUT 53

10 TESTING 67

11 HARDWARE AND SOFTWARE REQUIREMENTS 73

12 BIBLIOGRAPHY 75
 RAILWAY RESERVATION SYSTEM

INTRODUCTION
The railway reservation system is basically a database based project

done with help of python language. This project is very useful for the people to

book or cancel train tickets by sitting at home with one cell phone in their

hand. This project can be modified for various reservations.

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.

9
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 error 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 organizations. 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.

11
1
 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The System Development Life Cycle as used in the

Construction of the Server Appliance

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

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

15
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, 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

17
 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’ 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

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

21
DESIGN PHASE

The design phase involves converting the informational, functional, and

network requirements identified during the initiation and planning phases into
unified design specifications that developers use to script programs during
the development phase. Program designs are constructed in various ways.
Using a top-down approach, designers first identify and link major program
components and interfaces, then expand design layouts as they identify and
link smaller subsystems and connections. Using a bottom-up approach,
designers first identify and link minor program components and interfaces,
then expand design layouts as they identify and link larger systems and
connections. Contemporary design techniques often use prototyping tools
that build mock-up designs of items such as application screens, database
layouts, and system architectures. End users, designers, developers, database
managers, and network administrators should review and refine the
prototyped designs in an iterative process until they agree on an acceptable
design. Audit, security, and quality assurance personnel should be involved in
the review and approval process. During this phase, the system is designed to
satisfy the functional requirements identified in the previous phase. Since
problems in the design phase could be very expensive to solve in the later
stage of 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.

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

25
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
assesses the system security and issue a security certification and
accreditation prior to installation/implementation.

Multiple levels of testing are performed, including:

• Testing at the development facility by the contractor and possibly
supported by end users
• Testing as a deployed system with end users working together with
contract personnel
• Operational testing by the end user alone performing all functions.
Requirements are traced throughout testing, a final Independent
Verification & Validation evaluation is performed and all documentation
is reviewed and accepted prior to acceptance of the system.

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.

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

29
 FLOW CHART
4. THEN THE [Link]
DATA WILL BE PROGRAM WILL
SEND TO THE BE EXECUTED IN
PYTHON IDLE. PYTHON IDLE .
3. THE 2. AS THE
REQUIRED PYTHON AND
DATA WILL BE MYSQL ARE
TAKEN FROM CONNECTED
THE THE COMMAND
DATABASE. WILL BE SENT
TO MYSQL.
31
 SOURCE CODE

# MySQL connectivity

import [Link] as mc
mycon=[Link](host='localhost',user='root’,
password='smbm')
cursor=[Link]()
[Link]=True

s1="create database railway"

[Link](s1)

s1="use railway"
[Link](s1)

s1="create table railway(name varchar(100) , phno

varchar(15) primary key , age int(4) , gender
varchar(50) , from_f varchar(100) , to_t varchar(100)
,date_d varchar(20))"
[Link](s1)

s1="create table user_accounts(fname varchar(100) ,

lname varchar(100) , user_name varchar(100) ,
password varchar(100) primary key , phno varchar(15)
, gender varchar(50) , dob varchar(50) , age
varchar(4))"
[Link](s1)

# MAIN

def menu():
print()
print('\t\t* WELCOME *')
print('[Link]')
print('[Link]')
ch=int(input('DO YOU WANT TO CONTINUE OR NOT:'))
print('\n')

33
while ch==1:
print('WELECOME TO ONLINE RAILWAY RESERVATION
SYSTEM')
print('[Link] IN')
print('[Link] UP')
print('[Link] ACCOUNT')
print('[Link]')
ch1=int(input('ENTER YOUR CHOICE : '))

if ch1==1:
a=checking()
if a==True:
print('\t\t***************************')
print('\t\t* *')
print('\t\t* WELCOME *')
print('\t\t* *')
print('\t\t***************************')
print()
main()

else:
continue

elif ch1==2:
a=checking_1()
if a==True:
main()
else:
print('\t\tPASSWORD ALREADY EXISTS')
continue

elif ch1==3:
c=checking_2()
if c==True:
print('\t\tACCOUNT DELETED')
print()
continue
else:
print('\t\tYOUR PASSWORD OR USER_NAME
IS INCORRECT')
continue

35
 elif ch1==4:
print('\n')
print(‘\t’,’\t’,’\t***********’)
print('\t','\t','\t* *')
print('\t','\t',’\t*THANK YOU*')
print('\t','\t’,'\t* *')
print(‘\t’,’\t’,’\t***********’)
print('\n')
break

else:
print('\t\tERROR 404 : PAGE NOT FOUND')
break

def main():
print('[Link]')
print('[Link]')
c=int(input("Do you want to continue or not : "))
print('\n')
while (c==1):
print("\t\t*********************************")
print("\t\t* SELECT YOUR PREFERENCE *")
print("\t\t*********************************")
print()
print('[Link] BOOKING' , "\n" , '[Link]
CHECKING' , "\n" , '[Link] CANCELLING' , "\n" ,
'[Link] DETAILS' , "\n" , '[Link] OUT')
ch=int(input('Enter ur choice : '))
print('\n')
if ch==1:
ticket_booking()
elif ch==2:
ticket_checking()
elif ch==3:
ticket_cancelling()
elif ch==4:
checking_3()
elif ch==5:
print('\t\t*****************************')
print('\t\t* *')
print('\t\t* THANK YOU! *')
print('\t\t* *')
print('\t\t*****************************')

37
 print()
print()
break
else:
print('\t\tERROR 404: ERROR PAGE NOT
FOUND')

def ticket_booking():
import [Link]
mycon=[Link] (host='localhost',
user='root', password='smbm',database='railway')
cursor=[Link] ()
[Link]=True
nm=input('Enter your name: ')
phno=input('Enter your phone number: ')
age=int(input('Enter your age: '))
print('M=MALE' , '\n','F=FEMALE' , '\n' , 'N=NOT
TO MENTION')
gender=input('Enter your gender : ')
Gender=[Link]()
fr=input('Enter your starting point: ')
to=input('Enter your destination: ')
date1=input('Enter date(dd): ')
date2=input('Enter month(mm): ')
date3=input('Enter year(yyyy): ')
date=date1 + "/" + date2 + "/" + date3
a={'M':'MALE' , 'F':'FEMALE' , 'N':'NOT TO
MENTION'}
v=a[Gender]
s1="insert into railway
values('{}',{},{},'{}','{}','{}','{}')".format(nm,phn
o,age,v,fr,to,date)
[Link](s1)
[Link]()
print()
print('\t\t* BOOKED SUCCESSFULLY *')
print()

def ticket_checking():
import [Link]
mycon=[Link](host='localhost',us
er='root',password='smbm',database='railway')
cursor=[Link]()

39
 [Link]=True
print('[Link]')
print('[Link]')
ch=int(input("Do you want to continue or not: "))
print('\n')

if ch==1:
phno=int(input('Enter your phone number: '))
print('\n')
try:
s1="select * from railway where
phno={}".format(phno)
[Link](s1)
data=[Link]()[0]
Data=list(data)

a=['NAME','PHONE,NUMBER','AGE','GENDER','STARTING
POINT','DESTINATION','DATE']
print(a[0],'::::',Data[0].upper())
print(a[1],'::::',Data[1])
print(a[2],'::::',Data[2])
print(a[3],'::::',Data[3].upper())
print(a[4],'::::',Data[4].upper())
print(a[5],'::::',Data[5].upper())
print(a[6],'::::',Data[6])
print('\n')
except:
print('\t\tTICKET DOES NOT EXISTS'))

elif ch==2:
print('\t\tTHANK YOU')

else:
print('\t\tERROR 404 : PAGE NOT FOUND')

def ticket_cancelling():
import [Link]
mycon=[Link](host='localhost',
user='root',password='smbm',database='railway')
cursor=[Link]()
[Link]=True
print('[Link]')
print('[Link]')
ch=int(input("Do you want to continue or not: "))

41
 print('\n')

if ch==1:
phno=input('Enter your phone number: ')
print('\n')
s1="delete from railway where phno=phno"
[Link](s1)
print('\t\tTICKET CANCELLED')
print()

elif ch==2:
print('\t\tTHANK YOU')

else:
print('\t\tERROR 404 : PAGE NOT FOUND')

def checking_3():
import [Link]
mycon=[Link](host='localhost',
user='root',password='smbm',database='railway')
cursor=[Link]()
[Link]=True
a=input('USER NAME : ')
b=input('PASSWORD : ')
print()

try:
s1="select user_name from user_accounts where
password='{}'".format(b)
c1="select fname,lname from user_accounts
where password='{}'".format(b)
[Link](c1)
data1=[Link]()[0]
data1=list(data1)
data1=data1[0] + ' ' + data1[1]
[Link](s1)
data=[Link]()[0]
data=list(data)

if data[0]==a:
x=['FIRST NAME' , 'LAST NAME' , 'PHONE
NUMBER' , 'GENDER' , 'DATE OF BIRTH' , 'AGE']

43
 s1="select fname, lname, phno, gender,
dob, age from user_accounts where password='{}'"
.format(b)
[Link](s1)
data=[Link]()[0]
data=list(data)
print(x[0],':::',data[0])
print(x[1],':::',data[1])
print(x[2],':::',data[2])
print(x[3],':::',data[3])
print(x[4],':::',data[4])
print(x[5],':::',data[5])
print('\n')
else:
return False

except:
print('\t\tACCOUNT DOES NOT EXIST')

def checking_2():
import [Link]

mycon=[Link](host='localhost',user='
root',password='smbm',database='railway')
cursor=[Link]()
[Link]=True
print()
a=input('USER NAME : ')
b=input('PASSWORD : ')
try:
s1="select user_name from user_accounts where
password='{}'".format(b)
[Link](s1)
data=[Link]()[0]
data=list(data)
if data[0]==a:
print()
print('\t\t* IS THIS YOUR ACCOUNT *')
print()
s1="select user_name from user_accounts
where password='{}'".format(b)
c1="select fname,lname from user_accounts
where password='{}'".format(b)

45
 [Link](c1)
data1=[Link]()[0]
data1=list(data1)
data1=data1[0] + ' ' + data1[1]
[Link](s1)
data=[Link]()[0]
data=list(data)
if data[0]==a:
x=['FIRST NAME','LAST NAME','PHONE
NUMBER','GENDER','DATE OF BIRTH','AGE']
s1="select fname , lname , phno ,
gender , dob,age from user_accounts where
password='{}'" .format(b)
[Link](s1)
data=[Link]()[0]
data=list(data)
print(x[0],':::',data[0])
print(x[1],':::',data[1])
print(x[2],':::',data[2])
print(x[3],':::',data[3])
print(x[4],':::',data[4])
print(x[5],':::',data[5])
print('\n')
print('[Link]')
print('[Link]')
vi=int(input('Enter your choice : '))
print('\n')

if vi==1:
b1="delete from user_accounts
where password = '{}'".format(b)
[Link](b1)
return True

elif vi==2:
print('\t\tSORRY,RETRY')

else:
print('\t\tERROR 404 : PAGE NOT
FOUND')
return False
except:
print('\t\tACCOUNT DOES NOT EXIST')

47
def checking_1():
import [Link]
mycon=[Link](host='localhost',
user='root',password='smbm',database='railway')
cursor=[Link]()
[Link]=True
f=input("FIRST NAME: ")
l=input("LAST NAME: ")
a=input('USER NAME: ')
b=input('PASSWORD: ')
c=input('RE-ENTER YOUR PASSWORD: ')
ph=input("PHONE NUMBER: ")
print(' m=MALE' , '\n' , 'f=FEMALE' , '\n' ,
'n=NOT TO MENTION')
gen=input('ENTER YOUR GENDER: ')
print("ENTER YOR DATE OF BIRTH")
d=input("DD: ")
o=input("MM: ")
p=input("YYYY: ")
dob=d + '/' + o + '/' + p
age=input("YOUR AGE: ")
print('\n')
v={'m':'MALE' , 'f':'FEMALE' , 'n':'NOT TO
MENTION'}

if b==c:
try:
c1="insert into user_accounts
values('{}','{}','{}','{}','{}','{}','{}','{}')".form
at(f,l,a,b,ph,v[gen],dob,age)
[Link](c1)
print('\tWELCOME',f,l)
return True
except:
print('\t\tPASSWORD ALREADY EXISTS')
return False

else:
print('\t\tBOTH PASSWORDS ARE NOT MATCHING')

49
def checking():
import [Link]
mycon=[Link](host='localhost',
user='root',password='smbm',database='railway')
cursor=[Link]()
[Link]=True
print()
a=input('USER NAME : ')
b=input('PASSWORD : ')
print()

try:
s1="select user_name from user_accounts where
password='{}'".format(b)
c1="select fname,lname from user_accounts
where password='{}'".format(b)
[Link](c1)
data1=[Link]()[0]
data1=list(data1)
data1=data1[0] + ' ' + data1[1]
[Link](s1)
data=[Link]()[0]
data=list(data)[0]
if data==a:
print('\t HI! ', data1 , '\n')
print()
return True
else:
return False

except:
print('\t\tACCOUNT DOES NOT EXIST')
print()

menu()

51
 OUTPUT
CHOICE WINDOW

IF CHOICE IS 1(SIGN UP WINDOW)

53
IF CHOICE IS 2(SIGN UP WINDOW)

55
IF CHOICE IS 3(DELETE ACCOUNT)

IF CHOICE IS 4(EXIT)

IF CHOICE IS 5 OR MORE

57
SECOND CHOICE LIST AFTER LOGIN

IF CHOICE IS 1(TICKET BOOKING)

59
 IF CHOICE IS 2(TICKET CHECKING)

IF CHOICE IS 3(TICKET CANCELLING)

61
IF CHOICE IS 4(ACCOUNT DETAILS)

IF CHOICE IS 5(LOG OUT)

63
IF CHOICE IS 5 OR MORE

65
 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

67
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 behavior),
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.

69
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:
• Ape 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

71
 HARDWARE REQUIREMENTS

[Link] SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM (ANY) OR AMD
ATHALON (3800+- 4200+ DUALCORE)
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 : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS

I. Windows OS
II. Python
III. MySQL connector module

73
3
 BIBLIOGRAPHY

• Computer Science with Python - Class XII By :

• A Project Report On
RAILWAY RESERVATION SYSTEM By :
• Website: [Link]

75