• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Railway Ticket Issuing System (Online)
 

Railway Ticket Issuing System (Online)

on

  • 5,120 views

The software solution implements a Railway Ticket Issuing System (RTIS) for the Sri Lanka Railways Department (SLRD). The solution allows to overcome the extreme human intervention to the current ...

The software solution implements a Railway Ticket Issuing System (RTIS) for the Sri Lanka Railways Department (SLRD). The solution allows to overcome the extreme human intervention to the current ticket issuance process. The proposed system will be an automated system so that SLRD will be able to manage their ticketing transaction efficiently.

Team Members:
Rashmika Nawaratne
Malinga Perera
Rumal Perera
Chaamini Mangaleswaran
Dilaj Perera

Statistics

Views

Total Views
5,120
Views on SlideShare
5,120
Embed Views
0

Actions

Likes
0
Downloads
143
Comments
1

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Purchasing railway tickets without traveling to the railway stationAccording to the nature of the existing system, if passenger needs to buy a railway ticket then he should go to the railway station and buy railway ticket from the counter located in the station. There is no alternative procedure to buy a ticket without go to the station. This process gave rise to considerable passenger discomfort and waste their time and resources. Delay of the prevailing manual ticket issuing procedureTickets had to be purchased at the railway station from which the passengers are departing and are available for purchase only on the day that train departure. So passengers need to wait in long queues at congested stations to buy their tickets. This process cause to considerable passenger discomfort.Difficulty of the performance of railway counter staffAccording to the existing ticket issuance procedure, the sale is done through railway staffed service counters with a long queue of people waiting to buy the tickets. Monitoring of counter staff performance is too difficult, as there are no means to check opening times and hourly per clerk transactions. So instead of focusing on the primary task of selling tickets effectively, a large amount of effort was expended How to share the details about ticket issuance among the railway stationsInvalid ticketsThe conventional ticketing system used printed cards based on different series of ticket classified by destination class, date and route. At the railway station, the railway conductors check the validity of the ticket from the appearance of the ticket and punch it. There is no precise process to check the validity of them.
  • Credit card or mobile based paymentATIS will enable credit card payments for railway ticket issuance online, thereby facilitating electronic commerce for credit card holders. Also passengers who do not have credit card facilities can make payments via their mobiles. Enables purchasing railway tickets from any placePassengers who expect to buy a railway ticket without go to the railway station only need web browsing facilities and payment facilities. 24x7 available ticketingSince the system work in fully automated background, the railway tickets will be issued without any human intervention. Both ATIM and online ticket issuance will be manned 24/7, 365 days per year.Enables centralized control for monitoring and auditingAll major railway stations will be connected to state of the art data center located in the Western Province by high speed network.
  • High Speed Ticket IssuanceSince ATIS is a fully automated system, it no needs human (railway staff) intervention. TheATIMis capable to issue a ticket within 30 seconds. That means, the ticket issuing time of the ATIM is only depends of the time taken for filling requite data. It is also common for ticket purchasing via SLRD or LGP web sites. High ReliabilityThe major data center of the system is associated with the disaster recovery center (DRC). The DRC is established in order to minimize system failures due to loss of data and it will be manned 24/7, 365 days per year. Therefore, the system will be available at any time and the rate of failure occurrence of the system will be very little. User friendly GUIThe ATIM provides a very user friendly simple interface with comprehensive user guidance. Passengers can continue ticket purchasing procedure in their preferred language (Sinhala, English or Tamil). The ATIM s have touch screen, which are more intuitive. More details about the GUI of the ATIM will be discussed in the next slide.The SLRD and LGP provide a simple and comprehensive web page for railway ticket purchasing. When user makes some errors while entering the required details, relevant web server (SLRD or LGP) will provide comprehensive notice about the errors.Quick responseThe ATIMs are connected to the major data center (State of the art data center) through a high speed network. Also the data center is connected with Lanka Government Network through a high speed VPN. So, data sharing process between the ATIM and the data center and a web client and the data center will be very fast. It causes to make quick response.
  • As default the ATIM will be displayed in the screen in English. If passenger is not familiar with English language, He/she can select the preferred language by touching the appropriate button.Destination city can be selected by typing the name of that. When first few letters are typed, a list of possible destinations will be displayed. To move next step, the passenger needs to select the destination and touch the “NEXT” button.Then the ATIM will request the number of passengers. If age of the passenger is greater than 11 years, then he/she will be considered as an adult. Persons who are aged 4 – 11 are considered as children.After selecting departure date and departure time, the ATIM will display the list of trains with their information.Next, the passenger requires to select the class. At this occasion, the passenger will be able to know the price for a ticket. Then the ATIM will display all details about the current transaction (including total cost, departure and arrive time etc.). To continue the ticket purchasing process, the system will ask to make payments. Therefore if passenger needs to buy tickets, then he/she should insert currency notes into appropriate slot of the ATIM. After making correct payments, the railway tickets will be issued.
  • Now let us have an overview of the Major Stakeholders of this Project.Initially we’ll identify the Internal Stakeholders who are closely related to the proposed system.Railway Station StaffShould not resist to adopt the new system.If they have any resistance regarding this new system, it would be hard to accomplish our system goals.Should assist the Passengers in case of need.Railway ConductorsShould not resist to adopt the new system similar to the station staff.Should ensure the passengers use the new system in the correct manner.Railway Department AdministrationShould be specific and precise about requirementsShould set requirement prioritiesPromptly communicate changes to requirementsShare all the required information with the project teamShould provide resources to the Development Team as per to the contract.System EngineersMonitor the system in functioning 24/7Should recover the system as soon as possible in case of a failureProvide regular status report of the systemRailway PassengersPassengers are required to get familiar with the new system because it will benefit both the department as well as passengers in an effective manner.
  • Our External Stakeholders are also have a major contribution towards the success of the project.ICTA and Sri Lanka Government ICTA will implement the online ticket issuing portal in their LankaGate website.Therefore they should ensure the security and the confidentiality of customer information.Also we will be using Lanka Government Network as an reliable underlying information infrastructure backbone.Thus ICTA and Sir Lanka Government should provide high availability, security and reliability for the information communication.Mobile Service ProvidersShould provide SMS based billing and ticket issuing facilityShould guarantee 24/7 serviceSecure confidentiality of customer information BanksShould provide credit card based billingShould guarantee 24/7 serviceSecure confidentiality of customer information Internet Service ProvidersShould provide secure wide area network Should guarantee 24/7 serviceShould Provide secure VPN
  • The most important aspect of this kickoff meeting is to approve the software development process which we would be using throughout the development.The Railway Online Ticketing system is a brand new idea to implement in Sri Lanka. So with the development progress new requirements and ideas might take place. Thus we need to give chance to implement those ideas in the software as it goes. This reason and by taking into consideration the other characteristics of the proposed software, we would like to use an agile process model.Agile software development bases itself on an iterative and incremental approach. Software developers work on small modules, and respond to users' changed requirements rather than follow a specific or predetermined plan of action. The basic design is simple, and changes are made as work progresses.Unlike with traditional process models, testing and customer feedback occurs simultaneously with development. This method gives priority to collaboration over design. Interactions among stakeholders take priority over processes and tools, and working software takes priority over documenting procedures. Different developers may work on different modules, and integrate all modules together at the end.As the methodology of Agile Process Model we will be using Agile-Rational Unified Model.The main reason behind this is our development team has not much exposed to new agile process models such as extreme programming or Scrum. And we are not much interest in working with XP because it seems to be too light: XP doesn't explicitly show how to create some of the artifacts which management wants to see.  This is an unfortunate attitude because XP is a great process.Through-out our software engineers have been exposed to RUP model thus they are experts in it.In RUP, which management seems to love but developers seems leery of due to the large number of artifacts.  This is also unfortunate because the RUP has a lot to offer, and can be cut down to something quite useful.  The AUP lands between the two, adopting many of the agile techniques of XP and other agile processes yet retaining some of the formality of the RUP.  Taking into account the both above consideration, we would like to choose Agile Unified Model.
  • In the first 2 phases which are namely inception and elaboration, we will use this time to understand and model the solution domain. Therefore we will not be give a high priority for the stakeholders to make any changes to the system in this point of time. During the Engineering stage we try to avoid burdening the users with change control procedures. In turn, they should not expect firm commitments until the delivery team has implemented some of the requirements. It is acceptable to add, change, and reprioritize requirements on the stack in the early iterations as the users see fit.After high project risks were addressed and the team gets a fine understanding about the developing system, we will allow stakeholders to submit there change requirements. We will name this last 2 phases as Production stage.
  • You can see a high-level architectural diagram of the proposed automated ticket issuing system.In our railway department online ticket issuing system, we have identified 5 major components.Initially we have to implement the Application software with the main data store. The primary software should run with it.The Disaster Recovery System should be connected to the main data store and it should be manned 24/7, 365 days per year.The main data store should be connected to Lanka Government Network by a VPN.Mainly we should connect the Automatic Ticket Issuing Machine to the Remote Main Data Store and Application Software via Internet.Also we should make the online ticket issuing service available to Lanka Gate and Sri Lanka Railway Department Website
  • This diagram is a detailed level layered architecture of the software system we are implementing.To design the Software we will be using 5 tier architecture.The bottom most later in the application software is the data access later. The SOTA Data center will be connected to Main Data Store, Disaster Recovery Center and connected to Lanka Government Network Data center via high speed VPN.The 2nd layer is the transaction management layer. It will control all the transactions. Major aspect of this layer is commit and rollback of the transactions.The 3rd layer is the Business Logic Layer. It will handle all the main business functions.The 4th Layer is Authentication and Modification Layer. It will handle authentication, data modification according to the system requirements. And also encapsulation of data will be handled here.The External Service Portal will be distributed within all the 2nd, 3rd and 4th layers. The mobile services and Credit card payment will be handled via this.We will be using the SMS and Credit Card functions from Lanka Gate. Since we are loosely coupled with Lanka Gate here, in case lanka gate shuts down we will be able to get the same services from another vendor.The 5th layer is network communication layer. It will allow HTTP connections as well as WSDL services.The Lanka gate web site and SLRD website will be using the Online Ticket Issuing Service provides by the application architecture. The ATIM system is implemented with 3 tier architecture.At the bottom it will have ATIM client which is to be connected to Server-SideThen the logic layer and UI layer will be there.
  • The serial nature of Agile UP is normally captured in its four phases : 1Inception: This is the first phase where the initial scope of the entire project is identified. Based on the initial requirements analysis, we propose the potential architecture to the client, come with an agreement and obtain the initial funding for the project. 2 Elaboration: The second phase consists of proving the potential architecture of the system. We do this by making the technical design - both High Level Design and Low Level Design. HLD will focus on laying the overall architecture and framework for the project. It results in Project Decomposition into modules/functions/entities/classes etc. LLD incorporates the pseudo code and definition of all technical interfaces of the project. 3Construction: The third phase consists of construction phase where we build working software on a regular, incremental basis. Hence, construction phase consists of series of development releases. Development releases are small releases and have the potential of being released on the production server. However, they have not undergone pre-production steps like testing and deployment.4Transition: This last phase differs from the transition phase of RUP as instead of releasing the entire product in one release, the product is released in versions. The first production release is greater in time than others. The entire life cycle of AUP is repeated for every production release with few modifications. After every production release, the business requirements for the project are modified. Any new change requirements, after prioritizing, are added in the stack. The stack may be reprioritized. Changes, if needed are made in the technical designs. Then, the construction and the transition phases follow, where every iteration implements those number of tasks that can be implemented in the current iteration.Here we have adopted the four phases of RUP with slight modification namely Planning and Designing , Developing / Building, Validating , Deployment and Evaluating . As high importance goes to validating the system we have made that as a separate phase and post implementation validation is identified as Evaluating phase. The figure shows how each phase fit in to traditional AUP phases.
  • Project phases becomes important in the context of achieving the project’s purpose and its objectives stated by the policy. A milestone is the end of a stage that marks the completion of a work.Milestones can add significant value to project scheduling by giving an estimate when each task should be achieved Milestones are linked with project phases, where each phase is defined in terms of schedule and also in terms of specific accomplishments1.Planning and designing In this phase, the preliminary work is done to clarify the problem or opportunity and how a solution would look. All interested parties are consulted and the project scope – what is in and what is out – is clarified as well as initial costing and timelines. The project manager will clearly draws up the detailed project schedule and task and budget allocations. Altogether/ in groups will work on their assigned task and will come up with the finalised designs if necessary. Incase, project stakeholders are interviewed to ascertain the detailed requirements, possible solutions are discussed and one decided upon2. Developing/ BuildingThis is where the nuts and bolts work actually gets done. The solution is designed, built and finally implemented. Also the project stake holders are trained and educated about the overall processes and how the system works. Project management activities in this phase also include managing the project budget and schedule, reporting project progress, communicating with stakeholders and responding to project risks, issues and proposed changes.
  • 3. ValidatingThe process of validation generally occurs as one step or multiple steps of the process, usually in stages and is used to determine if the project is meeting the required specifications During this phase many different validations are carried out( for each instance a working model of the actual system is created in regular intervals) to make sure that all the necessary changes are incorporated to make it a error free customer friendly system4. DeploymentThis is where the actual software system is made available for normal useafter rigorous testing. Thus following are considered during the deployment phase Ensure that deployment, operational support, and maintenance resources are adequate.Ensure that adequate production and maintenance procedures are in place5. EvaluatingThe purpose of this final phase is to determine whether the project was a success and what learnings can be learnt and applied to future projects. Evaluation is typically conducted in order to answer three questions. Firstly, did the project deliver on time, within budget and to scope and quality requirements? Secondly, were project stakeholders and project team members satisfied with the project? Thirdly, did the project achieve the envisaged outcomes?
  • The purpose of Project Planning (High Level) is to begin to define the overall parameters of a project and to establish the appropriate project management and quality environment required to complete the project. The major deliverable for this process is the Project Initiation Plan. Hence all the stake holders can have a better understanding about how the things going to proceed and how they should be working according to the timeline.
  • The following are the project’s high-level milestones and the target dates for their completion. High-level milestones are the key ‘how are we doing’ thresholds of the project against which project progress can be measured. The diagram gives a better picture of the milestones with relation to time.At the Initiate Stage, information is at an overview level. Milestones identified at this early stage may be further broken down and revised during the project planning stage when the project schedule is created.High level milestones and timelines have three important goals:1. Provide measurement showing that tangible progress has been made on the project2. Ensure validation allowing the project to move on to the next step if the milestone is met or take corrective action if the milestone is not met3. Provide support for staff resource planning and budget preparation.
  • These are the main roles that are undertaking different responsibilities.
  • Project Manager The person responsible for developing, in conjunction with the Project Sponsor, a definition of the project. The Project Manager then ensures that the project is delivered on time, to budget and to the required quality standard (within agreed specifications). He/she ensures the project is effectively resourced and manages relationships with a wide range of groups (including all project contributors).The Project Manager is also responsible for managing the work of consultants, allocating and utilising resources in an efficient manner and maintaining a co-operative, motivated and successful team.
  • Project SponsorThe person who commissions others to deliver the project and champions the cause throughout the project. They will normally be a senior member of staff with a relevant area of responsibility that will be affected by the outcome of the project. They are involved from the start of the project, including defining the project in conjunction with the Project Manager. Once the project has been launched they should ensure that it is actively reviewed. The Project Sponsor is usually the one who has to negotiate a path through the tricky diplomatic areas of the project! 
  • Project Team MembersThe staff who actively work on the project, at some stage, during the lifetime of the project. They are responsible for following the best practices and complete according to the given time constrains. Some may have a specific role – for example, the Team might include a Project Administrator as well as AUP specific goals
  • System AdministratorManagement and support of the IT system environments
  • Systems DeveloperTo work with the Project Manager on defining and executing development requirements.
  • The Project Proposal The Project Proposal document is a pre-project document which is used as a kick-off point for any idea for a project. It should briefly outline the proposed approach, staffing, costs, timescales, business drivers and benefits.The Project CharterThe Project Charter is usually the first document that is created once an idea has been endorsed as a “Project”. It builds upon the Project Proposal, drilling down to the next level of detail.Business CaseThe Business Case defines WHY a project is being undertaken, and along with the Project Plan (the HOW) is the most important document a Project Manager will produce.Benefits Plan The Benefits Plan should document what the Project’s benefits are, how they will be realised and when, who is responsible for realising them, and how these benefits will be tracked and measured (both during the project and afterwards).Change Management Plan The Change Management Plan documents how Project changes will be raised, evaluated and approved to ensure that only appropriate changes are made to the base lined plan.Project Budget A Project Budget forecasts all of the Project's expenditure (and revenue). Once baselined, it is used as a living document to track actuals with the budget.Project Plan The Project Plan defines HOW a project will be delivered and along with the Business Case (the WHY) is the most important document a Project Manager will produce.___________________________________________________Business Process ImprovementThis specification is used to document changes to a business process, including: an outline of the current process; requirements to change the process; current problems and features to retain; proposed changes; and how these changes will be implemented.Business Requirements Specification The Business Requirements Specification is used to document all of the business’ requirements for the project.Business Requirements RegisterThe Business Requirements Register is the central repository for all business requirements (functional and non-functional).Options Analysis The Options Analysis can be used at any time in a project where it is not clear which direction the project should take, as there are a series of options to consider. The document provides details of the analysis undertaken to assess all of the various options available at that time, followed by a recommendation for a course of action.Implementation PlanThe Implementation Plan defines the Project’s strategy for moving from the old environment to the new, or the As-Is to the To-Be.Project Business Continuity PlanThis makes up one of the key components of the Implementation Plan. It provides alternative strategies should any of the elements of the implementation fail.
  • Test Plan The Test Plan details all the testing to be performed by the Testing team, including the overall test requirements and an integrated view of the project test activities.Training Strategy The Training Strategy provides an overview of the approach the project will take with training.________________________________________________________PIR QuestionnaireThe PIR Questionnaire is used to gather information and provoke thought regarding the delivery of the project.Post-Implementation ReviewThe Post-Implementation Review document is where the findings of the PIR workshop(s)and questionnaire are recorded.Project Closure ReportThe Project Closure Report is produced to formally shut down the Project.
  • We will communicate continuously, because we know that success depends on it. Here I have shown few of main ways that we will communicate among us.WhatWho/TargetPurposeWhen/FrequencyType/Method(s)Initiation MeetingAll stakeholdersGather information for Initiation PlanFIRST Before Project Start DateMeetingDistribute Project Initiation PlanAll stakeholdersDistribute Plan to alert stakeholders of project scope and to gain buy in.1 week Before Kick Off Meeting.Document distributed via hardcopy or electronically. Project Kick OffAll stakeholdersInitial project information presented to all.At or near Project Start DateMeetingUsing slide showsStatus ReportsAll stakeholders Update stakeholders on progress of the project.MonthlyDistribute electronically and post via web Team MeetingsEntire Project Team.To review detailed plans (tasks, assignments, and action items).Weekly for entire team. MeetingSponsor MeetingsSponsor(s) and Project ManagerUpdate Sponsors on status and discuss critical issues. Seek approval for changes to Project Plan.Monthly and also as needed when changes need to be made to Project Plan.MeetingPPO Audit/Review Project Manager, SLRD, SponsorsReview status reports, issues, and risks. To identify and communicate potential risks and issues that may affect the schedule, budget, or deliverables.MonthlyScheduled by the Project OfficeMeeting/ReportPost Project ReviewProject Manager, SLRD.Identify improvement plans, lessons learned, what worked and what could have gone better. Review accomplishments.End of Project or end of major phaseMeeting/Report Project Office will produce report.Presentations to Special Interest GroupsService providers and stakeholders.To update external groups to promote communication a create awareness of project interdependencies. At project milestones so as to communicate with other interested parties of changes that will be introduced outside of the Project Team.Presentation/DemonstrationPeriodic Demos and Target PresentationsStudents, day-to-day railway uses.To gain input from special groups and keep them abreast of the Project’s status.Presentation/Discussion
  • Risk is inevitable in everything we do. There may be commonplace risks that are almost inevitable, for example, the risk that a member of the team is sick for part of the project. There may be some unlikely but high impact risks, for example, the risk that the solution could cause the destruction of the organization. There are some risks in this project too. But we have smart solutionsRiskProbabilityImpactEffect on ProjectRisk Reduction ActionsE If it happens: Triggers & ActionsLoss to project of key staff.LowHighUnable to complete key tasksEmphasise importance of project within and outside the University.TriggersReports of absence, or diversion of staff to other workActionsIdentify alternative resources in case of unexpected absence. Investigate whether extra resources could either be involved or shadow any work dependent on a single member of staff. Ensure complete records of work are available at any point.Significant changes in user requirementsLow HighTime-quality-costEnsure that the user requirements are fully investigated and agreed before specification TriggersRequest for changes to agreed specificationActionsDiscuss impact of change on schedules or design, and agree if change to specification will proceed.Implement project change, if agreed.Changes in priorities of senior management.MediumHighRemoval of resource, lack of commitment, change in strategy or closure of project. Make sure that senior management are aware of the project, its relative importance, and its progress.TriggersAnnouncements in University publications, meetings etc.ActionsInform senior management of the knock on effects of their decisions.Retain any parts of the work of the project that could be useful in any future development.Ensure that the project is adequately documented to date.Poor capture of full User requirements. HighHighFailure to meet minimum requirements. Failure to achieve business benefits. Need to rework solution after rollout.Failed delivery. Focus on User Requirements capture at start of project. + Best people with appropriate knowledge and authority to decide and time to be involved. Accountable process owners. + Executive leadership and ongoing involvement.TriggersProject Sponsor/Feedback from User RepsActionsSystem accountability built into project and documentation standards. Monitor through workshops, feedback from pilots. Inadequate training – too little too late HighHighUsers unable to use system properly. Ensure training staff are involved from start of project.TriggersFeedback from training sessions/Training managerActionsReview training procedures, enhance.Poor business processesHighHighA system based on over-complicated, badly engineered business processes will itself be over-complicated and badly engineered. Revised business processes before constructing user spec. TriggersBusiness Process Analysis Reports/Key User.ActionsIf system development is getting bogged down in complex processes, review project. It may be necessary to go back to business processes and start again. Loss of power or internet connection at key roll-out, demo or training eventsLowLowUsers will not take the product seriously if it cannot be demonstrated to work.Check for scheduled outages.ActionsIf doing demos/training, have screen shots available locally in case of loss of connection 
  • Acceptance testing is the process that the parties to an agreement use to determine whether a product or service meets the requirements of the agreement. There are different types of acceptance tests depending on the product or service being provided.Acceptance tests are important because:They define whether the deliverables provided by the supplier meet the requirements agreed by the parties;The consequences of failing to pass an acceptance test are usually serious for the ICT supplier; andAcceptance usually triggers a substantial milestone payment, or payment of the total fee.Main GuidelinesOnly authorized users gain access to the System. An authorized user is a user who has an account on the system. Users include Station master, system administrators, etc. The user must type a valid username and password to gain access.Must allow user to select the appropriate details of the system, like destination, no of tickets, class of travelling. After selecting those user details this user must be directed to a pager where he can see the price of one ticket and Total amount, and ticket buying function.Must allow user to use his credit card and purchase tickets.Must validate the user credit card with PID.Must allow user to select the familiar language. Default language will be Sinhala and if user not familiar with Sinhala, he can choose English or Tamil.Other Product Guidelines UsabilitySpeed of UseThe System should respond within 5 seconds to every interaction.Fail safeSystem should contain a eject button to eject the card manually if the system is unable to eject automatically. (Due to a power failure or from an internal error)System should show whether the machine is working or out of order from a green and a red indicating light. LearnabilityAny staff member who intends to use the system should be able to use this after 1 day of training.Any passenger should be able to use the system only with the on system tour conducted on demand by the system.System should use instinctive approach for all the user interfaces. Cancel button should be coloured red. Back and forward buttons should be at lower left and right corners and coloured blue. OK/Commit buttons should be Green.Training MaterialUser manual should be available for the train department staff.DocumentationWhen the training mode is on, every action and button should give a note on what it is intended to do.Help icon will be displayed on every screen describing the screen and possible processes used this service (page). ReliabilityMaximum Failure RateSystem should be working with a maximum downtime of 10mins per week.Maximum down TimeIn case of power failure, the system should go into hibernate mode. And when the generator is on, this should come back to its previous status within 1 minute. Ease of RecoverySystem will have an external battery which can run for 30 minutes. Therefore the generator should start within that time.Errors and exceptionsSystem should provide a comprehensive error messages to users describing errors occurred during a process to take necessary actions according to the level of control of the user.If a critical error was found, it should immediately notify the main station. All errors and exceptions should be logged in a separate log file and should be transmitted at the end of the day. PerformanceResponse TimeSystem should respond within 5 seconds to every interaction. SecurityInternal SecurityShould not provide any attacker to get into the admin view mode by bypassing the login window.System should encrypt all the sensitive data when storing. External SecurityA CCTV camera should be setup in every ATIM for external security and it should be recorded 24/7 with a history of a week.Every connection made over the network should be encrypted with a 128 key encryption.  Infrastructure GuidelinesClientsEach ATIM and System Administrator PC will act as a client.ServersShould have separate server controlled by the railway department.NetworksA separate network (Private area network) should be used to communicate.
  • This shows only a set of user acceptance guide lines there is a complete set of them in the documents that we provided.

