ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

INDEX

# S. NO 1. 1.1 1.2 1.3 2.0 2.1 2.1.1 2.1.2 2.2 2.2.1 2.2.2 2.2.3 2.3 2.3.1 3.0 3.1 3.2 3.3 4.0 4.1 4.2 4.3 4.3.1 4.3.2 4.4 4.5 4.6 4.6.1 4.7 4.7.1 4.7.2 4.7.3 4.7.4 4.8 4.8.1 4.8.2 4.8.3
KIRC(IT)

SUBJECT Introduction Project Summary Purpose Scope Project Management Project Planning and Scheduling Project Development Approach Project Plan Risk Management Risk Identification Risk Analysis Risk Planning Estimation Effort Estimation System Requirements Study User characteristics Hardware and Software Requirements Constraints System Analysis Study of Current System Problem and Weakness of Current System Requirements of Current System User Requirements Resource Requirements Feasibility Study Requirement Validation Functions of System Usecase Data Modeling Flow chart E-R Diagram System Activity Data Dictionary Functional and Behavioural Modeling Context Diagram Data Flow Diagram: Level 0 & Level 1 Process Specification and Decision table

PAGE NO 1 1 2 2 4 4 4 5 7 7 8 8 8 8 10 10 11 11 12 12 12 13 13 14 15 17 18 18 19 19 21 22 23 27 27 28 29
Page 1

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062 30 30 31 31 35 36

5.0 5.1 5.2 5.3 6.0 7.0

Testing Testing Plan Testing Strategy Testing Methods Limitation and Future Enhancement Conclusion and Discussion

KIRC(IT)

Page 2

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

FIGURE INDEX

# S. NO

FIGURE NAME

PAGE NO

1.

Incremental Model

2.

Usecase Diagram

18

3.

Flow Chart for Visitor

19

4.

Flow Chart for Cinema Manager

20

5.

E-R Diagram

21

6.

System Activity Diagram

22

KIRC(IT)

Page 3

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

TABLE INDEX

# S. NO

TABLE NAME

PAGE NO

1.

Movie Detail

24

2.

Registration

24

3.

Review Detail

25

4.

Seat Info

26

5.

Seats

26

6.

Show Time

27

7.

Process Specification and Decision Table

29

KIRC(IT)

Page 4

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

1. INTRODUCTION
1.1PROJECT SUMMARY
The system covers all cinemas in a country, but depending upon needs, it can integrate cinemas of other countries as well. Any cinema has one or more rooms, and each room contains a set of seats. People should use our system to find particular movie-sessions by various search criteria like country, area, city, time, cinema or movie title. When entering the web-page the system automatically sets the search conditions to the local area, and a time interval spanning the rest of the current day. When the user has entered search criteria he or she will be presented with a list of session-links that fulfill the criteria or an empty list. Clicking a session link returns a graphical presentation of the room of the session, at which seats can be selected/deselected, a total prize displayed and a booking-commit button. A booking number will be displayed at the screen. The user can bring along this booking number and have the tickets printed later. If a user does not pay before some time limit, specified by the local cinema, before the session begins, the reservation will automatically be cancelled and the corresponding set of seats becomes available for other users. When the movie has been on for some timespan, which is also set by the cinema manager, booking or buying a ticket for that particular session is no longer possible. However, the session information is kept for some time to handle any costumer-requests or -complaints. Upon payment, printing the corresponding tickets is possible at any computer connected to the internet and a printer, or at any cinema covered by the system. The system provides functionality for a cinema manager to schedule future movies at his/her own cinema, i.e., entering sessions into the database, as well as changing the scheduling and correcting errors in scheduling (If any bookings have been made this becomes a bit more tricky!). Thus, the system has following kinds of modules, 1- System Administration 2- Cinema manager (persons who use cinema/Employees) 3- User/Customer (Searching, Booking, Paying)

the

system

for

their

If some cinema wants to be part of the system, someone responsible for managing the cinema must contact the system administration. The system administration will grant permission to the cinema so scheduling of movies at the particular cinema can be performed.

KIRC(IT)

Page 5

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

1.2PURPOSE
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 need not to due 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. The goals of our system are: 1. 2. 3. 4. 5. 6. To provide a anytime anyplace service for the customer To provide refund which is not available in the existing system To minimize the number of staff at the ticket box To promote the film on the internet To increase the profit To obtain statistic information from the booking record.

