Railway reservation system

by Nishi Sahlot (0924013022) Subham Bansal(09240130) Shehzad Khan(09240130)

Submitted to the Department of Information Technology in partial fulfillment of requirements for Project of Bachelor of Technology In IT, VI Sem

Sunderdeep Group of Institutions G.B. Technical University April,2012

Declaration
I hereby declare that this submission is my own work and that, to the best of my knowledge and belief, it contains no material previously published or written by another person nor material which to a substantial extent has been accepted for the award of any other degree or diploma of the university or other institute of higher learning, except where due acknowledgement has been made in text.

Railway Reservation System

Certificate
This is to certify that the work which is being presented in the project report entitled Railway Reservation Systemis an authentic report of work carried out under the super vision of MR.Mahesh Kumar Sharma as the project head in Sunderdeep group of Institutions by the students named Nishi Sahlot,Subham Bansal,shehzad Khan I here by certify that above statement made by the candidates is correct to the best of my knowledge.

Mr.Mahesh Kumar Sharma

Railway Reservation System

Acknowledgement
Finally as the report has been completed I thereby acknowledge the contribution of some people probably without whose work this project would not have been at all what it meant to be actually. First of all I would like to acknowledge the contribution of our projet supervisior Mr. Mahesh kumar Sharma whos teaching,timelysuggestions,well guideline and keen interest coupled with easy accessibility was a great help while making this project. And I would also like to appreciate the effort of my whole team for working as a team and their spectacular efferts which make this project to be possible easily.And the internet and books were also very helpful.

Railway Reservation System

Table Of Contents
1.INTRODUCTION
a. Current system b. Need ofproposed system

2.SYSTEMDEVELOPMENT LIFECYCLE 3.ANALYSIS

a. Requirement analysis b.RequirementSpecification

4.DESIGN

a. System Flow Diagram b. Modules identified c. Database Design i. E-R Diagram

5.IMPLEMENTATION
a. Platform Used i. Hardware Platform ii. Software Platform b. Implementation c. Testing i. TestingTechnique used

6.CONCLUSION

a. Important Features b. Limitations c. Future Work

Introduction
Abstract
In this emerging world of computers all most all manual system automatedand computerizedbutmaximumofthemaresocomplexandacommonuserisunabletoo peratethatsoftwaresystem.WearedevelopingtheOnlineRailwayReservationS ystemtomodelthepresentsystemandtoremovethedrawbacks. Thisprojectexploreshowcomputertechnologycanbeusedtosolvethe problemof user.Wespecifically propsway to computerize theadministrationandengineeringofficesofIndian RailwayOnline.Ahighspeedcommunicationnetworkneedstobedevelopedforint erconnectingthe offices ofrailways. This samecommunication network can be used to providehighspeedinternet connectiontothepublicandleasoutnetworkcapacitytointernet serviceproviders.

Railway reservation system

1.Introduction

1.1CurrentSystem

Indiaisthe7thlargestcountryintermsofgeographicalsize.This means there is a need for efficient means for long distance transportation.Thelongdistanceroadnetworkisverypoorlydeveloped inmost partsofIndia.Bulkoflongdistancetrafficiscarriedbythe IndianRailwayasaresultIndianrailways.Thereforeformsabackbone ofpublictransportinIndia.The efficiencyoftherailwaywillincrease resultofcomputerizationduetodramatic reductionincommunication timeamonggeographicallydispersedoffices.Forthe reservationofthe ticketapersongototicketcounteroftherailwayreservationofficeand expenditsvaluabletimeinstandingqueue.Nowtosavethattimewe haveafacilityofOnlineReservationnowwecanbookcancelorsearch other train information just by click on computer.

1.2Needofproposedsystem
To reduce complexity of existing system.Effective management of time. To make work easy, simple and error free. Effective utilization of available resource. To enhance the efficiency and diversification of services activities.User friendly. Interactive graphical user interface.

time

Thescopeofprojectdefinetheprojectfeasibilitythetechnology, finance , and resources best define in technology weather the 7

defectscanbereduced intheprojectandupwhichlevelfinancially, weathertheoverallprojectcostisaffordable.Timedescribetheweather theprojectionfinishingpointwillbeachieve ontimeorbeforetime resources required should be available at the rate of cost and time.

Systemdevelopmentlifecycle

