Railway Reservation Sysytem.docx

RAILWAY RESERVATION SYSYTEM A Project Report Submitted in partial fulfilment of the Requirements for the award of the Degree of University

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) By

AISHWARYA R WAGHMRE & SANDEEP L SINGH Seat Number-3039866 & 3039837 Under the esteemed guidance of

Mr. Kiran More Assistant Professor

DEPARTMENT OF INFORMATION TECHNOLOGY

SHETH N.K.T.T COLLEGE (Affiliated to University of Mumbai) THANE, 400605 MAHARASHTRA 2018-2019

PNR No.: ……………………

Roll no: ___________

1.

Name of the Student __________________________________________________________________

2.

Title of the Project __________________________________________________________________

3.

Name of the Guide __________________________________________________________________

4.

Teaching experience of the Guide ____________________________________

5.

Is this your first submission?

Yes

No

Signature of the Student

Signature of the Guide

Date: …………………

Date: …………………….

Signature of the Coordinator Date: …………………

NKTT COLLEGE (Affiliated to University of Mumbai) THANE-MAHARASHTRA-400605

DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE This is to certify that the project entitled, "RAILWAY RESERVATION SYSTEM", is bonafied work of MS. AISHWARYA R WAGHMARE & MR. SANDEEP L SINGH bearing Seat. No 3039866 & 3039837 submitted in partial fulfillment of the requirements for the award of degree of BACHELOR OF SCIENCE in INFORMATION TECHNOLOGY from University of Mumbai.

Internal Guide

Coordinator

External Examiner

Date:

College Seal

ACKNOWLEDGMENT We are pleased to present “Railway reservation system” project and take this opportunity to express our profound gratitude to all those people who helped us in completion of this project. We thank our college for providing us with excellent facilities that helped us to complete and present this project. We would also like to thank the staff members and lab assistants for permitting us to use computers in the lab as and when required. We express our deepest gratitude towards our project guide for her valuable and timely advice during the various phases in our project. We would also like to thank her for providing us with all proper facilities and support as the project co-coordinator. We would like to thank her for support, patience and faith in our capabilities and for giving us flexibility in terms of working and reporting schedules. We would like to thank all our friends for their smiles and friendship making the college life enjoyable and memorable and family members who always stood beside us and provided the utmost important moral support. Finally we would like to thank everyone who has helped us directly or indirectly in our project.

DECLARATION I hereby declare that the project entitled, “RAILWAY RESERVATION SYSTEM” done at N.K.T.T COLLEGE THANE has not been in any case duplicated to submit to any other university for the award of any degree. To the best of my knowledge other than me, no one has submitted to any other university. The project is done in partial fulfillment of the requirements for the award of degree of BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) to be submitted as final semester project as part of our curriculum.

Aishwarya R Waghmare & Sandeep L Singh

ONLI

TABLE OF CONTENTS Sr.no Chapter 1

Title Introduction 1.1 Background 1.2 Objectives 1.3 Purpose & Scope

Chapter 2 2.1 2.2 2.3 2.4 2.5

System Analysis Existing system Proposed system Hardware Requirement Software requirement Justification of platform

Chapter 3 3.1 3.2 3.3

System Design Module Division ER Diagram UML Diagram

Chapter 4 Implementation and Testing 4.1 Code 4.2 Testing Approach

Chapter 5

Results and Discussions

Chapter 6

Conclusion and Future Work

Chapter 7

References

Sign

INTRODUCTION

