Project

ONLINE RESERVATION FOR CINE MALLS VERSION 1.
0
SOFTWARE REQUIREMENT SPECIFICATION 28-02-2011
ANCHOR
ANCHOR
ONLINE RESERVATION
FOR CINE MALLS
Software Requirements Specification
Version 1.0
Team Guide: Ramanagouda.S.Patil
Members:
Rekha.B.Gowda
Sadruta.C.Shekar
Shilpasri.G.Bhat
Simhadri Sindhu
College Name: M.S.Ramaiah Institute of

Technology
Department: Computer Science and
Engineering
State: Karnataka
ANCHOR/MSRIT Page 1
ONLINE RESERVATION FOR CINE MALLS VERSION 1.0
ANCHOR
Revision History
DATE VERSION DESCRIPTION AUTHOR
15/02/11 1.0 ROUGH DRAFT ANCHOR
28/02/11 1.0 FINAL VERSION ANCHOR
ANCHOR/MSRIT Page 2
ANCHOR
Table of Contents
Description
1.0 Introduction
1.1 Purpose 5
1.2 Scope 5
1.3 Definition, Acronyms, and
Abbreviations 5
1.4 References 6
1.5 Technologies to be used 6
1.6 Overview 7
2.0 Overall Description

2.1 Product Perspective 7
2.2 Software Interface 8
2.3 Hardware Interface 8
2.4 Product Function 9
2.5 User Characteristics 9
ANCHOR/MSRIT Page 3
ANCHOR
2.6 Constraints 10
2.7 Architecture Design 11
2.8 Use Case Model Description 12
2.9 Class Diagram 13

Sequence Diagram 14
2.10 Database Design 15
2.11.1 ER Diagram 15
2.11.2 Schema 16
2.12 Assumptions and Dependencies 17
3.0 Specific Requirements

3.1 Use Case Reports 17
3.2 Supplementary Requirements 18
ANCHOR/MSRIT Page 4
ANCHOR
1. INTRODUCTION
1.1 PURPOSE:
This system overcomes the disadvantages prevailing in the current system like
standing in queue to buy tickets, visiting theatre for advance booking. Our
system enables user to book their tickets at ease through internet, update the
user with the new releases and upcoming shows.
1.2 SCOPE:
Online Ticket Reservation system for cine malls is the new option for people to
buy movie tickets. The Online Ticket Reservation system makes it more easier
for people to book tickets online through the respective website of the cine mall.
Ticket can also be bought in this way with credit or debit cards. This project
study on Online Ticket Reservation system for Cine malls helps to understand
the various aspect of ticket booking and new facilities offered by Cine malls in
Online Ticket Reservation. 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.
1.3 DEFINITION, ACRONYMS AND

ABBREVIATIONS:
• J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to

the Java platform, which is used for developing and running distributed java
applications.
• DB2 (IBM Database 2): It is a database management system that provides a

flexible and efficient database platform to raise a strong "on demand"
business applications.
ANCHOR/MSRIT Page 5
ANCHOR
• XML (Extensible Markup Language): It is a markup language that was

designed to transport and store data.
• Ajax (Asynchronous Java Script and XML): It is a technique used in java

script to create dynamic web pages.
1.4 REFERENCES:
• TGMC sample projects

• Scribd.com
• Fundamentals of world wide web by Robert Sebesta
• The complete reference J2EE- Jim Keogh
• Fundamentals of database systems- Elmasri and Navathe
1.5 TECHNOLOGIES TO BE USED:
• J2EE: (Servlet, JSP, Java Beans) Application architecture.

• DB2: IBM Database.
• Ajax: Asynchronous Java Script and XML.
• XML: Extension Markup Language.
• RAD: Development tool.
• Localization: 1Languages – English
ANCHOR/MSRIT Page 6
ANCHOR
1.6 OVERVIEW:
1.6.1 Overall Description:
Sound and stage Entertainment manages 1 movie theaters consisting of 5 halls.

The theater has a booking counter where people can buy tickets for the current
and upcoming shows. The online system developed is to facilitate the booking
of tickets in advance, select preferred seats.
Through internet it is possible for the application to provide real-time

information about the availability of seats and enables users to book movie
tickets. A database is also maintained that stores all the information. The web-
based interface will be connected to the database to fetch and store the data.
1.6.2 Specific Requirements:
• To obtain agreement regarding what the system will need to do when

interacting with outside parties, such as user or other systems
• To run the project in the production mode, one web server and database
server is needed and one operating system.
• To assist managerial decision as well as technical analysis constraints

