Project Report On Multiplex - Ticket Booking System

Synopsis on multiplex ticket Booking
Synopsis On Multiplex Ticket Booking
NAMECLASSROLLNO-
UNDER GUIDANCE OF Mr.
Table of Contents
1) Introduction
2) Background
3) Objective
4) Purpose 4.1) Purpose 4.2) Scope 5) Survey of Technology
6) Requirement and Analysis
7) Problem definition
8) Planning and Scheduling
9) Requirement and Specification 9.1.1) Software 9.1.2) Hardware 9.2) 9.3) 9.4) Preliminary Product Description Conceptual Model References
xxxxxxxxxxxxx
sssssssssssssssssssss
1. Introduction
In the fast changing world, information technology and information management are going to play an important role. We are living in the computer age during past some year .The computer has gaining popularity. Computer revolution found its way into almost every aspect of human life and living. A computer is admirably suited to handle any information and hence is an information processor that is, it can receive data, perform some basic operations on that data and produces results according to a predetermined program. Multiplex ticket booking is a web application that would facilitate online ticket booking of movies in a multiplex. Users would be provided to book their tickets according to their choice they can book ticket show of desired day and suitable timing the payment facility would also be provided online ticket cancelation process would also take place. This project is basically divided into two modules. First module is Admin Module which controls all the process whereas Member Module actually uses the software associated with the website.
xxxxxxxxxxxxx
2. Background
In the background of multiplex ticket booking the conventional process of ticket booking in which people have to stand in a queue for getting ticket of their favourite movies. This web application would remove almost all the paper work and things would be much more advanced and using the facilities of advanced web technology the possibility of not getting the ticket and returning back to their home by the people would also get eliminated because the people would book the ticket online and if successed. In the process then only they would go for movies.
xxxxxxxxxxxxx
3. Objective
Todays world is computer world because most of work is doing with the help of computer. Dependency on computer is behind the few reasons. We cannot easily manage to store large number of data or information single handily. If we will be need some information or data in urgency then we cannot manage in manually these works are very difficult if we cannot use computer. So the objective of this project is to overcome the limitation of the manual approach. This project is started towards systematically automating all the work that is done manually at present. Their aim is to focus following aspects: The main objective is to automate non computer environment To save manpower. It will speed the processing of data and transaction. It will provide all the error reporting and handling features, so that the user is warned and made aware of any foreseen errors. Thus it will reduce the error rate. It will provide various ways through which we generate various types of report. It will provide best security features such as provisions of passwords.
xxxxxxxxxxxxx
4. Purpose and Scope 4.1 Purpose:The purpose of this web application is to provide facilities to the user or viewers so that they can book their respective tickets online sitting. Anywhere just using this web application from the owners point of view the huge gathering on the multiplex for getting ticket can also be minimized and less efforts would have been done by the owner of the multiplex to manage such a huge crowed specially on the first show or first day of the release of a movie.
4.1 Scope:The scope of this web application is very vast and useful from the users point of view as well as management point of view. This web application can be further extended to add some new functionalities services security measures in the feature.
xxxxxxxxxxxxx
5. Survey of Technology
After the release of Internet Information Services 4.0 in 1997, Microsoft began
researching possibilities for a new Web application model that would solve common complaints about ASP, especially with regard to separation of presentation and content and being able to write "clean" code. Mark Anders, a manager on the IIS team, and Scott Guthrie, who had joined Microsoft in 1997 after graduating from Duke University, were tasked with determining what that model would look like. The initial design was developed over the course of two months by Anders and Guthrie, and Guthrie coded the initial prototypes during the Fall of 1997. The initial prototype was called "XSP"; Guthrie explained in a 2007 interview that, "People would always ask what the X stood for. At the time it really didn't stand for anything. XML started with that; XSLT started with that. Everything cool seemed to start with an X, so that's what we originally named it." The initial prototype of XSP was done using Java, but it was soon decided to build the new platform on top of the Common Language Runtime (CLR), as it offered an object-oriented programming environment, garbage collection and other features that were seen as desirable features that Microsoft's Component Object Model platform did not support. Guthrie described this decision as a "huge risk", as the success of their new Web development platform would be tied to the success of the CLR, which, like XSP, was still in the early stages of development, so much so that the XSP team was the first team at Microsoft to target the CLR. With the move to the Common Language Runtime, XSP was re-implemented in C# (known internally as "Project Cool" but kept secret from the public), and the name changed to ASP+, as by this point the new platform was seen as being the successor to Active Server Pages, and the intention was to provide an easy migration path for ASP developers. Mark Anders first demonstrated ASP+ at the ASP Connections conference in Phoenix, Arizona on May 2, 2000. Demonstrations to the wide public and initial beta release of ASP+ (and the rest of the .NET Framework) came at the 2000 Professional Developers Conference on July 11, 2000 in Orlando, Florida. During Bill Gates' keynote presentation, Fujitsu demonstrated ASP+ being used in conjunction with
xxxxxxxxxxxxx sssssssssssssssssssss
COBOL, and support for a variety of other languages was announced, including Microsoft's new Visual Basic .NET and C# languages, as well as Python and Perl support by way of interoperability tools created by ActiveState. Once the ".NET" branding was decided on in the second half of 2000, it was decided to rename ASP+ to ASP.NET. Mark Anders explained on an appearance on The MSDN Show that year that, "The .NET initiative is really about a number of factors, it's about delivering software as a link building service, it's about XML and Web services and really enhancing the Internet in terms of what it can do ... we really wanted to bring its name more in line with the rest of the platform pieces that make up the .NET framework."[4] After four years of development, and a series of beta releases in 2000 and 2001, ASP.NET 1.0 was released on January 5, 2002 as part of version 1.0 of the .NET Framework. Even prior to the release, dozens of books had been written about ASP.NET,[7] and Microsoft promoted it heavily as part of its platform for Web services. Guthrie became the product unit manager for ASP.NET, and development continued apace, with version 1.1 being released on April 24, 2003 as a part of Windows Server 2003. This release focused on improving ASP.NET's support for mobile devices.
xxxxxxxxxxxxx
Net Framework
The .NET Framework (pronounced dot net) is a software framework that runs primarily on Microsoft Windows. It includes a large library and supports several programming languages which allow language interoperability (each language can use code written in other languages). Programs written for the .NET Framework execute in a software environment (as contrasted to hardware environment), known as the Common Language Runtime (CLR), an application virtual machine that provides important services such as security, memory management, and exception handling. The class library and the CLR together constitute the .NET Framework. The .NET Framework's Base Class Library provides user interface, data access, database connectivity, cryptography, web application development, numeric Algorithms, and network communications. Programmers produce software by combining their own source code with the .NET Framework and other libraries. The .NET Framework is intended to be used by most new applications created for the Windows platform. Microsoft also produces a popular integrated development environment largely for .NET software called Visual Studio.
xxxxxxxxxxxxx
History
Microsoft started the development on the .NET Framework in the late 1990s originally under the name of Next Generation Windows Services (NGWS). By late 2000 the first beta versions of .NET 1.0 were released.[2] Version 3.0 of the .NET Framework is included with Windows Server 2008 and Windows Vista. Version 3.5 is included with Windows 7, and can also be installed on Windows XP and the Windows Server 2003 family of operating systems.[3] On 12 April 2010, .NET Framework 4 was released alongside Visual Studio 2010. The .NET Framework family also includes two versions for mobile or embedded device use. A reduced version of the framework, the .NET Compact Framework, is available on Windows CE platforms, including Windows Mobile devices such as smart phones. Additionally, the .NET Micro Framework is targeted at severely resource-constrained devices.
xxxxxxxxxxxxx
6. Requirement and Analysis