1.3 SCOPE
1. The web page (e.g. The time table page, the main page) will be generated automatically according to the data in database. 2. A way in which the customer can create its own account(member registration). 3. A way in which the users (both customer and staff) can login to the system to perform different operation. 4. A way in which the customer can modify its own data. 5. A way in which the customer can commit order by just clicking the seat (which is shown on the screen) and insert some card data.(some simple operation) 6. A way in which the customer can cancel the order and get the refund. 7. A way in which the customer can check the ticket record according to the transaction number. 8. A way in which the staff can use the system to add data (e.g. film description) to the database. 9. The system can verify the data before transaction. 10. The system can generate the time table automatically (by just input the length of the film) or the time table is set by the staff. (2 operating mode for the staff to insert data). 11. The system can generate some statistic information according booking and ticket selling record. 12. Users can check film data by clicking on a certain film on main page(e.g. The cinema which will show this films). 13. Users can check a cinema data by clicking on a certain cinema on main page(e.g. which film is now showing).

KIRC(IT)

Page 6

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

2.0 PROJECT MANAGEMENT

2.1 PROJECT PLANNING AND SCHEDULING

2.1.1 PROJECT DEVELOPMENT APPROACH 1. Analyzing current system: Checking online ticket booking websites. Observing and analyzing the system working.

2. Gathering requirement according to the analysis 3. Designing the objectives, plans, structure of system and system model 4. Creating Database for system modules: System Administration: Every organization needs system administrators to man their systems. The system administration will grant permission to the cinema so scheduling of movies at the particular cinema can be performed. A system administrator may also be responsible for incorporating new, and upgrading existing systems. Periodic checking, analyzing and implementation of fault tolerant systems also form an integral part of a seasoned server administrators job. Cinema Manager: If some cinema wants to be part of the system, cinema manager responsible for managing the cinema must contact the system administration & provide day to day report about every activity held in the system. New distribution formats, like digital distribution through DVD, are also being implemented. New films are being released across a larger number of theaters with a large number of prints in order to maximize theatrical revenues in the shortest time period. This is also one of the jobs of Cinema Manager. User/Customer: Uses the system to buy & cancel movie tickets online. Every customer has a unique customer id which acts as its primary key. The basic role of the customer is to inquire about the availability of the tickets and other features of the movieplex. 5. Establishing connectivity between system forms & Database: Employees interact with customers to develop awareness and respond to their goals and needs. Satisfied employees are motivated employees; that is, they have the motivational resources to deliver adequate effort and care to their customers.
Page 7

KIRC(IT)

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

They have the resources, training, and responsibilities to understand and serve customer needs and demands. Employees strongly contribute to our systems success by having a customer-centric approach in their work and in their work-related interactions. The system administration will grant permission to the cinema so scheduling of movies at the particular cinema can be performed.

6. Testing to check if application is running successfully 7. Creating Documentation & Report

2.1.2 PROJECT PLAN

Our system implements Incremental model. Incremental development is at the heart of a cyclic software development process developed in response to the weaknesses of the waterfall model. It starts with an initial planning and ends with deployment with the cyclic interactions in between. The incremental build model is a method of software development where the model is designed, implemented and tested incrementally (a little more is added each time) until the product is finished (tickets in our system). It involves both development and maintenance. The product is defined as finished when it satisfies all of its requirements. This model combines the elements of the waterfall model with the iterative philosophy of prototyping. The product is decomposed into a number of components, each of which are designed and built separately (termed as builds). Each component is delivered to the client (user) when it is complete. This allows partial utilization of product and avoids a long development time. It also creates a large initial capital outlay with the subsequent long wait avoided. This model of development also helps ease the traumatic effect of introducing completely new system all at once.

KIRC(IT)

Page 8

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

Figure 1: INCREMENTAL MODEL

