Embed Size (px)
Citation preview
AN ONLINE CINEMA BOOKING SYSTEM
A Report of Project 2
Submitted by
CHHAVI GAUR
17SCSE1044135
1713111001 in partial fulfilment for the award of the degree of
BACHELOR OF COMPUTER
APLLICATION
SCHOOL OF COMPUTING SCIENCE AND ENGINEERING
Under the Supervision of
MS. SAUMYA CHATURVEDI
ASSISTANT PROFESSOR
SCHOOL OF COMPUTING AND SCIENCE AND ENGINEERING
BONAFIDE CERTIFICATE
Certified that this project report “AN ONLINE CINEMA BOOKING/TICKET PURCHASING SYSTEM.” is the bonafide work of “CHHAVI GAUR (1713111001)” who carried out the project work under my supervision.
SIGNATURE OF HEAD SIGNATURE OF SUPERVISIOR
Dr. MUNISH SHABARWAL MS. SAUMYA CHATURVEDI
Professor & Dean, ASSISTANT PROFESSOR,
School of Computing Science & School of Computing Science
Engineering & Engineering
ACKNOWLEDGEMENT I take this occasion to thank God, almighty for blessing me with his grace and taking our
endeavour to a successful Culmination. I extend my sincere and heartfelt thanks to my
esteemed guide, Ms saumya Chaturvedi, for providing me with the right guidance and advice
at the crucial junctures and for showing me the right way. I extend my sincere thanks to my
respected Head of the division DR. Thirunavukkarasu k., for allowing me to
use the facilities available. I would like to thank the other faculty members also at this
occasion. Last but not the least, I would like to thank my friends and family for the support
and encouragement they have given me during the course of this work. I also thanks to my
senior Saurabh Sharma.
ABSTRACT Welcome to newly designed website cinema ticket booking is a faster, cleaner and a tad more
personal website, specially designed to make your booking experience better. Log on,
navigate and find out for yourselves and if time permits leave your valuable feedback.
Customers may view the contents of any movie show at any time and may book any movie
ticket as needed. The program automatically calculates the subtotal and grand total. When a
visitor decides to finally book the ticket, the order information including the buyer&39; s
name, address and billing instruction is stored in the database securely and payment has been
made. The combo booking is also provided at the time of booking the ticket and there’s a
wonderful facility of delivering the combos at your seat when you are watching the movie.
You need to register a new user whenever you have first visited or site then for future it will
be stored in our database permanently and you can book you movie ticket at any time you
want with this username and password.
TABLE OF CONTENTS
CHAPTER NO. TITLE PAGE NO.
ABSTRACT iv
LIST OF FIGURES vi
1. INTRODUCTION 1
1.1 PURPOSE OF SYSTEM
1.2 PROBLEM ANALYSIS
1.3 PRELIMINARY STUDY
2. SYSTEM ANALYSIS 3
2.1 EXISTING SYSTEM
2.2 PROPOSED SYSTEM
2.3 NEED FOR COMPUTERIZATION
3. MODULES 5
3.1 ADMINISTRATOR MODULE
3.2 USER MODULE
3.3 BOOKING MODULE
3.4 THEATRE CREATION
4. PROJECT DESCRIPTION 6
5. SYSTEM DESIGN 7
5.1 DATA FLOW DIAGRAM
5.5 SEQUENCE DIAGRAM
5.3 CLASS DIAGRAM
5.4 ER DIAGRAM
5.5 USE CASE DIAGRAM
6. DEVELOPMENT ENVIROMENT 14
6.1 HARDWARE REQIUREMENTS
6.2 SOFTWARE REQUIREMENTS
6.3 SOFTWARE DESCRIPTION
6.4 BACKEND DESCRIPTION
7. SYSTEM TESTING 22
7.1 UNIT TESTING
7.2 INTEGRATION TESTING
7.3 SYSTEM TESTING
7.4 ACCEPTANCE TESTING
8. SYSTEM IMPLEMENTATION 28
8.1 USER INTERFACES
8.2 CODING
8.3 RESULT
9. CONCLUSION 46
10. REFERENCES 47
LIST OF FIGURES
FIGURE NO. FIGURE NAME
FIGURE 1 DFD LEVEL-0
FIGURE 2 DFD LEVEL-1
FIGURE 3 DFD LEVEL-2
FIGURE 4 ENTITY-RELATIONSHIP DIAGRAM
FIGURE 5 CLASS DIAGRAM
FIGURE 6 USE CASE CUSTOMER DIAGRAM
FIGURE 7 USE CASE ADMIN DIAGRAM
FIGURE 8 SYSTEM ARCHITECTURE DIAGRAM
FIGURE 9 DATABASE TABLE OF USER
FIGURE 10 DATABASE TABLE OF ASSIGN MOVIE
FIGURE 11 DATABASE TABLE OF BOOKING
FIGURE 12 DATABASE TABLE OF MOVIE
FIGURE 13 DATABASE TABLE OF THEATRE
FIGURE 14 DATABASE TABLE OF USER
FIGURE 15 HOME APGE
FIGURE 16 CONTACT US PAGE
FIGURE 17 MOVIE CHECKOUT PAGE
FIGURE 18 USER LOGIN PAGE
FIGURE 19 USER REGISTRATION PAGE
FIGURE 20 MOVIE ADDING PAGE
FIGURE 21 THEATRE ADDING PAGE
FIGURE 22 MOVIE DELETING PAGE
FIGURE 23 THEATRE SELECTING PAGE
FIGURE 24 MOVIE AND THEATRE SEARCHING PAGE
FIGURE 25 MOVIE SEARCHING PAGE
FIGURE 26 MOVIE BOOKING PAGE
FIGURE 27 MOVIE SELECTING AND BOOKING PAGE
FIGURE 28 SELECTING THEATRE PAGE
FIGURE 29 RESERVATION ID AND OTHER DETAIL
FIGURE 30 ENTER USER DEATIL PAGE
FIGURE 31 RESET PASSWORD
FIGURE 32 PASSWORD SUCCESSFUL CHANGE
CHAPTER I
INTRODUCTION This project is aimed to provide the customers facility to book tickets for cinema halls online, through which they can book tickets anytime, anywhere. E-ticket system is basically made for providing the customer an anytime and anywhere service for booking the seat in the cinema hall and to gather information about the movies online. The user can easily be able to know about the movies released and then make the choice. In this project, we will illustrate our system by providing DFD (Data Flow Diagrams) on some functions. And we will also provide some process description and data dictionary. Admin can use the system to insert and delete data (e.g. film description, time table) which will update the webpage (webpage are dynamic page, changing according to the data in database). Also, admin can check the statistic information from the system.
1.1. Purpose of the System
The main purpose of our online ticket booking system is to provide another way for the customer to buy cinema ticket. It is an automatic system. After inserting the data to database, staff needs not to do with the order receive through the system. In fact, there is similar system on the internet, but there is no refund method found in the existing system. This system is basically aimed to provide the customer the complete information of the movie, according to which the customer can book the tickets and the refund facility provides more flexibility to the system.
The goals of our system are:
1. To provide a anytime anyplace service for the customer2. To minimize the number of staff at the ticket box3. To promote the film on the internet4. To increase the profit5. To obtain statistic information from the booking record.
1.2. Problem Analysis
The basic aim of problem analysis is to obtain clear understanding of the needs of the clients and the users, what exactly is desired from the software, and what the constraints on the solution are. Analysis leads to the actual specification. The problem analysis approach is defined by means of the following approaches. There are three basic approaches to problem analysis.
informal Approach.
Conceptual modelling-based Approach Prototyping Approach.
In this project we use Conceptual modelling-based Approach to understand the exact requirement of the organization.
1.3. Preliminary Investigation and Study
The preliminary investigation starts as soon as someone either a user or a member of a particular department recognizes a problem or initiates a request, to modify the current computerized system, or to computerize the current manual system. An important outcome of the preliminary investigation is determining whether the system is feasible or not. The evolutional study consists of the following parameters to check the non-functional requirements. They are:
Reliability: The system will consistently perform its intended function. For e.g. The important information must be validated.
Efficiency: Unnecessary data will not be transmitted on the network and database server will be properly connected.
Reusability: The system can be reused in any organization or site of the same group, by defining the organization master definition under software license agreement.
Integrity: Only System Administrator has rights to access the database, not every user can access all the information. Each user will be having rights to access the modules.
CHAPTER-II
SYSTEM ANALYSIS
2.1. EXISTING SYSTEM
NOT USER FRIENDLY
The existing system is not user friendly because the ticket buying process is very slow and data is not maintained efficiently.
MANUAL CONTROL
All calculations to generate report is done manually so there is greater chance of errors.
TIME CONSUMING
Every work is done manually so we cannot given the ticket in the middle of the session or as per the requirement because it is very time consuming.
Limitations in Existing System:
1. Difficult to buy the tickets2. Not User Friendly3. Manual control4. Lots of paperwork5. Time consuming6. Low level security7. Low level accuracy and efficiency
2.2. PROPOSED SYSTEM
Our proposed system is an automated format of the above Slated paper based work. Here the entire process is computerized thus by reducing the man power and the entire manual work. This system provides a computerization method for the organization can easily handle their particular details. It’s very easy to maintain user details. And easy to search the movie for the particular theatre and book the tickets. This system consuming the less amount of timing, so avoiding the peoples standing on the long queue. this system minimizes the paperwork load.
Advantages
1. User Friendly accessing.2. Reports are easily generated.3. Very less paper work.4. Computer operator control.
5. Time consumption is low6. This system provides High level security.7. Efficiency level is higher than the existing system.
2.3. NEED FOR COMPUTERIZATION
To overcome the drawbacks in the existing system we need computerization. This process is computerized with ASP.NET. Every day there is a greater number of processes involved in all over the Organization. It is tedious to verify each one. This lead to lot of time and resources being wasted. Hence the organization is dedicated to computerize the system. This system is used to inform the problems from the production department or any other departments, the clients can easily get knowledge of the problem by consulting with other clients. This is very useful when it gets computerized. Data reliability and maintainability is very easy. Better information accuracy and user can manipulate the data quickly. We can protect the data from the unauthorized user access. The management can make it way more enhanced manner than the past when it carried out by a well computerized process.
CHAPTER-III
MODULES
It is based on an 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 movie available, list of theatres.
3.1. Administrator module
3.2. User module
3.3. Ticket booking module
3.4. Theatre creation
MODULE DESCRIPTION
3.1. ADMINISTRATOR MODULE
The administrator module that allows creating the user login and it maintain the user details, movie details, theatre details, and checks the no of seats available.
3.2. USER MODULE
The user can first registration in enter the personal details, and user login and if you want to update personal details and you and update. The user collects all information like movies details, theatre details.
3.3. BOOKING MODULE
Booking module allows to user check the movies and search for the particular theatre. And this module is used to check the availability of tickets. The tickets available in theatre after that the users will book the tickets online.
3.4. THEATRE CREATION
Theatre creation module allows to user view the theatre details like
CHAPTER-IV
PROJECT DESCRIPTION
The project “Online Cinema Ticket Booking System” is fully described with the following modules such as: Administrator module, User module, Ticket booking module and Theatre creation. All these modules work in the system and produces different types of results such as the administrator module that allows creating the user login and it maintain the user details, movie details, theatre details, and checks the no of seats available.
The user can first registration in enter the personal details, and user login and if you want to update personal details and you and update. The user collects all information like movies details, theatre details. Booking module allows to user check the movies and search for the particular theatre. And this module is used to check the availability of tickets. The tickets available in theatre after that the users will book the tickets online. Theatre creation module allows to user view the theatre details like Ac, non-Ac and available tickets, which movie presently running on this theatre. Any user they can access the system through website easily.
CHAPTER V
Implementation or architecture diagrams
5.1 DATAFLOW DIAGRAM
A data flow diagram (DFD) is a graphical representation of the " flow" of data through an information system.
LEVEL-0
LEVEL-0
Administrator Information
Cinema Ticket
Booking System
Management
Reports on the movie information
Reports on the Theatre
Information
User information
Reports user Profile and
Available seats
FIG 1: DFD LEVEL -0
LEVEL-1
FIG 2: DFD LEVEL-1
LEVEL -2
FIG 3: DFD LEVEL-2
5.2 ER diagram An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database. A type of diagram used in data modelling for relational data bases.
FIG 4: ENTITY-RELATIONSHIP DIAGRAM
5.3 Class diagram A class diagram is an illustration of the relationships and source code dependencies among classes in the Unified Modelling Language (UML). In this context, a class defines the methods and variables in an object, which is a specific entity in a program or the unit of code representing that entity.
FIG 5: CLASS DIAGRAM
5.4 Use Case diagram A use case diagram is a graphic depiction of the interactions among the elements of a system. A use case is a methodology used in system analysis to identify, clarify, and organize system requirements.
FIG 6: USE CASE CUSTOMER DIAGRAM
FIG 7: USE CASE ADMINISTRATOR DIAGRAM
5.5 System Architecture
FIG 8: SYSTEM ARCHITECTURE DIAGRAM
CHAPTER-VI
DEVELOPMENT ENVIRONMENT
6.1. Hardware Requirements:System : Pentium IV 2.4 GHz.
Hard Disk : 40 GB.
Ram : 512 Mb.
6.2. Software Requirements:Operating system : Windows 7 Ultimate (32-bit)
Coding Language : ASP.NET
Data Base : MS-ACCESS
6.3. SOFTWARE DESCRIPTION
MICROSOFT.NET FRAMEWORK
Features OF .Net
Microsoft .NET is a set of Microsoft software technologies for rapidly building and
integrating XML Web services, Microsoft Windows-based applications, and Web solutions.
The .NET Framework is a language-neutral platform for writing programs that can easily and
securely interoperate. There’s no language barrier with .NET: there are numerous languages
available to the developer including Managed C++, C#, Visual Basic and Java Script.
The .NET framework provides the foundation for components to interact seamlessly, whether
locally or remotely on different platforms. It standardizes common data types and
communications protocols so that components created in different languages can easily
interoperate.
“.NET” is also the collective name given to various software components built upon
the .NET platform. These will be both products (Visual Studio.NET and Windows.NET
Server, for instance) and services (like Passport, .NET My Services, and so on).
THE .NET FRAMEWORK
The .NET Framework has two main parts:
1. The Common Language Runtime (CLR).
2. A hierarchical set of class libraries.
The CLR is described as the “execution engine” of .NET. It provides the environment within
which programs run. The most important features are
Conversion from a low-level assembler-style language, called Intermediate
Language (IL), into code native to the platform being executed on.
Memory management, notably including garbage collection.
Checking and enforcing security restrictions on the running code.
Loading and executing programs, with version control and other such features.
The following features of the .NET framework are also worth description:
Managed Code
The code that targets.NET, and which contains certain extra Information “metadata”
to describe itself. Whilst both managed and unmanaged code can run in the runtime, only
managed code contains the information that allows the CLR to guarantee, for instance, safe
execution and interoperability.
Managed Data
With Managed Code comes Managed Data. CLR provides memory allocation
and Deal location facilities, and garbage collection. Some .NET languages use Managed Data
by default, such as C#, Visual Basic.NET and JScript.NET, whereas others, namely C++, do
not. Targeting CLR can, depending on the language you’re using, impose certain constraints
on the features available. As with managed and unmanaged code, one can have both managed
and unmanaged data in .NET applications - data that doesn’t get garbage collected but instead
is looked after by unmanaged code.
Common Type System
The CLR uses something called the Common Type System (CTS) to strictly enforce
type-safety. This ensures that all classes are compatible with each other, by describing types
in a common way. CTS define how types work within the runtime, which enables types in
one language to interoperate with types in another language, including cross-language
exception handling. As well as ensuring that types are only used in appropriate ways, the
runtime also ensures that code doesn’t attempt to access memory that hasn’t been allocated to
it.
Common Language Specification
The CLR provides built-in support for language interoperability. To ensure that you
can develop managed code that can be fully used by developers using any programming
language, a set of language features and rules for using them called the Common Language
Specification (CLS) has been defined. Components that follow these rules and expose only
CLS features are considered CLS-compliant.
THE CLASS LIBRARY
.NET provides a single-rooted hierarchy of classes, containing over 7000
types. The root of the namespace is called System; this contains basic types like Byte,
Double, Boolean, and String, as well as Object. All objects derive from System. Object. As
well as objects, there are value types. Value types can be allocated on the stack, which can
provide useful flexibility. There are also efficient means of converting value types to object
types if and when necessary.
The set of classes is pretty comprehensive, providing collections, file, screen,
and network I/O, threading, and so on, as well as XML and database connectivity.
The class library is subdivided into a number of sets (or namespaces), each
providing distinct areas of functionality, with dependencies between the namespaces kept to a
minimum.
LANGUAGES SUPPORTED BY .NET
The multi-language capability of the .NET Framework and Visual
Studio .NET enables developers to use their existing programming skills to build all types of
applications and XML Web services. The .NET framework supports new versions of
Microsoft’s old favorites Visual Basic and C++ (as VB.NET and Managed C++), but there
are also a number of new additions to the family.
Visual Basic .NET has been updated to include many new and improved
language features that make it a powerful object-oriented programming language. These
features include inheritance, interfaces, and overloading, among others. Visual Basic also
now supports structured exception handling, custom attributes and also supports multi-
threading.
Visual Basic .NET is also CLS compliant, which means that any CLS-
compliant language can use the classes, objects, and components you create in Visual
Basic .NET.
Managed Extensions for C++ and attributed programming are just some of the
enhancements made to the C++ language. Managed Extensions simplify the task of migrating
existing C++ applications to the new .NET Framework. C# is Microsoft’s new language. It’s
a C-style language that is essentially “C++ for Rapid Application Development”. Unlike
other languages, its specification is just the grammar of the language. It has no standard
library of its own, and instead has been designed with the intention of using the .NET
libraries as its own. Microsoft Visual J# .NET provides the easiest transition for Java-
language developers into the world of XML Web Services and dramatically improves the
interoperability of Java-language programs with existing software written in a variety of other
programming languages.
Active State has created Visual Perl and Visual Python, which enable .NET-
aware applications to be built in either Perl or Python. Both products can be integrated into
the Visual Studio .NET environment. Visual Perl includes support for Active State’s Perl Dev
Kit.
Other languages for which .NET compilers are available include
FORTRAN
COBOL
Eiffel
ASP.NET
XML WEB SERVICES
Windows Forms
Base Class Libraries
Common Language Runtime
Operating System
Figure 5.2.1 .NET Framework
C#.NET is also compliant with CLS (Common Language Specification) and supports
structured exception handling. CLS is set of rules and constructs that are supported by the
CLR (Common Language Runtime). CLR is the runtime environment provided by
the .NET Framework; it manages the execution of the code and also makes the
development process easier by providing services C#.NET is a CLS-compliant language.
Any objects, classes, or components that created in C#.NET can be used in any other CLS-
compliant language. In addition, we can use objects, classes, and components created in
other CLS-compliant languages in C#.NET .The use of CLS ensures complete
interoperability among applications, regardless of the languages used to create the
application.
CONSTRUCTORS AND DESTRUCTORS:
Constructors are used to initialize objects, whereas destructors are used to destroy
them. In other words, destructors are used to release the resources allocated to the object.
In C#.NET the sub finalize procedure is available. The sub finalize procedure is used to
complete the tasks that must be performed when an object is destroyed. The sub finalize
procedure is called automatically when an object is destroyed. In addition, the sub finalize
procedure can be called only from the class it belongs to or from derived classes.
GARBAGE COLLECTION
Garbage Collection is another new feature in C#.NET. The .NET Framework
monitors allocated resources, such as objects and variables. In addition, the .NET
Framework automatically releases memory for reuse by destroying objects that are no
longer in use. In C#.NET, the garbage collector checks for the objects that are not
currently in use by applications. When the garbage collector comes across an object that is
marked for garbage collection, it releases the memory occupied by the object.
OVERLOADING
Overloading is another feature in C#. Overloading enables us to define multiple
procedures with the same name, where each procedure has a different set of arguments.
Besides using overloading for procedures, we can use it for constructors and properties in
a class.
MULTITHREADING:
C#.NET also supports multithreading. An application that supports multithreading can
handle multiple tasks simultaneously, we can use multithreading to decrease the time
taken by an application to respond to user interaction.
STRUCTURED EXCEPTION HANDLING
C#.NET supports structured handling, which enables us to detect and remove
errors at runtime. In C#.NET, we need to use Try…Catch…Finally statements to create
exception handlers. Using Try…Catch…Finally statements, we can create robust and
effective exception handlers to improve the performance of our application.
THE .NET FRAMEWORK
The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet.
OBJECTIVES OF .NET FRAMEWORK
1. To provide a consistent object-oriented programming environment whether object codes
is stored and executed locally on Internet-distributed, or executed remotely.
2. To provide a code-execution environment to minimizes software deployment and
guarantees safe execution of code.
3. Eliminates the performance problems.
There are different types of application, such as Windows-based applications and Web-
based applications.
6.4. BACKEND DESCRIPTION
MICROSOFT ACCESS
Access offers a variety of features for different database needs. It can be used to
develop five general types of applications:
Personal applications
Applications used to run a small business
Department applications
Corporations- wide applications
Front-end for enterprise-wide client/server applications
Backend tables can be linked to the front-end applications. The process of linking to
backend tables is almost identical to that of linking to tables in other access databases. After
the back end tables have been linked to the front-end applications, they can be treated like
any other linked tables. Access utilizes ODBC to communicate with the back end tables. Our
application sends an Access SQL statement to the Access Jet Engine.
Jet translates the Access SQL statement into ODBC SQL. The ODBC SQL statement
is then sent to the ODBC Manager. The ODBC manger locates the correct ODBC driver and
passes it the ODBC SQL statement. The ODBC driver, supplied by the back end vendor,
translates the ODBC SQL statement into the back-end’s specific dialect. The back end
specific is sent to the SQL server and to the appropriate database.
DATABASE
A database is an organized list of data that can be queried to find information quickly
and easily based and chosen reference point, such as a last name or security number. In
database terminology, the columns are called fields and the rows are called records. This kind
organization in a database is called a data table, or just a table.
ACCESS
Access is a RDBMS that you can store and manipulate large amount of information.
A relational database is a database, which consist of tables of related information that are
linked together based on key field. <S Access supports GUI features and entire programming
language, VBA (Visual Basic or Application) that can be used to develop richer and more
developed application. MS Access database can act as a backend database for VB. While
using VB as a front-end tool, MS Access supports the user with its powerful DBMS
functions.
MAIN ELEMENTS OF ACCESS
ACCESS is an object-oriented program. Objects are modules, which provide
information and program, which the user can directly apply to create application.
Access has the following windows
1. Data base Windows 2. Tables
3. Queries 4. Forms
5. Reports 6. Macros
7. Modules 8. Relationship
DATABASE WINDOWS
In Access all, objects a dataase are stored in a single file and the file name has an
MDB extension.
Tables
Tables are the primary building block of ACCESS database. All data’s are stored in
tables.
Queries
A query is a question that you ask of the data that I stored in the tables of your
database
NEW FEATURES IN MS ACCESS
MS Accesss offers many new and improved features to help create powerful databse
applications.
New objects, properties , methods and others language elements
Accessing the Internet or an intranet from your applicaions
Creating custom objects with class modules.
Cjstomizing menus and tool bars in your applications
Removing source code from uyour applications.
Working with version 3.5 of the micro-soft ject database engine.
Replicating only a specified part of a database.
Using new featurs in the module window
Using the object browser as a reference for objects and their numbers.
CHAPTER-VII
SYSTEM TESTING
A “Program unit” stands for a routine or a collection of routines implemented by an
individual programmer. It might even be a stand-alone program or a functional unit a larger
program.
7.1. UNIT TESTING:
Unit testing is performed prior to integration of the unit into a larger system. It is like
Coding and debugging -> unit testing -> integration testing. A program unit must be tested
for Functional tests, Performance tests, Stress tests and Structure tests. Functional tests refer
to executing the code with standard inputs, for which the results will occur within the
expected boundaries. Performance test determines the execution time spent in various parts
of the unit, response time, device utilization and throughput. Performance testing will help
the tuning of the system.
Stress tests drive the system to its limits. They are designed to intentionally break the
unit. Structure tests verify logical execution along different execution paths. Functional,
performance and stress tests are collectively known as “Black box testing”. Structure testing
is referred to as “White box” or “glass box” testing. Program errors can be classified as
missing path errors, computational errors and domain errors.
Even if it looks like all possible execution paths have been tested, there might still
exist some more paths. A missing path error occurs, when a branching statement and the
associated computations are accidentally omitted. Missing paths can be detected only by
functional specifications. A domain error occurs when a program traverses the wrong path
because of an incorrect predicate in a branching statement. When a test case fails to detect a
computational error there is said to be a coincidental error.
Debugging:
Debugging is eliminating the cause of known errors. Commonly used debugging
techniques are induction, deduction and backtracking. Debugging by induction involves the
following steps:
1. Collect all the information about test details and test results
2. Look for patterns
3. Form one or more hypotheses and rank /classify them.
4. Prove/disprove hypotheses. Re examine
5. Implement appropriate corrections
6. Verify the corrections. Re run the system and test again until satisfactory.
Debugging by deduction involves the following steps:
1. List possible causes for observed failure
2. Use the available information to eliminate various hypotheses
3. Prove/disprove the remaining hypotheses
4. Determine the appropriate corrections
5. Carry out the corrections and verify
Debugging by backtracking involves working backward in the source code from Point where
the error was observed. Run additional test cases and collect more information.
7.2. INTEGRATION TESTING:
Integration testing strategies include bottom-up (traditional), top-down and sandwich
strategies. Bottom-up integration consists of unit testing, followed by sub system testing,
followed by testing entire system. Unit testing tries to discover errors in modules. Modules
are tested independently in an artificial environment known as a “test harness”. Test
harnesses provide data environments and calling sequences for the routines and subsystem
that are being tested in isolation.
Disadvantages of bottom-up testing include that harness preparation, which can
sometimes take almost 50% or more of the coding and debugging effort for a smaller product.
After testing all the modules independently and in isolation, they are linked and executed in
one single integration and in isolation; they are linked and executed in one single integration
run. This known as “Big bang” approach to integration testing. Isolating sources of errors is
difficult in “big bang “approach.
Top-down integration starts with the main routine and one or two immediately next lower
level routines. After a thorough checking the top level becomes a test harness to its
immediate subordinate routines. Top-down integration offers the following advantages.
1. System integration is distributed throughout the implementation phase. Modules
are integrated as they are developed.
2. Top-level interfaces are first test
3. Top-level routines provide a natural test harness for lower-level routines.
4. Errors are localized to the new modules and interfaces that are being added.
Though top-down integrations seem to offer better advantages, it may not be
applicable in certain situations. Sometimes it may be necessary to test certain critical
low-level modules first. In such situations, a sandwich strategy is preferable.
Sandwich integration is mostly top-down, but bottom-up techniques are used on some
modules and sub systems. This mixed approach retains the advantages of both
strategies.
5. System integration is distributed throughout the implementation phase. Modules
are integrated as they are developed.
6. Top-level interfaces are first test
7. Top-level routines provide a natural test harness for lower-level routines.
8. Errors are localized to the new modules and interfaces that are being added.
Though top-down integrations seem to offer better advantages, it may not be
applicable in certain situations. Sometimes it may be necessary to test certain critical low-
level modules first. In such situations, a sandwich strategy is preferable. Sandwich
integration is mostly top-down, but bottom-up techniques are used on some modules and sub
systems. This mixed approach retains the advantages of both strategies.
7.3. SYSTEM TESTING:
Software testing is an important element of software quality assurance and represents
the ultimate review of specification design and coding. The user tests the developed system
and changes are made according the needs. The testing phase involves testing of developed
system using various kinds of data. An elaborated test data is prepared and system using the
data. Whole testing is noted and corrections are made.
TESTING OBJECTIVES:
Testing is a process of executing a program with the intent of finding on errors.
A good test is on that has a high probability of finding an undiscovered errors.
Testing is vital to the success of the system. System testing is the state of implementation,
which ensures that the system works accurately before live operations commence. System
testing makes a logical assumption that the system is correct and that the goals are
successfully achieved.
7.4. ACCEPTANCE TESTING:
Acceptance testing involves planning and execution of functional tests, performance
tests and stress tests in order to check whether the system implemented satisfies the
requirements specifications. Quality assurance people as well as customers may
simultaneously develop acceptance tests and run them.
In addition to functional and performance tests, stress test are performed to determine
the limits/limitations of the system developed. For example, a complier may be tested for its
symbol table overflows or a real-time system may be tested for its symbol table overflows or
a real-time system may be tested to find how it responds to multiple interrupts of
different/same priorities.
Acceptance test tools include a test coverage analyzer, and a coding standards
checker. Test coverage analyzer records the control paths followed for each test case. A
timing analyzer reports the time spent in various regions of the source code under different
test cases. Coding standards are stated in the product requirements. Manual inspection is
usually not an adequate mechanism from detecting violations of coding standards.
RUN WITH TEST DATA:
In the case the system was run with some sample data. Specification testing was also done for
each conditions or combinations for conditions.
RUN WITH LIVE DATA:
The system was tested with the data of the old system for a particular period. Then the new
reports were verified with the old
CHAPTER VIII
System Implementation
8.1 USER INTERFACES
SCREENSHOTS OF IMPLEMENTATION
Fig 9: database table of user
Fig 10: database table of assign movies
Fig 11: database table of booking
Fig 12: database table of movie
Fig 13: database table theatre
Fig 14: database table of user
Fig 15: Home page
Fig 16: contact us page
Fig 17: movie checkout page
Fig 18: login page
Fig 19: user registration page
Fig 20: movie adding page
Fig 21: theatre adding page
Fig 22: movie deleted page
Fig 23: theatre selecting page
Fig 24: theatre and movie search page
Fig 25: movie searching page
Fig 26: movie booking page
Fig 27: selecting and booking page
Fig 28: select seat in theatre
Fig 29: reservation id and other detail page
Fig 30: enter user detail email id page
Fig 31: change password page
Fig 32: password change successful page
CODINGDATABASE OF ONLINE MOVIE TICKET SYSTEM
GO/****** Object: Table [dbo].[tbluser] Script Date: 05/05/2020 17:38:32 ******/SET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGOSET ANSI_PADDING ONGOCREATE TABLE [dbo].[tbluser](
[id] [int] IDENTITY(1,1) NOT NULL,[username] [varchar](100) NULL,[upass] [varchar](20) NULL,[gender] [varchar](20) NULL,[phone] [varchar](20) NULL,[email] [varchar](100) NULL,[uaddrs] [varchar](100) NULL,[age] [int] NULL,[userType] [varchar](50) NULL,
CONSTRAINT [PK__tbluser__3213E83F03317E3D] PRIMARY KEY CLUSTERED (
[id] ASC)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]) ON [PRIMARY]GOSET ANSI_PADDING OFFGOSET IDENTITY_INSERT [dbo].[tbluser] ONINSERT [dbo].[tbluser] ([id], [username], [upass], [gender], [phone], [email], [uaddrs], [age], [userType]) VALUES (2, N'kumar', N'kumar', N'Male', N'900000000', N'[email protected]', N'Noida', 35, N'u')INSERT [dbo].[tbluser] ([id], [username], [upass], [gender], [phone], [email], [uaddrs], [age], [userType]) VALUES (3, N'admin', N'admin', N'Male', N'900000000', N'[email protected]', N'ABC', 40, N'a')SET IDENTITY_INSERT [dbo].[tbluser] OFF/****** Object: Table [dbo].[tbltheatre] Script Date: 05/05/2020 17:38:32 ******/SET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGOSET ANSI_PADDING ONGOCREATE TABLE [dbo].[tbltheatre](
[tid] [int] IDENTITY(1,1) NOT NULL,[tname] [varchar](100) NULL,[taddress] [varchar](100) NULL,[tmanager] [varchar](100) NULL,[tsize] [int] NULL,[ttcost] [numeric](18, 2) NULL,
PRIMARY KEY CLUSTERED (
[tid] ASC)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]) ON [PRIMARY]GO
SET ANSI_PADDING OFFGOSET IDENTITY_INSERT [dbo].[tbltheatre] ONINSERT [dbo].[tbltheatre] ([tid], [tname], [taddress], [tmanager], [tsize], [ttcost]) VALUES (1, N'PVR', N'Uttar Pradesh', N'T.B Sharma', 150, CAST(50.00 AS Numeric(18, 2)))INSERT [dbo].[tbltheatre] ([tid], [tname], [taddress], [tmanager], [tsize], [ttcost]) VALUES (2, N'PVR Cenema', N'New Delhi', N'T.B Roy', 150, CAST(50.00 AS Numeric(18, 2)))SET IDENTITY_INSERT [dbo].[tbltheatre] OFF/****** Object: Table [dbo].[tblmovie] Script Date: 05/05/2020 17:38:32 ******/SET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGOSET ANSI_PADDING ONGOCREATE TABLE [dbo].[tblmovie](
[id] [int] IDENTITY(1,1) NOT NULL,[moviename] [varchar](100) NULL,[director] [varchar](150) NULL,[Createdateavailable] [datetime] NULL,[movieactres] [varchar](150) NULL,[movierating] [numeric](18, 1) NULL,[movieimage] [varchar](200) NULL,
CONSTRAINT [PK_tblmovie] PRIMARY KEY CLUSTERED (
[id] ASC)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]) ON [PRIMARY]GOSET ANSI_PADDING OFFGOSET IDENTITY_INSERT [dbo].[tblmovie] ONINSERT [dbo].[tblmovie] ([id], [moviename], [director], [Createdateavailable], [movieactres], [movierating], [movieimage]) VALUES (1, N'housefull 4', N'Farhad Samji', CAST(0x0000ABB20119A997 AS DateTime), N'Starring Akshay Kumar Riteish Deshmukh Bobby Deol Kriti Sanon Pooja Hegde Kriti Kharbanda', CAST(5.0 AS Numeric(18, 1)), N'housefull 4.jpg')INSERT [dbo].[tblmovie] ([id], [moviename], [director], [Createdateavailable], [movieactres], [movierating], [movieimage]) VALUES (2, N'bala', N'Amar Kaushik Starring Ayushmann Khurrana Bhumi Pednekar ', CAST(0x0000ABB2011A58A3 AS DateTime), N'Yami Gautam', CAST(4.0 AS Numeric(18, 1)), N'bala.jpg')INSERT [dbo].[tblmovie] ([id], [moviename], [director], [Createdateavailable], [movieactres], [movierating], [movieimage]) VALUES (3, N'satyameva jayate 2', N'Milap Zaveri ', CAST(0x0000ABB2011AAB83 AS DateTime), N' Divya Khosla Kumar,John Abraham', CAST(4.0 AS Numeric(18, 1)), N'satyameva jayate 2.jpg')SET IDENTITY_INSERT [dbo].[tblmovie] OFF/****** Object: Table [dbo].[tblbooking] Script Date: 05/05/2020 17:38:32 ******/SET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGOSET ANSI_PADDING ONGOCREATE TABLE [dbo].[tblbooking](
[bookid] [int] IDENTITY(1,1) NOT NULL,[email] [varchar](50) NULL,[tname] [varchar](50) NULL,[mname] [varchar](50) NULL,[showdate] [date] NULL,[showtime] [varchar](30) NULL,[nooftickets] [int] NULL,[seatno] [varchar](50) NULL,
[cost] [numeric](18, 2) NULL, CONSTRAINT [PK__tblbooki__8BEA95C51920BF5C] PRIMARY KEY CLUSTERED (
[bookid] ASC)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]) ON [PRIMARY]GOSET ANSI_PADDING OFFGO/****** Object: Table [dbo].[tbassignmovie] Script Date: 05/05/2020 17:38:32 ******/SET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGOSET ANSI_PADDING ONGOCREATE TABLE [dbo].[tbassignmovie](
[mapingid] [int] IDENTITY(1,1) NOT NULL,[moviename] [varchar](100) NULL,[theatrename] [varchar](100) NULL,[dateavailable] [date] NULL,
CONSTRAINT [PK__tbassign__6879BE241FCDBCEB] PRIMARY KEY CLUSTERED (
[mapingid] ASC)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]) ON [PRIMARY]GOSET ANSI_PADDING OFFGOSET IDENTITY_INSERT [dbo].[tbassignmovie] ONINSERT [dbo].[tbassignmovie] ([mapingid], [moviename], [theatrename], [dateavailable]) VALUES (1, N'housefull 4', N'PVR', CAST(0x0D410B00 AS Date))INSERT [dbo].[tbassignmovie] ([mapingid], [moviename], [theatrename], [dateavailable]) VALUES (2, N'housefull 4', N'PVR Cenema', CAST(0x0E410B00 AS Date))INSERT [dbo].[tbassignmovie] ([mapingid], [moviename], [theatrename], [dateavailable]) VALUES (3, N'bala', N'PVR', CAST(0x1B410B00 AS Date))INSERT [dbo].[tbassignmovie] ([mapingid], [moviename], [theatrename], [dateavailable]) VALUES (4, N'satyameva jayate 2', N'PVR Cenema', CAST(0x1B410B00 AS Date))SET IDENTITY_INSERT [dbo].[tbassignmovie] OFF/****** Object: Default [DF_tblmovie_dateavailable] Script Date: 05/05/2020 17:38:32 ******/ALTER TABLE [dbo].[tblmovie] ADD CONSTRAINT [DF_tblmovie_dateavailable] DEFAULT (getdate()) FOR [Createdateavailable]GO
HOME.ASPX.CS CODINGusing System;
using System.Data;using System.Configuration;using System.Collections;using System.Web;using System.Web. Security;using System.Web.UI;using System.Web.UI.WebControls;using System.Web.UI. WebControls.WebParts;using System.Web.UI.HtmlControls;using System.Data.SqlClient;
public partial class home : System.Web.UI.Page{ SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); protected void Page_Load(object sender, EventArgs e) { con.Open(); SqlDataAdapter da = new SqlDataAdapter("SELECT distinct(e.movieimage) FROM tblmovie e INNER JOIN tbassignmovie j ON e.moviename = j.moviename where dateavailable > getdate()", con); DataSet ds = new DataSet(); da.Fill(ds); Repeater1.DataSource = ds.Tables[0]; Repeater1.DataBind(); con.Close();
} protected void Button1_Click(object sender, EventArgs e) { con.Open(); SqlDataAdapter da1 = new SqlDataAdapter("select userType ,username from tbluser where email='" + TextBox1.Text + "'and upass='" + TextBox2.Text + "'", con); DataSet ds2 = new DataSet(); da1.Fill(ds2); if (ds2.Tables[0].Rows.Count > 0) { if(ds2.Tables[0].Rows[0][0].ToString() == "a") { Session["email"] = TextBox1.Text; Response.Redirect("~/Admin/Adminhome.aspx"); } else if (ds2.Tables[0].Rows[0][0].ToString()=="u") { Session["uname"] = ds2.Tables[0].Rows[0][1].ToString(); Session["email"] = TextBox1.Text; Response.Redirect("~/user/userhome.aspx"); } } else Response.Write("<script>alert('invalid id or password ')</script>");
con.Close();
} USERREG.ASPX.CS
using System;using System.Data;using System.Configuration;using System.Collections;using System.Web;using System.Web.Security;using System.Web.UI;using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;using System.Web.UI.HtmlControls;using System.Data.SqlClient;public partial class user_userreg : System.Web.UI.Page{ protected void Page_Load(object sender, EventArgs e) {
} SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);
protected void Button1_Click(object sender, EventArgs e) { string gen=""; if(RadioButton1.Checked) gen=RadioButton1.Text; else gen=RadioButton2.Text; con.Open();
SqlCommand cmd = new SqlCommand("insert into tbluser(username,upass,gender,phone,email,uaddrs,age,userType) values('" + uname.Text.Trim() + "','" + upwd.Text.Trim() + "','" + gen + "','" + uphno.Text.Trim() + "','" + Umailid.Text.Trim() + "','" + uadrs.Text.Trim() + "'," + Convert.ToInt16(uage.Text.Trim()) + ",'u')", con); if (cmd.ExecuteNonQuery() > 0) Response.Write("<script>alert('Inserted')</script>"); else
Response.Write("<script>alert('Error')</script>");
} protected void Button2_Click(object sender, EventArgs e) { uname.Text = ""; upwd.Text = ""; uphno.Text = ""; Umailid.Text = ""; uadrs.Text = ""; uage.Text = "";
}}
XMLFILE.XML
<?xml version="1.0" encoding="utf-8" ?><Advertisements> <Ad> <ImageUrl>~/images/1.jpg</ImageUrl> <height>240</height> <width>65</width> <NavigateUrl> http://www.aw-bc.com/newpearsonchoices </NavigateUrl> <AlternateText>New Pearson Choices</AlternateText>
</Ad> <Ad> <ImageUrl>~/images/2.jpg</ImageUrl> <height>240</height> <width>65</width> <NavigateUrl>http://www.pearsoned.com</NavigateUrl> <AlternateText>Pearson Ed</AlternateText> </Ad> <Ad> <ImageUrl>~/images/3.jpg</ImageUrl> <height>240</height> <width>65</width> <NavigateUrl>http://www.pearsoned.com</NavigateUrl> <AlternateText>Pearson Ed</AlternateText> </Ad> </Advertisements>
RESULT: In our project: with this cinema ticketing system; cinema companies can satisfy
comfortable facilities to their customers. The relationship between cinema\ manager,
employee, and customer satisfy a good communication to complete ticketing process. With
this platform we developed, we are hoping to reduce time wasting, avoid misunderstandings,
provide easy data flow, customer pleasure, and less hard work. We believe that we have
accomplished our goals and satisfied with the code we developed.
CHAPTER-IX
CONCLUSION
This project “Online Cinema Ticket Booking System” handles the theatre employees
and Viewer/Customer details into MS-ACCESS database in a secured manner. This system is
more innovative to use, any user can make up an easier and faster transactions between
Customers and Theatres. This site can be used under any theaters for flexibly of handling the
databases, to get dispatches the data to process them for individual usages. Thus it makes the
system more flexible, and more reliable for use. For all the above this site is the perfect place
for the users especially customers who preferred to book ticket online, and entered into the
current trend. Thus the entire project of Cinema Ticket Booking System is clearly tested; all
the modules are working correctly, as well as the output is verified.
CHAPTER X
REFERENCES
1. Elmasri and Navathe, “Fundamentals of Database Systems” , 3/e, Addison - Wesley,
2001.
2. A Silberschaltz, H.F. Korth, and S sudarshan, “Database System Concepts”, 3/e, Tata
Mcgraw Hill,1997.
3. Thomas M. Connolly, Carolyn E. Begg, “Database Systems & Practical Approach to
Design Implementation and Management”, 4/e, Addison – Wesley, 2005
4. Ye, P., & Yu, B. (2018). Customer Satisfaction Attribution Analysis of Hotel Online Reviews Based on Qualitative Research Methods. In Proceedings of the 2nd International Conference on E-Education, E-Business and E-Technology (pp. 93–98). Association for Computing Machinery.
5. Burmistrov, I. (2009). Mobile Air Ticket Booking. In European Conference on Cognitive Ergonomics: Designing beyond the Product –- Understanding Activity and User Experience in Ubiquitous Environments. VTT Technical Research Centre of Finland.
6. Morjaria, N., Ross, T., & May, A. (2013). Fostering Social Innovation: Identifying Lead Users for Participatory Design. In Proceedings of the Biannual Conference of the Italian Chapter of SIGCHI. Association for Computing Machinery.
7. Balaji, V., & Kuppusamy, K. (2016). Accessibility Evaluation of Indian Railway Websites. In Proceedings of the International Conference on Informatics and Analytics. Association for Computing Machinery.
8. Sahoo, S., Mohanty, S., & Majhi, B. (2017). A Light Weight Three Factor Based
Authentication Scheme for Multi-Server Environment Using Smart Cards. In Proceedings of the 2017 the 7th International Conference on Communication and Network Security (pp. 43–47). Association for Computing Machinery.
9. Bhuvaneswari, A., & Karpagam, G. (2010). Applying Fluent Calculus for Automated and Dynamic Semantic Web Service Composition. In Proceedings of the 1st International Conference on Intelligent Semantic Web-Services and Applications. Association for Computing Machinery.
10. Garai, A., & Finger, M. (2010). Using Governance Framework for E-Governance Development: An Analysis of the Indian Rail Transport. In Proceedings of the 4th International Conference on Theory and Practice of Electronic Governance (pp. 96–102). Association for Computing Machiner.
