Railway Reservation Computer Python Project
Railway Reservation Computer Python Project
01 ACKNOWLEDGEMENT 04
02 INTRODUCTION 05
04 PROPOSED SYSTEM 06
07 FLOW CHART 15
08 SOURCE CODE 16
09 OUTPUT 19
10 TESTING 20
12 BIBLIOGRAPHY 24
ACKNOWLEDGEMENT
lOMoARcPSD|20300694
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 deep sense of gratitude to the luminary The Principal, Sainik School
Amaravathinagar who has been continuously motivating and extending their helping hand to
us.
I express my sincere thanks to the academician The vice Principal, Sainik School
Amaravathinagar, for constant encouragement and the guidance provided during this 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.
The railway reservation system system is basically a database based project done with
help of python language. This project is very use full 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.
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.
PROPOSED SYSTEM
lOMoARcPSD|20300694
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.
INITIATION PHASE
The Initiation Phase begins when a business sponsor identifies a need or an opportunity.
• 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.
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.
• 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
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
alevel of detail sufficient for systems design to proceed. They need to be measurable, testable,
and relate to the business need or opportunity identified in the Initiation Phase. The
requirements that will be used to determine acceptance of the system are captured in the Test
and Evaluation MasterPlan.
• Further define and refine the functional and data requirements and document 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 c onstructed in various ways. Using a top-down approach, designers first identify
and link majorprogram components and interfaces, then expand design layouts as they
identify and link smaller subsystems and connections. Using a bottom-up approach, designers
first identify and link minor program components and interfaces, then expand design layouts
as they identify and link larger systems and connections. Contemporary design techniques
often use prototyping tools that build mock-up designs of items such as application screens,
lOMoARcPSD|20300694
database layouts, and system architectures. End users, designers, developers, database
managers, and network administrators should review and refine the prototyped designs in an
iterative process until they agree on an acceptable design. Audit, security, and quality
assurance personnel should be involved in the review and approval process. During this
phase, the system is designed to satisfy the functional requirements identified in the previous
phase. Since problems in the design phase could be very expensive to solve in the later stage
of the software development, a variety of elements are considered in the design to mitigate
risk.
These include:
• Preparing detailed logic specifications for each software module. The result is a draft
System Design Document which captures the preliminary design for the system.
• Everything requiring user input or approval is documented and reviewed by the user.
Once these documents have been approved by the Agency CIO and Business Sponsor,
the final System Design Document is created to serve as the Critical/Detailed Design
for the system.
• 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
• 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
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.
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:
FLOW CHART
SOURCE CODE
import mysql.connector
mycon=mysql.connector.connect(host=’localhost’,user=’ root’,passwd=’manager’)
cursor=mycon.cursor() mycon.autocommit=True
s1="create database railway" cursor.execute(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))" cursor.execute(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))" cursor.execute(s1)
def ticket_booking():
import mysql.connector Mycon=mysql.connector.connect (host=’localhost’,
User=’root’, passwd=’manager’, database=’railway’) Cursor=mycon.cursor
() mycon.autocommit=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=gender.upper()
fr=input(’enter ur 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,phno,age, v,fr,to,date)
cursor.execute(s1) print(’BOOKED
SUCCESSFULLY’)
mycon=mysql.connector.connect(host=’localhost’,user=’
root’,passwd=’manager’,database=’railway’) cursor=mycon.cursor()
mycon.autocommit=True a=input(’USER NAME:’) b=input(’PASS WORD:’) try:
s1="select user_name from user_accounts where password=’{}’".format(b)
c1="select fname,lname from user_accounts where password=’{}’".format(b)
cursor.execute(c1) data1=cursor.fetchall()[0]
data1=list(data1) data1=data1[0]+’ ’+data1[1]
cursor.execute(s1) data=cursor.fetchall()[0]
data=list(data)[0] if data==a:
print(’ HII ’,data1) return True else:
return False except: print(’ACCOUNT
DOES NOT EXIST’)
def checking_3():
import mysql.connector
mycon=mysql.connector.connect(host=’localhost’,user=’
root’,passwd=’manager’,database=’railway’) cursor=mycon.cursor()
mycon.autocommit=True a=input(’USER NAME:’) b=input(’PASS WORD:’) try:
s1="select user_name from user_accounts where password=’{}’".format(b)
c1="select fname,lname from user_accounts where password=’{}’".format(b)
cursor.execute(c1) data1=cursor.fetchall()[0] data1=list(data1) data1=data1[0]+’
’+data1[1] cursor.execute(s1) data=cursor.fetchall()[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) cursor.execute(s1) data=cursor.fetchall()[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])
else:
return False except:
print(’ACCOUNT DOES NOT EXIST’)
menu()
OUTPUTS
CHOICE WINDOW
IF CHOICE IS4(EXIT)
IF CHOICE IS 5 OR MORE
IF CHOICE IS 5 OR MORE
lOMoARcPSD|20300694
TESTING
TESTING METHODS
Software testing methods are traditionally divided into black box testing and white
box testing. These two approaches are used to describe the point of view that a test engineer
takes when designing test cases.
SPECIFICATION-BASED TESTING
The black box tester has no "bonds" with the code, and a tester's perception is very
simple: a code must have bugs. Using the principle, "Ask and you shall receive," black box
testers find bugs where programmers don't. But, on the other hand, black box testing has been
said to be "like a walk in a dark labyrinth without a flashlight," because the tester doesn't
know how the software being tested was actually constructed.
That's why there are situations when (1) a black box tester writes many test cases to
check something that can be tested by only one test case, and/or (2) some parts of the back
end are not tested at all. Therefore, black box testing has the advantage of "an unaffiliated
opinion," on the one hand, and the disadvantage of "blind exploring," on the other.
White box testing, by contrast to black box testing, is when the tester has access to the
internal data structures and algorithms (and the code that implement these)
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.
• Windows OS
• Python
• mysql connector modulle