The incremental model shows a process, where developers are to follow these phases in order: Software Planning: This stage establishes the basic structure, evaluates feasibility and risks associated with the project, and describe appropriate management and technical approaches. Software Requirements Specification: A requirements specification for a software system - is a complete description of the behavior of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation. Software analysis and design: It is a process of problem-solving and planning for a software solution. After the purpose and specifications of software are determined, software developers will design or employ designers to develop a plan for a solution. It includes low-level component and algorithm implementation issues as well as the architectural view. System integration: It is the bringing together of the component subsystems into one system and ensuring that the subsystems function together as a system. It is the process of linking together different computing systems and software applications physically or functionally, to act as a coordinated whole. Software deployment: It is all of the activities that make a software system available for use. The general deployment process consists of several interrelated activities with possible transitions between them. These activities can occur at the producer site or at the consumer site or both. Because every software system is unique, the precise processes or procedures within each activity can hardly be
KIRC(IT) Page 9

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

defined. Therefore, "deployment" should be interpreted as a general process that has to be customized according to specific requirements or characteristics. Software testing and evaluation: It is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. Software testing can also be stated as the process of validating and verifying that a software program/application/product: 1. Meets the business and technical requirements that guided its design and development; 2. Works as expected; and 3. Can be implemented with the same characteristics.

2.2 RISK MANAGEMENT

Project risks are characteristics, circumstances, or features of the project environment that may have an adverse affect on the project or the quality of its deliverables. Known risks identified with this project have been included below. A plan will be put into place to minimize or eliminate the impact of each risk to the project. Risks management is a series of steps help a software team to understand unmanaged and manage uncertainly. Risk management planning assumes that mitigation efforts have failed and that the risk has become a reality. The example, the project is well under way and no of people announces that they will be leaving

2.2.1 RISK IDENTIFICATION

Performance risk The degree of uncertainly that the Messaging system has somewhat lower security if not properly maintained. Cost risk The degree of uncertainly that project budget will maintain because Messaging system has several modules. Support risk Here in fast forward world new technology will come in short time which has extra functionality then the current Messaging system so our system has support features like easy to correct, adapt, and enhance Schedule risk The degree of uncertainly that the project schedule will be maintain and that the product will be delivered
KIRC(IT) Page 10

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

2.2.2 RISK ANALYSIS

Risk analysis and management are a series of steps that helps a software teams to understand and manage uncertainty. Many problems can plague a software project. The taxonomy presented here uses function as primary criterion. Risk analysis tools Identifying potential risks and developing plan to mitigate, monitor and manage then is paramount importance in large projects risk analysis tools enable project manager to build a risk table by providing details guidance in the identification and analysis of risk. We have analyzed several risks for our project Customer characteristics, Process definition, Technology to be build, Group size and experience.

2.2.3 RISK PLANNING

Each risk is documented individually using risk information sheet, we have managed plan that has been documented and the project has begun, we have collected all the information that can be used for further future analysis. We think hard about the software; about to build and ask yourself what can go wrong. Create our own list and ask other members of the software team to do the same Also risk table is sorted by probability and impact to rank risk.

2.3 ESTIMATION:
2.3.1 EFFORT ESTMATION The necessity of cost estimation stems from the requirements of scheduling and cost planning. For lack of more precise methods, cost estimation for software development is almost always based on a comparison of the current project with previous ones. Due to the uniqueness of software systems, the number of comparable projects is usually quite small, and empirical data are seldom available. But even if there are exact cost records of comparable projects, these data are based on the technical and organizational conditions under which the comparable project was carried out at that time. The technical and organizational conditions are variable parameters, which makes empirical data from comparable projects only an unreliable basis for estimates.
KIRC(IT) Page 11

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

3.0 SYSTEM REQUIREMENTS STUDY

3.1 USER CHARACTERISTICS: No technical experience is required basic knowledge of handling system is sufficient.

System Administration: Every organization needs system administrators to man their systems. The system administration will grant permission to the cinema so scheduling of movies at the particular cinema can be performed. A system administrator may also be responsible for incorporating new, and upgrading existing systems. Periodic checking, analyzing and implementation of fault tolerant systems also form an integral part of a seasoned server administrators job. Before implementing any rule or regulation, cinema manager must consult System administrator and discuss all possible outcomes of their implementations.

Cinema Manager: If some cinema wants to be part of the system, cinema manager responsible for managing the cinema must contact the system administration & provide day to day report about every activity held in the system. New distribution formats, like digital distribution through DVD, are also being implemented. New films are being released across a larger number of theaters with a large number of prints in order to maximize theatrical revenues in the shortest time period. This is also one of the jobs of Cinema Manager. Cinema Manager must keep a check on day to day activities taking place in the multiplex and submit each and every report to System Administrator in due time. User/Customer: Uses the system to buy & cancel movie tickets online. Every customer has a unique customer id which acts as its primary key. The basic role of the customer is to inquire about the availability of the tickets and other features of the movieplex. Explaining the whole process, first of all, user has to login using his user id which acts as a primary key and the password. Then he/she checks out the available shows and based on available timing, he/she makes an entry for booking ticket online.

