ADITYA INSTITUTE OF POST GRADUATE STUDIES

(Affiliated to Andhra University)

R.T.O Office Road, Ayodya Nagar, Kakinada-533003
Ph no. 0884-2346661

CASE STUDY ON
ONLINE MOVIE RESERVATION SYSTEM
BY
Ch.Srinivas
U.SriDivya
Sk.Mastan Shareef

III MCA I SEMESTER

Under the Esteemed Guidance of
Mrs.Aruna
Lecturer in Computer Science

DEPARTMENT OF COMPUTER SCIENCE

ADITYA INSTITUTE OF POST GRADUATE STUDIES
KAKINADA-533003
(2008-2011)

-1-
 ADITYA INSTITUTE OF P.G STUDIES
(Approved by A.I.C.T.E. New Delhi)
(Affiliated to Andhra University)
Under the Management of Aditya Academy
KAKINADA-533003,ph:2376662

DEPARTMENT OF COMPUTER SCIENCE

CERTIFICATE

This is certify that it is a bonified record of the Case Study work

entitled "ONLINE MOVIE RESERVATION SYSTEM" done by
Srinivas, SriDivya, Sk.Mastan Shareef during the period 2010-2011 in
partial fulfillment of the requirements for the award of Degree "Master Of
Computer Applications" in the Department of Computer Sciences, Aditya
Institute of Post Graduate Studies, kakinada.

(Mrs.Aruna) (Mrs.D.BEULAH)
Internal Guide Head of the dept.
Department of Comp.Sc.

External Examiner

-2-
 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

-3-
 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

-4-
 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
bank’s credit or debit card with customer . An alternative mechanism also exists for
people who doesn’t have a bank card . This procedure involves via phone
conferences .

-5-
 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

-6-
REQUIREMENTS ANALYSIS DOCUMENT

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 .

DRAWBACKS IN EXISTING SYSTEM:

 Need of extra manual effort.

 It used to take much time to receive Tickets

 Wastage of time will be high .

-7-
PROPOSED SYSTEM

. 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
bank’s credit or debit card with customer . An alternative mechanism also exists for
people who doesn’t have a bank card . This procedure involves via phone
conferences .

ADVANTAGES OF PROPOSED SYSTEM:

 Very fast and accurate.

 No need of any extra manual effort.
 No fever of data loss.
 Just need a little knowledge to operate the system.
 Doesn’t require any extra hardware device.
 At last very easy to receive the tickets.

-8-
 MODULE DISCRIPTION:

The list of modules incorporated with “ONLINE MOVIE RESERVATION

SYSTEM” is

 Customer Info Module

 Theatre Management Module
 Movie Information Module

 Manager Reports

Customer Info Module :

This module deals with the management of the customers information
such as the personal details-his name, login id, password ,etc.,
Importance of modules in any software development side is we can easily
understand what the system we are developing and what its main uses are. At
the time of project we may create many modules and finally we combine them
to form a system.
Movie Information Module:
This module deals with the management of the movie information such as the
hiring of the movie, payments criteria, its information maintenance etc.

Theatre Management Module:

This module deals with the management of the Theatre related with the movies that
were past dealt, current projects in his account etc.

Manager Reports Module:

This module is specified for the purpose of the report generation for the
Manager on his desired requests.

-9-
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
don’t 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 -
Throughput is the rate at which incoming requests are completed.
Throughput defines load on the system and is measured in operations per
a time unit. It may be the number of transactions per second .

Concurrency, the number of users or threads working simultaneously, is

important too. Even if users are connected, but not active, they still hold
the same resources.
• Performance: Fast retrieval of employee’s information required by
the Central Management from the database through SQL.

• Availability: This project has been tested successfully which needs

all requirements as specified and giving accurate output as needed.
So the organization can implement this project easily.

• Reliability: In the Current System, we are providing the security to

the employee information and authoring data to only Central
Management and allowing effective retrieval of data. It is also
helpful in optimum utilization of time.

- 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 UML’s 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 -
Modeling yields an understanding of a system. No one model is ever
sufficient. Rather, we often need multiple models that are connected to
one another in software development in order to understand anything but
the most trivial system. For software intensive systems, this requires a
language that addresses the different views of a system’s architecture as it
evolves throughout the software development lifecycle.
The vocabulary and rules of a language such as the UML tells us how to
create and read well formed models, but they don’t tell us what models
they should create and when we should create them. That’s the role of
software development process. A well defined process will guide us in
deciding what artifacts to produce, what activities and what workers to
use to create them and manage them, and how to use those artifacts to
measure and control the project as a whole.

