6/20/2020

Mid Term Assignment 1

 Department of Computer Science

Software Design Document

for

Cinema Management System

Table of Contents
1. Introduction.................................................................................................................................3
1.2 Scope.....................................................................................................................................3

1
 Department of Computer Science

1.3 Target Audience.........................................................................................................................3

1.3 Glossary:...............................................................................................................................3
1.4 References.............................................................................................................................4
1.5 System Overview..................................................................................................................4
2. System Architecture......................................................................................................................4
2.1 Elements:.....................................................................................................................................4
2.2 interfaces....................................................................................................................................4
2.3 Component Diagram of Cinema Management System..............................................................5
2.4 Architectural Style and Design Decisions...................................................................................6
2.5 Data flow Diagram......................................................................................................................6
2.6 Use Case Model...........................................................................................................................7
3.6.1 Registered user Module................................................................................................7
3.6.2 Un-registered/Viewer user Module..............................................................................8
3.6.3 Admin Module...............................................................................................................8
3.7 Description of Use Case Model.............................................................................................9
3. Detailed Description of Modules..................................................................................................9
3.1 Complete Package Diagram........................................................................................................9
3.2 Class Diagram............................................................................................................................10
3.3 Sequence diagram.....................................................................................................................11
4. Data Design.................................................................................................................................13
4.1 Database design: ERD...............................................................................................................13
4.2 Data Dictionary.........................................................................................................................14
5. The Design of User interface.......................................................................................................15
5.1 Overview of user interface.......................................................................................................15
5.2 Screen Images...........................................................................................................................15

2
 Department of Computer Science

1. Introduction
This software documentation contains a detailed design description of a cinema
management system. The purpose of this system is to provide the facility for the customers
to purchase tickets for cinema halls online, anytime, anywhere.
1.1 Purpose
This software design document is designed to describe in detail the software architecture
and design of the cinema management system. The document will provide an overview for
meeting customer needs competently. In addition, the document provides diverse system
design perspectives and simplify system comprehension by providing multiple system design
views.
1.2 Scope
We must develop a database system and provide relevant information to their users. The
scope of this design document is to reinforce the functional and non-functional
requirements described in the SRS through design implementation. The document will
describe the system’s components, database design, architecture, and interfaces. This is
achieved by using architectural design, class diagrams, sequence diagrams, relationship
diagrams and user interfaces.
1.3 Target Audience
This document is intended for CineSmart cinema management system’s developers and
technical staff.

1.3 Glossary:

ERD Entity Relationship Diagram

Visual studio Visual Studio dev tools & services make app development easy for any
platform & language.
MySQL MySQL is an open-source relational database management system.
PHP Hypertext Preprocessor; programming language originally designed for
web development.
SRS Software Requirement Specifications
UML Unified Modeling Languages

3
 Department of Computer Science

1.4 References
1. SDD Template: https://people.utm.my/norsham/files/2017/02/SDD-Template-v1.1-
SCSJ2203.pdf
2. Software requirement Specification of Cinema Management system
3. https://cse.final-year-projects.in/

1.5 System Overview

Cinema management system is designed for its customer’s ease. Its setup is in such a way that user
will access the process of ticket sales and bookings in hand. In this database, customer can book
tickets for movie and can get the information and services anywhere and anytime regarding movies
airing in the cinema. This design document will give an architectural view of this system, including
design specification and all the interfaces.

2. System Architecture
2.1 Elements:
A brief description of all the major components of cinema management system is given below:

 User/viewer Management
This is one of the main components of the system in which user interaction is made. User
can visit the website, view movie information, book tickets and perform payment
transactions. User can also create an account by signing up and can login with that account
anytime he wants to visit the website.
 Admin
Admin has all the rights of administration, authentication security and information. It can
grant access to the system. It has the right to alter database. It can create new user account
and can remove existing ones and so on.
 Movies
It includes all the movie information i.e. movie name, date time, hall name etc. movie
information on the website is displayed through this component.
 Tickets
This component shows the movie ticket information, informing availability of tickets and all
other relative data etc.
 Halls
It contains all the halls’ information and display movie information with respect to halls.

2.2 interfaces
 Viewer management component

Create account/ login: this interface will allow users to create account or login with existing account
options.

User profile: user can view, update, and edit his profile.

 Movie component
Movie information: In this interface user can see movies available for in cinema. User can
click on a movie to view its information.

4
 Department of Computer Science

Buy Ticket: movie information will display the option of going back and buy ticket along with
the relative information. Buy ticket will take the user to another interface on which user can
add ticket information such as ticket numbers, hall name, ticket value etc. and then by
entering transaction information user can get the tickets.
 Halls component
Halls: in this interface user can see all the halls view with names. By clicking on a hall user
can view the movie available for show In that specific hall.
 Contact us:
This interface allow user to ask questions and add comments for the CineSmart website.
User can enter any query related to cinema information and can also contact through the
given information.

2.3 Component Diagram of Cinema Management System

Movie
Data Access

Viewer
Data Access Database

Encryption and
database
Cinema
Tickets connector
Management Data Access
System

Halls
System Admin
Data Access

Payments
Data Access
Figure 1 Component Diagram

5
 Department of Computer Science

2.4 Architectural Style and Design Decisions

Under MVC Structural design and Client/Server Architecture, the Cinema management system will
be built. Viewer can search the internet and access via CineSmart website and view the cinema
management program. MVC design offers a distinction between presentation and interaction. The
project is having three main components including the Model framework which manages the system
information and its processes, the View framework, manages display of data in front of users and
the controller framework which controls user engagements and passes these interactions to system
manager. The User comes in contact with the application via user interface. he machine programs
run on the cloud server that is connected to the database server.