KIRC(IT)

Page 12

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

3.2 HARDWARE AND SOFTWARE REQUIREMENTS

Hardware Requirements: The application is supposed to run on systems with the minimum requirement of Intel Core 2 Duo processor- Cache 3MB L2 , 2.53 GHz clock speed,1066 MHz FSB.

Software Requirements: The application is supposed to run on all Windows operating Systems (NT/2000/XP/Vista/7), with the browser same as Internet Explorer 8.

FRONTEND AND BACKEND: The brief details of the project are as followsProject Name: ONLINE TICKET BOOKING SYSTEM Frontend: Adobe Dreamweaver CS3, Java Backend: SQL Server 2005 Modules: System Administration, Cinema Managers, User/Customer

3.3 CONSTRAINTS
Regulatory policies: It is a mandatory that no text book must be left empty or contains insufficient data. Hardware limitations: There must be a 64 MB on board memory. Control functions: The software must be very user-friendly and display appropriate error messages. Interfaces to other applications: Not applicable. Parallel operations: It must support many users simultaneously. Reliability requirements: Data redundancy and use of special/blank characters must be avoided. Safety/security considerations: The application must be exited always normally.

KIRC(IT)

Page 13

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

4.0 SYSTEM ANALYSIS

4.1 STUDY OF CURRENT SYSTEM
o Manual Work o Every new employees information was stored in Excel sheet. o No source for viewing project progress for client. o Submitting day to day report to seniors by mailing manually. o Appraisal was carried out using paper and pen. o Documents were submitted using mails. o Lack of accuracy and speed. o Insufficient information. o Not access to anywhere in the world.

4.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM

In the current scenario, this process is relatively slow and prone to human errors. Also, due to the involvement of lots of files and paper. Centralize storing of information and sharing of information between State & District was not supported. Because of manual work and person dependency involved, Reliability was also decreased Verification and validation process is complex and involve lots of person dependency. Just in time availability of information and report preparation is not involved in manual system.

KIRC(IT)

Page 14

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

4.3 REQUIREMENTS OF NEW SYSTEM

Common Requirement identified: Provide the right information to the right people at the right time. Availability of just-in-time information Reduced person dependency Streamlined flow of information Effective reporting and presentation of required data Reliable information availability Easy verification/validation process Improved decision making process Expedite the execution of internal processes Effective coordination among branches Faster computing and accounting Improve response time through automated operation

4.3.1 USER REQUIREMENTS The main requirement for the new system is to make the old one to be computerized. By making it computerized everyone in the company can use it and also it saves a lot of time. Just taking information about how to use the new system any employee can work on it and make decisions from it.

Functional Requirements Following are the functional requirements: Authentication Facility: User will require a user name and password to enter the system. User can login by entering the user name and password. Checking the type of user: Type of user is checked (Employee/Administrator) and accordingly access rights are assigned. View Records: An employee can view only his record and an administrator can view records of all the employees. Update record: A clerk can directly update any applicants record. Delete Record: This can only be done by clerk if record is not scrutinized and authorized. Add Records: This can only be done by clerk. He can add the details of any new application.
Page 15

KIRC(IT)

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

Authorize Record: The General Manager can authorize the application. Scrutinize Record: This can only be done by using Administrator. Assign Username and password: Admin assigns username and password to every new user who is allowed to access the system. Searching: This is done by the user if it is authenticated by the admin.

User non-functional Requirement: Following are the user non-functional requirements: It must provide a better GUI so it is easy to navigate for the user. It should provide help whenever necessary. There should be tool-tips facility so it dont impatient the user. It must be triggering an appropriate message when an unexpected event occurs. There should be accurate user manual. Each button should have appropriate picture on it. Different buttons should have appropriate icons. There should be facility like clock and calendar.