imposed by the platform.
2. OVERALL DESCRIPTION:
This section describes the functions of the project and their aims. This also
includes constraints and requirements of the project.
2.1 PRODUCT PERSPECTIVE:
A clean interface is built which is easy to understand and work on so that a

person having little knowledge in field of computers can also work easily and
book online ticket for movies.
ANCHOR/MSRIT Page 7
ANCHOR
The web pages are present to provide the user interface on customer client side.
Communication between customer and server is provided through HTTP
protocol.
The client software is to provide the user interface on system user client side
and for this TCP/IP protocols are used.
On the server side web server are EJB and database server for storing the
information.
2.2 SOFTWARE INTERFACE:
Front End Client: Web Browser, Operating system, GnuPGshell.
Web Server: IBM http server
Data Base Server: DB2 Express-C
Back End: Cgidev2
2.3 HARDWARE INTERFACE:
Client side:
Internet explorer 6.0
Processor: Pentium IV 2.0 and above
RAM: 256 MB
ANCHOR/MSRIT Page 8
ANCHOR
Server side:
Processor : Pentium IV 2.0 and above
RAM: 1GB
Disk space: 4GB
2.4 PRODUCT FUNCTION:
It tells the short note about the product.
Movie Details: Customer may view the movie timing at a date their name and
number of tickets.
Reservation: After checking the number of seats available the customers reserve
the tickets for the shows.
Billing: After reserving the required amount of tickets, the customer pays the
amount which is done at the counter of the cine malls.
2.5 USER CHARACTERISTICS:
The user should be aware of the normal internet usage and comfortable with the
browser interface. He should be aware of the booking system for ticket
reservation in cine malls. The user need not know about the internal structure of
the programming language and its working.
ANCHOR/MSRIT Page 9
ANCHOR
2.6 CONSTRAINTS:
• User can login to the system through the first page of the application
• User can change the password after logging into the system
• User should be able to create a new login for the accessing the reservation
facility.
• Query the films on show for two weeks (Only two weeks advance
reservation is available) should be there.
• See his current reservations on different movies along with the details.
• 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.
• A calendar should be there which helps the person to select dates. It
should also show the public and nation holidays.
• The system should automatically show the fare for the corresponding
shows and amount of money to be paid for selected seats.
ANCHOR/MSRIT Page 10
ANCHOR
2.7 ARCHITECTURE DESIGN:
Reservation information
User authentication Reservation process Production of tickets
Home page Movie database Calendar
ANCHOR
2.8 USE CASE DIAGRAM:

Registration
Check by movie
<Extends>
Check movie data Check by date

Visitor
<Extends>
<Extends> Check by time
Buy ticket
<include>
Login
Member <include> Update personal data
Insert movie data
<include>
Update movie data

Admin login
<include>
Administrator Delete movie data

<include>
ANCHOR
2.9 CLASS DIAGRAM:

CINEMA MALL
Name: string 1
1 MANAGER
ADMINISTRATOR Location: string
Login: string
Alogin() 1
Login: string 1
Password: string
1 Mlogin()
Password: string Reset_password()
Reset_password () 1
n
1
SCREENS
Screen no :integer SEATS

