Software Test Plan for Automated Ticket Issuing System for Dhaka Subway Systems
Railway Ticket Issuing System (Online)
-
Upload
rashmika-nawaratne -
Category
Technology
-
view
6.490 -
download
0
description
Transcript of Railway Ticket Issuing System (Online)
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
• 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 tickets
Problem Domain
Slide 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
The ATIS will have a major data center to manage data about the tickets. Major railway stations and the major data center are connected through a high speed network that is implemented by the SLRD.
A disaster recovery center is established in order to minimize system failures due to loss of data.
Hand held Barcode Readers can determine the validity of the ticket. Once a railway ticket is scanned, status of the ticket will be update in the system.
The ATIS is envisioned to enable railway ticket issuance online via the Lanka Gate Country Portal and from the SLRD website with Credit Card or Mobil based payments. After making payments, passengers will be provided an image of the purchased ticket. It contains a barcode and passengers are supposed to take a printed copy of that.
The ATIM accepts Sri Lankan currency notes and issues a bar code contained tickets.
Automated Ticket Issuing System
Purchasing ticketsVia the SLRD websiteVia the LGCPFrom ATIM s
Use of Bar Code Readers
Validating tickets
Through a High Speed Network
Sharing data
Slide 5
• Credit card or mobile based payment• Enables purchasing railway tickets from
any place• 24x7 available ticketing• Enables centralized control for monitoring
and auditing
Main features
Slide 6
• High speed ticket issuance• High Reliability• User friendly GUI• Quick response
Main features
Slide 7
User Friendly GUI
Starting window
Select Destination
Date of Departure
Select Dep. TimeNum of Passengers
Select Preferred Train
Select the Class
Transaction Detail
Payments
Successful PaymentSlide 8
• Railway Station Staff• Railway Conductors• Railway Department Administration• System Engineers• Railway Passengers
Project StakeholdersInternal Stakeholders
Slide 9
• ICTA• Sri Lanka Government• Mobile Service Providers• Banks• Internet Service Providers
Project StakeholdersExternal Stakeholders
Slide 10
Agile Unified Process
Slide 11
Change Requirements of StakeholdersAgile Unified Process
Slide 12
System Architecture
Lanka Government Network
Internet
VPN
Disaster Recovery System
Main Data-store
Automatic Ticket Issuing Machine
Lanka Gate
SLRD Website
Slide 13
Slide 14
Agile Unified ProcessMajor Phases
Slide 15
Phase 2 – Developing / Building
Completion of Railway Ticket and ATIM designs
Cost and Estimate Acceptance
Completion of Online Ticket Issuing Web Service design in SLRD website via LankaGate Country Portal
Major Phases and Milestones
Finalization of Technical Architecture and Infrastructure Design
Phase 1 -Planning and Designing
Connecting SLDR Data Centre with Lankan Government Network
Connecting Major Railway Stations with State-of-Art Data Centre by a High Speed Network
Installation of ATIM and all necessary hardware in Major Railway Stations
Establishment of State-of-Art Data Centre in Western Province
20/09/11
15/11/11
28/01/12
5/01/12
25/11/11
1/11/11
18/11/11
23/10/11
Slide 16
Phase 4 – Deployment
Completion of Successful Test runs
Establishment of DRC (Disaster Recovery Centre ),manned 24/7,365 days
Launching the online ticket issuing services with proper public awareness
Major Phases and Milestones
Training all Railway Conductors regarding the operation of Handheld Barcode Readers and staff regarding the overall new system
5/03/12
Updating and Required correction
Termination of contract after expected successful outcome
•Termination of contract after expected successful outcome
25/7/12
8/04/12
5/04/12
22/02/12
15/6/12
Phase 3 – Validating
Phase 5 – Evaluating
Completion of Post Implementation Review
30/7/12
Slide 17
Major PhasesHigh level Timeline
Planning and Designing
Developing / Building
Validating
Evaluating
Deployment
5
4
3
2
1 15/11/11
No Name Start Finish
Sep-Nov Dec-Feb Mar-May June - Aug
18/10/11
1/09/11
29/01/12
5/01/12 5/04/12
8/04/12 25/7/12
12/4/12 30/7/12
Slide 18
High Level Timeline Major Milestones
Slide 19
Main Project Roles
Project Manager
Systems Developer
Project Team Members
Project Sponsor
Project Administrator or Co-ordinator
6
5
4
3
2
1
System Administrator
Slide 20
Project Manager
Responsibilities
Templates
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:
Developing and maintaining a detailed project plan.
Slide 21
Project Sponsor
Responsibilities
Templates
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.
Prioritizing project goals with other ongoing projects.
Communicating with other key organizational representatives.
Slide 22
Project Team Members
Responsibilities
Templates
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
Defining requirements for reporting and interfacing
User training
Slide 23
System Administrator
Responsibilities
Templates
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.
Development and operation of technical testing programmes.
Production of technical documentation to agreed quality standards.
Slide 24
Systems Developer
Responsibilities
Templates
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.
Development and operation of technical testing programmes.
Production of technical documentation to agreed quality standards.
Reporting on progress/issues to management and users.
Slide 25
Developing/Building
Planning and designing
The Project Proposal
The Project Charter
Business Case
Benefits Plan
Change Management Plan
Project Budget
Project Plan
Business Process ImprovementBusiness Requirements Specification
Business Requirements Register
Options Analysis
Implementation Plan
Project Business Continuity Plan
Documentation
Slide 26
Evaluating
Validating / Deployment
Test Plan
Training Strategy
PIR Questionnaire
Post-Implementation Review
Project Closure Report
Documentation
Slide 27
Target: Students, day-to-day railway uses.Purpose: To gain input from special groups and keep them abreast of the Project’s status.Frequency: As required.Method: Presentation/Discussion
Target: Entire Project Team.Purpose: To review detailed plans (tasks, assignments, and action items).Frequency: Weekly for entire team.Method: Meething
Target: All stakeholdersPurpose: Update stakeholders on progress of the project.Frequency: MonthlyMethod: Distribute electronically and post via web
We will be connected with you till the successful ending, because we know that success depends on it.
Communication
Monthly
Status Reports
Weekly
Team Meetings
3 As Required
Periodic Demos and Target Presentations
2
1
Slide 28
But we have smart solutionsThere Are Risks
Loss to project of key staff.
Loss of power, internet at key events
Changes in priorities of senior management.
Inadequate training – too little too late
Significant changes in user requirements
Poor capture of full User requirements.
Poor business processes
7
6
5
4
3
2
1
Changes in priorities of senior management.
✓
✓
✓
✓
✓
✓
✓
Identify 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.
Ensure that the user requirements are fully investigated and agreed before specification
Make sure that senior management are aware of the project, its relative importance, and its progress.
Focus on User Requirements capture at start of project. Best people with appropriate knowledge and authority to decide on requirements
Ensure training staff are involved from start of project.Review training procedures, enhance.
Revised business processes before constructing user spec. Check for scheduled outages.
Slide 29
Because we know that user rejection is the last thing you want.
User Acceptance Guidelines
We will allow few stuff members(after 1 hour training) and passengers(average passengers without any training) to use the system for couple of hours and observe them. They should be able to learn and use it with low number of errors.
How we are going to test that
Any 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 colored red. Back and forward buttons should be at lower left and right corners and colored blue. OK/Commit buttons should be Green.
Learnability
1 2
Slide 30
Just to ensure that customer is satisfied!!!There are MORE!!!
System should be working with a maximum downtime of 10mins per week.
Should have separate server controlled by the railway department.
If a critical error was found, it should immediately notify the main station.
System should respond within 5 seconds to every interaction.
System should show whether the machine is working or out of order from a green and a red indicating light.
Each ATIM and System Administrator PC will act as a client.
✓
✓
✓
✓
✓
✓
✓
User manual should be available for the train department staff.
Slide 31
THANK YOU!