4.3.2 RESOURCE REQUIREMENTS A Windows Computer ASP.NET is a Microsoft technology. To run ASP.NET you need a computer capable of running Windows. Windows 2000 , XP or Vista If you are serious about developing ASP.NET applications you should install Windows 2000 Professional or Windows XP Professional. In both cases, make sure you install the Internet Information Services (IIS) from the Add/Remove Windows components dialog

4.4 FEASIBILITY STUDY

The feasibility study is highly dependent on the type of developer, the enduser answer the application on hand. In feasibility study the system constraints are defined and the system is checked against these constraints whether it is feasible or not. This is done by analyzing the problem at the global level. To do a well founded feasibility study one should performed as much analysis of the problem as is needed. The study should be done
KIRC(IT) Page 16

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

with time duration taken under consideration. On the basis of the project definition during the early stages of the analysis, we proceed to identify alternative solution. For each suggested solution, we analyze costs answer delivery dates. Thus the feasibility study tries to uncover the future aspects of the software development. There are different category of feasibility study and they are :

Operational Feasibility: Operational feasibility measures how well does the system works or performs. How helpful it for the end-user who use the system to extract or store information through the system. Having done the operational feasibility study of this system one can conclude.

Technical Feasibility: The feasibility deals with the technical details of the system such as, Whether the tools for the development of the system are available or not? Are developers aware of these technologies? What are the alternative tools that can be used? The compatibility of the system with the environment?

Schedule Feasibility: Projects are bound to be completed within a particular time limit. We need to evaluate this deadlines before starting the project and should check that whit the available resources whether the project can be completed in time or not.

Implementation Feasibility: Under the study of implementation feasibility, we've got to draw the figure to the certain issues, like:
KIRC(IT) Page 17

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

Is it possible to install the software within the given environment? whether the system which is being developed will run in the environment available with us? Will the system be approved by the management of the Organization? Will the system cause any harm to the operations of the organization?

Operationally the system can be installed and it can work according to its functionalities. There would be very little barriers in implementation, if application will be prepared according to the hardware barriers. The management has already approved the software to be developed and it would in fact help in user's operation or day-to-day activities. Economic Feasibility: Economic feasibility addresses to the following issues:

Economical feasibility deals with the fact that will the system be cost effective? Does the organization have enough budgets to develop the system? Will the system provide profit to the organization?

4.5 REQUIREMENTS VALIDATION

In this phase, the requirements are checked to discover if they are complete, consistence and in accordance with what customers really want from the system. This type of the study is used to determined that the proposed project request is feasible or not and likelihood of the system will be useful to the organization. Here we have got the Project request for Online ticket booking system. During the Analysis period we have collected the information about the Online ticket booking system and the organization also that after making this Online ticket booking system. it is up to how much level beneficial to the organization for which we have made.

KIRC(IT)

Page 18

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

4.6 Functions of Systems

4.6.1Usecase:
System
LOGIN

SELECT MOVIE,DATE & TIME

SELECT AVAILABLE SEATS

ADMIN

CONFORM/ CANCELLATION

SEE MOVIE REVIEW USER

PAYMENT

UPDATE MOVIE DETAIL

CINEMA MANAGER

INSERT NEW MOVIE DETAIL

Figure 2: USE CASE DIAGRAM

KIRC(IT)

Page 19

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

4.7 DATA MODELING

4.7.1 FLOW CHART Flow chart for user:
USER

REGESTRA TION

INVALID

LOGIN
VALID

MOVIE DETAIL SHOW TIME

SELECT AVAILABLE SEATS

CONFIRM TICKETS

PAYMENT

DISPLAY CONFIRMATION MESSAGE

Figure 3: FLOW CHART FOR USER

KIRC(IT)

Page 20

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

Flow chart for cinema manager:

USER
INVALID

LOGIN
VALID

MOVIE DETAIL

SHOW TIME

CANCELLATIO N

DISPLAY CONFIRMATION MESSAGE

Figure 4: FLOW CHART FOR CINEMA MANAGER

KIRC(IT)

Page 21

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

4.7.2 E-R DIAGRAM

DATE MOVIE_ID

TIME

ID CUSTOMER_NAME

SHOW TIME
MOVIE NAME EMAIL ID -1 -* USER NAME PASSWORD MOVIE_ID TYPE OF SEAT

CUSTOMER_ID TIMING

DETAIL DETAIL

SCREEN NO

ADDRESS

-1 -1 -* -*

