The Great Mind Challenge - Project Scenario Template

Note: Already filled information should not be changed

1. Name of the Project Online Ticket Reservation system for Cine Malls.

Internet based Online ticket reservation system for Cinema Halls which can
be accessed throughout the Net and can be accessed by any one who has
2. Objective/ Vision a net connection. This application will automate the reservation of tickets
and enquiries about availability of the seats. This application includes
email confirmation for the tickets.

A. User
3. Users of the System B. Manager
C. Administrator

The Cinema hall has a web site and anyone can access it through internet.
The cinema hall is a multiplex which has 5 screens. Each screen has 3
different types of seats/classes. Only 50% of the seats are available for
online reservation.
i. User can login to the system through the first page of the
application
ii. User can change the password after logging into the system
iii. User should be able to create a new login for the accessing the
reservation facility.
iv. The login Id and password should be sent to the mentioned email
address if a new account is created.
v. Query the films on show for two weeks (Only two weeks advance
reservation is available) should be there.
Functional
vi. See his current reservations on different movies along with the
4. Requirements
details.
(Atleast Eight)
vii. User should be able to choose the seats which are available for a
certain class. User can select seats from different classes as well for same
show and screen also.
viii. User can select the mode of transfer of tickets whether through the
courier or collection at the counter (as per that fare will be charged).
ix. Debit/Credit Card payments for reservation of tickets
x. SMS / Mail should be sent to the concerned person about the
confirmation of the ticket to the specified mobile no. / email
address.
xi. A calendar should be there which helps the person to select dates.
It should also show the public and nation holidays.
xii. The system should automatically show the fare for the
corresponding shows and amount of money to be paid for selected seats.
i. Secure access of confidential data (user’s details). SSL can be
used.
Non-functional
5. requirements (Atleast ii. 24 X 7 availability
Four) iii. Better component design to get better performance at peak time
iv. Flexible service based architecture will be highly desirable for
future extension
6. Optional features a. Make a database of people whosoever login. Decide on the
various details of the people that would be stored in the database
(like name, age group, address, location, system-login, password
in cryptic form, etc).
b. Help-pages to assist the user of the system in the form of
Q&A.
 c. Create other sub-systems like automatic notification,
screens for various functions (like login,calendar,reservation etc)
d. Data encryption should be done as it deals with the credit
cards and related things.

A. Professional look and feel

B. Use of AJAX atleast with all registration forms
User interface
7. 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

A. Electronic Reservation Entry Ticket

B. No. of tickets booked / cancelled
8. Reports
C. Tickets Booked / Cancelled between Dates
D.

A. High level of security to the private information provided by the

customers
9. Other important issues B. Decide on a reservation policy and other related aspects like how
many screens that multiplex has and what is the fare structure of different
types of tickets, number of daily show and timings.
10. Team Size 4
Technologies to be
11. UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
used
• ROSE/RSA / WebSphere Modeler
• Eclipse/ RAD / Lotus Forms Designer / Portlet Factory

12. Tools to be Used

• WebSphere Portal/ WAS/ WAS CE / WPS
• 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
13.
include
C. Database backup and DDL Script
D. Complete Source code