DECLARATION

We hereby declare that the project entitled “Movie World” submitted to the
department of Information Technology, Hyderabad for partial fulfillment of the
requirement for the award of Bachelor of Technology in Information Technology is
a result of original work carried out by us.

This work in original has not been submitted so far in part or full for any other institute
or University.
 ACKNOWLEDGEMENT

We thank the almighty for giving us the courage " perseverance in completing
the project. This project itself is an acknowledgement for all those who have given us
their heart-felt-co-operation in making it a grand success.

We are thankful to our principal, Prof.------------ for providing the

necessary infrastructure and labs. We are greatly indebted to, Head of Information
Technology, Mr.------------ for providing valuable guidance at every stage of this
project work.

We are also thankful to the project coordinator, Mr.------- for extending their
sincere " heartfelt guidance through out this project work. Without their supervision
and many hours of devoted guidance, stimulating " constructive criticism, this thesis
would never come out in this form.

It is a pleasure to express our deep and sincere gratitude to the project

Guide Mr,---------- and are profoundly grateful towards the unmatched help
rendered by him. &ur special thanks to all the lectures of Information Technology,
for their valuable advises at every stage of this work.

Last but not the least( we would like to express our deep sense and earnest
thanks giving to our dear parents for their moral support and heartfelt cooperation in
doing the project. We would also like to thank our friends, whose direct or indirect help
has enabled us to complete this work successfully.
 COMPANY PROFILE

)atapoint has been actively in the profession of sourcing IT professionals from the year
*000. We have since placed scores of candidates from different skill sets, with varying
levels of experience. Having established a reputation as a good placement organization,
we are constantly approached by adept professionals, in pursuit of better opportunities,
which helps us maintain an updated database of present and potential IT connoisseurs in
demand home and abroad

)atapoint endeavors to be a pioneer in Recruiting and manpower consulting thanks to

strategic alliances with leading multinational companies in India and US of America.
&ur technically competent, experienced, and certified consultants will help our
clientele to get the right manpower at the right time. We take pride in having top-notch
companies who make enable us to have faith in the future through maintaining high
quality in screening, hiring and management.

)atapoint has identified a number of areas of thrust in the emerging and ever growing
IT industry and virtue of which, we would focus all our energies to get on to the fast
track in the shortest possible period. We pursue requirements from leading 0orporate
in India and abroad. The company is also entering into a memorandum of
understanding with leading companies in India " USA for placements.
 Abstract

1. Objective:

The main aim of this Movie World is online booking tickets for various movies in Registered

theatres by the users.

2. Problem Definition:
Here details about Now playing movies and no of tickets available in a
particular theatre for particular movie, Movie Details, ticket cost for
registered users

3. Existing System:

Present System developed in asp .ln asp there are some limitations.
➢ lt is scripting language
➢ lt is very code complexity
➢ There is server controls in asp
➢ lt Doesn$t Support language interoperabilty
.
4. Proposed System:

Asp.net Support code behind technology

lt supports different controls like html controls, server
controls lt Supports language interoperability
This project contains three modules
1 .Admin
2. Booking tickets
3. Users

1 Admin: In this module administrator has to register the theatres assign

movies to theatres, register users,
2. Booking tickets: In this details about booked tickets and tickets

booking Admin can update and delete purchase, sales and other

details.

3. Users: In this users can see the showing movies and upcoming movies details ,
ticket booking and Registering as members.

CONTENTS

1. INTRODUCTION

i. PURPOSE OF PROJECT

ii. SCOPE OF PROJECT

iii. PROJECT OVERVIEW

2. PROJECT ANALYSIS

i. EXISTING SYSTEM

ii. PROPOSED SYSTEM

iii. H/W and S/W SPECIFICATIONS

3. SYSTEM DEVELOPMENT ENVIRONMENT

&. PROJECT DESIGNING

i. DFD (Data Flow DiaqranS)

ii. UML DiaqranS

iii. ER DiaqranS

iv. DB DeSiqn

v. ScreenS
5. PROJECT TESTING

i. 1erformance Testing

ii. Unit Testing

iii. Integration Testing

6. CONCLUSION

7. FUTURE ENHANCEMENT

8. BIBLIOGRAPHY

Project Introduction

The purpose of this document is to present an overall description and

listing of the functionality of The Testing Assistant for Regression Testing. It
will explain the scope of the project as well as describe the system
environment. This document will also include an easily traceable means by
which the user can trace each functionalitys brief description to its full
description. Also included is a user interface specification whereby the user
can demonstrate interface standards to be used in designing the system.
Furthermore" considerations regarding non-functional re$uirements and
system evolution are addressed.
This document is intended for users of the system including Unit Testers"
unit test supervisors" and any individuals involved in testing a new system in
development. This document will also be used as a reference for the
developers of The Testing Assistant for Regression Testing.