Railway Ticket Issuing System (Online) Railway Ticket Issuing System (Online) Presentation Transcript

  • solutions done right
  • Vision The software solution implements a Railway Ticket Issuing System (RTIS) for the Sri Lanka Railways Department (SLRD). The solution allows to overcome the extreme human intervention to the current ticket issuance process. The proposed system will be an automated system so that SLRD will be able to manage their ticketing transaction efficiently.Slide 2
  • Problem Domain • Purchasing railway tickets without traveling to the station • Delay of the prevailing manual ticket issuing procedure • Difficulty of monitoring the performance of railway counter staff • Invalid ticketsSlide 3
  • Automated Ticket Issuing System (ATIS) ATIS is a complete solution for issuing railway tickets. It provides resolutions for all the mentioned problems. The ATIS consists of a network of Automated Ticket Issuing Machine(ATIM)s and a web based solution.Slide 4
  • Automated Ticket Issuing System The ATIS is envisioned to Purchasing tickets The ATIS will have a major enable railway ticket issuance online via theto manage data data center Lanka Gate Via the SLRD website about the tickets. Major Country Portal and from the Via the LGCP SLRD website with Credit Card railway stations and the From ATIM s Hand held Barcodeare After or Mobil based payments. major data center Readers making payments, passengers connected through a high can determine the validity of Validating tickets will be provided an image of the the ticket. Once that is speed network a railway purchased ticket. It contains a Use of Bar Code Readers ticket is scanned, the SLRD. implemented by status of barcode and passengers are the ticket willtake update incopy supposed to be a printed thedisaster recovery center is A system. of that. Sharing data established in order to minimize system failures due The ATIM accepts Sri Lankan Through a High Speed to loss of data. currency notes and issues a bar Network code contained tickets.Slide 5
  • Main features • Credit card or mobile based payment • Enables purchasing railway tickets from any place • 24x7 available ticketing • Enables centralized control for monitoring and auditingSlide 6
  • Main features • High speed ticket issuance • High Reliability • User friendly GUI • Quick responseSlide 7
  • User Friendly GUI Starting window Select Destination Date of Departure Select Dep. Time Num of Passengers Select Preferred Train Select the Class Transaction Detail Payments Successful PaymentSlide 8
  • Project Stakeholders Internal Stakeholders • Railway Station Staff • Railway Conductors • Railway Department Administration • System Engineers • Railway PassengersSlide 9
  • Project Stakeholders External Stakeholders • ICTA • Sri Lanka Government • Mobile Service Providers • Banks • Internet Service ProvidersSlide 10
  • Agile Unified ProcessSlide 11
  • Agile Unified Process Change Requirements of StakeholdersSlide 12
  • System Architecture Disaster Recovery System SLRD Website Lanka Gate Main Data-store VPN Automatic Ticket Issuing MachineSlide 13
  • Slide 14
  • Agile Unified Process Major PhasesSlide 15
  • Major Phases and Milestones Phase 1 -Planning and Designing Cost and Estimate Acceptance 20/09/11 Finalization of Technical Architecture and Infrastructure Design 23/10/11 Completion of Online Ticket Issuing Web Service design in SLRD website via 18/11/11 LankaGate Country Portal Completion of Railway Ticket and ATIM designs 15/11/11 Phase 2 – Developing / Building Establishment of State-of-Art Data Centre in Western Province 1/11/11 Connecting SLDR Data Centre with Lankan Government Network 25/11/11 Connecting Major Railway Stations with State-of-Art Data Centre by a High Speed 5/01/12 Network Installation of ATIM and all necessary hardware in Major Railway Stations 28/01/12Slide 16
  • •Termination of contract after expected successful outcome Major Phases and Milestones Phase 3 – Validating Training all Railway Conductors regarding the operation of Handheld Barcode 5/03/12 Readers and staff regarding the overall new system Establishment of DRC (Disaster Recovery Centre ),manned 24/7,365 days 22/02/12 5/04/12 Completion of Successful Test runs Phase 4 – Deployment Launching the online ticket issuing services with proper public awareness 8/04/12 Phase 5 – Evaluating 15/6/12 Completion of Post Implementation Review Updating and Required correction 25/7/12 Termination of contract after expected successful outcome 30/7/12Slide 17
  • High level Timeline Major Phases No Name Start Finish Sep-Nov Dec-Feb Mar-May June - Aug 1 Planning and Designing 1/09/11 15/11/11 2 Developing / Building 18/10/11 29/01/12 3 Validating 5/01/12 5/04/12 4 Deployment 8/04/12 25/7/12 5 Evaluating 12/4/12 30/7/12Slide 18
  • High Level Timeline Major MilestonesSlide 19
  • Main Project Roles 1 Project Manager 2 Project Sponsor 3 Project Team Members 4 Project Administrator or Co-ordinator 5 Systems Developer System Administrator 6Slide 20
  • Project Manager Responsibilities Managing and leading the project team. Recruiting project staff and consultants. Managing co-ordination of the partners and working groups engaged in project work. Detailed project planning and control including: Templates Developing and maintaining a detailed project plan.Slide 21
  • Project Sponsor Responsibilities Championing the project and raising awareness at senior level. Approving strategies, implementation plan, project scope and milestones. Resolving strategic and policy issues. Driving and managing change through the organization. Templates project goals with other Prioritizing ongoing projects. Communicating with other key organizational representatives.Slide 22
  • Project Team Members Responsibilities Provide functional expertise in an administrative process Work with users to ensure the project meets business needs Documentation and analysis of current and future processes/systems Identification and mapping of information needs Templates Defining requirements for reporting and interfacing User trainingSlide 23
  • System Administrator Responsibilities Management and support of the various environments. Network operating systems management and support. Database management and support. Back-up and disaster recovery measures. Contributing to technical strategy, policy and procedure. Templates Development and operation of technical testing programmes. Production of technical documentation to agreed quality standards.Slide 24
  • Systems Developer Responsibilities Working with the Project Manager on definition of development requirements and priorities. Data Migration. Interfaces with other systems. Reporting configuration and deployment. Set up and maintenance of security rights and access permissions. Contributing to technical strategy, policy and procedure. Templates operation of technical testing Development and programmes. Production of technical documentation to agreed quality standards. Reporting on progress/issues to management and users.Slide 25
  • Documentation Planning and designing Developing/Building The Project Proposal Business Process Improvement The Project Charter Business Requirements Specification Business Case Business Requirements Register Benefits Plan Options Analysis Change Management Plan Implementation Plan Project Budget Project Business Continuity Plan Project PlanSlide 26
  • Documentation Validating / Deployment Evaluating PIR Questionnaire Test Plan Post-Implementation Review Training Strategy Project Closure ReportSlide 27
  • Communication We will be connected with you till the successful ending, because we know that success depends on it. Status Reports 1 Monthly Target: Students, day-to-day railway uses. All stakeholders Entire Project Team. Team Meetings Purpose: To gain stakeholders on progress Update input from plans (tasks, review detailed special of the project. and action items). groups and keep them abreast of the assignments, Project’s status. Frequency: Monthlyfor entire team. Weekly 2 Weekly Method: Distribute electronically and post Frequency: As required. Meething via web Method: Presentation/Discussion Periodic Demos and Target Presentations 3 As RequiredSlide 28
  • There Are Risks But we have smart solutions ✓ 1 Loss to project of key staff. Identifyon User Requirements Focus alternative resources Ensure training staff ✓ 2 Significant changes in user requirements Check that the user Make sure scheduledare Ensure for that senior outages. Revised business processes in case offrom are aware of the involvedatunexpected project. management startfully requirements are project. captureconstructing user spec. start of of before absence. Investigate whether investigated and agreed project, its relative importance, Best people withprocedures, Review training appropriate ✓ 3 Changes in priorities of of senior management. Changes in priorities senior management. extraits progress. and resources authority to knowledge and could either before specification enhance. ✓ 4 Poor capture of full User requirements. be involved or shadow any decide on requirements work dependent on a single ✓ 5 Inadequate training – too little too late member of staff. Ensure complete records of work are ✓ 6 Poor business processes available at any point. ✓ 7 Loss of power, internet at key eventsSlide 29
  • User Acceptance Guidelines Because we know that user rejection is the last thing you want. Learnability How we are going to test that Any staff member who intends to use the We will allow few stuff members(after 1 1 system should be able to use this after 1 2 hour training) and passengers(average day of training. passengers without any training) to use Any passenger should be able to use the the system for couple of hours and system only with the on system tour observe them. They should be able to conducted on demand by the system. learn and use it with low number of errors. System should use instinctive approach for all the user interfaces. Cancel button should be colored red. Back and forward buttons should be at lower left and right corners and colored blue. OK/Commit buttons should be Green.Slide 30
  • There are MORE!!! Just to ensure that customer is satisfied!!! System should be working with a maximum downtime of ✓ 10mins per week. ✓ System should respond within 5 seconds to every interaction. User manual should be available for the train department ✓ staff. System should show whether the machine is working or out ✓ of order from a green and a red indicating light. If a critical error was found, it should immediately notify the ✓ main station. ✓ Each ATIM and System Administrator PC will act as a client. Should have separate server controlled by the railway ✓ department.Slide 31
  • THANK YOU!