System analysis is the main features of the software development. It can be said that it is the heart of any of the system. The analysis needs an expert supervision and person should be minimum System analysis with experience of 3 to 5 years. One can use Analysis tools to analyze the system. Some of the tools we have used to analyze the problem is given below
6.1 Analysis Tools 6.1.1 Data Collection Tools: In order to get the information for our proposed application we approached the Analyze Infotech, and collected the information related to our application. This was necessary to make general software, which can be used by any Business/Organization.
6.1.2 Charting Tools

The graphical Representation of system and activities help us to understand the minor problems and the flow of information very easily, which can become very helpful in analysis as well as to generated the new systems requirement. Graphical representation is always better than normal text. We made E-R diagram and Data Flow Diagram to collect all the information and build relationship among the external entities. In order to understand the flow of information in the system the Data Flow Diagram plays a very important role. E-R Diagram is used to convert the entities and relationship in the relational tables.
6.1.3 Dictionary Tool This tool helps us to maintain and record the data & description of system element through data items, Processes and data sources. This basically helps us about the information flow among various units.
6.2 Identification of Need Goal of analysis hear is recognition of the basic problem elements as perceived by the top management as well as Business administrator and understand
application in the system context. In order to identify the need, there is a need to establish contact with various Business staff and software development organization. 6.3 Feasibility Study All projects are feasible given unlimited resources and infinite time! Unfortunately, the development of computer based system is more likely to be plagued by a scarcity of resources and difficult delivery dates. It is both necessary and prudent to evaluate the feasibility of the project at the earliest possible time. Months or years of effort, Money loss and untold professional embarrassment can be averted I few better understand the project at its study time. This type of study determines if an application can and should be developed. Once it has been determining that, application is feasible. After that analyst can go ahead and prepares the project specification, which finalizes project requirements. Feasibility studies are undertaken within tight time constraints.The developed system is started after considering the main three types of feasibilities that are discussed below :-
6.3.1. Technical Feasibility As we know the technical feasibility is concerned with specifying equipment and software that will successfully satisfy the user requirement. The technical needs of the system may vary considerably, but might include: The facility to produce outputs of advertisements, shopping and mailing in a given time for ease of use. Response time under certain condition is minimal. Ability to process a certain volume of transaction at a particular speed. Facility to communicate data to distinct location. In examining the technical feasibility, configuration of the system is given more importance than the actual make of hardware. The configuration should give the complete picture about the systems requirements- how many workstations are required, how these units are interconnected so that they could operate and communicate smoothly.
xxxxxxxxxxxxx
6.3.2 Economical Feasibility Economic analysis is the most frequently used technique for evaluating the effectiveness of the proposed system. More commonly known as cost/benefits analysis, the procedure is to determine the benefits and savings that are expected from the purposed system and compared with costs. If benefits outweigh cost, a decision is taken to design and implement the system. Otherwise, further justification or alternative of the proposed system will have to be made if it has a chance of being approved. This is an ongoing effort that improves in accuracy at each phase of the system life cycle. The analysis part also clears the doubt of economic problems which could be possible in developing the system. As already mentioned that the company has to just pay the developed software cost and not other investment is needed at the time of implementation of the new system as the preliminary requirements already exist in the company. 6.3.3 Operational Feasibility Proposed projects are beneficial only if they can be turned into information system that will meet the financial management requirements of the
business/organization. This test of feasibility asks if the system will work when it developed and installed. Are there major barriers to implementation?
xxxxxxxxxxxxx
Some of the important questions that are useful to test the operational feasibility of a project are given below: Is there sufficient support for the project from the implementation? From user? If the present system is well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance. Are current business methods acceptable to the user? If they are not, user may welcome a change that will bring about a more operational and useful system Have the user been involved in the planning and development of the project? If they are involved at the earliest stage of project development, the chances of resistance can be possibly reduced. Will the proposed system cause harm? Will it produce poorer result in any case or area? Will the performance of staff member fall down after implementation? Issue that appears to be quite minor at the early stage can grow into major problem after Implementation. Therefore, it is always advisable to consider operational aspects carefully. The system is developed keeping in mind that it should be user friendly and easy to operate hence the system is operational feasible.
7. Problem Definition
Almost every activity in the world today is controlled by computer driven software programs. His trend was first accommodated by engineering applications
in the past. However, as the life style became more and more complex, every area of human interaction was invaded by various software systems, such as real time, business, simulation, embedded, web based, personal and more recently, artificial intelligence software etc.
The proposed application is an electronic voting system which is being designed to replace the existing manual voting system. There is no existing computerized system. All the work is performed manually. The manual system is not secure enough.
The proposed system has following key features:Features: It reduces the paperwork and increased automation Very fast processing Efficient management of information Improved security Data safety through redundancy Integrity of the data is maintained Transparency in the system.
6. Planning and Scheduling
8.1 Project Planning
Planning: Planning is an ongoing function that provides the framework for operational activity and decision-making. A plan is a predetermined course action. It represents goals and activities necessary to achieve these goals. Planning is very important in every aspect of development work. Good managers carefully monitor developments at various phases. Improper planning leads to failure of the project.
Project life cycle has three stages:1. Project Initiation- Development team prepares the project plans and finalizes the outcome of each phase. In this stage team also prepares the comprehensive list of tasks involves in each phase, and the project assigns responsibilities to the team members, depending on their skills. 2. Project Execution- In this stage, the team develops the product. In case of online examination, team will develop the online examination management. This stage consists of following phase: 1. Requirement Analysis 2. High Level Design 3. Low Level Design 4. Construction 5. Testing 6. Acceptance
3. Project Completion: In this stage, the team has to update the site regularly. Each new enquiry has to add by the Field Officer as according to their area. This stage is very important for the freshness of the site.
xxxxxxxxxxxxx
8.2 Project Scheduling 8.2.1 PERT CHART: A PERT chart is a project management tools used to schedule, organize, and coordinate tasks within a project. PERT stands for Program Evaluation Review Technique. A PERT chart presents a graphic illustration of a project as network diagram consisting of numbered nodes(either circles or rectangles) representing events, or milestones in the project linked by labeled vectors (directional lines) representing tasks in the project. The direction of the arrows on the lines indicates the sequence of tasks.
Alpha Testing SRS And Design
3
Programming
5
30 10
8
Beta Testing
10
10
10
15
2 4 10 6 10 7 10
59
11
Buy Hardware
Writing Manuals
User Test
User Requirement And Analysis
Installation
Training
8.2.2 GANTT CHART: Gantt Chart is also known as Time Line Charts. A Gantt Chart can be developed for the entire project or a separate chart can be developed for each function. A tabular form is maintained where rows indicate the tasks with milestones
and columns indicate duration (weeks/months). The horizontal bars that spans across columns indicate duration of the tasks.
January Requirement Gathering Design Test Cases Coding Testing Build
February
March
April
Requirement Specification
9.1.1 Software 1.Visual Studio 2008 2.Sql Server 2005
xxxxxxxxxxxxx
3.AJAX 4.Filezilla 5.Microsoft Office 2008
9.1.2 Hardware Pentium IV Processor 512 MB RAM 40 GB HDD Color Monitor Keyboard, Mouse
9.2 Preliminary Product Description

