Introduction

Overview of the
design
The design is to show the direction how the web page is built and to obtain clear end enough in
each information needed to drive the actual implementation of web page.
It is based on understanding of the model the web page built on the system design also focus on
decomposing the system into manager parts.

Purpose
This software design description (SDD) will provide detail description of the requirements for
online movie ticketing system for cinema. This SDD helps end users, project managers and
software developers to have clear understanding of the online movie ticketing system and its
functionality that allows the software to be developed. This SDD will be used by the software
developer as guideline to develop the system. End users and project managers will be able to see
if the software developer can develop the system according to their needs or requirements.
If not according to their expectation, end users and project managers can specify how to change
the relevant requirements to conform to their expectation and software developer will change this
SDD to conform to the need of end users and project managers.
This document is intended for the users, developers, admin, evaluators and is will also serving as
reference for the future researchers.

Scope
The software is web based designed to advertise the company and meet the users needs. The
project comes with the new movie trailers, upcoming shows ,on show movie in the cinemas, live
streaming and box offices. Users can purchase available movie tickets and lookup for price and
starting time.
The website also provides the customers feedbacks about the movie and updates the most
watchable movie. Users can also invite their relative and friends through sharing in other
website. The website shall give the user options to print the ticket.

Design goal
The objectives of designing are to model a system with high quality. Implementing of high
quality system depends on the nature of the design created by the designer .If one wants to make
changes to the system after it has been put in to operation depends on the quality of the system
design. So if the system is designed perfectly, it will be easy to make changes to it.
The goal of the system design is to manage complexity by dividing the system in to manageable
pieces.
Some of the goals are listed below.
Security: The system should be secured from unauthorized user.
Modifiability: The system should be modifiability to modify different services
depending on the need of the institute.
Flexibility: The system able to change to suit new condition or situation.
Efficiency: The system must do what it is supposed to do efficiently without the problem.

Design constrains

The online movie ticketing system for a cinema shall be web based system run on to

different browsers such as internet explorer, Mozilla Firefox, goggle chrome and safari
The system shall be developed using javascript,PHP programming language and android
The system shall be run using mysql database server.

Hardware Environment

RAM
hard disk(HDD)

Software Environment

The online cinema ticketing

The online ticketing system shall connect to the internet provider
The online ticketing system shall connect with mysql database
The online ticketing system shall display the propriety and accurate website upon
the user needs

Availabity or volatility of resources

Standards of compliance

Architectural strategy
System design
The design of the system is the most critical factor the affecting the quality of the
software; it has major impact on the later phases, particularly testing and
maintenance.
The output of this phase is design the document.
This document is blueprint or plan for the solution.
Aims to identify the modules that should be in the system. The specification of the
module and how they interact with each other to produce the desired results.
Finally at the end of the system design all the major data structures, file formats and
the major modules in the system and their specifications are decided.

System
Customer

Admin

Cinema
ticketing
system

Data base

Employee

Subsystem decomposition
Customer
Fail
Fail

Successful

Registration successful
form
Fail

Admin

Employee

Successful
Stored

display info

Databas
e

Employee

Admin

Movie
Database

Customer

Subsystem description
Registration subsystem operation:
Customer can register to the system.

Login setting subsystem

Admin, customer and employee can login into the system.

Customer cinema ticketing subsystem operation

Displays list of film and schedule
Customer can reserve film and schedule

Admin assign film and schedule subsystem operation

Admin can assign film, time and date in different program.

Customer explore home page subsystem operation

Customer can visit explore the web

Component diagram
In this Diagram components of the system will be wired showing that there is relation among
components, management of the system, database and operation preformed on database such
issue. This in some extent show which component or object will be accessed by whom and what
type of security infrastructures it is using.

Deployment diagram
Deployment diagram shows physical communication links between hardware items. And
relationship between physical machine and processes. It also shows how the software and the hard
ware component work together.

Data storage (database design)

Physical design
A database may be thought of as a set of related files, related files mean that record of
one file may be associated with the records in the file.
The convention of based systems emphasized that the application and files where built
around it. The database environment emphasizes the data independently of the
application that use the data.
The application is allowed to evolve around the database design such that it can adapt to
changing needs. Data becomes the central resource in the database environment.
Information system is built around this central resource to give flexible access to data.

Table for customers

Attribute

Data type

Firstname
Lastnamed
Username
Accountno
Id
Password

Varchar(12)
Varchar(13)
Varchar(14)
Integer(16)
Integer(23)
Varchar(7)

Table for admin

Attribute

Data type

Username
Password

Varchar(23)
Integer(8)

Table for employee

Attribute

Data type

Username
Password

Varchar(23)
Integer(8)

Table for movies

Attribute

data type

Id
Title
Movie_type
Length_time
Photo

Varchar(14)
Varchar(12)
Varchar(12)
time
Varchar(12)

Table for the schedule

Attribute
Movie
Movie_type
Movie_length
Show_date
Show_time
Price

Datatype
Varchar(12)
Varchar(12)
Integer(12)
Varchar(12)
Time
Integer(10)

Create table customer(id integer,

Firstname varchar(12),
Lastname varchar(12),
Username varchar(12),
Accountno integer,
Password varchar(12)
);
Create table admin(username varchar(23),
Password varchar(8));
Create table employee(username varchar(23),
Password varchar(8));

Create table movies (Id Varchar(14),

Title Varchar(12) ,

Movie_type Varchar(12),
Length_time time,
Photo Varchar(12)
);

Create table schedule(Movie Varchar(12),

Movie_type Varchar(12),
Movie_length Integer(12),
Show_date Varchar(12),
Show_time Time,
Price Integer(10)
);

Integrity constraints and

security aspects
Integrity: only the system administrator has rights to access the database not every user can
access all the information. Each user will be having the rights the modules.
Starting the cinema online ticketing system will show the customer to register first register and
login in to the system. Then next reserve or select their choice of film and schedule and day from
the existing list of information, automatically the system generate ticket for the appropriate
customer.

Team
structure
responsibilities
Project title:online cinema ticketing system
no
name
id
Responsibities
1
Gathering data
2
Requirement analyis
3
4
5
6

and