-1 -*

-* -1 -1 -* -1 -* -1-* MOVIE DETAIL

CUSTOMER
PHONE NO -1 -*

REGESTRATI ON

ADMIN

CINEMA MANAGER
-* -1

REVIEW DETAIL

SEAT DETAIL TYPE OF SEAT -1 -*

-1 MUSIC -* MOVIE NAME

TRANSECTION_ID

SEAT INFO
SEAT NO

SCREEN NO

IMAGE

REVIEW INFO
DIRECTOR

SHOW TIME MOVIE_ID SHOW DATE

MOVIE DETAIL

RELEASE DATE PRODUCER DESCRIPTION STAR CAST

Figure 5 : E-R diagram

KIRC(IT)

Page 22

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

4.7.3 SYSTEM ACTIVITY

Activity diagrams describe the workflow behavior of a system. Activity diagrams are similar to state diagrams because activities are the state of doing something. The diagrams describe the state of activities by showing the sequence of activities performed. Activity diagrams can show activities that are conditional or parallel.

ENTER USERID AND PASSWORD

MOVIE DETAIL

SELECT MOVIE FROM REVIEW

SELECT MOVIE

SELECT DATE

SELECT TIME

TYPE OF SEAT

SELECT SEAT FROM AVAILABLE SEATS

VIEW OUTPUT(CONFIRMATION MESSAGE)

Figure 6: SYSTEM ACTIVITY DIAGRAM

KIRC(IT)

Page 23

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

4.7.4 DATA DICTIONARY:

As a system data model is derived, many named entities, relationships and so forth will be identified. The names given to the entities should be chosen to given the reader some clues to their meaning, However, Further description of the named entities is usually needed to make the model understandable. The description can be informal or formal. Whatever approach is used, it is always worth collecting all description in a single repository or data dictionary. A data dictionary is simplicity, a list of names used by the system, arranged alphabetically. Other information such as the data of creation, the creator, and the representation of the entity may also be included depending on the type of model which is being developed.

Advantages of Using Data Dictionary:

It is a machine for name management. Many different people who have to invent names for entities and relationship may develop a large system model. It serves as a store of organizational information, which can link analysis, design, implementation and evolution. As the system is developed , information is taken to inform development.

The tabular form data dictionary for this project is given below: Movie_detail Registration Review detail Seat Info Seats Show time

(1) Movie Detail:

KIRC(IT) Page 24

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

Table 1: MOVIE DETAILS Key Primary None None Column Name movie_id movie_name type_of_seat Data Type int nvarchar(50) text Allow null Not null Not null Not null Description Movie id Movie name Type of seat and prise Screen no of movie

None

screen_no

nvarchar(5)

Not null

(2) Registration:
Table 2: REGISTRATION Key Primary None None None None None None None Column Name user_id password first_name last_name email_id address phone_no user_type Data Type nvarchar(15) nvarchar(25) varchar(25) varchar(25) nvarchar(50) nvarchar(100) nvarchar(50) char(1) Allow null Not null Not null Not null Not null Not null Not null Not null Not null Description User id password First name Last name e-mail id address Phone no User type(admin or visitor) User name

None

username

nvarchar(25)

Not null

(3) Review Details:

KIRC(IT) Page 25

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

Table 3: REVIEW DETAILS Key Foreign None None Column Name movie_id movie_name image Data Type int nvarchar(50) nvarchar(100) Allow null Not null Not null Not null Description Movie id Movie name Poster image of movie Producer of movie Director of movie Actor /Actress and costars Music person name Release date of movie Review movie of

None None None

producer director starcast

varchar(50) varchar(20) varchar(150)

Not null Not null Not null

None

music

varchar(20)

Allow null

None

release_dare

nvarchar(15)

Not null

None

description

text

Allow null

KIRC(IT)

Page 26

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

(4) Seat info:

Table 4: SEAT INFO Key None Column Name TransactionID int Data Type Allow null Not null Description Transaction id for seats reserved Reserved Seat nos Movie id selected for reservation Date of show Time of show Screen no of movie Prise and type of reserved seat

None None

SeatNo movie_id

nvarchar(50) int

Not null Not null

None None None None

show_date show_time screen_no type_of_seat

varchar(20) varchar(20) nvarchar(50) text

Not null Not null Not null Not null