The “railway ticket reservation system” has been developed to override the problems prevailing in the practicing manual system. This software is supported to eliminate an in some cases reduce the hardships faced by this existing system. More over this system is designed for the particular need of the company to carry out operations in a smooth and effective manner. The application is reduced as much as possible to avoid errors while entering the data.it also provides error messages while entering invalid data. no formal knowledge is needed for the user to use the system. Thus by this all it proves it is user-friendly. railway ticket reservation system, as described above, can lead to error free, secure, reliable and fast management system. It can assist the user to concentrate on the record keeping. Thus it will help organization in better utilization of resources. Every organization, whether big or small, has challenges to overcome and managing the information of terminals, trains, fare, customers, booking. Every railway ticket reservation system has different train needs, therefore we design exclusive employee management systems that are adopted to your managerial requirement. This is designed to assist in strategic planning, and will help you ensure that your organization is equipped with the right level of information and details for your future goals. Also, for those busy executive who are always on the go, our system come with remote access fe1.1atures, which will allow you to manage your workforce anytime, all the times. These systems will ultimately allow you to better manage resources.

BACKGROUND IR begins online ticket reservation of I-ticket on Aug. 3, 2002. IRCTC has launched E-ticket facility in August 2005 for IR, which can be booked on www.irctc.co.in It was launched all over the country at the same time. And it is picking up fast; some 300 per cent per month growth has been noted for it. Passenger Reservation System (PRS): CONCERT - country-wide network for computerized enhanced reservation and ticketing - developed by CRIS, is a total networking solution to Indian Railways Passenger Reservation System. In June,1987 an early system for computerized reservations begins operating at Mumbai VT for a few trains (pre- CONCERT). The complete network become operational on 18th April 1999, and has been working satisfactorily since then. PRS network of the Indian Railways has enabled reservations in any train, date, or class, between any pair of stations to the travelling public on about 2000 terminals across the country. CONCERT has been installed at more than 1,721 locations with 6,731 terminals handling more than 3,000 trains and more than 3.3 crore passengers are being booked with average passenger earnings of Rs. 1300 crore per month. On 14th Feb. 2008 all time high 1.9 million transactions were done.

OBJECTIVES 1] To reduce paperwork. 2] Reduced operational time. 3] Increased accuracy and reliability. 4] Fast Process. 5] Increased operational efficiency. 6] Data security. This software package can be readily used by non-programming personal avoiding human handled chance of error. This project will be used by three types of users i. Railway Administrator ii. Authorized Railway Reservation counters iii. Passengers Administrator can access and modify the information stored in the database of this system. This includes adding and updating of train, station, train routes and also managing the user and the passenger details etc. Reservation counters can work on the system forms only but cannot modify the information which is only accessed by Administrator. Passengers can register by providing personal details, make fresh reservation and book one or more (limited to 3 seats per ticket) seats, view past booking and can ever do cancellation of booked ticket, can check seat availability in trains and get the fare details. Department Director can maintain daily updates in details and print reports (e.g. Passenger Current Status) according to need. Administrator is must be an authorized user. Application can be upgraded according to user’s and administrator’s requirements with little changes. New features can be added as per requirements.

PURPOSE AND SCOPE This project has a large scope as it has the following features which help in making it easy to use, understand and modify it: Automation of Reservation Status No Need to do Paper Work. To save the environment by using paper free work. To increase the accuracy and efficiency of the software. Management of Online Database. Management of Online Payment. Main Points are:  Simplified Management of Passengers.  Can be used online.  Online Payment System.  Human friendly interface.

The purpose of railway reservation system is to automate the existing manual system by the help of computerized equipment and full-fledged computer software, fulfilling their requirements, so that their valuable data can be stored for a longer period with easy accessing and manipulation of the same. The required software and hardware are easily available and easy to work with. fast management system. It can assist the user to concentrate on their other activities rather to concentrate on the record keeping. Thus it will help organization in better utilization of resources. The organization can maintain computerized records without redundant entries. That means that one need not be distracted by information that is not relevant, while being able to reach the information. The aim is to automate its existing manual system by the help of computerized equipment and fullfledged computer software. Fulfilling their requirements, so that their valuable data can be stored for a longer period with easy accessing and manipulation of the same. Basically the project describes how to manage for good performance and better services for the clients.