The UML is more than just a bunch of graphical symbols. Rather, behind
each symbol in the UML notation is a well-defined semantics. In this
manner, one developer can write a model in the UML, and another
developer, or even another tool, can interpret that model
umambigously.UML addresses the specification of all the important
analysis, design and implementation decisions that must be made in
developing and deploying a software-intensive system.

The UML is not a visual programming language, but its models can be
directly connected to a variety of programming languages. This means
that it is possible to map from a model in the UML to a programming
language. Things that are best expressed graphically are done so in the
programming language. This mapping performs forward engineering: The
generation of code from a UML model into a programming language. The
reverse is also possible. Unless we encode that information in the
implementation, information is lost when moving from models to code.

- 13 -
Reverse engineering thus supports tool support with human intervention.
Combining these two paths of forward code generation and reverse
engineering yields roundtrip engineering, meaning the ability to work in
either a graphical or textual view, while tools keep the two views
consistent. In addition it this direct mapping, the UML is sufficiently
expressive and unambiguous to permit the direct execution of models, the
simulation of systems, and the instrumentation of running systems.

The UML is intended primarily for software-intensive systems. It has

been used effectively for such domains as

• Enterprise information systems

• Banking and financial services
• Telecommunications
• Transportation
• Defense/aerospace
• Retail
• Medical electronics
• Scientific
• Distributed web based services

The UML is not limited to modeling software. In fact, it is expressive

enough to model non-software systems, such as workflow in the legal
system, the structure and behavior of a patient healthcare system, and
design of hardware.
Rational Machines was founded by Paul Levy and in 1981 to
provide tools to expand the use of modern software engineering practices,
particularly explicit modular architecture and iterative development.
Rational was sold for US$2.1 billion a tailorable process that guided

- 14 -
development tools that automated the application of that accelerated
adoption of both the process and the tools.

Rational Rose is a tool ser produced and marketed by Rational

Software Corporation (now owned by IBM). Rose is an operational tool
set that uses UML as it means for facilitating the factor of domain
semantics and architecture/design intent. UML has a number of different
notations, allowing the specification of the artifacts of design from many
perspectives and for different objectives during the computer engineering
lifecycle. Most of these notations are directly supported through the Rose
tool set.

One of the unique characteristics of rose is its ability to be

extended through use of its “Add-in” capability. This allows tool
functionality to be extended in a number of different directions, such as
by adding new tools, modifying existing ones and adding whole new
complementary conceptual design methods into the Rose toolset. The
complete fabric of UML and its realization in the Rose set of components
is made available to the user/engineer. I have found that these interfacing
capabilities are poorly documented. They should do a better job of
documenting this capability and making the information more widely
available, as I think it is a valuable platform in which to explore research
ideas in design and analysis methods.

I have found UML and Rose to be useful in a wide range of

modeling situations, and typically will use it to simply organize the
concepts of a domain I am studying, so that it is easier for me to organize
and retain a basic comprehension of the information in that domain—
leveraging the mind’s ability for “chunking” information into organized

- 15 -
structures to more easily manage complexity and enhance retention of
knowledge structure.

Use case diagram:

A use case specifies the behavior of a system or a part of a system and is

a description of a set of sequences of actions, including variants that a
system performs to yield an observable result of value to an actor.

We apply use cases to capture the intended behavior of the system we are
developing, without having to specify how that behavior is implemented.
Use cases provide a way for developers to come to a common
understanding with your system’s end users and domain experts. In
addition, use cases serve to help validate your architecture and to verify
your system as it evolves during development. As we implement our
system, these use cases are realized by collaborations whose elements
work together to carry out each use case.

Use case diagrams are one of the five diagrams in the UML for modeling
the dynamic aspects of systems. Use case diagrams are central to
modeling the behavior of a system, a subsystem or a class. Each one
shows a set of use cases and actors and their relationship.

Use case diagrams are important for visualizing, specifying and

documenting the behavior of an element. They make systems, subsystems
and classes approachable and understandable by presenting an outside
view of how those elements may be used in context. Use case diagrams
are also important for testing executable systems through forward
engineering and for comprehending executable systems through reverse
engineering.