P&O()*T O+)&+I)W
-escribe the contents and organization of the rest of this document. /ince there is already a
Table of *ontents" this overview will be less formal but more informative. -escribe the two
basic remaining sections" the Overall -escription and the &e$uirements /pecification.

1. PURPOSE OF PROJECT

Man ua I Pr oc e S S

SeIect
Searching movie


uSerS
Select Theatre

Book ticketS

Display ticket

Why the new SyStem?

With the new system the following activities get more momentum.

1. The actual process of the organization can be modularized into two different
independent views

➢ User view

➢ System administrators view

 *. The user at any time can view the required information whether seats
available for particular movie in a particular theatre.He can collect all information
like as Movie
)etails,theatre )etails.

3. The information while it is collected can referentially be segregated into their

respective databases from single window, saving the time of multiple data

entries.

>. If planned in an organized manner the users can be provided an online

terminal where they can access the information at their own hands with out

the basic intervention manually.

5. The user can first Registration in enter the 1ersonal details, and User login

and If you want to update personal )etails and you and update.

@.The User 0an book tickets and After insert movie and theatre )etails and display

1ayment )etails.

A. The user collect all information like as theatre )etails and movie

8. Administrator is maintain the Movie )etails ,Theatre details, and 0heck the user

details .

C. The Administrator check the user account details, admin got the ))/0heck ,

&ffer clear the 1ayment in bank. Administrator is Active the user for tickets

2. SCOPE OF THE PROJECT

The scope of project DMovie WorldE is to enable the User to select theatre
and then book the desired seatnos in available seates.Motive of this is to booking
tickets online

3. PROJECT OVERVIEW
 It is a web based online project . The main aim of the project is any user
they can access the system through website at any time without going to the
company. As a new user also he can collect all information like as a movies Available
,list of theatres

1. AdminiStrator moduIe

*. USer moduIe

3. Ticket bookinq moduIe

1) AdminiStrator moduIeF
The Administrator is maintain the user )etails ,Movie details,

Theatre details, and 0heck the 7o of seats available . .

2. USer moduIe

The user can first &egistration in enter the Personal details" and User

login and If you want to update personal -etails and you and update. The user

collect all information like Movies details,Theatre )etails.

3. Bookinq moduIe:

The Users will search for the movie and then go for theatre then booking the tickets

online

PROJECT ANALYSIS
5. Existing System:

Present System developed in asp .ln asp there are some limitations.
 ➢ It is scripting language
➢ It is very code complexity
➢ There is server controls in asp
➢ It Doesn$t Support language interoperability
.
6. Proposed System:

Asp.net Support code behind technology

It supports different controls like html controls, server
controls It Supports language interoperability

After underStandinq the exiStinq SySten and underStandinq the need for
developinq a new SySten different people involved in the related activitieS have been
conSulted. The data needed for the Study haS been collected fron conpany recordS.

The conputerization of thiS SySten would avoid the wronq interpretation and bad
calculation of data .The SySten help the uSer to See any docunentS, Source code, taSkS,
activitieS, tean infornation with detailS at the click of a button. The record data iS
naintained and backed up Such a way that data iS not loSS. The Speed of the SySten
could alSo increaSe.

3. H/W AND S/W SPECIFICATION

SOFTWARE CONFIGURATION

OPERATING PLATFORM : WINDOWS 2000/NT/XP

RDBMS : SQLSERVER 2000

SOFTWARE : VS.NET 2003

FRONT END TOOL : ASP.NET

HARDWARE CONFIGURATION

RAM : 128MB
 HARD DISK : MINIMUM 20 GB

SYSTEM DEVELOPMENT ENVIRONMENT

1. HTML

WHAT IS HTML?

To publiSh infornation for qlobal diStribution, one needS a univerSity-

underStood lanquaqe, a kind of publiShinq nother tonque that all conputerS nay
potentially underStand. The publiShinq lanquaqe uSed by the World Wide Web iS HTML
(Hyper Text Markup Lanquaqe)

HTML GiveS AuthorS The MeanS To

1. PubliSh online docunentS with headinqS, text, tableS, liSt, photoS etc.
2. Retrieve online infornation via hypertext linkS, at the click of a button
3. DeSiqn fornS for conductinq tranSactionS with renote ServiceS, for uSe in
Searchinq infornation, nakinq reServation, orderinq productS etc.;
4. IncludeS SpreadSheetS, video clipS, Sound clipS, and other applicationS directly
in the docunentS.

Some HTML TaqS

<HTML> :Startinq an HTML taq

<HEAD> : Creatinq a web paqe'S head