(5) Seats:
Table 5: SEATS Key primary Column Name SeatNo Data Type nvarchar(50) Allow null Not null Description Total seats on the screen

KIRC(IT)

Page 27

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

(6) ShowTime:

Table 6: SHOW TIME Key Foreign key None None Primary key Column Name movie_id Date Time ID Data Type int Varchar(50) Varchar(50) int Allow null Not null Not null Not null Not null Description Movie id Date of show Time of show Identity no for date

4.8 FUNCTION AND BEHAVIOURAL MODELING

4.8.1 CONTEXT DIAGRAM

USER

SEAT INFO ONLINE TICKET BOOKING FOR MULTIPLEX DISPLAY SERVICE

ADMIN

TO UPDATE MOVIE INFO

Figure 7: CONTEXT DIAGRAM

KIRC(IT)

Page 28

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

4.8.2 DATA FLOW DIAGRAM Level 0:

USER SEAT INFO UPDATE MOVIE DETAIL

ADMIN

ONLINE TICKET BOOKING FOR MULTIPLEX

DISPLAY SERVICE

CONFORM BOOKING

Figure 8: DFD LEVEL-0

Level 1:
REGESTRATI ON

USER

LOGIN

MOVIE DETAIL

SHOW TIME

CONFORM MESSAGE DISPLAY

CANCELLATI ON

PAYMENT

CONFORM TICKET BOOKING

SELECT AVAILABLE SEAT

DISPLAY CONFORMATI ON MESSAGE REMAINING SEAT INFO

SEAT

Figure 9: DFD LEVEL-1

KIRC(IT)

Page 29

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

4.8.3 PROCESS SPECIFICATION AND DECISION TABLE

First user will get username and password through Admin (i) If user name and password equals Then Login to the main page. Select activity from menu list If not selected Then print error message Else enable task (Searching, ,View,cancellation) End if Else print error message (ii) If select movie If select available seats Then Enter the seat no If not valid Then print Error message Else Confirm tickets If user click for cancellation of tickets Then tickets are cancelled Else continue End if End if

KIRC(IT)

Page 30

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

5.0 TESTING

What is Software Testing? Testing involves operation of a system or application under controlled conditions and evaluating the results. The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go determine if things happen when they shouldn't or things don't happen when they should. It is oriented to detection.

The need of Testing. No matter how good a programmer is, no application will ever be one hundred percent correct. Testing is important to ensure that the application works as efficiently as possible and conforms to the needs of the system. Testing should be carried out throughout the development of the application, not just after the application has been developed, as at this stage it would take a great deal of effort to fix any bugs or design problems that may have occurred. In effect, the earlier that testing shows up problems, the quicker and easier it is for these problems to be rectified.

5.1 TESTING PLAN The test plan identifies a testing task set, the work products to be developed, and the way in which results are to be evaluated, recorded, and reused. An Intranet Application Test Plan identifies: 1. A task set to be applied as testing commences, 2. The work product to be produced as each testing task is executed, and 3. The manner, in which the results of testing are evaluated, recorded and reused when regression testing is conducted.

KIRC(IT)

Page 31

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

5.2 TESTING STRATEGY The overall strategy for web app or intranet testing can be summarized as following 10 steps: 1. The content model for the window application is reviewed to uncover errors. 2. The interface model is reviewed to ensure that all use-cases can be accommodated. 3. The design model for the window application is reviewed to uncover navigation errors. 4. The user interfaces is tested to uncover errors in presentation and/or navigation mechanics. 5. Selected functional components are unit selected. 6. Navigation throughout the architecture is tested. 7. The window application is implemented in a variety of different environmental configuration and is tested for compatibility with each configuration. 8. Security tests are conducted in an attempt to exploit vulnerabilities in the window application or within its environment. 9. Performance test are conducted. 10. The window application is tested by a controlled and monitored population of end users.

5.3 TESTING METHODS System Testing: This testing ensures that application program written in isolation work properly when they are integrated into the total system. This strategy was considered to find discrepancies between system and its original objectives, current specification and systems documentations. The primary concern is to check the compatibility of individual modules. This testing worked perfectly and found out some flaws in our module particularly based on interaction with other module and all of them were resolved properly. In addition, we also verified the following checks:

Completeness Checking: Determines whether all required fields on the input have actually been entered. Combination checking: Cross checks all the relationships and validations on each field.