Front End: Back End: Microsoft Visual Studio 2008 Sql server 2005
Operating System: WINDOWS 2000 PROFESSIONAL/WINDOWS XP There are mainly two modules in the project3.1. Admin 3.2. Member
3.1 Admin Features a) The admin can add new movies b) Can update the schedule or timing of shows. c) Can cancel a show. d) Can view reports according to different criteria like availability of seats in a particular show. e) Reports related to total money collected in a day or in a particular show.
3.2 Member Features a) Users Registration. b) User login. c) Can book tickets according to their choice. d) Can cancel ticket booked. e) Can view status of show. f) Can generate report about different shows according to timing or ticket cost.
CONCEPTUAL MODEL
DATA FLOW DIAGRAM
ADMIN Multiplex Ticket Booking MEMBER
REVENUE
TICKET
CONTEXT LEVEL DFD

xxxxxxxxxxxxx
E-R DIAGRAM
Member_id ddd State City Address Id Password E-mail Mobile
Password
E-mail_id
MEMBER
ADMIN
Addres s Mobile Timing
Create
Morng show Evening show
MOVIE SHEDULE
Noon show
Allot Ticket
Name
Generate
Cust_id City ShowDetail s details Revenue
CUSTOMERS
Name E-mail
REPORTS
Cust_Details
Tables 1. Emp. Detail
xxxxxxxxxxxxx
Name Column User Name Password Name Email LName Mobile Address Country State City Pin
Data Type Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Numeric(10,0) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Numeric(8,0)
Allow Nulls (Primary Key) Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls
2. MOVIE DETAILS Name Column Movie_id Name Releasing_date Closing_details Data Type Varchar(50) Varchar(50) Numeric(10,0) Numeric(10,0) Allow Nulls (Primary Key) Allow Nulls Allow Nulls Allow Nulls
3. Morning show1\ CUSTOMER details
xxxxxxxxxxxxx
Name Column Movie_id Timing Customer_id Customer_name Ticket_no Gold Silver Date
Data Type Varchar(50) DateTime Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) DateTime
Allow Nulls (Primary Key) Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls
4. Morning show1\ TICKET details
Name Column Movie_id Total_Gold Total_Silver Available_Gold Available_Silver Date
Data Type Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) DateTime
Allow Nulls (Primary Key) Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls
5. Morning show2\ CUSTOMER details
xxxxxxxxxxxxx
6. Morning show2\ TICKET details
7. Afternoon show1\ CUSTOMER details
xxxxxxxxxxxxx
8. Afternoon show1\ TICKET details
9. Afternoon show2\ CUSTOMER details
xxxxxxxxxxxxx
10. Afternoon show2\ TICKET details
xxxxxxxxxxxxx
11. Evening show1\ CUSTOMER details
12. Evening show1\ TICKET details
13. Evening show2\ CUSTOMER details