2.5 Data flow Diagram

Data flow diagram is a visual depiction of system-wide interactions. A DFD also gives the
understanding of the data that is used in the system.

Manage movie details

Admin Login to
System

Manage show details

Forgot
password Check
roles of Manage movie category details
access

Manage tickets details

Send Manage
email to modules
user
Manage booking details

Manage show details

Manage System Admins Manage user roles

Figure 2 data flow diagram

6
 Department of Computer Science

2.6 Use Case Model

A use case diagram describes an interface between the system and the actors as a series of
messages. Actor may include humans, systems, and processes. Our use case model has three actors:
A user having an account, can Login, book ticket, cancel ticket and perform transactions. Second is
unregistered user/viewer, he can just view some information and he must register to use the
services. The last one is Admin who maintains the database. He has access to all the management
system, can add or remove or update information regarding movies and users etc.

3.6.1 Registered user Module

Select Movie

Select Time and Hall

Class
ic

Select Ticket Type Gold

Login Premiuim
Select Seat

Payment through
debit/credit card
Registered User

Cancel Ticket
Update profile

Get Refund

Figure 3 Use Case 1

3.6.2 Un-registered/Viewer user Module

7
 Department of Computer Science

v
Create Account

View Movies Information

Un-registered User
Figure 4 Use Case 2

3.6.3 Admin Module

Add Movie Records

Delete Movie Records

Login
Accoun
t
Delete Movie Records

Admin
Manage User Accounts

Figure 5 Use Case 3

3.7 Description of Use Case Model

Use case 1: This use case displays the functionality of a Registered User in this management system.
A registered user can avail all the available options of the system. He can view movie information,
book tickets, and perform transactions. He can also update his own profile.

8
 Department of Computer Science

Use case 2: An unregistered user can visit the website and view movie information, but he will not
be able to book tickets. For this purpose, he can create new account.

Use case 3: admin module has all the rights and access to the system. He can modify users,
database, and all other information in the system.

3. Detailed Description of Modules

3.1 Complete Package Diagram
IT is a UML structure diagram that displays packages and their dependencies. It displays diverse
views of system. It is blend of classes and use cases. Packages involve classes and their relationships,
and elements such as characteristics, functions and messages are expressed in other UML diagram
not as direct components of packages.

Users Website Functionality

Registered User Index Book Ticket

History
Access Has
Admin Admin Cancel Tickets
Book Ticket

Unregistered user Register View Information

user Status

Access

Databases

MySql

php

Server
3.2 Class Diagram
It describes a of group of objects whose characteristics, processes, and relationships are identical.

Figure 6 complete package diagram

Movie Class
Tickets Class
Movie_id: int 9
ticket_id: int
Movie_name:
ticket_tyoe:
Category: 1 N timing: datetime
Start_time: datetime
 Available_tickts: int

Addmovie() M Addbooking()
Editmovie()
Editbooking()
Delmovie()
Cancelbooking()
Searchmovie()

Department of Computer Science

Halls Class Viewers Class

viewer_id: int
Hall_id: int viewer_name:
Hall_name: email:
Start_time: datetime dateofbirth: date
Sart_date:; datetime Ticket_id: datetime

AddShow() Addviewer()
EditShow() Editviewer()
DelShow() Delviewer()
SearchShow() Searchviewer()

Figure 7 class diagram

10
 Department of Computer Science

3.3 Sequence diagram

Buy Ticket interface Movies

user

User search for

available movies Check for available
movies

Select movie

Save the selection

Confirmation message

Figure 8 Sequence diagram 1

11
 Department of Computer Science

Registered Unregistered
Admin movies Buy Ticket Payment
user user/viewer

2. Add Movie Record

1. Return status

3. Update movie records

4. Return status
6. delete Movie Record
5. Return void
7. Show Movies
8. return Movies

10. login 9. Get registered

11. Book Tickets

12. Make Payments

14. Ticket confirmation

13. Cancel Tickets

15. Return payments

16. Return payments

17. View movies

18. logout

Figure 9 Sequence diagram 2

12
 Department of Computer Science

4. Data Design
4.1 Database design: ERD

Figure 10 Entity relationship Diagram

13
 Department of Computer Science

4.2 Data Dictionary

1- MOVIE

Field name Data type Field size Description

movieid Int 10 Id of Movie
moviename String 25 Movie Name
Start_time Datetime - Date and Time of Movie
Category String 40 Category of Movie

2- Tickets

Field name Data type Field size Description

Ticket_id Int 10 Id of Tickets
Seat_no Int 10 Seat number
Tickets_Available Int 10 Number of tickets available
Buying_time datetime - Date and time at which tickets is Bought
Price Int 20 Price of tickets

3- Halls

Field name Data type Field size Description

Hall_id int 10 Id of Halls
Hall_Name string 20 Hall Name
MaxCapacity int 25 Maximum Capacity Of Hall

14
 Department of Computer Science

4- Viewers

Field name Data type Field size Description

V_Id int 10 Id of Viewer
V_Name string 25 Viewer Name
Email string 25 Email Address of Viewer
DOB date - Date of Birth
Ticket_id int 10 Foreign key references to Tickets

5. The Design of User interface

5.1 Overview of user interface
This system has mainly used visual C# for main interfaces designing. Php is used to validate input
data from user. User is fully guided through error messages to input right information and how to
correct wrong ones. Main interface that user will first interact with, is the HOME page. On that home
page user can see a general interface showing images of movie displaying in the cinema. From that
page user can choose other available option whether to login, view further information or buy
tickets etc.

5.2 Screen Images

Home Page

15
 Department of Computer Science

Contact us

Halls

Movies

16
 Department of Computer Science

Movie info

Booking

17
Department of Computer Science

18