SYSTEM ANALYSIS

EXISTING SYSTEM

Present system is manual. The Project Metrics has to enter all the details of project, documents, and tasks. It also maintenance the team information and also efforts estimation. For this purpose the organization maintain the size of the document, source code and update the information about team member’s details manually, which is much of time consuming process. Limitations of the manual system are as follows: 1.

It is time consuming

1.

It leads to error prone results

1.

It consumes lot of manpower to better results

1.

It lacks of data security

1.

Retrieval of data takes lot of time

1.

Percentage of accuracy is less

1.

Reports take time to produce

1.

Hence Computerization of the existing system is proposed.

PROPOSED SYSTEM

The system will store all the data in a single centralized database. The database will contain the following information.

1.Passenger Details. 2.Station Details. 3.Train Details. 4.Fare Details. 5. User Details.

REQUIREMENT ANALYSIS A Software Requirement Specification (SRS) is a requirements specification for a software is a complete description of the behavior of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. Use cases are also knownas functional requirements. In addition to use cases, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements that impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints) The initial specifications of user requirements may be based on interviews with the database users and on the de signers own analysis of the enterprise. The basic issues that the SRS writer(s) shall address are the following: •External interfaces. How does the software interact with people, the system’s hardware, other hardware, and other software? •Performance. What is the speed, availability, response time, recovery software functions, etc.? •Attributes. What is the portability, correctness, maintainability, security, etc. considerations? In software engineering, a functional requirement defines a function of a software-system or component. A function is described as a set of inputs, the behavior and outputs. Functional requirements may be calculations, technical details, data manipulation and processing specific functionality that show how a use case to be fulfilled. Typically, a generates functional requirements after building use cases. However, this mayhavee x c e p t i o n s s i n c e s o f t w a r e d e v e l o p m e n t i s a n i t e r a t i v e p r o c e s s a n d s o m e t i m e c e r t a i n 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. Atypical functional requirement will contain a unique name and number, a brief summary, and a rationale. This information is used to help the reader understand why the requirement is needed, and to track the requirement through the development of the system. The core of the requirement is the description of the required behavior, which must be a clear and of the required behavior. This behavior from organizational or business rule, or it may be discovered through elicitation sessions with users, stakeholdersand other experts within the organization.

HARDWARE REQUIREMENT

1. Processor: Intel CORE i3 2. Hard Disk: 50 GB min 3. Memory: 1GB RAM or above 4. Others: Internet Connection

SOFTWARE REQUIRMENT 1. Front End: ASP.NET 2. Back End: SQL SERVER 2008 3. Operating System: Windows 7 or above. 4. Frame Work: .NET Framework

REQUIREMENT SPECIFICATION FUNCTIONAL REQUIREMENTS: 1.REQUEST TIME TABLE: Passenger requests database to display railway timetable. 2. DISPLAY TIMETABLE: Database displays timetable to the customer. 3. REQUEST TO RESERVE TICKET: Passenger requests the clerk to reserve his/her ticket. 4.INPUT DETAILS: Clerk asks customer to enter details for the reservation of ticket. 5.RESERVE TICKET: Ticket is reserved and customer pays the fare. 6.REQUEST TO PRINT: Customer requests to print the ticket. 7.PRINT TICKET: Ticket is been printed and handled to the customer. CANCELLATION OF TICKET: REQUEST TO CANCEL TICKET: Customer requests to cancel his/her ticket for which he/she has to give the PNR number. C ANCEL TICKET: Once the PNR number is received, the ticket is cancelled. NON-FUNCTIONAL REQUIREMENTS:

In systems engineering and requirements engineering, nonfunctional requirements arerequirements that specify criteria that can be used to judge the operation of system, rather than specific behaviors. Non-functional requirements are often called qualities of a system. Other ”quality attributes”, “quality goals” and “quality of service requirements” .Qualities, i.e. nonfunctional requirements can be divided into 2 main categories:1.Execution qualities such as security and usability are observable at run time.2.Evolution qualifies, such as extensibility and scalability embody in the static structure of the software system. The Non-Functional requirements of our project are: Time: This project should be completed within the stimulated time period. Cost: The cost involved in marketing the project should be less. Usability: This requirement is present, as this system will interact with the user. Reliability: This system must be highly robust. Performance: It should be fast enough to produce output.

FEASIBILITY STUDY

As the name implies, a feasibility study is used to determine the viability of an idea, such as ensuring a project is legally and technically feasible as well as economically justifiable. It tells us whether a project is worth the investment – in some cases, a project may not be doable. There can be many reasons for this, including requiring too many resources, which not only prevents those but also may cost more than an organization would earn back by taking on a project that isn’t profitable. A feasibility study evaluates the project’s potential for success; therefore perceived objectivity is an important factor in the credibility of the study for potential investors and lending institutions. There are some types of feasibility study –separate areas that a feasibility study examines, described below: 1.

Technical feasibility study: - The assessment focuses on the technical

resources available to the organization determine whether the technical resources meet capacity and whether the technical team is capable of converting the ideas into working system. Technical feasibility also involves evaluation of the hardware, software, and other technology requirements of the proposed system. As the availability of all technical resources this project is technically feasible . 2.

Legal feasibility study:- This assessment investigates whether any aspect of the

project conflicts with legal requirements like zoning laws, data protection acts or social media laws.

3.

Economic feasibility study:- This assessment typically involves the cost benefit

analysis of the project , helping organization determine the viability , cost , and benefits associated with a project before financial resources are allocated.

SYSTEM DESIGN

MODULE DIVISION Admin: A] Add train B] Add train schedule C] Add station for train D] Add fare

User: A] Sign up B] Search train C] Master of passenger D] Book ticket E] Print ticket F] Check PNR status     

Train management module: use for managing the train details. Booking module: use for managing the detail of booking. Customer module: use for managing the details of customer. Timetable management module: use for managing the information and details of the timetable. Station module: use for managing the station detail.

  

Fare module: use for the managing the fare information. Login module: use for the managing the login detail. User module: use for the managing user of the system.

UML DIAGRAMS

Use case diagram

Sequence diagram

Class diagram

Activity diagram

1] For Booking

2] For Cancel Ticket

Collaboration Diagram

State chart diagram

Component Diagram A] component in view classes

B] Component in controller classes

DATA FLOW DIAGRAM

Deployment diagram

PROJECT PLANNING

Software project planning is task which is performed before the production of software actually starts. For project planning it is necessary to keep in mind that Break down project task into smaller, manageable form. Find out various tasks and correlate them. The project planning must also describe the execution, management and control of the project. Project Planning may include following key points: Research:





Research for existing software similar to the one.



Identify the problem to solve in bus pass system.

Design: 



Design the user friendly software.



Define the functionalities of software.

Development:





Development can be gone through two units.



One unit is frontend and other unit is backend.

Review:

 



Integrate all the components or modules.



Test the whole system with the help of experts.



Invite Non -I t people to take review of the software or application.

WBS: (WORK BREAKDOWN STRUCTURE)

PRELIMINARY PRODUCT DESCRIPTION PRODUCT OVERVIEW:

We are assuming that users have a simple understanding of operating website. Basic text field entry and typing skills are assumed by all users.

STAKEHOLDERS:



User:

 Encourage them to utilize the public transportation

system and create the ability to purchase the pass to the bus.



System Administrator:



Want an easy to access database to handle calls from users of drivers asking questions about entries in the database. Admin can edit information or add/remove entire entries from the database side. Analysis working on the preliminary investigation should accomplish the following objectives:     

Client and understand the project request. Determine the size of the project. Determine the technical and operational feasibility of alternative

approaches.  

The organization will obviously be able to gain benefit such as saving

