Experiment 1

AIM: Write problem statement of the case study: Online movie booking system.

A software is to be developed for online movie ticket booking. The system should allow staff/admin to
insert, update and delete data such as film description, time table etc. The user can register or login.
User account contains information such as name, phone number, email, address, languages etc. A user
needs to login to access the facilities of the system which include:

1. Search: The user can search for a movie or a cinema. The user should be able to view the cinemas
where the searched movie is available preferably near the user’s location. Details of the different
shows of the chosen cinema (like date, time, language etc.) should be shown. The system should
also provide information about currently running movies at the cinema they search.

2. Booking: After searching for a movie, the user can book seats for a particular show. Prices of
different seats are different and also depend upon the cinema. A confirmation mail should be send
to the user to confirm their booking and payment. Payment can be made through debit card,
credit card, net banking and e-wallet. A SMS should be sent to the user’s registered mobile number
containing information about seat numbers and other show details.

3. Cancellation: User can cancel their booking and get money refunded within a limited time
period.

4. View movie details: User can view information about the movie like synopsis, rating, release
date, cast; etc. Option for booking ticket for the particular movie should be shown which should
show a list of cinemas where the movie is currently running.
 Experiment 2
AIM: Draw data flow diagram level 0, 1 and 2 for case study: Online movie booking system.

a. Level 0

Transaction Accounting
details system
User account
maintenance
Administrator Online movie
ticket booking View movie information,
system view user information,
availability

Users
Ticket and booking info
 b. Level 1

Search movie name /Cinema

User
Reservation
request
Booking ID
Payment details 4. Online
Enter username booking
and password 5. Cancellation

Accounting
Validate system
Update
Booking details
Update

1. Login
Retrieve info.

Enter username User Account Info

and password

User Info
Admin Entry 6. User account
maintenance Retrieve info. 2. Search
movie
New movies
and movie
schedule
Movie schedule

3. Movie
schedule Retrieve info.
management

Movies details
c. Level 2

1. Login process

Enter username and Enter username and

User password password Administrator

Login
Retrieve information

User Account info

2. Search movie process

Cinema Name Movie schedule

Display Retrieve information

User
Display Retrieve information
Movie Name movie
information
Movie details
 3. Movie Schedule management process

Cinema Name Movie schedule

Display Retrieve information

Administrator Retrieve information

Movie Name Display
movie
information
Movie details

Enter/update/delete
movie Update
Process
movie

Enter/update/delete
schedule Update
Process
schedule

4. Online booking process

Ticket request Movie schedule

User Check Retrieve information
availability

Payment Validate
Payment
mode process

Accounting
System
Payment details
Decrease number of
E-ticket seats
Issue ticket
Booking ID and show
details
Booking details
 5. Cancellation process

Booking ID Booking details

User Validate Retrieve information

Payment details
Movie schedule Refund

Increase number of seats

Update Update details

6. User account management process

Access user account

information Display user
Administrator Retrieve information
account
information
User Account
info
Enter/update/delete user Validate
account information /update user Update
account
information
 Experiment 3
AIM: Draw the Entity-Relationship diagram for case study: Online movie booking system.
 Experiment 4

AIM: Draw the Use Case Diagram for the case study – Online Movie Ticket Booking System.
 Experiment 5

AIM: Prepare SRS document case study – Online Movie Ticket Booking System.

1. Introduction

This document aims at defining the overall software requirements for Online Movie Ticket Booking
System. Efforts have been made to define the requirements exhaustively and accurately. The final
product will be having only features/functionalities mentioned in this document and assumptions for
any additional functionality/feature should not be made by any of parties involved in
developing/testing/implementing/using the product.

1.1 Purpose

The main purpose of online ticket booking system is to provide another way for the customer to buy
cinema ticket. It is an automatic system. This system is aimed to provide the customer the complete
information of the movie, according to which the customer can book the tickets and the refund facility
provides more flexibility to the system.

1.2 Scope

The application should be able to run on any system regardless of the operating system or hardware;
within reason. It can be accessed using a simple internet connection on a home users desktop
computer or laptop. The application is designed for all types of users regardless of their ageor
experience to perform various transactions. It must function effectively and maintain an efficient level
of service.

1.3 Definitions, Acronyms and Abbreviations

 User: A registered individual who visits the website and owns an account in bank
 Username: Username must be unique and minimum 8 characters and maximum of 15 characters
 Password: Unique word given to each user as a secret code
 OMTBS: Online Movie Ticket Booking System

1.4 References

 IEEE Recommended Practice for Software Requirement Specifications-IEEE Std 830-1998

 Software Engineering by K.K. Aggarwal and Yogesh Singh

1.5 Overview
The rest of SRS document describes the various system requirements, interfaces, features and
functionalities in detail. The information presented in SRS is organized into five sections. The first
section states the purpose of the Software Requirement Specification document and defines the scope
of product. This section also includes definition and acronyms. The second section provides top-level
description and the main features of the system. A description of the different external entities that
interact with the system, including the main user, is also included in this section. The third section
contains all the software requirements to a level of detail sufficient to enable designers to design the
system and testers to test that system.