- 16 -
A use case diagram is a diagram that shows a set of use cases and actors
and their relationships.

A use case diagram is just a special kind of diagram and shares the
same common properties as do all other diagrams- a name and graphical
contents that are a projection into a model.

We apply use case diagrams to model static use case view of a

system. This view primarily supports the behavior of a system-the
outwardly visible services that the system provides in the context of its
environment.

When we model the static use case view of a system, you will typically
apply use case diagrams in one of two ways.

1. To model the context of a system

Modelling the context of a system involves drawing a line around the
whole system and asserting which actors lie outside the system and
interact with it.

2. To model the requirements of a system

Modelling the requirements of a system involves specifying what that
system should do, independent of how that system should do it. Here
we will apply use case diagrams to specify the desired behavoiur of
the system. In this manner, a use case diagram lets you view the whole
system as a black box; you can see what’s outside the system and you
can see how that system reacts to the things outside, but you can’t see
how that system works on the inside.

- 17 -
 Use cases diagrams depict:

• Use cases: A use case describes a sequence of actions that provide

something of measurable value to an actor and is drawn as a
horizontal ellipse.
• Actors: An actor is a person, organization, or external system that
plays a role in one or more interactions with your system. Actors
are drawn as stick figures.
• Associations: Associations between actors and use cases are
indicated in use case diagrams by solid lines. An association exists
whenever an actor is involved with an interaction described by a
use case. These are modeled as lines connecting use cases and
actors to one another with an optional arrowhead on one end of the
line. The arrow head is often used to indicate the direction of initial
invocation of the relationship or to indicate the primary actor
within the use case. The arrowheads are typically confused with
dataflow and as a result I avoid their use.

Use case templates:

Participating actors:

• Theatre manager
• Customer

Flow of events:

• The Theatre manager entered through login

• After login Theatre manager check the availability of tickets.
• Theatre manager allocate some extra tickets to Customers.
• Theatre manager maintain movie information like addition,
updation and deletion.

- 18 -
 • Customer can also entered through login . After login check the
availability of tickets .

Exceptional flow of events:

• Invalid customer check.

• Customer master removes customer details if he is not available.
• Theatre manager removes movie details if it is not necessary.

USECASE Diagram of Online Movie Reservation System:

Use Case Templates for Manager,Custmer login:

- 19 -
Use case name Manager or customer Login

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 Manager or customer must

know their user id and
password.

Exit condition Manager or customer doing

all the tasks successfully .

Use Case Templates for AddMovieDetails:

Use case name AddMovie Details

Participating Manager

Flow of events (i)Manager enters his/her

identity number and password to
login the system.
(ii)Manager checks the required
movie details.
(iii)Manager enters the details in
the form and submit the form.

Entry condition Manager must know their user id

and password.

Exit condition Manager doing all the tasks

successfully.

Use Case Templates for CheckAvailabilityDetails:

- 20 -
Use case name CheckSAvailabilityDetails

Participating Customer,
Manager

Flow of events (i)Customer enters his/her

identity number to login the
system.
(ii)Customer checks the required
details.

Entry condition Customer or Manager must know

their user id and password.

Exit condition Customer doing all the tasks

successfully and Manager doing all
the tasks successfully.

- 21 -
CLASS DIAGRAM :

- 22 -
Fig Showing the overall representation of class diagram

SEQUENCE DIAGRAM

- 23 -
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
simple message has a two-line arrowhead; a synchronous message has a
half-arrowhead.
Time:

- 24 -
 Time starts at the top and progresses towards the bottom. A
message that's closer to the top occurs earlier in time than a message
that's closer to the bottom.

Fig Showing the overall representation of sequence diagram

COLLABORATION DIAGRAM

- 25 -
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 a number(start with 1),increasing
monotonically for each messages in the flow of control i.e 2,3,…………
To show nesting messages you will use decimal numbers i.e
1.1,1.2,1.3…………..

- 26 -
Fig Showing the overall representation of Collabration diagram

- 27 -
STATE CHART DIAGRAM :

ACTIVITY DIAGRAM :

ACTIVITY DIAGRAM

An activity diagram in much similar to a flowchart. It shows steps,

decision point, and branches. It is an extension of the state diagram. The
state diagram shows the state of an object and represents activities as
arrows connecting the state. The activity diagram highlights the activities.

Each activity is represented as rounded rectangle, more oval in