2.1Definition
Asoftwareprocessmodelorasoftwareengineeringisanabstract representation ofa software process. It is a software development strategythat encompassestheprocess,methodsandtoolslayersplus the generic phases namely definitionphase, development phase and supportphase.Aprocessmodelis chosen basedonthenatureofthe project and application, the methods and tools to be used and the controls and deliverables that are required.

2.2SpiralModel

Thespiralmodel,alsoknownasthespirallifecyclemodel,isa systemsdevelopmentlifecyclemodelusedininformationtechnology(IT). Thismodelof developmentcombinesthefeaturesoftheprototyping modelandthewaterfall model.Thespiralmodelisfavoredforlarge, expensive, and complicated projects. The steps in the spiral model iteration can be generalized as follows: 1.The system requirements are defined in as much detail as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system. 2.A preliminary design is created for the new system.This phase is the most important part of "Spiral Model". In this phase all possible (and available) alternatives, which can help in developing a cost effective project are analyzed and strategies to use them are decided.This phase has been added specially in order to identify and resolve all the possible risks in the project development. If risksindicate any kind of uncertainty in requirements, prototyping maybe used to proceed with the available data and find out possible solution in order to deal with the potential changes in the requirements. 3.A firstprototype of the new system is constructed from the preliminary design.This is usually a scaled-down system, and

RailwayReservationSystem representsan approximation of the characteristics of the final product. 4.A second prototype is evolved by a fourfold procedure: 1.Evaluating the first prototype in terms ofits strengths, weaknesses, and risks; 2.Defining the requirements of the second prototype; 3.Planning and designing the second prototype; 4.Constructing and testing the second prototype.

Spiral Model:-

10

3.Analysis
3.1 REQUIREMENTANALYSIS:

Requirementsareafeatureofasystemordescriptionofsomething that is capable of doing in order to fulfill the systemspurpose. Itprovides the appropriate mechanism for understanding what the customerwants,analyzingtheneeds,assessingfeasibility,negotiating a solution, specifying the solution unambiguously, validating the specificationandmanagingtherequirementsastheyaretranslatedinto an operational system. Requirement Analysisis a task done under software engineering and software design. While requirements engineering specifiessoftwaresoperationalcharacteristics i.e. function,databehavior, indicates softwaresinterfaceconstraints, requirementsanalysisletthesoftwareengineer(calledanalysis)torefinethesoft ware allocation and construct models of data, functional and behavioral domains.Moreover,requirementsanalysisprovidessoftwaredeveloper with a representation of data, function and behavior that can be convertedtodata,architectural,interfaceandcomponent-leveldesigns. Atlast,wecansaythattherequirementspecificationmakesavailable, thedeveloperandthecustomer,ameans toassessquality,oncethe software has been built. Softwarerequirementsanalysiscanbecategorizedintofourareas effort, as followsEvaluation and synthesis Modeling Specification Review of

11

RailwayReservationSystem Theanalyststartswiththestudiesofsystemspecificationandthe softwareprojectplan.Itisthenimportanttounderstandthesoftwarein asystemcontext.Also,thereviewofthesoftwarescope,usedtogenerate planningestimate,isnecessary.Next,communicationforanalysismust beestablished,soastoensureproblemrecognition.Thereasonbehind is recognize the basic problem elements perceived by customer.

to

Thenextmajorareaofeffortforanalysis isproblemevaluationand solutionsynthesis.Theengineer(oranalyst)mustdefinealldataobjects thatareextremelyobservable.Hemustevaluatethecontentandflowof information.Also,hemust defineanddescribeallsoftwarefunctions, understand software behavior in the context of the system affected events,establishthecharacteristicsofsystem interface,anduncover additional design constraints. Afterevaluatingthecurrentproblemsanddesiredinformation(i.e., inputand output),theengineerandanalystsynthesizingoneormore solutions.Initially,thedataobjects,processingfunctionsandthesystem behavioraredefinedindetail.Once establishingthisinformation,the analystthenconsidersbasicarchitecturesforimplementation.Thusthe processofevaluationandsynthesisproceedsuntilbothanalystandthe customer are sure that software can be adequately specified for subsequent development steps. Duringtheevaluationandsynthesisactivity,theanalystcreates thesystem modelsoastobetterunderstanddataandcontrolflow, functionalprocessing,operationalbehaviorandtheinformationcontent. The model provides a base for software design and the creation of specifications for the software.