<TITLE> : Givinq a web paqe `S body

</HEAD> : Endinq a web paqeS head

</BODY> : Endinq a web paqeS body

</HTML> :Endinq a web paqe

<FORM> : Creatinq a HTML fornS

<INPUT TYPE=BUTTON> : Creatinq a buttonS

<INPUT TYPE=CHECKBOX> : Creatinq a checkboxeS

<INPUT TYPE=SUBMIT> : Creatinq a Subnit button

<INPUT TYPE=TEXT> : Creatinq a text fieldS

HTML 4.0

HTML 4.0 extendS with nechaniSnS for Style SheetS, Scriptinq, franeS enbeddinq
objectS, inproved Support for riqht to left and nixed direction textS, richer tableS and
enhancenentS to forn, offerinq inproved acceSSibilitieS for people with diSability

2. INTRODUCTION TO JAVA SCRIPT

WHAT IS JAVA SCRIPT?

 JavaScript, oriqinally Supported by NetScape Naviqator, iS the noSt popular Web
Scriptinq lanquaqe today. JavaScript letS you enbed proqranS riqht in your Web paqeS
and run theSe proqranS uSinq the Web browSer. You place theSe proqranS in a
<SCRIPT> elenent. If you want the Script to write directly to the Web paqe, place it
in the <BODY> elenent.

EX: <HTML>

<HEAD>

<TITLE></TITLE>

</HEAD>

<BODY>

<SCRIPT LANGUAGE=”JavaScript”>

</SCRIPT>

</BODY></HTML>

JAVASCRIPTS OBJECTS

JavaScript iS an object-oriented lanquaqe. JavaScript coneS with a nunber of

predefined objectS.

ObjectS of the JavaScript

1. Docunent: CorreSpondS to the current Web paqe'S body. USinq thiS object,
you have acceSS to the HTML of the paqe itSelf, includinq the all linkS, inaqeS
and anchorS in it.
2. Forn: HoldS infornation about HTML fornS in the current paqe.
3. Frane: ReferS to a frane in the browSer'S window.
4. HiStory: HoldS the recordS of SiteS the Web browSer haS viSited before reachinq
the current paqe.
 5. LocationF Holds information about the location of the current web page.
@. 7avigatorF Refers to the browser itself, letting you determine what browser the
user has.
A. WindowF Refers to the current browser window.

JAVASCRIPTS EVENTS

Some of the events of 4avaScript

1. on 0hangeF &ccurs when data in a control, like a text field, changes.

*. on 0lickF &ccurs when an element is clicked.
3. on 3ocusF &ccurs when an element gets the focus.
>. on Mouse )ownF &ccurs when a mouse button goes down.
5. on ResetF &ccurs when the user clicks the reset button.

JAVASCRIPTS FUNCTIONS

De0lara4ion of f/n04ion

SyntaxF function function name ;<

Write these functions in JS0RI1TK tag.

3. INTRODUCTION A+OUT .NET

Overvie5 of 42e .NET Frame5or8

The .72T 3ramework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. The .72T

3ramework is designed to fulfill the following objectivesF

• To provide a consistent object-oriented programming environment whether

object code is stored and executed locally, executed locally but Internet-distributed, or

executed remotely.

• To provide a code-execution environment that minimizes software deployment

and versioning conflicts.

• To provide a code-execution environment that guarantees safe execution of code,

including code created by an unknown or semi-trusted third party.

• To provide a code-execution environment that eliminates the performance

problems of scripted or interpreted environments.

• To make the developer experience consistent across widely varying types of

applications, such as Windows-based applications and Web-based applications.

• To build all communication on industry standards to ensure that code based on

the .72T 3ramework can integrate with any other code.

The .72T 3ramework has two main componentsF the common language runtime and

the .72T 3ramework class library. The common language runtime is the foundation of

the .72T 3ramework. 8ou can think of the runtime as an agent that manages code at

execution time, providing core services such as memory management, thread

management, and remoting, while also enforcing strict type safety and other forms of

code accuracy that ensure security and robustness. In fact, the concept of code

management is a fundamental principle of the runtime. 0ode that targets the runtime is

known as managed code, while code that does not target the runtime is known as

unmanaged code. The class library, the other main component of the .72T 3ramework,

is a comprehensive, object-oriented collection of reusable types that you can use to

develop applications ranging from traditional command-line or graphical user interface

(GUI) applicationS to applicationS baSed on the lateSt innovationS provided by

ASP.NET, Such aS Web FornS and XML Web ServiceS.

The .NET Franework can be hoSted by unnanaqed conponentS that load the connon

lanquaqe runtine into their proceSSeS and initiate the execution of nanaqed code,

thereby creatinq a Software environnent that can exploit both nanaqed and

unnanaqed featureS. The .NET Franework not only provideS Several runtine hoStS,

but alSo SupportS the developnent of third-party runtine hoStS.

For exanple, ASP.NET hoStS the runtine to provide a Scalable, Server-Side

environnent for nanaqed code. ASP.NET workS directly with the runtine to enable

Web FornS applicationS and XML Web ServiceS, both of which are diScuSSed later in

thiS topic.

Internet Explorer iS an exanple of an unnanaqed application that hoStS the runtine (in

the forn of a MIME type extenSion). USinq Internet Explorer to hoSt the runtine

enableS you to enbed nanaqed conponentS or WindowS FornS controlS in HTML

docunentS. HoStinq the runtine in thiS way nakeS nanaqed nobile code (Sinilar to

MicroSoft® ActiveX® controlS) poSSible, but with Siqnificant inprovenentS that only

nanaqed code can offer, Such aS Seni-truSted execution and Secure iSolated file

Storaqe.

FeatureS of the Connon Lanquaqe Runtine

The connon lanquaqe runtine nanaqeS nenory, thread execution, code execution,

code Safety verification, conpilation, and other SySten ServiceS. TheSe featureS are

intrinSic to the nanaqed code that runS on the connon lanquaqe runtine.

With reqardS to Security, nanaqed conponentS are awarded varyinq deqreeS of truSt,

dependinq on a nunber of factorS that include their oriqin (Such aS the Internet,

enterpriSe network, or local conputer). ThiS neanS that a nanaqed conponent niqht or

niqht not be able to perforn file-acceSS operationS, reqiStry-acceSS operationS, or other

SenSitive functionS, even if it iS beinq uSed in the Sane active application.

The runtine enforceS code acceSS Security. For exanple, uSerS can truSt that an

executable enbedded in a Web paqe can play an anination on Screen or Sinq a Sonq,

but cannot acceSS their perSonal data, file SySten, or network. The Security featureS of
the runtime thus enable legitimate Internet-deployed software to be exceptionally

feature rich.

The runtime also enforces code robustness by implementing a strict type- and code-

verification infrastructure called the common type system ;0TS<. The 0TS ensures that

all managed code is self-describing. The various Microsoft and third-party language

compilers generate managed code that conforms to the 0TS. This means that

managed code can consume other managed types and instances, while strictly

enforcing type fidelity and type safety.

In addition, the managed environment of the runtime eliminates many common

software issues. 3or example, the runtime automatically handles object layout and

manages references to objects, releasing them when they are no longer being used. This

automatic memory management resolves the two most common application errors,

memory leaks and invalid memory references.

The runtime also accelerates developer productivity. 3or example, programmers can

write applications in their development language of choice, yet take full advantage of

the runtime, the class library, and components written in other languages by other

developers. Any compiler vendor who chooses to target the runtime can do so.

Language compilers that target the .72T 3ramework make the features of the .72T

3ramework available to existing code written in that language, greatly easing the

migration process for existing applications.

While the runtime is designed for the software of the future, it also supports software

of today and yesterday. Interoperability between managed and unmanaged code

enables developers to continue to use necessary 0&M components and )LLs.

The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services, managed code is never interpreted.

A feature called just-in-time ;4IT< compiling enables all managed code to run in the

native machine language of the system on which it is executing. Meanwhile, the

memory
manager removes the possibilities of fragmented memory and increases memory

locality-of-reference to further increase performance.

3inally, the runtime can be hosted by high-performance, server-side applications, such

as MicrosoftR SGL ServerS and Internet Information Services ;IIS<. This infrastructure

enables you to use managed code to write your business logic, while still enjoying the

superior performance of the industry s best enterprise servers that support runtime

hosting.

0ommon Type System

The common type system defines how types are declared, used, and managed in the

runtime, and is also an important part of the runtime s support for cross-language

integration.

Language Interoperability

)escribes built-in support for cross-language interoperability and introduces the

0ommon Language Specification.

W2a4 i1 42e Common Lanq/aqe Spe0ifi0a4ion7

2xplains the need for a set of features common to all languages and identifies 0LS

rules and features.

Wri4inq CLS-Complian4 Code

)iscusses the meaning of 0LS compliance for components and identifies levels of 0LS

compliance for tools.

Common T3pe S314em

)escribes how types are declared, used, and managed by the common language

runtime.

Me4ada4a and Self-De10ri9inq Componen41

2xplains the common language runtimes mechanism for describing a type and

storing that information with the type itself.

. 72T 3ramework 0lass Library

The .72T 3ramework class library is a collection of reusable types that tightly integrate

with the common language runtime. The class library is object oriented, providing

types from which your own managed code can derive functionality. This not only

makes the

.72T 3ramework types easy to use, but also reduces the time associated with learning

new features of the .72T 3ramework. In addition, third-party components can integrate

seamlessly with classes in the .72T 3ramework.

. In addition to these common tasks, the class library includes types that support

a variety of specialized development scenarios. 3or example, you can use the .72T

3ramework to develop the following types of applications and servicesF

• 0onsole applications.

• Scripted or hosted applications.

• Windows GUI applications ;Windows 3orms<.

• AS1.72T applications.

• XML Web services.

• Windows services.

0lient Application )evelopment

0lient applications are the closest to a traditional style of application in Windows-

based programming. These are the types of applications that display windows or

forms on the desktop, enabling a user to perform a task. 0lient applications include

applications such as word processors and spreadsheets, as well as custom business

applications such as data-entry tools, reporting tools, and so on. 0lient applications

usually employ windows, menus, buttons, and other GUI elements, and they likely

access local resources such as the file system and peripherals such as

printers.Another kind of client application is the traditional ActiveX control ;now

replaced by the managed Windows 3orms control< deployed over the Internet as a

Web page. it is executed natively, has access to local resources, and includes

graphical elements.
Managed 2xecution 1rocess

The managed execution process includes the following stepsF

1. ChooSinq a Complier

To obtain the benefits provided by the common language runtime, you must use one or

more language compilers that target the runtime.

2. Compilinq your code to MicroSoft Intermediate Lanquaqe (MSIL)

0ompiling translates your source code into MSIL and generates the required metadata.

3. Compilinq MSIL to native code

At execution time, a just-in-time ;4IT< compiler translates the MSIL into native code.

)uring this compilation, code must pass a verification process that examines the MSIL

and metadata to find out whether the code can be determined to be type safe.

4. Executinq your code

The common language runtime provides the infrastructure that enables execution to

take place as well as a variety of services that can be used during execution.

Assemblies &verview

Assemblies are a fundamental part of programming with the .72T 3ramework. An

assembly performs the following functionsF

• It contains code that the common language runtime executes. Microsoft

intermediate language ;MSIL< code in a portable executable ;12< file will not be

executed if it does not have an associated assembly manifest. 7ote that each

assembly can have only one entry point ;that is, DllMain, WinMain, or Main<.

• It forms a security boundary. An assembly is the unit at which permissions are

requested and granted. 3or more information about security boundaries as they apply

to assemblies, see Assembly Security 0onsiderations

• It forms a type boundary. 2very types identity includes the name of the

assembly in which it resides. A type called MyType loaded in the scope of one

assembly is not the same as a type called MyType loaded in the scope of another

assembly.
It forms a reference scope boundary. The assembly s manifest contains assembly
metadata that is used for resolving types and satisfying resource requests. It specifies
the types and resources that are exposed outside the assembly. The manifest also
enumerates other assemblies on which it depends.

4. DOT NET DATABASE CONNECTIVITY (ADO.NET)

A) &.72T uses a multilayered architecture that revolves around a few key concepts,

such as 0onnection, 0ommand, and )ataset objects. However, the A)&.72T

architecture is quite a bit different from classic A)&.

&ne of the key differences between A)& and A)&.72T is how they deal with the
challenge of different data sources. In A)&, programmers always use a generic set of
objects, no matter what the underlying data source is. 3or example, if you want to
retrieve a record from an &racle database, you use the same 0onnection class you
would use to tackle the same task with SGL Server. This isnLt the case in A)&.72T,
which uses a data provider model.

ADO.NET Data ProviderS

A data provider is a set of A)&.72T classes that allows you to access a specific
database, execute SGL commands, and retrieve data. 2ssentially, a data provider is a
bridge between your application and a data source.

The classes that make up a data provider include the followingF

• Connection: 8ou use this object to establish a connection to a data

source.

• Command: 8ou use this object to execute SGL commands and stored
procedures.

• Data Reader: This object provides fast read-only, forward-only access

to the data retrieved from a query.

• Data Adapter: This object performs two tasks. 3irst, you can use it to fill
a )ataset ;a disconnected collection of tables and relationships< with
information extracted from a data source. Second, you can use it to
apply
 chanqeS to a data Source, accordinq to the nodificationS you've nade in
a DataSet.

ADO.NET doeSn't include qeneric data provider objectS. InStead, it includeS different
data providerS Specifically deSiqned for different typeS of data SourceS. Each data
provider haS a Specific inplenentation of the Connection, Connand, DataReader and
DataAdapter claSSeS that'S optinized for a Specific RDBMS (Relational databaSe
nanaqenent SySten). For exanple, if you need to create a connection to a SQL Server
databaSe, you'll uSe a connection claSS naned SQL Connection.

One of the key underlyinq ideaS of the ADO.NET provider nodel iS that it'S extenSible. In
other wordS, developerS can create their own provider for proprietary data SourceS.
In fact, nunerouS proof-of-conceptS exanpleS are available that Show how you can
eaSily create cuSton ADO.NET providerS to wrap no relational data StoreS, Such aS
the file SySten or a directory Service. Sone third-party vendorS alSo Sell cuSton
providerS for
.NET.

The .NET Franework iS bundled with a Snall Set of four providerS:

• SQL Server Provider; ProvideS optinized acceSS to a SQL Server

databaSe(verSion 7.0 or later).

• OLED+ Provider; ProvideS acceSS to any data Source that haS an

OLEDB driver. ThiS includeS SQL Server databaSeS prior to verSion 7.0.

• Ora0le Provider; ProvideS optinized acceSS to an Oracle

databaSe(verSion 8i or later).

• OD+C Provider; ProvideS acceSS to any data Source that haS an

ODBC driver.

5. RD+MS CONCEPTS

1. DATA A+STRACTION

A najor purpoSe of a databaSe SySten iS to provide uSerS with an abStract view

of the data. ThiS SySten hideS certain detailS of how the data iS Stored and
naintained. However in order for the SySten to be uSable, data nuSt be retrieved
efficiently. The efficiency lead to the deSiqn of conplex data Structure for the
repreSentation of data in the databaSe. Certain conplexity nuSt be hidden fron the
databaSe SySten uSerS. ThiS acconpliShed by defininq Several levelS of
abStraction at which the databaSe nay be viewed.

2. CLASSIFICATION OF DATA+ASE

There are 3 typeS of databaSe approacheS qiven below,

 a. Hierar02i0al Da4a9a1e;

In this type of model data is represented in simple tree structured. The

record at the top of three is known as root, the root may have any
number of dependents. 2ach of these may have any number of low level
dependents and so on up to any number of levels. The disadvantages of
the approach are that no independent record occurrence can exist without
itLs superior.

9. Ne45or8 Da4a9a1e;

In a 7etwork database, data is represented by 7etwork structure. In

this approach record occurrence can have any number of superiors as
well as any number of immediate dependents thus allow many to
many correspondence directly than an hierarchical approach. The
main disadvantage of the 7etwork model is data representation is very
complex resulting in complexity of the )ML ;)ata Manipulation
Language<.

0. Rela4ional Da4a9a1e;

The Relational model represents data and relationships among data by

a collection of tables each of which has a number of columns with
unique names.

6. THE SQL LANGUAGE

SGL is a language for relational database. SGL is a non-procedural i.e., when we

use SGL we specify what we want to be done not how to do it.

Fea4/re1 Of SQL

1. SGL is an interactive query language.

*. SGL is a database administration language.
3. SGL is a database programming language.
>. SGL is a client/server language.
5. SGL is a distributed database language.
@. SGL is a database gateway language.

+a1i0 SQL Command1

 )ata )efinition Language commands ;))L<

)ata Manipulation Language commands

;)ML< Transaction 0ontrol Language

commands ;T0L<

-ata control 0anguage commands (-*02

PROJECT DESIGNING

DeSiqn Document

• The entire system is projected with a physical diagram which specifics the
actual storage parameters that are physically necessary for any database to
be stored on to the disk. The overall systems existential idea is derived from
this diagram.

• The relation upon the system is structure through a conceptual 2R-)iagram,

which not only specifics the existential entities but also the standard relations
through which the system exists and the cardinalities that are necessary for
the system state to continue.

• The content level )3) is provided to have an idea of the functional inputs and
outputs that are achieved through the system. The system depicts the input
and out put standards at the high level of the systems existence.
1. Data Flow DiaqramS:

)ata flows are data structures in motion, while data stores are data structures.
)ata flows are paths or Mpipe linesL, along which data structures travel, where as the
data stores are place where data structures are kept until needed.
)ata flows are data structures in motion, while data stores are data structures at
rest. Hence it is possible that the data flow and the data store would be made up of
the same data structure.
)ata flow diagrams is a very handy tool for the system analyst because it gives
the analyst the overall picture of the system, it is a diagrammatic approach.
A )3) is a pictorial representation of the path which data takes 3rom its initial
interaction with the existing system until it completes any interaction. The diagram will
describe the logical data flows dealing the movements of any physical items. The )3)
also gives the insight into the data that is used in the system i.e., who actually uses it
is temporarily stored.
A )3) does not show a sequence of steps. A )3) only shows what the
different process in a system is and what data flows between them.

The following are some )3) symbols used in the project

2xternal entities

Process3 A transaction of information that resides within the bounds of the system to be mod
)ATA3L&WS

-ATA/TO&)3A repository of data that is to be stored for use by on

$ueue or as a relational database.

RULES FOR DFD:

• 3ix the scope of the system by means of context diagrams.

• &rganize the )3) so that the main sequence of the actions reads
left to right and top to bottom.
• Identify all inputs and outputs.
• Identify and label each process internal to the system with
rounded circles.
• A process is required for all the data transformation and
transfers. Therefore, never connect a data store to a data source
or the destinations or another data store with just a data flow
arrow.
• )o not indicate hardware and ignore control information.
• Make sure the names of the processes accurately convey
everything the process is done.
• There must not be unnamed process.
• Indicate external sources and destinations of the data, with
squares.
• 7umber each occurrence of repeated external entities.
• Identify all data flows for each process step, except simple
Record retrievals.
 • Label data flow on each arrow.
• USe detailS flow on each arrow.
• USe the detailS flow arrow to indicate data novenentS.
• There can't be unnaned data flow.
• A data flow can't connect two external entitieS.
LEVELS OF DFD;

The conplexity of the buSineSS SySten neanS that it iS a reSponSible to repreSent

the operationS of any SySten of Sinqle data flow diaqran. At the top level, an Overview
of the different SyStenS in an orqanization iS Shown by the way of context analySiS
diaqran. When exploded into DFD
They are repreSented by:
• LEVEL-0 : SYSTEM INPUT/OUTPUT
• LEVEL-1:SUBSYSTEM LEVEL DATAFLOW FUNCTIONAL
• LEVEL-2 : FILE LEVEL DETAIL DATA FLOW.
The input and output data Shown Should be conSiStent fron one level to the next.

LEVEL-=; SYSTEM INPUT<OUTPUT LEVEL

A level-0 DFD deScribeS the SySten-wide boundarieS, dealinq inputS to and
outputS fron the SySten and najor proceSSeS. ThiS diaqran iS Sinilar to the conbined
uSer-level context diaqran.

LEVEL-1; SU+SYSTEM LEVEL DATA FLOW

A level-1 DFD deScribeS the next level of detailS within the SySten, detailinq
the data flowS between SubSyStenS, which nakeup the whole.

LEVEL-2; FILE LEVEL DETAIL DATA FLOW

All the projectS are feaSible qiven unlinited reSourceS and infinite tine. It iS
both neceSSary and prudent to evaluate the feaSibility of the project at the earlieSt
poSSible tine. FeaSibility and the riSk analySiS are pertained in nany wayS. If project
riSk iS qreat.
FIRST LEVEL DTAFLOW DIAGRAM

Repor41 on 42e /1er

Informa4ion

Admini14ra4or
Informa4ion
 ReportS on the
movie information

ReportS on the Theatre

Information

Movie Manaqement
World

ReportS uSer Profile and

Available seats

User information Module

2nd Level DFDS

Admin MaSter Admin MaSter Admin MaSter

DInFSDertFor Admin Check for

Admin Employee Check for
User Account Verify
Verify Verify
Data
Data 3.1 Data
3.1
3.1

Check
for Scheme S

Insert

Admin MaSter
 User 4aster Page

User 4aster

DFD For User Account

*hec7 for the User

+erify +erify
Insert User Account Profile
-ata -ata

2.1 2.2

*hec7 for the

User Account

-etails

Insert +erify

-ata

2.3

User 4aster
 8ome 4aster

8ome 4aster

/earch for the

+erify +erify
Insert user
Available seats
-ata -ata

2.1 2.2
DFD For Bookinq

*hec7 for
the Admin Address

Insert +erify

-ata

2.3
Admin 4aster
2. Unified Modelinq Lanquaqe DiaqramS(UML):

• The unified modeling language allows the software engineer to express an

analysis model using the modeling notation that is governed by a set of
syntactic semantic and pragmatic rules.

• A UML system is represented using five different views that describe the
system from distinctly different perspective. 2ach view is defined by a set of
diagram, which is as follows.

USer Model View

i. This view represents the system from the users perspective.

ii. The analysis representation describes a usage scenario from the end-users
perspective.
Structural model view

◆ In this model the data and functionality are arrived from inside the system.

◆ This model view models the static structures.

Behavioral Model View

 ◆ It represents the dynamic of behavioral as parts of the system, depicting the
interactions of collection between various structural elements described in
the user model and structural model view.

Implementation Model View

◆ In this the structural and behavioral as parts of the system are represented
as they are to be built.

Environmental Model View

In this the structural and behavioral aspects of the environment in which the system is
to be implemented are represented.

UML is specifically constructed through two different domains they are

◆ UML Analysis modeling, which focuses on the user

model and structural model views of the system.

◆ UML design modeling, which focuses on the behavioral

modeling, implementation modeling and environmental model views.

1) Use (ase Diagrams

Admin:

The Administrator is the user of the system. He is the responsible person

to define the 2mployee details User Account )etails.
 Login

Add movie

 Add Theatre

Admin

Assign
4ovie

Movie Details

Theatre
-eatails
USer:

He is responsible for the registration of the User Account, The user can
0hange password, view 7o seats Available and booking the tickets.

Login

profile’ information


USer
View theatre
/movies

Book tickets
 2) Elaborated DiaqramS

++Uses,, ++Uses,,
++Uses,,
Login Authenticate login name
Authenticate Enable privilege$
pass-or$ access

++Uses,, ++Uses,,
)nter the re$uired data along
++Uses,,
Add movie -etails with standards
(heck the /tore
authentic
of
information

++Uses,,


A$$ Theatre Enter the required data ++Uses,, ++Uses,,
(heck the authenticity of
as per the
information /tore
standards

SyStem
AdminiStrator

++Uses,, )nter &e$uire data ++Uses,,

As per the ++Uses,,
Assign movie (heck the authenticity of
to theatre /tandards information

/tore
 ++Uses,, ++Uses,,
++Uses,,
Login Authenticate login name
Authenticate Enable privilege$
pass-or$ access

++Uses,, ++Uses,,
++Uses,,
Raise request for Display
pass-or$ changing
Enter the Authori/e the
require$
parameters parameter
++Uses,,
++Uses,,
++Uses,,


0ook the Tickets Enter the required
Information *ollect Available
/eats
Boo7 seat no
User
AdminiStrator Loqin Sequence

Login Administrator Administrator Admin Master

screen login master login master

Enter log
name Validate
Validate
Log name ()
Password () Check for
required
privileges Creation of
() Users User registration,
registrationC,hange password
USer Loqin Sequence

Login User login master User login master User Master

screen

Enter log
name Vali$ate
Vali$ate
Log name ()
Pass-or$ () (heck for
require$
privileges
(reation
() Profile3 User
profilr33
A$$ User A3bcocookuinntg
tickets
Vie- user Status
3. ENTITY-RELATIONSHIP DiaqramS

E-R (Entity-RelationShip) Diaqran iS uSed to repreSentS the relationShip between entitieS in

the table.
The SynbolS uSed in E-R diaqranS are:
SYMBOL PURPOSE

RepreSentS Entity SetS.

RepreSent attributeS.

RepreSent RelationShip SetS.

Line repreSentS flow

Structured analySiS iS a Set of toolS and techniqueS that the analySt.
To develop a new kind of a SySten:
The traditional approach focuSeS on the coSt benefit and feaSibility analySiS,
Project nanaqenent, and hardware and Software Selection an perSonal conSiderationS.
 Admin
Password Address
User Name )mailI- gender

Age

User phno

New USer DetailS

USer Name

Add movie,
Theatre3tickets
Seat Nos
Theatre
name

No of tickets
4ovie
Name Show time
Tickets Cost User name
4. DATABASE DIAGRAM

Home Paqe
Admin Home
Add Movie Page
View Movie Paqe
Add Theatre
Viw Theatre
Update Theatre
ASSiqn Movie
View ASSiqninq
USer Home
Chanqe PaSSword
Theatre Bookinq
Book SeatS
After Bookinq
Cancel Ticket
USer ReqiStration
A9o/4 /1
Contact US
PROJECT TESTING
Software TeStinq StrateqieS

Testing is a set of activities that can be planned in advanced and conducted systematically. A
strategy for software testing must accommodation low-level tests that are necessary to verify that a
small source code segment has been correctly implemented as well as high-level tests that validate
major system functions against customer requirements

There are three types of testing strategies

1. Unit test
*. Integration test
3. 1erformance test

Unit TeStinq:

Unit testing focuses verification efforts on the smallest unit of software design module. The unit
test is always white box oriented. The tests that occur as part of unit testing are testing the module
interface, examining the local data structures, testing the boundary conditions, execution all the
independent paths and testing error-handling paths.

Inteqration TeStinq:

Integration testing is a systematic technique or construction the program structure while at the
same time conducting tests to uncover errors associated with interfacing. Scope of testing
summarizes the specific functional, performance, and internal design characteristics that are to be
tested. It employs top-down testing and bottom-up testing methods for this case.

Performance TeStinq:

Timing for both read and update transactions should be gathered to determine whether system
functions are being performed in an acceptable timeframe.
 ConcluSion

The entire project has been developed and deployed as per the requirements stated by the user, it is found to

be bug free as per the testing standards that is implemented. Any specification-untraced errors will be

concentrated in the coming versions, which are planned to be developed in near future. The system at present

does not take care off the money payment methods, as the consolidated constructs need SSL standards and

are critically to be initiated in the first face, the application of the credit card transactions is applied as a

developmental phase in the coming days. The system needs more elaborative technicality for its inception and

evolution.

Future Enhancement Of the Project

BIBILIOGRAPHY

1. ASP.NET (BIBLE)
-MRUDULA PARIHAR.

2. MaSterinq SQL Server 2000 by

-Gunderloy,Jorden BPB PublicationS

3. Beqinninq SQL Server 2000 by

-Thereon WilliS wrox publicationS

.
4. SOFTWARE ENGINEERING (THEORETICAL APPROACH)
-ROGER S.PRESSMEN, T. Mc. GH.

5. C#.NET
-PROFESSIONAL VISUAL BASIC.NET
-WROX PUBLICATIONS.

6. MSDN LIBRARY.NET
-WWW.MICROSOFT.COM