n
Total seats: integer 1 n Seat id: integer
1 Seats left: integer Seat status:string
Movieid : integer
Class name: string Classtypeid: integer
actor: string
Movie id: integer Typeprice: integer
Actress: string
n Timings[]: integer Getstatus ()
Name : string
getscreendetails() 1
Setstatus ()
Production : string
gettimingdetails()
Gettype()
Period: integer 1
Getprice ()
Duration: integer
getscreendetails() TICKETS
n 1
gettimingdetails() ID: integer
Price: integer
LOG INFO
USER Date: date 1 1
Logid: integer n
Uid : integer Time: time
Ticketed: integer
Email :string Screenid: integer
Ticketprice: integer
1
Password: string Movieid: integer
getlogdetails ()
n
Name:string Seatno: integer
showlogdetails()
Address: string Userid: integer
ANCHOR/MSRIT getticketdetails() Page 13
Dob: date
getuserdetails() showticketdetails()
ANCHOR
SEQUENCE DIAGRAMS
User Tickets Movie Screen Seats Log
Login,Get user
details()
Choose movie
Get movie
Insert details()
ticket
Get date()
Choose
Get
Choose screen screen
Get timing
Choose timing details()
Choose seat-type
Getprice()
Choose seats Gettype()
Getstatus(
Setstatus(
Insert log
Getorder details()
Get log
details()
ANCHOR
2.10 DATABASE DESIGN
2.11.1 ER DIAGRAM
name
password login address
password
DOB
ADMIN uid USER
mobile no
Email id
chan- Buys
ges
director
name date ticket_id
m_id production time

price
MOVIES rated TICKETS
actor period
actress duration
mainta
played reser -ined in
booked
in -ves
for
have
SCREENS SEATS LOG INFO
seats_left
screen_no
seat_id seat_status log_id
timings
total_seats
class_type
ANCHOR
2.11.2 SCHEMA:
CINEMALL
name location alogin mlogin
ADMINISTRATOR
login password
MANAGER
Mlogin password
SCREENS
Screen no Total seats Seats left Class name Movie id
TIMINGS
ID price date time Screen id Movie id Screen no User id
SEATS
Seat id Seat status Class type Type price
USER
User id Email id Ph no dob password address
LOG INFO
Log id T Id
MOVIES
Movie id name actress actor duration production period Director
HAVE_SEATS
Screen_id Seat_id
ANCHOR
2.11 ASSUMPTIONS AND DEPENDENCIES:
This subsection of the SRS should list each of the factors

that affect the requirements stated in the SRS. These
factors are not design constraints on the software but are,
rather, any changes to them that can affect the
requirements in the SRS. For example, an assumption may
be that a specific operating system will be available on the
hardware designated for the software product. If, in fact,
the operating system is not available, the SRS would then
have to change accordingly.
3. SPECIFIC REQUIREMENTS:
3.1 USE CASE REPORTS:
There are three users for this system. They are administrator,
manager and user. The case diagram below shows the overall
view. The user can check the current movies, show timings
but to reserve seats he has to create a login. He has to collect
the tickets at the counter, otherwise they can be sold to
ANCHOR
someone else. The administrator maintains the information

about the users, and all the other necessary details.
3.2 SUPPLEMENTARY REQUIREMENTS:
Whenever the online ticket reservation is being done by the

user, the system should not face any breakdown in the supply
of power otherwise data could be lost.
While in operation any error occurs then there must be a

technical person to solve it.
High speed network connection is required so that the data

can travel swiftly.

Project

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Project

Diunggah oleh

Hak Cipta:

Format Tersedia

ONLINE RESERVATION FOR CINE MALLS VERSION 1.

College Name: M.S.Ramaiah Institute of

2.0 Overall Description

2.9 Class Diagram 13

2.12 Assumptions and Dependencies 17

3.0 Specific Requirements

1.3 DEFINITION, ACRONYMS AND

• J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to

• DB2 (IBM Database 2): It is a database management system that provides a

• XML (Extensible Markup Language): It is a markup language that was

• Ajax (Asynchronous Java Script and XML): It is a technique used in java

• TGMC sample projects

1.5 TECHNOLOGIES TO BE USED:

• J2EE: (Servlet, JSP, Java Beans) Application architecture.

Sound and stage Entertainment manages 1 movie theaters consisting of 5 halls.

Through internet it is possible for the application to provide real-time

1.6.2 Specific Requirements:

• To obtain agreement regarding what the system will need to do when

• To assist managerial decision as well as technical analysis constraints

2.1 PRODUCT PERSPECTIVE:

A clean interface is built which is easy to understand and work on so that a

2.2 SOFTWARE INTERFACE:

Front End Client: Web Browser, Operating system, GnuPGshell.

Web Server: IBM http server

Data Base Server: DB2 Express-C

Back End: Cgidev2

2.3 HARDWARE INTERFACE:

Internet explorer 6.0

Processor: Pentium IV 2.0 and above

Processor : Pentium IV 2.0 and above

Disk space: 4GB

2.4 PRODUCT FUNCTION:

It tells the short note about the product.

2.5 USER CHARACTERISTICS:

2.7 ARCHITECTURE DESIGN:

User authentication Reservation process Production of tickets

Home page Movie database Calendar

2.8 USE CASE DIAGRAM:

Check movie data Check by date

<Extends> Check by time

Member <include> Update personal data

Insert movie data

Update movie data

Administrator Delete movie data

2.9 CLASS DIAGRAM:

Screen no :integer SEATS

User Tickets Movie Screen Seats Log

Choose seats Gettype()

2.10 DATABASE DESIGN

m_id production time

ID price date time Screen id Movie id Screen no User id

Seat id Seat status Class type Type price

User id Email id Ph no dob password address

Movie id name actress actor duration production period Director

2.11 ASSUMPTIONS AND DEPENDENCIES:

This subsection of the SRS should list each of the factors

3.1 USE CASE REPORTS:

someone else. The administrator maintains the information

3.2 SUPPLEMENTARY REQUIREMENTS:

Whenever the online ticket reservation is being done by the

While in operation any error occurs then there must be a

High speed network connection is required so that the data

Anda mungkin juga menyukai