3.2 REQUIREMENTSPECIFICATION:
A Software Requirements Specification (SRS) is acomplete descriptionofthebehaviorofthesystemtobedeveloped.Itincludesa setofusecasethatdescribesalltheinteractionsthattheuserswillhave with the software. Use cases are also known as Functional Requirements. Non-Functional Requirementsare requirements which impose constraints on the design or implementation (such as performance requirements, quality standards, or design constraints).

12

RailwayReservationSystem

3.2.1FUNCTIONALREQUIREMENTS:
In software engineering, a functional requirement defines a functionofasoftware-systemorcomponent.Afunctionisdescribedasa setofinputs,thebehaviorandoutputs.Functionalrequirementsmaybe calculations,technical details,datamanipulationandprocessingand other specific functionality that show how a use case to be fulfilled. Typically, a requirements analyst generates functional requirements after building use cases. However, this may have exceptions sincesoftware development is an iterative process and sometime certain requirements are conceived prior to the definition of the use case. Both artifacts (use cases documents and requirements documents) complement each other in a bidirectional process. Atypicalfunctionalrequirementwillcontainauniquenameand number,abriefsummary,andarationale.Thisinformationisusedto helpthereaderunderstandwhytherequirementisneeded,andtotrack requirement through the development of the system.

the

Thecoreoftherequirementisthedescriptionoftherequired behavior,whichmustbeaclearandreadabledescriptionoftherequired behavior.Thisbehaviormaycomefromorganizationalorbusinessrule, or it may be discovered through elicitation sessions with users, stakeholders and other experts within the organization. Software requirements must beclear, correct unambiguous, specific and verifiable.

13

RailwayReservationSystem DetailedDescription of Functional Requirements:

Template fordescribingfunctional requirements.

Purpose Inputs adescription of the functional requirement its reason(s) whataretheinput;inwhatformwilltheyarrive;fromwhat sourcescantheinputcome;whatarethelegaldomainsof each input Describesthe outcome rather than the implementation; includesanyvaliditychecksonthedata,exacttimingof eachoperation(ifneeded),howtohandleunexpectedor abnormal situations Theform,shape,descriptionandvolumeofoutput;output timing;rangeofparametersintheoutput;unitmeasureof the output; process by which the output is stored or destroyed;processforhandlingerrormessageproducedas output

Processing

Outputs

3.2.2NONFUNCTIONAL REQUIREMENTS:
Insystemsengineeringandrequirementsengineering,non-functional requirementsarerequirementswhichspecifycriteriathatcanbeusedto judge theoperation of system, rather than specific behaviors. Nonfunctionalrequirementsareoften calledqualitiesofasystem.Other terms for non-functional requirements are constraints, qualityattributes, qualitygoalsand quality of service requirements .Qualities,i.e.non-functional requirementscanbedividedinto2main categories: 1.Executionqualities,suchassecurityandusability,areobservable at runtime. 2.Evolution qualities, such as extensibilityand scalability, embody in thestatic structure of the software system. The nonfunctional requirements in our projects are:Time:The project should be completed within the stipulated time period.

14

RailwayReservationSystem Cost:The cost involved in marketing theproject should be less. Usability:This requirementis present, as this system will interact with user. Reliability:This system must be highly robust. Performance:It should be fast enough to produce the output.

3.3USECASEANALYSIS:
UseCase Analysisis an object-oriented method for designing informationsystemsbybreakingdownrequirementsintouserfunctions. Eachcaseisatransactionorsequenceofeventsperformedbyuser.Use casesarestudiedtodeterminewhatobjectsarerequiredtoaccomplish them and how they interact with other objects. 3.3.1GOALS OF USECASEANALYSIS: Designsystemfromusersperspective.Communi catesystembehavior in usersterms. 3.3.2CHARACTEISTICS OF USE-CASEANALYSIS: USE-CASE:The specific ways in which the system is used. Each usecase expresses endtransaction. a completethought or end-to-

3.3.3SOMEKEY COMPONENTS OF USE CASEANALYSIS: ACTORS:Entitiesthatuseorareusedbysystem,typicallypeople, butcouldbeothersystemsordevicesaslongaslongastheyare outside the system being specified. CONNECTIONS:Connections from actors to use cases. RELATIONSHIPS: Relationships betweenactors or between use cases.

