The Great Mind Challenge - Project Scenario Template

Note: Already filled information should not be changed

i. Online Ticketing
Name of the Project

Plan a ticketing application completely in a local language, including a

1. Objective/ Vision payment gateway.
This service is to be delivered without any assistance from a helper

1. An average user like yourself.

2. Users of the System 2. Application managers.
Service providers such as airlines, railways

Consumer:
1. Simplicity.
2. Easy intake of users’ needs: Origin, Destination, Dates, Price-
preferences.
3. Payment possibilities in local language. (Simulate what the
credit/device card/element could look like.)
4. End-to-end functions for ticket booking.
5. Simple interface for Terms & Conditions.
6. Double verification with minimum time-out between finalization of trip,
re-verification of travel details and completion/confirmation of
ticketing.
7. Print-out in local languages. Second copy in English.

Application Managers:
Functional
1. Track usage of services in languages.
3. Requirements
2. Track validity of translations of services provided if there are reports of
(Atleast Eight)
problems.
3. Ensure simplicity and correct correspondence of services purchase.
4. Find approaches to simplify transactions.

Service providers:
1. Track number of tickets being booked in local languages and use it to
enhance user experience in those languages.
2. Ensure original information is perfectly localized to remove any
duplication or ambiguity of specifications.
3. Ensure completeness of user experiences in local languages.
Some of these are design aspects and you could provide templates for
these activities.
Devise approaches and principles for these to be done

i. Secure access of confidential data (user’s details). SSL can be

used.
Non-functional
ii. 24 X 7 availability
4. requirements (Atleast
Four) iii. Better component design to get better performance at peak time
iv. Flexible service based architecture will be highly desirable for
future extension
5. Optional features . Simulation of trip-cancellation

A. Professional look and feel

B. Use of AJAX atleast with all registration forms
User interface
6. C. Browser testing and support for IE, NN, Mozila, and Firefox.
priorities
D. Use of Graphical tool like JASPER to show strategic data to admin
E. Reports exportable in .XLS, .PDF or any other desirable format

7. Reports Any relevant useful reports

1. Payment process simplification.

8. Other important issues 2. Assurance for user that the ticket is authentic.
Assurance for user that payment is secure
9. Team Size 2 – 4 members
Technologies to be
10. UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
used
• ROSE/RSA / WebSphere Modeler
• Eclipse/ RAD / Lotus Forms Designer / Portlet Factory
• WebSphere Portal/ WAS/ WAS CE / WPS
11. Tools to be Used
• DB2 Express – ‘C’ or DB2 UDB
• Tivoli CDP/TSM / Tivoli Directory Server
• Linux will be the preferred OS.
A. Online or offline help to above said users, Application deployment
executive and developer
Final Deliverable must B. Application archive ( .war/.ear ) with source code
12.
include
C. Database backup and DDL Script
D. Complete Source code