in operating cost, reduction in paper, better utilization of human resources and more presentable image increasing goodwill 

The initial cost setting up the system will include the cost of hardware

and software and maintenance.

CONCEPTUAL MODEL WATERFALL MODEL

The model that is basically being followed is the WATERFALL MODEL, which states that the phases are organized in a linear order. First of all the feasibility study is done. Once that part is over the requirement analysis and project planning begins. If system exists one and modification and addition of new module is needed, analysis of present system can be used as basic model. The design starts after the requirement analysis is complete and the coding begins after the design is complete. Once the programming is completed, the testing is done. In this model the sequence of activities performed in a software development project are: Requirement Analysis Project Planning System design Detail design Coding Unit testing integration & testing

• • • • • • • Here the linear ordering of these activities is critical. End of the phase and the output of one phase is the input of other phase. The output of each phase is to be consistent with the overall requirement of the system. Some of the qualities of spiral model are also incorporated like after the people concerned with the project review completion of each of the phase the work done. WATERFALL MODEL was being chosen because all requirements were known before hand and the objective of our software development is the computerization/automation of an already existing manual working system.

DATABASE DESIGN 1] Admin table: Column name ID USERNAME PASSWORD

Data type INT VARCHAR (50) VARCHAR (50)

Constraint PRIMARY KEY UNIQUE KEY NOT NULL

Data type BIG INT VARCHAR (50) VARCHAR (50) INT VARCHAR (50)

Constraint PRIMARY KEY UNIQUE KEY NOT NULL NOT NULL

Data type BIG INT VARCHAR (50) VARCHAR (50) INT VARCHAR (50) VARCHAR (50) INT

Constraint PRIMARY KEY NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL FOREIGN KEY

Data type INT VARCHAR (20)

Constraint PRIMARY KEY UNIQUE KEY

Data type INT CHAR (20) CHAR (20)

Constraint PRIMARY KEY UNIQUE KEY NOT NULL

2] User table: Column name USER ID USER NAME EMAIL ID PHONE NO TYPE

3] Passenger master table: Column name ID NAME GENDER AGE GOV ID NAME GOV ID NO USER ID

4] Station table: Column name STATION ID STATION NAME

5] Train table: Column name TRAIN ID TRAIN NAME TRAIN TYPE

6] Train running schedule: Column name TRAIN ID DAY

Data type INT DATE/TIME

Constraint FOREIGN KEY NOT NULL

Data type INT INT VARCHAR (50) DATE/TIME DATE/TIME

Constraint FOREIGN KEY NOT NULL NOT NULL NOT NULL NOT NULL

Data type INT VARCHAR (50) VARCHAR (50) INT INT VARCHAR (50) DOUBLE

Constraint PRIMARY KEY NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL

7] Route table: Column name TRAIN ID STOP NUMBER SOURCE/DESTINATION ARRIVAL TIME DEPT TIME 8] Ticket table: Column name PNR PASSENGER NAME GENDER AGE SEAT NO CLASS FARE

SCHEMA DESIGN

SECURITY ISSUES DATA TRANSFER The system will use secure sockets in all transactions that include any confidential customer’s information. The system will not leave any cookies on the customer’s computer containing the user’s password. The system will confirm all transactions which the customers web server.

DATA STORAGE The customer’s web server will never display a customer’s password. It will always be echoed with special character’s representing typed characters. The customer’s web browser will never display a customer’s credit card number after retrieving from database. The system’s back end servers will never display a customer’s password. The customer’s password may be reset but never shown. The system’s back end servers shall only accessible to authenticated administrators. The system’s back end database will always be in encrypted.

IMPLEMENTATION & TESTING

COADING 1. USER REGISTRATION using System; using System.Collections.Generic; using System.Linq; using System.Net; using System.Net.Http; using System.Web.Http; using System.Web.Http.Results; using Rail.Data.Models; using Rail.Data.Context;