appearance that the state icon. An arrow represents the transaction from
one activity to the next. Like the state diagram, the activity diagram has a
starting point represented by a filled-in circle, and an endpoint
represented by a bull's eye.

- 28 -
Fig Showing the overall representation of Activity diagram

- 29 -
 System Design Document

Introduction

- 30 -
purpose of the system: Online Movie reservation system is used to create
new user and easily he can reserve the tickets by login into the organization .
Design Goals: Using this system, we can create an effective communication
media between two or more persons of an organization which is very fast in nature.
Ordinary methods for communications in an organization.

Current Software Architecture:

Proposed Software Architecture:
II. Subsystem decomposition: Human resource management System is
decomposed into registration, login, logout all these details entered into the database.

:WindowsHost
Register DataBase
:WindowsHost

:compensation
details database

Login Logout

:WindowsHost

apc:pc :training detail

s database

:Iexplorer

Hardware and Software Mapping(Deployment Diagram):

:WindowsHost

emp personal
details database
- 31 -
 :WebServer

Figure: Deployment Diagram:

Persistent Data Management:

- 32 -
Access Control and Security:
Providing Access Control:
In access control mechanisms different actors have access to different
functionalities and three approaches.
a. Global access table

b. Access control list

c. Capabilities

a. Global Access table: It represents explicitly every cell in the

matrix as a(Actor, class, Operation). This access table determines if an
actor has access to a specific object requires looking up to the
corresponding tuple. If no such tuple is defined, access is denied.

b. Access Control list: It associates a list of(Actor, Operation) pair

with each class to be accessed. Empty cells are discarded. Every time
an object is accessed, its access list is checked for the corresponding
actor and operation.

c. Capabilities: A capability associates a(class, operation) pair with an

actor. A allows an actor access to an object of the class described in the
capabilities.

Designing Global control flow:

Control flow is the sequence of actions in a system. In object-oriented systems
sequential actions include which operation should be executed in which order. There
are three possible control flow mechanisms.
a. Procedural driven control

b. Event driven control

c. Threads

- 33 -
 a. Procedural driven control:
The operations wait for input whenever they need data from an actor.
This Kind of control flow is mostly used in systems in procedural
languages.

b. Event driven control:

A main loop waits for an external event. Whenever the event becomes
available, it is dispatched to the objects mostly the events are associated with
based on information.
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.

Identifying boundary conditions:

We need to examine the boundary conditions of a system i.e to decide how the
system is started, initialized and shutdown. In every system deal with major failures
which has data corruption, network outages, software errors, power outages.
In general we identify the boundary use cases by examining each
subsystems and each persistent data.

Configuration:
For each persistent object, we examine which use cases are created, which use
cases are destroyed.

Startup and shutdown:

For each component, we add three different use cases i.e. start, shutdown and
configure the components.

Exception handling:
Exception handlings are by three different resources.
• Hardware failure.
• changes in the OS environment.
• Software fault.

Boundary Condition: We try to keep security to the data and all functionalities.

- 34 -
- 35 -
OBJECT DESIGN DOCUMENTATION
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

Interface documentation guidelines:

Interface documentation guidelines and coding conventions are the single

most important factors. That can improve communications between developers
during object design.
The following are the used in Client Provisioning object design.
• Classes are named with singular nouns
• 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.

• Com(For JDBC Speciation which is in MySql)
• Test
• User details

- 36 -
- 37 -
TESTING
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

- 38 -
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

* 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.

LIST OF TEST CASES PREPARED

I tested step wise every peace of code, taking care that every statement in this
executed at least once. The white box testing is also called Glass box testing.

I have generated a list of test cases, sample data. This is used to check all
possible combinations of execution paths through the code at every module level.

2. FUNCTIONAL TESTING (BLACK BOX)

INTRODUCTION

The testing method considers a module as a single unit and checks the unit at
interface and communication with other modules rather getting in to details at
statement level. Here the module will be treated as a black box that will take some
input and generate output. Output for a given set of input combinations are
forwarded to other modules.

LIST OF TEST CASES PREPARED

Test cases that reduce by a count that a greater than one, the
number of additional test cases that much be designed to achieve
reasonable testing.
Test cases that tell us some thing about the presence or absence of
lessons of errors, rather than an error associated only with the specific

- 39 -
test at hand.

CONCLUSION
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.

- 40 -
- 41 -