Data Type Varchar(50) DateTime Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50)
14. Evening show2\ TICKET details
xxxxxxxxxxxxx
15.Charges table Name Column Movie_id Morning_show1 Morning_show2 Afternoon_show1 Afternoon_show2 Evening_show1 Evening_show2 Gold_charges Silver_charges Data Type Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Numeric(5,0) Numeric(5,0) Allow Nulls (Primary Key) Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls Allow Nulls
15.NEWSINFO table
Name Column sNo info
Data Type Integer Varchar(50)
Allow Nulls (Primary Key) Not Null
16.MOVIECHARGES table
Name Column sno Day Timing Charge
Data Type Integer Varchar(50) Varchar(50) Varchar(50)
Allow Nulls (Primary Key) Not Null Not Null Not Null
17.INITIAL CODE table
Name Column sno ticketNo show customerId
Data Type Integer Varchar(50) Varchar(50) Varchar(50)
Allow Nulls (Primary Key) Not Null Not Null Not Null
9.4 References
Software Engineering
By: Roger S. Pressman Black Book (Visual Studio) Referenced Sites:
www.msdn.microsoft.com www.microsoft.com
xxxxxxxxxxxxx
xxxxxxxxxxxxx

Project Report On Multiplex - Ticket Booking System

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Project Report On Multiplex - Ticket Booking System