namespace Rail.Data.Controllers {

public class UserRegistrationController : ApiController { Rail.Data.Context.MasterContext _masterDb = new MasterContext(); // GET: api/UserRegistration [HttpPost] [Route("api/UserRegistration/ResisterUser")] public IHttpActionResult ResisterUser([FromBody] UserRegistration user) { try { if (ModelState.IsValid) {

var existUser = _masterDb.UserRegistrations.FirstOrDefault(x=> x.UserId == user.UserId); if (existUser != null) { return BadRequest("User alredy exist"); } DateTime zeroTime = new DateTime(1, 1, 1); TimeSpan span = DateTime.Now - user.DateOfBirth.Date; int years = (zeroTime + span).Year - 1; //var u = Convert.ToDateTime(user.DateOfBirth.ToString("dd MM yyyy hh:mm:ss tt")); // if(((DateTime.Now - user.DateOfBirth.Date).TotalDays) >= 18 ){ } var p = new UserRegistration { Id = Guid.NewGuid(), Name = user.Name, UserId = user.UserId, Password = user.Password, Email = user.Email, Gender = user.Gender, DateOfBirth = user.DateOfBirth}; _masterDb.UserRegistrations.Add(p); _masterDb.SaveChanges(); } } catch (Exception e) { } return Ok(); } } }

2.ADD TRAIN MODEL namespace Rail.Data.Models {

using System; using System.ComponentModel.DataAnnotations; using System.ComponentModel.DataAnnotations.Schema;

/// <summary> /// /// [Table("TRAINS")] public class Train { /// <summary> /// /// [Key] [Column("ID", Order = 0)] public Guid Id { get; set; } /// <summary> /// /// [Column("TRAIN_ID", Order = 1)] public string TrainId { get; set; }

/// <summary> /// /// [Column("TRAIN_NAME", Order = 2)] public string TrainName { get; set; }

} } function StationModel(model) { this.id = ko.observable(model.Id); this.stationId = ko.observable(model.StationId); this.stationName = ko.observable(model.StationName);

this.toData = function () { return { 'Id': this.id(), 'StationId': this.stationId(), 'StationName': this.stationName() }; }

this.canSave = function () { var model = this.toData(); // if (!isEqual(this.raw.UserName, model.UserName)) return true; return false; } this.raw = model; }

//event StationId value check function ValidateNumber(event) { var theEvent = event || window.event; var key = theEvent.keyCode || theEvent.which; key = String.fromCharCode(key);

var regex = /^[0-9]$/; if (!regex.test(key)) { theEvent.preventDefault ? theEvent.preventDefault() : (theEvent.returnValue = false); } // var val = document.getElementById("txtmob").value; }

function AppViewModel() { var vm = this; vm.config = ko.observable(); vm.stationId = ko.observable(); vm.stationName = ko.observable(); vm.isSelected = ko.observable(false); vm.selectedRow = undefined; vm.selected = ko.observable(new StationModel({}));

/* Users table implementations */ var columns = [ { title: 'Sr', data: 'id', render: function (data, type, row, meta) { var index = meta.row.length ? meta.row[0] : meta.row; return index + meta.settings._iDisplayStart + 1; } }, { title: 'Station Id', data: 'StationId', "width": "25%" }, { title: 'Station Name', data: 'StationName' }

]; vm.table = $('#users').DataTable({ columns: columns, responsive: true, info: false, "oLanguage": { "sSearch": "" } }); $('#users tbody').on('click', 'tr', function () { var model = vm.table.row(this).data(); if (model) { vm.selectedRow = this; vm.selected(new StationModel(model)); vm.isSelected(true); } }); $('#button').click(function () { table.row('.selected').remove().draw(false); });

// event update vm.onUpdate = function () { var data = vm.selected().toData(); if (data.Id != undefined && data.StationName != "" && data.StationName != undefined) { $.ajax({ type: 'POST', url: 'http://localhost:54081/api/Admin/UpdateStation' + "?_:" + (new Date()).getTime(), // data: { UserName: data.UserName }, data: JSON.stringify(data), //datatype: "json", contentType: 'application/json' }).done(function (response) { vm.table.row(vm.selectedRow).data(response.p);

vm.selected(new StationModel({})); vm.clear(); // report success $.Notify({ caption: 'Success', content: "StationId updated successfully.", type: 'success', icon: "<span class='mif-checkmark'>" }); }).fail(function (x, h, r) { var response = JSON.parse(x.responseText); $.Notify({ caption: 'Update error', content: response.Message, type: 'warning', icon: "<span class='mif-checkmark'>" }); }); } else { $.Notify({ caption: 'Update error', content: "Nothing has changed.", type: 'warning', icon: "<span class='mif-checkmark'>" }); } } // event delete vm.onDelete = function () { var data = vm.selected().toData(); if (data.Id) { $.ajax({ type: 'DELETE', url: 'http://localhost:54081/api/Admin/DeleteStation/' + data.Id + "?_:" + (new Date()).getTime(), // data: { UserName: data.UserName }, //data: JSON.stringify(data), //datatype: "json", contentType: 'application/json' }).done(function (response) { vm.table.row(vm.selectedRow).remove().draw(); vm.clear();

$.Notify({ caption: 'Success', content: "User removed successfully.", type: 'success', icon: "<span class='mif-checkmark'>" }); }).fail(function (x, h, r) { var response = JSON.parse(x.responseText || {}); $.Notify({ caption: 'Update error', content: response.Message || 'Something went wrong. Please try again.', type: 'warning', icon: "<span class='mifcheckmark'>" }); }); } else { $.Notify({ caption: 'Update error', content: "Nothing has changed.", type: 'warning', icon: "<span class='mif-checkmark'>" }); } }

