Professional Documents
Culture Documents
CASE STUDY ON
ONLINE MOVIE RESERVATION SYSTEM
BY
Ch.Srinivas
U.SriDivya
Sk.Mastan Shareef
(Mrs.Aruna)
Internal Guide
(Mrs.D.BEULAH)
Head of the dept.
Department of Comp.Sc.
External Examiner
ACKNOWLEDGEMENT
We avail this opportunity to express our deep sense of gratitude and hearty
thanks to Mrs.Aruna who is the internal guide of this problem for his constant
guidance ,keen interest open-minded discussions on his encouragement given during
this period during this period and preparation of case study.
It gives us immense pleasure he express pleasure our deeply felt gratitude to
words Mr.N.SeshaReddy,honourable chairman,AIPS,Kakinada.We also thank
Mr.Nagendra Kumar , principal and Mrs. D. Beulah, Head of the Department of
Computer Science for their co-operation and for providing excellent lab facilities.
We are very much thankful to the faculty members of our college ,and also to
the lab technicians and Classmates for their continuous support and co-operation
during this case study.
Although a leaflet title "Acknowledgements cannot represent our true feelings
for all these persons" ,we feel very much thankful to all of them and also to our
parents for encouraging us,giving us all the moral support requires and to all people
who making these endeavour a reality.
U.SriDivya
Ch.Srinivas
Sk.Mastan Shareef
DECLARATION
We have by declare that the case study entitled " ONLINE
MOVIE RESERVATION SYSTEM " has been developed by us under
the super vision of Mrs.Aruna faculty of AIPS, and submitted to AIPS,
kakinada in partial fulfillment for the requirements for the case study.
Ch.Srinivas
U.SriDivya
Sk.Mastan Shareef
ABSTRACT
The system is a Online movie reservation System development for the
Theatres. It is a concept of developing a web portal . where a customer can make
movie tickets in theatres that are made available in the site .The transfer of tickets is
also done immediately .
1 . Availability of tickets on mentioned date and time in specified city .
2 . Online booking
3 . Information of shows running in theatres
4 . Special offers
The provision for money transactions are portal . This requires possession of
banks credit or debit card with customer . An alternative mechanism also exists for
people who doesnt have a bank card . This procedure involves via phone conferences
.
INDEX
1. Introduction
2. Problem Statement
3. Requirement Analysis Document
3.1.Introduction
3.2.Current System
3.3.Proposed System
3.4.System Models
4. System Design document
4.1.Introduction
4.2.Current Software Architecture
4.3.Proposed Software Architecture
5. Testing Specifications
5.1.Structural Testing
5.1.1.Introduction
5.1.2.List of Test Cases
5.2.Functional Testing
5.2.1.Introduction
5.2.2.List of Test Cases
EXISTING SYSTEM
.
The managers of Theatres falls short of controlling the issuing of tickets .
The decision for appraisal of next show tickets in advance is difficult .He is not
provided with the detailed project information done or to be assigned based on
Application / Verticals. For issuing the tickets need the extra manual effort and take
much time to receive the tickets .
PROPOSED SYSTEM
.
MODULE DISCRIPTION:
The list of modules incorporated with ONLINE MOVIE RESERVATION
SYSTEM is
Customer Info Module
Theatre Management Module
Movie Information Module
Manager Reports
Functional Requirements
Customer Master: It deals with customer details that are entering
the details of customer when customer login into the organization
and whenever changes are required, this will handle through the
sub module which is update customer master and whenever we
dont require the details of customer, it will delete from the dabase.
Ticket Transactions: This functionality maintains the information
of ticket transactions. It maintains the information of tickets has
been taken by each customer and also which tickets are available.
Bill Payments: This module maintains payment information of
each customer for a movie.
Cancellation of Tickets : If the user want to cancel the reserved
tickets he can cancel the tickets , but it has to be done with in the
given time .
Non-Functional Requirements:
These are necessary for system design and development. If there is
written performance requirements, it just means that they exists in heads
of administrators, but nobody bothered to write them down and made sure
that everybody agrees with them. Then non functional requirements
would be the input for performance testing and capacity planning. These
are the 3 classes of performance requirements:
1. Response time
2. Throughput
3. Concurrency
Response times or processing times define how fast requests would be
processed. Acceptable response times should be defined in each particular
case. A time of 30 minutes can be excellent for a big batch job, but
absolutely unacceptable for getting a web page in a customer portal.
- 10
- 11
Introduction to UML
The Unified Modeling Language is a standard language for writing
software blueprints. The UML may be used to visualize, specify,
construct, and document the artifacts of a software intensive system.
The UML is appropriate for modeling systems ranging from
enterprise information systems to distributed Web-based applications and
even to hard real time embedded systems. It is a very expressive language
addressing all the views needed to develop and then deploy such systems.
Even though it is expressive, the UML is not difficult to understand and
to use. Learning to apply the UML effectively starts with forming a
conceptual model of the language, which requires three major elements:
the UMLs basic building blocks, the rules that dictate how these building
blocks may be put together, and some common mechanisms that apply
throughout the language.
The UML is only a language and so is just one part of a software
development method. The UML is process independent, although
optimally it should be used in a use case driven, architecture-centric,
iterative, and incremental.
The UML is a language which provides a vocabulary and the rules for
combining words in that vocabulary for the purpose of communication. A
modeling language is a language whose vocabulary and rules focus on the
conceptual and physical representation of a system. A modeling language
such as the UML is thus a standard language for software blueprints.
- 12
or
even
another
tool,
can
interpret
that
model
- 13
- 14
- 15
- 17
can see how that system reacts to the things outside, but you cant see
how that system works on the inside.
Use cases diagrams depict:
- 18
- 19
Participating
Manager, customer
Flow of events
(i)Manager or customer
enters his/her identity
number to login the system.
(ii)Manager or customer
checks the required details.
Entry condition
- 20
Exit condition
AddMovie Details
Participating
Manager
Flow of events
Entry condition
Exit condition
CheckSAvailabilityDetails
Participating
Customer,
Manager
Flow of events
Entry condition
- 21
Exit condition
- 22
- 23
CLASS DIAGRAM :
- 24
SEQUENCE DIAGRAM
Sequence diagram describes the interactions between design components
and environment. Instance of these design component appear on the
horizontal axis of the diagram, with interaction such as events,
operations, and time placed on the vertical axis. A sequence diagram
describes how objects interact with each other and how message are sent
and received between the objects.
A sequence diagram shows an interaction arranged in time
sequence. The instance participating in the interaction. Sequence sub
state occur one after the other. A line separates concurrent sub states. The
arrow lines gives the interaction among the object takes places in a
specified sequence and the sequence takes time to go from beginning to
end. The sequence diagram shows how objects communicate with one
another. The objects represented in usual way as named rectangle.
Message represented as solid line arrow and time required by vertical
lines. The objects are at top of the diagram from left to right. Extending a
line from object is called life time.
Objects:
The objects are laid out near the top of the diagram from left to right.
Extending downward from each object is dashed line called object's
lifeline. Along the lifeline is narrow rectangle called an activation that
represents an execution of an operation the object carries out.
Message:
A message can be simple, synchronous, asynchronous,. A simple message
is a transfer of control from one object to another. If an object sends a
synchronous message, it waits for an answer to the message before it
proceeds with its business. If an object sends asynchronous message, it
doesn't wait for an answer before it proceeds. In the sequence diagrams, a
- 25
COLLABORATION DIAGRAM
A collaboration diagram represents the organization of objects that
participate in an interaction. You form a collaboration diagram by first
placing the objects that participate in the interaction.Next you represent
with links that connect these objects as the arcs.Finally you can represent
these links with the messages that object send and receive. Collaboration
diagram have 2 features that distinguish from sequence diagram:
There is a path to indicate how one object is linked to another.you can
attach a stereotype to the far end of link with <<local>> and <<global>>.
There is a sequence number to indicate the time order of messages.you
prefix
these
messages
with
number(start
with
1),increasing
- 27
- 28
ACTIVITY DIAGRAM :
ACTIVITY DIAGRAM
- 30
- 31
:WindowsHost
Register
DataBase
:WindowsHost
:compensation
details database
Login
Logout
:WindowsHost
apc:pc
:training detail
s database
:Iexplorer
emp personal
details database -
32
:WebServer
- 33
a.
- 34
b.
c.
Threads:
Threads are concurrent variations of procedure driven control i.e the
system can create an arbitrary number of threads, each thread
corresponding to different threads. If a thread needs additional data, it
waits for input from an actor.
Configuration:
For each persistent object, we examine which use cases are created, which use
cases are destroyed.
Exception handling:
Boundary Condition: We try to keep security to the data and all functionalities.
- 35
Introduction
Object design tradeoffs
One of the design criteria for any software development is buy Vs build.
However the system needs a special solution for managing the transactions done in
backing the following are the naming conventions.
Name of the functions which is used to create details should be end with the
word details
name of the buttons that are used to take decisions should use the words like
accepting or satisfying
Methods are named with verb phrases, field and patterns with noun phrases.
Error status is written via an exception only and not a return value.
Packages:
A UML grouping concepts denoting that a set of objects or classes are related.
Packages are used in use case and class diagram dealt with the complexity associated
with large no. of use cases and concepts.
The following are the packages in the Ravindra system.
Test
User details
- 37
TESTING
- 38
Testing is the major quality control measure used during software development. The
basic function is to detect errors in the software. Testing plays a critical role in quality
assurance for software. Due to the limitation of the verification methods for the
previous phases, design and requirements faults also appear in the code. Testing is
used for detecting these errors. In addition to detecting the error introduced during the
coding phase.
Testing is a dynamic method for verification and validation, where the system
to be tested is actually executed and behavior of the system, from which the presence
of faults can be reduced.
LEVELS OF TESTING
In order to uncover the errors present in different phases we have the concept
of levels of testing. The basic levels of testing are,
Client Need
Accepting Testing
Requirements
System Testing
Design
Integration Testing
Code
Unit testing
System Testing
The philosophy behind testing is to find errors. Test cases are devised
with this in mind. A strategy employed for system is code testing. The code testing
examines the logic of the program. To follow this method we developed some test
data that resulted in executing every instruction in the program and module i.e every
path is tested. Systems are not designed as entire nor are they tested as single
systems. To ensure that the coding is perfect two types is performed or for that
matter is performed on all systems.
Types of Testing
- 39
* Unit Testing
* Link Testing
Unit testing focuses on verification effort on the smallest unit of software i.e
the module. During the uncover errors with in the boundary of the module.
1. STRUCTURAL TESTING (WITH BOX)
INTRODUCTION
White box testing are also called as unit testing focuses verification effort on
the smallest unit of software i.e the module. Using the detailed design and the
process specifications testing is done to uncover errors with in the boundary of the
module. All the modules must be successful in the unit test before the start of
integration testing.
CONCLUSION
- 40
We can conclude that project is very essential and useful for any
Organization to manage its resources effectively and plan for future
projects. It is very effective and low-cost communication with high
reliability.
BIBILIOGRAPHY
1. Object Oriented Software Engineering - Bernd Bruegge, Allen
H.Dutoite.
2. Object Oriented Software Engineering: Practical software
development using UML & Java Timothy C. Lethbridge & Robert
Laganiere.
- 41