The errors reported during all these stages of testing have been corrected out right away.
KIRC(IT) Page 32

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and code generation. Testing is process of executing a program with the intent of finding a error and a successful test is one that uncovers an as-yet-undiscovered error. It is essential for stability and better output of system. Software is tested from two different perspectives and in both cases the intent is to find the maximum numbers of errors with minimum amount of effort and time. Testing strategies is a general approach to the testing process rather than a method of devising particular system or component tests. Different testing strategies may be adopted depending on the type of system to the tested and the development process used. So considering functional oriented nature of this software we adopted mixture of following strategies. 1. The internal program logic is exercised using White Box testing techniques, also known as Glass Box testing. This is the code testing strategies in which test cases are developed that result in executing every instruction in a module and hence every path through the program is tested and all program logic is examined. 2. Software requirements are exercised using Black Box testing techniques, also known as Behavioral testing. This specification testing strategy in which the specification are examined starting what to do and how to it should perform under various conditions. Than test cases are developed for each condition and combination of condition and submitted for processing. By evaluating the results, programs performance according to its specified requirements is determined. This is more efficient than code testing since it focuses on way software is expected to be used. A strategy fro software may also be viewed in the context of the spiral model. Unit testing begins at the development of each stage as module progress as in evolutionary model each different module can be used separately. First the unit testing is done. Then testing progress to Integration testing where focus id on design and construction of the module architecture. Moving further we encounter validation testing where requirements established as a part of software requirements analysis are validated against the software that has been constructed. Finally we arrive at System Testing, where the software and other system elements are tested as whole. Different testing strategies may be adopted depending on the type of the system to be tested and the development process used. Considering functional nature of Production module.

KIRC(IT)

Page 33

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

Unit Testing: Unit testing plays very important role in the testing process. Before applying all type of testing, unit testing is done to check any type of errors are there or not. Unit Testing is undertaken when a module has been coded and successfully reviled.

Module Testing: Individual modules are tested in the module testing.

Black-Box Testing Black box testing is an approach to testing where the tests are derived from the program or component specification. Black box testing is also known as Functional Testing because the tester is only h the functionality and not the implementation of the software. In my project I input all the information that is necessary for it. I also check for validation. The numeric field does not accept the character type of data or any other type of symbols.

White-Box Testing White box testing is an approach to testing where the tests are derived from knowledge of the softwares structure and implementation. This approach is sometimes called Structural Testing, glass box testing or clear-box testing. In my project I give meaningful name to all variables and constants, forms, labels, etc. I made functions for validation checking. So there is no need to write the code for validation multiple times.

KIRC(IT)

Page 34

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

Gray Box Testing In using this strategy Black box testing can be combine with knowledge of database as SQL for database query and adding/loading data sets to confirm functions, as well as query the database to confirm expected result.

6.0 LIMITATION AND FUTURE ENHANCEMENT

One of the areas in which we will try to expand our application in the future is to provide the user with the facility to upload his/her questions automatically.Another area where we will like to expand is to provide credit card validation. We can also add credit card validation facilities so invalid credit card number will be rejected.We will also try to make the site more generalized by allowing people from still wider range to be able to user our website.

7.0 CONCLUSION AND DISCUSSION

Self Analysis of Project Viabilities As we have been assigned a full day training period, I cover all the aspects of 3-TIER architecture concept in half month and worked also with the window services Problem Encountered and Possible Solutions Problem: When I was doing R&D on window service, it was difficult for me how to install that window service Solution: I just search the blogs corresponding to window services and find the way of installing window services Problem: Adding the process into schedule task without using login c credentials Solution: It was not possible to add any process in schedule task without using login credentials Problem: List view control Solution: Inheriting grid view inside list view

KIRC(IT)

Page 35

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

SUMMARY OF PROJECT WORK I feel very well after completion of this project. I have faced almost all the difficulties we have been taught in software engineering and its prior knowledge helped us to take care of all the delays.

KIRC(IT)

Page 36

ONLINE MULTIPLEX TICKET BOOKING SYSTEM

090260116056 090260116062

Bibliography

Books Referred: Object Oriented Analysis And Design with UML Software engineering (Pressman)

Websites Referred: www.google.com www.bookmyshow.com

KIRC(IT)

Page 37