// event cancel vm.onCancel = function () { vm.clear(); vm.stationId(""); vm.stationName(""); } // method vm.clear = function () { vm.stationId(""); vm.stationName(""); vm.selected(new StationModel({})); vm.isSelected(false); }

vm.onSubmit = function () { //var mydate = vm.dob();

if (vm.stationId() != "" && vm.stationId() != undefined && vm.stationName() != "" && vm.stationName() != undefined) { if (vm.stationId().length ==3) { $.ajax({ type: 'POST', url: 'http://localhost:54081/api/Admin/AddStation' + "?_:" + (new Date()).getTime(), data: JSON.stringify({ StationId: vm.stationId(), StationName: vm.stationName() }), contentType: 'application/json' }).done(function (response) { if (response.Type == "Error") { $.Notify({ caption: 'Retrive Error', content: response.Result, type: 'warning', icon: "<span class='mif-checkmark'>" }); } else { vm.table.row.add(response.p).draw(); vm.clear(); $.Notify({ caption: 'Success', content: "Station Added successfully.", type: 'success', icon: "<span class='mif-checkmark'>" }); } }).fail(function (x, h, r) { var response = JSON.parse(x.responseText); $.Notify({ caption: 'Add error', content: response.Message, type: 'warning', icon: "<span class='mif-checkmark'>" }); }); } else { $.Notify({ caption: 'Add Error', content: "StationId should be 3 digits", type: 'warning', icon: "<span class='mif-checkmark'>" }); }; } else { $.Notify({ caption: 'Add Error', content: "Failed all mandatory field", type: 'warning', icon: "<span class='mif-checkmark'>" });

} } vm.getValue = function () { $.ajax({ method: 'get', url: '/api/Config/GetValueConfig' + "?_:" + (new Date()).getTime(), contentType: "application/json; charset=utf-8", success: function (data) { return data; }, error: function (x, h, r) { console.log(x); } }); }