15

RailwayReservationSystem

3.4USECASEDIAGRAM:
Auseis adescriptionof asystemsbehaviorasit respondsto arequest that originates from outside of that system. The usecase techniqueisusedin softwareandsystemengineeringtocapturethe functionalrequirementsofasystem.Usecasesdescribetheinteraction betweenaprimaryactor-theinitiatoroftheinteraction-andthesystem itself,representedasasequenceofsimplesteps.Actorsaresomethingor someonewhichexistsoutsidethesystemunderstudy,andthat takes partinasequenceofactivitiesinadialoguewithasystem,toachieve somegoal:theymaybeendusers,othersystems,orhardwaredevices. Eachusecaseisa completeseriesofevents,describesfromthepoint view of the actor. 3.4.1USECASENAME: Ausecasenameprovidesuniqueidentifiersfortheusecase.It shouldbe writteninverb-nounformat,shoulddescribeanachievable goalandshouldbe sufficientfortheendusertounderstandwhatthe use case is about. 3.4.2GOAL: Withoutagoalausecaseisuseless.Thereisnoneedforause casewhen thereisnoneedforanyactortoachieveagoal.Abriefly describes what the user intends to achieve with this use case. 3.4.3ACTORS: Anactorissomeoneorsomethingoutsidethesystemthateither actsonthe system-aprimaryactororisactedonbythesystem-a secondaryactor.Anactormaybeaperson,adevice,anothersystem,or time.Actorsrepresentthedifferentrolesthatsomethingoutsidehasin itsrelationshipwiththesystemwhosefunctionalrequirementsarebeing specified.Anindividualintherealworldcanberepresentedbyseveral actors if they have different roles and goals in regards to a system. 3.4.4PRECONDITIONS: Apreconditionssectiondefinesalltheconditionthatmustbetrue describesthestateofthesystem)forthetriggertomeaningfully causetheinitiationoftheusecase.Thatis,ifthestatedescribesinthe preconditions, the behavior of the use case is indeterminate. (i.e.,

16

RailwayReservationSystem 3.4.5POSTCONDITION: Thepostconditionssectiondescribeswhatthechangeinthestate ofthe systemwillbeaftertheusecasecompletes.Postconditionsare guaranteed to be true when the use case ends. SIMPLEUSECASEDIAGRAMFORONLINERAILWAYRESERVARION SYSTEM:

USER REQUEST FOR BOOKING TICKET

REQUEST FOR TICKET CANCELATION

REQUEST FOR OTHER QUERY

SYSTEM ADMINISTRATOR

VALIDATEUSER

VIEWTRANSACTION 17

RailwayReservationSystem

3.5USECASEDIAGRAM DESCRIPTION:
In theticket reservation system, users are the passenger, the counterclerkandthereservationandticketingsystem(R&Tsystem). Takeeachuserand identifytherolesplayed,whichwouldleadusto identify the roles played. Which, in turn, would lead us to an identificationofuse case? Tableshowstheresultoftheprocessof identifying theuse case. Table showsthe result of the process of identifyingtheusecase;letustakethepassenger(auserofsystem).A passengerasausermayplayoneorthreeroles.i.e.passenger,counter clerk, reservation and ticketing system.

18

RailwayReservationSystem

4.DESIGN
4.1SYSTEMFLOWDIAGRAM:

ASystemFlowDiagram(SFD)showstherelationshipbetweenthe, majorcomponentsinthesystem.Itisasystematicrepresentationofan algorithmoraprocess.Thestepsinaprocessareshownwithsymbolic shapes,andtheflowoftheprocessisindicatedwitharrowsconnecting symbols.

the

In order to improvea process, it is first necessary to understand its operationindetail.Describingthisintextlackstheclarityofapictorial diagram,whereindividualstepsaremoreeasilyseen.Theflowchartisa simple mapping tool that shows the sequence of actions within a process, inaformthatiseasytoreadandcommunicate.The mappingofwhatfollowswhat isshownwitharrowsbetweensequentialactionboxes,as intheillustration.Thisalsoshowstheboxesforprocessstartandend points of which there are normally one each. Processbecomesmorecomplexwhendecisionsmustbemadeon which,outofanalternativesetofaction,mustbetaken.Thedecisionis showninaflowchart asadiamondshapedboxcontainingasimple question to which the answer is yes or no.

19

RailwayReservationSystem

PASSENGER

PROCESS RESERVATON

ADMINISTRATOR

CHACK DATABASE

PROCESS CANCELLATION

CANCELATION AUTHORITY

DATABSE

CHECK STATUS

ENQUIRY AUTHORITY

DATABSE

20

RailwayReservationSystem

Hereare6stepswhichcanbeusedasaguideforcompletingflow diagrams: 1.Describe the process to be charted and to givea chart the title. 2.Start witha triggereventi.e.beginstodrawdiagrambyfirst describing the event which initiatesthe process. 3.Note each successive action concisely and clearly. 4.Gowiththemainflowi.e.whenwereachapointatwhichthe flowchart branches into a numberof alternatives, and the resulting complexitythreatens tooverwhelmtheexercise,choosethemost important alternative to continue flowcharting with. 5.Make cross reference to supporting information. 6.Followtheprocessthroughtoausefulconclusion(endatatarget point).

21

RailwayReservationSystem

SYSTEMFLOWCHART:

START

USER NAME&PASSWORD

IFVALID

GOBACK

ENTER LOCATION Respondto Request AndTicket Booked EndUser Respond to Request and Ticket Cancel

CUSTOMER -1

CUSTOMER-2

CUSTOMER-3

22

RailwayReservationSystem

COMPLEX FLOWCHARTFORORRSDECISION CONTROL:

Start

InputUser Name

Compareittovaliduserlist MaintainedatServer

Yes

Is User Valid

No

Wantto Logout

Yes

Deny Login

No EntertheTrainName,no, Source&Destination

Logout

Stop Is Train Available X 23

RailwayReservationSystem

Is User Authorized

Access Denied

EntertheOperationto Be Performed

Is Option Reservati onof Ticket Yes

No

BookTicket

Is Option Cancelof Ticket No Yes CancelTicket Y

24

RailwayReservationSystem Y

Yes

Is Option Other Information

No

Give Information

AskWhatYouWant

25

RailwayReservationSystem

SystemUser

Request

Server

ServerResponse

LEVEL1DFD OFORRS

26

RailwayReservationSystem

Userand Password SystemUser UserValidation

File Request Servicesto User Server Response

LEVEL2DFD OFORRS

27

DESTINATION

RailwayReservationSystem RUNNING_DAY

SOURCE TRAIN

TRAIN_NO

TRAIN_NAME 1_AC

2_AC

BELONG_TO TRAVELS TATION TRAVEL DATE

DISTANCE

SECOND _CLASS

CHARGE

FARE

DISTANCE BELONG_TO SLEEPER TRAIN_NO CLASS TIME RESRVATION SEAT FIRST_CLASS

STATUS

DATE_OF_JRNY

PNR_NO. SOURCE PASSENGER_DTL 28

RailwayReservationSystem

5. IMPLEMENTATION
5.1PlatformUsed

5.1.1HardwarePlatform:
Clientside: Processor:166 MHz or above RAM:64 MB HardDisk Space: 100 MB

Serverside: Processor:166 MHz or above RAM:64 MB HardDisk Space: 300 MB

5.1.2 SoftwarePlatform:
OperatingSystem:- Windows Xp FrontEnd: - Microsoft Visual Studio 2005 BackEnd: - Sql Server 2005

29

RailwayReservationSystem

1.2 ImplementationLevelDetails:
Databasetable being used is:

Fieldname PNR_Number Source Destination

Data type Numeric Varchar

VarcharTr ain_name VarcharTr ain_number VarcharD eparture_from_source VarcharAr rival_at_destination VarcharD ate_of_journy Name_of_passenger Sex Age Address Nvarchar Telephone_number Numeric 30 Numeric Char Char Numeric

Class Distance Seat_no.

Varchar Numeric Numeric

31

Railway ReservationSystem

5.3Testing:
Softwaretestingisacriticalphaseofsoftwarequalityassurance.It indicates the ultimate review of specification, design and code generation.Oncesourcecodehasbeengenerated,softwaremustbe testedto uncoverandcorrectmaximumpossibleerrors,beforebeing delivered.Testingemphasizesonasetofmethodsforthecreationoftest cases that fulfill overall testing objectives. The primary objectives of software testingare as follows: 1.Testing is a process of executing a program to find an error in it. 2.Agoodtestcaseshouldhaveahighprobabilityoffindinganas- yetundiscoverederror. 3.Atestcasewillbeconsideredsuccessfulifituncoversanas-yetundiscoverederror.

5.3.1TESTINGTECHNIQUEUSED: 1.UNIT TESTING:Unittestingaimstheverificationeffortonthesmallestunit of softwaredesigni.e.,asoftwarecomponentormodule.Ituses procedural designasaguidetotestmajorcontrolpathsand uncovererrorswithin themoduleboundary.ItisaWhitebox orientedandthestepcanbe conductedinparallelformultiple components. Unittestingisadynamicmethodforverification,wherethe program isactuallycompiledandexecuted.Itisoneofthemost widelyusedmethods, andthecodingphaseissometimescalled codingandunittestingphase.Thegoalofunittestingis to testmodulesor units,notthewholesoftwaresystem.Unittestingis mostoftendonebytheprogrammerhimself/herself.Thegoal of Unittestingistoisolateeachpartoftheprogramandshowthat the individual parts are correct. A unittest provides a strict, writtencontractthatthepieceofcodemustsatisfy.Asaresult,it affords several benefits.

32

RailwayReservationSystem

2.INTEGRATIONTESTING:Integrationtestingisaphaseofsoftwaretestinginwhich individual software modules are combined and tested as a group.It follows snit testing and precedes system testing. The major objective of integration testing is to tackle the problem of integrationi.e.puttingallthemodulestogether.Onemodulecan haveaninadvertent, adverse effecton another,subfunctions, when combined, may not be magnified to unacceptable levels; globaldatastructurecancauseproblemsandtotruncatethislist of problems we use integration testing. IntegrationtestingstrategyusedisBottom-UpIntegration Testing.In itallthebottomorlowlevelmodules,proceduresor functions are integrated and then tested. After the integration testingoflowerlevelintegrationmodules,thenextlevelofmodules will be formed and can be used for integration testing. This approachishelpfulonlywhenallormostofthe modulesofthe samedevelopmentlevelareready.Thismethodhelpstodetermine thelevelsofsoftwaredevelopmentand makeseasiertoreport testing progress in the form of a percentage.

3.VALIDATIONTESTING:Attheclimaxofintegrationtesting,softwareisdevelopedas apackage havingalltheerrorsuncoveredandcorrected.Atthis time,afinalseriesofsoftware testMaybeing.Itiscalledvalidation testing. Validation succeeds when software function in a reasonably expectablemanner. Validation attemptsto uncover errors, but the emphasis is on the requirements level i.e. the things that will be immediately apparent to the customer.

33

RailwayReservationSystem

6. CONCLUSION
6.1 LIMITATIONOFTHEPROJECT:
1.Themostsignificantlimitationofoverprojectisitsdependency overthe serverbecauseofthiswhenisfailthenwholeworkistobe stopped. 2.Response timeof the system mayvary because of variable network speed. 3.Anotherlimitationofourprojectisthatinthissoftwareand requirement is high comparison of existing system. hardware

6.2DIFICULTIESENCOUNTERED:
Thereweremanydifficultiesthatcame in ourwayin theprocess of development of this real time project some of them are illustrated below. 1.Real time transfer of the file with minimum time delay. 2.Searching an efficient security package and studying its usage. 3.Enablingthemultiuserenvironmentandsimultaneoususageof files.

6.3 FUTUREENHANCEMENT: 1.Extra and user defined security needs can be employed during request
and response. 2.Recordsof client activities can be maintained. 3.Anotherenhancementwouldbetoaddmoremodulestocoverall information off the system.

6.4 CONCLUSION:
Ratherthandesigningmanuallywehavemadeuseofcomputeras oncethatdatasareinput it performsaccurate function. Thereisno chanceoffaultormiscalculationifthedataarefeededcorrectly.Useof thecomputershassolvedmanyproblems,whicharefacedwhilemanual calculation. This is not the end but beginning of the versatile, efficient and outsourcing railway reservation system. This is the one which is

34

RailwayReservationSystem compatibletoalloperatingsystem.Bymakingthisweprojectwemade footsteptowardsthepathofprogressofplatformindependent reservation system. small railway

35

36