Enviado por

Direitos autorais:

Formatos disponíveis

Synopsis on multiplex ticket Booking

Synopsis On Multiplex Ticket Booking

UNDER GUIDANCE OF Mr.

Synopsis on multiplex ticket Booking

4) Purpose 4.1) Purpose 4.2) Scope 5) Survey of Technology

6) Requirement and Analysis

8) Planning and Scheduling

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

6. Requirement and Analysis

6.1.2 Charting Tools

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

6. Planning and Scheduling

8.1 Project Planning

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

Alpha Testing SRS And Design

User Requirement And Analysis

Synopsis on multiplex ticket Booking

January Requirement Gathering Design Test Cases Coding Testing Build

Synopsis on multiplex ticket Booking

3.AJAX 4.Filezilla 5.Microsoft Office 2008

9.2 Preliminary Product Description

Synopsis on multiplex ticket Booking

ADMIN Multiplex Ticket Booking MEMBER

CONTEXT LEVEL DFD

Synopsis on multiplex ticket Booking

Synopsis on multiplex ticket Booking

Member_id ddd State City Address Id Password E-mail Mobile

Morng show Evening show

Tables 1. Emp. Detail

Synopsis on multiplex ticket Booking

3. Morning show1\ CUSTOMER details

Synopsis on multiplex ticket Booking

4. Morning show1\ TICKET details

Name Column Movie_id Total_Gold Total_Silver Available_Gold Available_Silver Date

Data Type Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) DateTime

5. Morning show2\ CUSTOMER details

Synopsis on multiplex ticket Booking

6. Morning show2\ TICKET details

Name Column Movie_id Total_Gold Total_Silver Available_Gold Available_Silver Date

Data Type Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) DateTime

7. Afternoon show1\ CUSTOMER details

Synopsis on multiplex ticket Booking

8. Afternoon show1\ TICKET details

Name Column Movie_id Total_Gold Total_Silver Available_Gold Available_Silver Date

Data Type Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) DateTime

9. Afternoon show2\ CUSTOMER details

Synopsis on multiplex ticket Booking

10. Afternoon show2\ TICKET details

Name Column Movie_id Total_Gold Total_Silver Available_Gold Available_Silver Date

Data Type Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) DateTime

Synopsis on multiplex ticket Booking