$.ajax({ method: 'get', url: '/api/config/GetValueConfig' + "?_:" + (new Date()).getTime(), contentType: "application/json; charset=utf-8", success: function (data) { //self.dataModel.setConfig(data); /*Get Stations*/ $.ajax({ type: 'GET', url: data.Urls.Data + 'api/Admin/GetStations' + "?_:" + (new Date()).getTime(), contentType: 'application/json', }).done(function (response) {

vm.table.clear(); vm.table.rows.add(response.p).draw(); }).fail(function (x, h, r) { $.Notify({ caption: 'Error', content: "Failed to retrieve Users.", type: 'error', icon: "<span class='mif-checkmark'>" }); }); }, error: function (x, h, r) { console.log(x); } }); } ko.applyBindings(new AppViewModel());

TESTING APPROACH As the project is on bit large scale, we always need testing to make it successful, if each components work properly in all respect to gives desired output for all kind of inputs then project is said to be successful. So the conclusion is to take the project successful, it needs to be tested.

UNIT TESTING Unit testing focuses verification efforts on the smallest unit of the software design, the module. This is also known as Module testing. The modules are tested separately. This testing carried out during programming stage itself. In this testing each module is found to be working satisfactorily as the expected output from the modules.

INTEGRATION TESTING Data can be grossed across an interface, one module can have adverse efforts on another, and integration testing is systematic testing for construction the program structure while at the same time conducting tests to uncover errors associated with in the interface. The objective is to take unit tested modules and build a program structure. All the modules are combined and tested as a whole. Here correction is difficult because the isolation of cause is complicate by the vast expense of the entire program. Thus in integration testing stop, all the errors uncovered are corrected for the text testing steps.

USER ACCEPTANCE TESTING User acceptance of a system is the key factor of the success of any system. The system under study is tested for the user acceptance by constantly keeping in touch

with the prospective system users at the time of developing and making changes wherever required.

TEST CASE DESIGN

Sr No. 1.

2.

3.

Test case name Admin login

User login

User registration

Input Non-Admin Went for login Admin-with Valid user Name and password Non-Register user want to login

Expected output System shows over invalid admin

Actual output As Expected

Remark

As Expected

Pass

Went to homepage

Invalid username password

Enter Invalid working username and username and password working password Invalid Enter correct username and username and password wrong password Go to Enter correct homepage username and password If all of Fill all As textbox is textbox or Expected empty repaired field Enter improper

Pass

Email is wrong

Pass

format of email Enter less or more 10digit mobile no

4.

Train registration

All details with correct value Keep textbox of train id and train name empty Enter train id alphabetic Enter correct train id and empty name

5.

6.

Passenger registration

Station Registration

Mobile no should 10digit You are registered successfully Fill all the field mandatory

As Expected

Pass

As Expected

Pass

As Expected

Pass

Train id should be in number Fill all the mandatory textbox

Enter correct detail of train id and train name

Show train registration successfully

Keep all the textbox is empty

Fill all mandatory fields

Enter all correct details

Show message passenger Registration Successfully

Keep all textbox is empty

Fill all the Mandatory Field

Enter all Correct details

Show message Station

Registration Successfully 7.

Route page

Enter stop no is already entered

Message show stop no is already entered

Keep all textbox is empty

Show message fill All mandatory field

Enter all correct value

Message show route registration is Successfully

As Expected

Pass

RESULTS AND DISCUSSION

USER REGISTRATION

This page is used to show user registration

ADD TRAIN

This page is used to show for adding train.

CONCLUSION & FUTURE WORK

1. We want to our application as it is more user friendly and simple. 2. Main thing which attract users 3. Who provide SMS feature for student exam and result information. 4. More enhancement can be implemented like:  Better user interface for the students  Audio visual aids  More interactive features to enhance the quality of E-Learning. 5. Make the site more dynamic and user friendly.

References     

www.irctc.com www.indianrail.com www.yatra.com www.wikipedia.org www.trainenquiry.com