MOVIE PLUS

Software Requirements Specification

INT220

Preetham Reddy
12221668

Prepared for
Continuous Assessment 3
Autumn 2024
Software Requirements Specification (SRS)
Project: Movie Plus

INTRODUCTION

This Software Requirements Specification (SRS) document outlines the

requirements for the "Movie Plus" project, providing guidance for software
developers in designing and implementing a PHP-based web platform for movie
ticket bookings. The document details the purpose, scope, and requirements for
building and testing the platform's functionalities.

1.1 Purpose

The purpose of this SRS is to define the functional and non-functional

requirements for Movie Plus, covering user registration, login, browsing of
movies, and showtime booking. This document is a reference for developers and
stakeholders to understand the project’s goals, features, and constraints.
1.2 Scope

1. Software Product: Movie Plus is a web-based platform for users to browse

movie information and book showtimes. It uses PHP as the backend, SQL for data
storage, and the TMDb API for movie data.

2. Core Functionalities:

- Movie Listings: Display movies using data retrieved from the TMDb API.

- User Authentication: Secure login and registration system using PHP for
backend processing.

- Static Showtimes: Provide non-real-time, static theater and showtime options

for users to book tickets.

3. Application of Software:

- Benefits: Allows users to explore movies and book tickets in a straightforward

web interface.

- Goals: To create a user-friendly platform where movie browsing and ticket

booking are intuitive and responsive.

1.3 Definitions, Acronyms, and Abbreviations

- PHP: Hypertext Preprocessor, a server-side scripting language used for backend

development.

- TMDb API: The Movie Database API, used to retrieve movie data such as titles,
genres, and ratings.

- SQL: Structured Query Language, used for database operations to store user and
booking data.

- CRUD: Basic operations in SQL: Create, Read, Update, Delete.

1.4 References
1. PHP Documentation

2. SQL Documentation

3. TMDb API Documentation

1.5 Overview

This document covers the Movie Plus architecture, requirements, and

specifications, including both functional and non-functional aspects, UI details,
and external interfaces.

2. GENERAL DESCRIPTION

2.1 Product Perspective

Movie Plus serves as a stand-alone, PHP-based web application. SQL manages

data storage for users and booking records, while TMDb API integration provides
real-time movie information. Theater locations and showtimes are static data,
displayed for users to make selections.

2.2 Product Functions

- User Authentication: Enables user registration and login.

- Movie Listings: Displays movie information retrieved from the TMDb API.

- Showtimes and Booking: Provides static options for theaters and showtimes.

- Confirmation Page: Displays a booking confirmation with movie and showtime

details.

2.3 User Characteristics

Users should be comfortable with basic browsing and have familiarity with
using web forms.

2.4 General Constraints

- Data Limitations: Only static showtime and theater data are available, as real-
time information is not feasible.

- Internet Dependency: The application requires an internet connection to fetch

movie data from the TMDb API.

- Server Load: Not optimized for high traffic, as this project is not intended for
production deployment.

2.5 Assumptions and Dependencies

- Database Dependency: SQL database for managing user and booking

information.

- API Dependency: TMDb API for movie details.

- Browser Compatibility: Developed to work across modern web browsers

(Chrome, Firefox, etc.).

3. SPECIFIC REQUIREMENTS

3.1 External Interface Requirements

3.1.1 User Interfaces

- Home Page: Allows users to log in, register, or browse movies.

- Dashboard: Displays a list of movies using data from the TMDb API.
- Movie Details Page: Shows details of selected movies, with options to choose
showtimes.

- Booking Confirmation: Displays a confirmation page with selected movie and

showtime details.

3.1.2 Hardware Interfaces

- Server Hardware: Requires a server capable of running PHP and SQL.

3.1.3 Software Interfaces

- PHP: Backend logic for processing user registration, login, and booking
functions.

- SQL Database: Stores user data, registration details, and booking information.

- TMDb API: Fetches movie information.

3.1.4 Communications Interfaces

- HTTPS Protocol: Ensures secure and encrypted communication between users

and the server.

3.2 Functional Requirements

3.2.1 User Authentication

1. Introduction: Manages user registration and login.

2. Inputs: Username, password, and email (for registration).

3. Processing: Validates credentials against the SQL database.

4. Outputs: Grants or denies access to the user.

5. Error Handling: Displays errors for incorrect credentials or registration issues.

3.2.2 Movie Listing and Details

1. Introduction: Allows users to browse movies and view detailed information.

2. Inputs: User selects a movie to view details.

3. Processing: Calls the TMDb API to retrieve movie details.

4. Outputs: Displays movie information and static showtimes.

5. Error Handling: Shows error messages if the API fails to retrieve data.

3.2.3 Showtimes and Booking

1. Introduction: Users select showtimes and theaters (static data) to book tickets.

2. Inputs: Theater and showtime selection.

3. Processing: Saves booking information to the SQL database.

4. Outputs: Shows a booking confirmation page.

5. Error Handling: Displays errors if there is an issue with saving booking details.

3.5 Non-Functional Requirements

3.5.1 Performance

- Load Time: Pages should load within 3 seconds on a stable connection.

3.5.2 Reliability

- Data Consistency: SQL database backups to ensure data reliability.

3.5.3 Availability

- Uptime: High availability is desired, but the application is not intended for
production.

3.5.4 Security

- Encryption: HTTPS and secure password handling practices to protect user data.

3.5.5 Maintainability

- Modularity: Code should be modular for easy future modifications.

3.5.6 Portability

- Compatibility: Cross-browser compatibility to support modern web browsers.

3.7 Design Constraints

- TMDb API Limitations: Limited to available data from TMDb.

- SQL Database: SQL is used for managing user information and booking data.

3.9 Other Requirements

- Accessibility: Should follow basic web accessibility standards.

- Compliance: Complies with standard security and data protection guidelines.

4. ANALYSIS MODELS

4.1 Data Flow Diagrams (DFD)

Level 1 DFD:

- User Authentication Process: Users register or log in, with credentials verified
against the SQL database.

- Movie Data Fetching: PHP backend requests movie data from the TMDb API for
display on the platform.

- Booking Process: Users select a movie, theater, and showtime, and booking data
is saved in the SQL database.

Level 2 DFD:

1. User Registration: User data is saved in the SQL database upon successful
registration.

2. Movie Selection: Users select movies, and details are retrieved from the TMDb
API.

3. Booking Confirmation: Booking details are saved in SQL, and users receive
confirmation.
APPENDICES

A.1 Appendix 1

Setup instructions for PHP environment, SQL database installation, and

TMDb API integration.

A.2 Appendix 2

Sample structure for static theater and showtime data.