ABDULRAHMAN AL-SUMAIT UNIVERSITY

CHUKWANI ZANZIBAR

DEPARTMENT OF MATHEMATICS AND COMPUTER SCIENCE

COURSE TITLE: SOFTWARE ENGINEERING

SPECIALIZATION: MC

COURSE CODE: CS231

LECTURER NAME: MADAM: RAYA IDRISSA

TYPE OF WORK: GROUP ASSIGNMENT 02

YEAR OF STUDY: THIRD SEMESTER 2023/2024

DATE OF SUBMISSION: 18/12/2023

NAME SPECIALIZATION & REG NUMBER

1. HAJI SALMIN SALUM 22/MC/011
2. ABDILAH MOHAMED SUWEDI 22/MC/004
1.The stakeholders:

The stakeholders in a movie ticketing booking web application can be categorized into primary
and secondary stakeholders.

Primary stakeholders:

• Customers: Individuals who use the web application to book movie tickets.
• Movie Theaters: Organizations that provide movie screening facilities and partner with
the web application to sell tickets.
• Web Application Provider: The company or organization that develops and maintains the
movie ticketing booking web application.
• Payment Gateway Providers: Companies that facilitate secure online payment
transactions between customers and the web application.

Secondary stakeholders:

• Movie Studios and Distributors: Entities involved in producing and distributing movies
who benefit from increased ticket sales facilitated by the web application.
• Movie Review Websites: Platforms that provide movie reviews and ratings, which may
be integrated into the web application to help customers make informed decisions.
• Advertising Agencies: Organizations that may collaborate with the web application
provider or theaters to promote movies and increase ticket sales.
• Regulatory Authorities: Government bodies responsible for enforcing regulations related
to online ticketing, consumer protection, and data privacy.

2. The system boundaries:

The system boundaries of a movie ticketing booking web application define what is included
within the scope of the system and what lies outside of it. In this case, the system boundaries
encompass the interactions between users (customers) and the web application itself.

The system boundaries include:

• User Interface: The front-end component of the web application through which customers
interact with the system. This includes search functionality, ticket selection, seat
reservation, payment processing, and confirmation.
• Backend Infrastructure: The server-side components that handle customer requests,
process transactions, communicate with external systems (such as payment gateways),
and store relevant data.
 • Integration Interfaces: APIs or other integration methods used to connect with external
systems such as movie theaters’ inventory management systems or third-party services
for reviews/ratings.

The system boundaries exclude:

• Physical movie theaters themselves, as they are not part of the web application.
• The customer’s internet connection and device, as these are external to the system.

3. The system components:

A movie ticketing booking web application typically consists of several interconnected

components that work together to provide the desired functionality. These components can
include:

• User Interface: The front-end component responsible for presenting the user interface to
customers, including search forms, movie listings, seat selection, and payment screens.
• Database: A backend component used to store and retrieve data related to movies,
theaters, showtimes, customer profiles, bookings, and payment transactions.
• Backend Server: The server-side component responsible for handling customer requests,
processing transactions, and coordinating communication between other components.
• Payment Gateway Integration: An interface that connects the web application with third-
party payment gateway providers to securely process online payments.
• Movie Theater Integration: Interfaces or APIs used to connect with movie theaters’
systems to retrieve showtime availability and update ticket inventory in real-time.
• Authentication and Security: Components responsible for user authentication, session
management, encryption of sensitive data (e.g., passwords), and protection against
common security threats like cross-site scripting (XSS) or SQL injection.

4. The system requirements:

System requirements define the functional and non-functional characteristics that a movie
ticketing booking web application should possess. Here are some examples of system
requirements:

Functional Requirements:

• User Registration: The ability for customers to create accounts and manage their profiles.
• Movie Search: A search feature allowing users to find movies based on criteria such as
title, genre, location, or date.
• Seat Selection: Customers should be able to view available seats for a particular
showtime and select their preferred seats.
 • Booking and Payment Processing: Customers should be able to add tickets to their cart,
proceed to checkout, and complete the payment securely.
• Confirmation and Ticket Generation: After successful payment, customers should receive
a confirmation email or digital ticket with relevant details.
• Order History: Customers should have access to their booking history and be able to view
or modify existing bookings.

Non-functional Requirements:

• Performance: The system should be able to handle a high volume of concurrent users,
ensuring fast response times and minimal downtime.
• Security: The application should implement secure authentication mechanisms, protect
sensitive customer data, and prevent unauthorized access.
• Usability: The user interface should be intuitive, easy to navigate, and provide clear
instructions for each step of the booking process.
• Scalability: The system should be designed to handle increasing user demand without
significant performance degradation.
• Compatibility: The web application should be compatible with various web browsers and
devices to accommodate a wide range of users

USE CASE DIAGRAM

CLASS DIAGRAM