Ticket Booking System

46

Click here to load reader

Transcript of Ticket Booking System

Page 1: Ticket Booking System

TICKET BOOKING SYSTEM

1. INTRODUCTION

1.1 OVER VIEW OF PROJECT

The project “TICKET BOOKING SYSTEM” is done to automate the manually

done processes of the organization. The system insights towards customizing the requirement

of the tickets section of the company. It also performs separate date wise report and makes

updating of the records like the number of child tickets, number of adult tickets booked which

is made for the bill. The project also has separate module that deals with the process of

cancellation of tickets.

The system has unique login id and password for the staffs and the administrator

holds the rights to manipulate the system and to view the reports. The ticket booking profiles

and the ticket cancellation profiles are maintained by the system. The tickets booked by the

customers are maintained and the cost of the total number of tickets is calculated

automatically. The project is been planned to provide all the features which will support the

needs of the concern. The proposed system is framed in such a way that it overcomes all the

problems and adds more features to the system.

This project include the following modules, these are,

Employee Details Module

Ticket Booking Details Module

Ticket Cancellation Details Module

Reports

1

Page 2: Ticket Booking System

TICKET BOOKING SYSTEM

1.2.ORGANIZATION PROFILE

Name of the Company - BLACK THUNDER THEME PARK (P) LTD

Factory Address - BLACK THUNDER THEME PARK (P) LTD

Ooty Main Road, Mettupalayam.

Contact Number - 04254 226632 – 40 (9Lines)

Built-up Area - 65 Acres

Total No of Employees - 100 members

Staff - 70 Members

Workers - 30 Members

Organization‘s Awards - IAAPI awards for BEST ENVIRO – FRIENDLY

and SAFETY PRACTICES for 2001 -2002.

IAAPI awards for MOST INNOVATIVE RIDE and

TOTAL NUMBER and VARIETY OF RIDES

for 2009 - 2010

E – Mail - [email protected]

Website - btpark.org

2

Page 3: Ticket Booking System

TICKET BOOKING SYSTEM

1.3.SYSTEM CONFIGURATION

HARDWARE CONFIGURATION

Hard Disk : 80 GB

Floppy Disk : 1.44 MB

RAM : 256 MB (min), 1 GB (max)

Processor : Pentium IV

Memory : 128 MB

Monitor : 17” color monitor

Keyboard : Logitech

Mouse : Optical

Speed : 600 MHZ (min), 3.2 GHZ (max)

SOFTWARE CONFIGURATION

Operating system : Windows 98

Front-End : Visual Basic 6.0

Back-End : MS Access 2003

3

Page 4: Ticket Booking System

TICKET BOOKING SYSTEM

4

Page 5: Ticket Booking System

TICKET BOOKING SYSTEM

1.4. SOFTWARE FEATURES

ABOUT VISUAL BASIC 6.0

Microsoft Visual Basic is one of the best GUIs and version 6.0 is the latest Version of

the popular programming language. With its new features, Visual Basic is an even stronger

contender in the application development area then ever before.

Microsoft Visual Basic, the fastest and easiest to create applications for Microsoft

windows. Visual Basic provides with a complete set of tools to simplify Rapid Application

Development (RAD).

WHAT IS VISUAL BASIC 6.0?

The “Visual” part refers to the method used to create the graphical user

interface (GUI), Rather than writing numerous lines of code to describe the appearance and

location of interface elements, we simply add rebuilt objects into place on screen. The

“Basic” part refers to the BASIC (Beginners All - Purpose Symbolic Instruction Code)

language, a language used by more programmers than any other language in the history of

computing. Visual Basic has evolved from the original BASIC language and now contains

several hundred statements, functions and keywords, many of which relate directly to the

windows GUI.

The purpose of Visual Basic 6.0 is to develop robust stand-alone application, games,

and utilities less time than it takes in other languages. We can use also ActiveX technology to

create internet-enabled applications that are limited only by our imagination.

Visual Basic 6.0 is the newest addition to the family of Visual Basic products. It

allows us to create Windows applications for our PC without being an expert in C++ or other

programming languages.

Visual basic is a powerful programming language for the development of high level,

graphical based application. It helps the users to enter data in a more simple way using forms.

5

Page 6: Ticket Booking System

TICKET BOOKING SYSTEM

It is much more a programming environment than just a language. It is adaptive to single or

multiple user environments.

Visual Basic introduces some newly advanced features like:

Data access:

Any kind of database can be linked with these visual

basic forms. Accessing records is made easy.

Controls:

The VB applications include different controls such as

Data grid, Data Combo. We can add or remove

controls in a Visual basic application.

Languages:

Some interesting functions are available that helps to

access methods or events.

Wizards:

The application helps to develop wizards that help the

user in a simple way.

The data access is found along with specialized techniques such as object linking and

data binding which is more effective under such techniques. The internet related with this VB

is a dynamic factor. The controls and events play a vital role in creating user friendly

applications.

6

Page 7: Ticket Booking System

TICKET BOOKING SYSTEM

MS-ACCESS

Microsoft Access 2003 is collectively called a database. A database is a

collection of information that is related to a particular subject or purpose, such as tracking

customer records or maintaining a book collection.

Here, you can manage all the information from a single database file. Within the file,

you can use:

Tables to store data.

Queries to find and retrieve the data that is required.

Reports to analyze and print data in a specific layout.

7

Page 8: Ticket Booking System

TICKET BOOKING SYSTEM

2. SYSTEM STUDY

2.1. EXISTING SYSTEM:

The existing system is not flexible as all the procedures with respect to both the

search and show process is done manually.

This increases the paper work of the office which includes the ticket booking and

ticket cancellation works.

Thus there arises confusion because it will be confusing to check all the details.

DRAWBACKS OF THE EXISTING SYSTEM

1.1. Readability of records is constrainedReadability of records is constrained

All the records may not be handled or written by the same

person. So the format will be different resulting in loss.

2.2. Paper records are easily damaged with timePaper records are easily damaged with time

The life time of paper records are very less that it easily gets

damaged. It faces the risk of loss of data.

3.3. Expenditure is highExpenditure is high

Manual system need more man power for its functioning than

computer systems. Expenditure is high in terms of salary and time.

4.4. SecuritySecurity

The manual system losses the security because it is handled by

many number of persons to enter the transactions. No proper handling of

manipulation of data.

8

Page 9: Ticket Booking System

TICKET BOOKING SYSTEM

5.5. Need lot of manpowerNeed lot of manpower

The manual system in the existing system needs lot of

manpower to maintain various details in each section.

2.2. PROPOSED SYSTEM:

The proposed system overcomes all the limitations of the existing system. And it

gives a clear view of the work to be done. It maintains the data safe and secure. The

system moreover builds a better communication between the users.

The report is generated from the list of orders and there is no chance of missing even

a single item.

MERITS

Involves faster processing of data,

Flexible,

Very less paper work,

Easy availability of data and

Cost effective

9

Page 10: Ticket Booking System

TICKET BOOKING SYSTEM

3. SYSTEM ANALYSIS

3.1. DATA FOLW DIAGRAM

10

Page 11: Ticket Booking System

TICKET BOOKING SYSTEM

3.2. ENTITY RELATIONSHIP DIAGRAM

11

Page 12: Ticket Booking System

TICKET BOOKING SYSTEM

4. SYSTEM DESIGN

4.1 TABLE DESIGN

1. Table Name: Employee Details

PrimaryKey: empid

Field Name Data Type Size Description

empid Text 9 Employee ID

empname Text 50 Employee Name

dob Date/Time - Date Of Birth

doj Date/Time - Date Of Joining

design Text 50 Designation(Post)

salary Double 8 Salary of an Employee

dept Text 50 Department of an Employee

12

Page 13: Ticket Booking System

TICKET BOOKING SYSTEM

2. Table Name: Ticket Details

PrimaryKey: transid

Field Name Data Type Size Description

transid Integer 2 Transaction ID of A Ticket

childtic Integer 2 Number Of Child Tickets

adulttic Integer 2 Number Of Adult Tickets

tottic Integer 2 Total Number Of Tickets

amount Double 8 Total Amount

dob Date/Time - Date Of Booking

13

Page 14: Ticket Booking System

TICKET BOOKING SYSTEM

4.2. INPUT DESIGN

The input design is the process of entering data to the system. The input design goal is

to enter to the computer as accurate as possible. Here inputs are designed effectively so that

errors made by the operations are minimized. The inputs to the system have been designed in

such a way that manual forms and the inputs are coordinated where the data elements are

common to the source document and to the input. The input is acceptable and understandable

by the users who are using it.

The quality of the system input determines the quality for system output. Input

specification describes the manner in which data entered the system processing.

Input design is the process of converting user-originated inputs to a computer-based

format input data are collected and organized into group of similar data. Once identified,

appropriate input media are selected for processing.

The input design also determines the user to interact efficiently with the system. Input

design is a part of overall system design that requires special attention because it is the

common source for data processing error. The goal of designing input data is to make entry

easy and free from errors.

Five objectives of the input design are:

1. Effectiveness

2. Accuracy

3. Ease to use

4. Consistency

5. Attractiveness

The main objectives that are done during the input design are:

i. Data is collected from the source

ii. Transfer of data to an input form is done

iii. Data is converted to a computer acceptable form

iv. The converted data is verified

v. Data is checked for its accuracy

14

Page 15: Ticket Booking System

TICKET BOOKING SYSTEM

4.3. OUTPUT DESIGN

The output design was done so that results of processing could be communicated to

the users. The various outputs have been designed in such a way that they represent the same

format that the office and management used to.

Computer output is the most important and direct source of information to the user.

Efficient, intelligible output design should improve the systems relationships with the user

and help in decision making. A major form of output is the hardcopy from the printer.

Output requirements are designed during system analysis. A good starting point for

the output design is the Data Flow Diagram (DFD). Human factors educe issues for design

involves addressing internal controls to ensure readability.

15

Page 16: Ticket Booking System

TICKET BOOKING SYSTEM

5. SYSTEM TESTING AND IMPLEMENTATION

5.1. UNIT TESTING

Unit testing is concerned with the testing of a small module. Using the detailed design

description as a guide, important control paths are tested to uncover the errors within the

boundary of the module. The module interface is tested to ensure that the information flows

in and out of the program unit under test. The local data structure is ensured that the variables

are exercised to ensure that all statements in the module are executed at least once. Number

of input/output operations, database exceptions and expressions are also tested in each and

every module.

5.2 INTEGRATION TESTING

Integration testing is proceeded with bottom up approach. In bottom up integration

testing, an individual module is first tested from a test harness. Once a set of individual

module has been tested, they are then combined into a Collection of modules, known as

builds, which are then by a second harness. This process can combine until the build consists

of the entire application. The main objective of the integration testing is to take the unit tested

modules and to build a program structure that has been dictated by design. Once all modules

are unit tested they are put together for integration testing process. All the unit-tested

modules are combined and integrated. This type of testing is a must because the information

can be lost across an interface. One module can have an inadvertent, adverse effect on the

other sub functions may not produce desired results when integrated.

5.3 VALIDATION TESTING:

The validation testing provides a way for validating all the inputs entered by the user. It

also helps in notifying the cross committed. This is the method for testing the incorrect

inputs.

16

Page 17: Ticket Booking System

TICKET BOOKING SYSTEM

5.4 SYSTEM TESTING

Testing is a process used to help identify the correctness, completeness and quality of

developed computer software. There are many approaches to software testing, but effective

testing of complex products is essentially a process of investigation, not merely a matter of

creating and following rote procedure. One definition of testing is “the process of questioning

a product in order to evaluate it”, where the “questions” are thing the tester tries to do with

the product answers with its behavior in reaction to the probing of the tester.

The quality of the application can and normally does vary widely from system to

system but some of the common quality attributes include reliability, stability, portability,

maintainability and usability.

Testing objective include

Testing is a process of executing a program with the intent of finding

an error.

A good test case is one that has a high probability of finding an as yet

undiscovered error.

A successful test is one that uncovers an as yet undiscovered error.

Testing should systematically uncover different classes of errors in a minimum

amount of time and with a minimum amount of effort, a benefit of testing is that it

demonstrates that the software appears to be working as stated in the specifications. The data

collected through testing can also provide an indication of the software‘s reliability and

quality. But, testing cannot show the absence of defect—it can only show that software

defects are present.

17

Page 18: Ticket Booking System

TICKET BOOKING SYSTEM

5.5. SYSTEM IMPLEMENTATION:

System implementation is the stage in the project where the theoretical design is turned

into working system. The most crucial stage is giving the users confidence that the new system

will work effectively and efficiently.

The performance of reliability of the system was tested and it gained acceptance. The

system implemented successfully. Implementation is a process that means converting a new

system into operation.

Proper implementation is essential to provide a reliable system to meet organization

requirements. During the implementation stage a live demonstration was undertaken and

made in front of end-users. The various features provided in the system where discussed

during implementation

The following are the steps involved in the implementation Plan:

Test information system with sample data

Detection and correction of errors

Make necessary information changes in the system

Check information with the existing system

Installment of hardware and software

18

Page 19: Ticket Booking System

TICKET BOOKING SYSTEM

6. SCOPE FOR FURTHER ENHANCEMENT

The software has been developed in such a way that it can accept modifications and

further changes. The software is very user friendly and future any changes can be done

easily.

Software restructuring is carried out. Software restructuring modifies source code in an

effort to make it amenable to future changes.

To enrich the application usage and time consumption this system could be implemented

in network environment. Thus the backend for this project can be modified like that to

give the feature.

19

Page 20: Ticket Booking System

TICKET BOOKING SYSTEM

7. CONCLUSION

The project, which was done in TICKET BOOKING SYSTEM, was very useful to

me. This project gave me a good experience to create my own software. This project helped

me to know things in VISUAL BASIC 6.0 and MS-ACCESS 2003.

This project also helped me to obtain detailed knowledge about VISUAL BASIC 6.0

and MS-ACCESS 2003.

This project will satisfy all the requirements of the organization and it is implemented

after carrying out various types of testing and was found to run efficiently.

Advantages

Reduces the time consumption

Fast and Economical

Accurate Calculation

20

Page 21: Ticket Booking System

TICKET BOOKING SYSTEM

BIBLIOGRAPHY

1. Steven Holzner - “VisualBasic 6 programming”,2008 Edition

Dreamtech Publications.

2. Roger S Pressman - “Software Engineering”, 2000 Edition,

Dreamtech Publications.

3. Elias M.Awad, - “System Analysis and Design” Galgotia Publications

Pvt. ltd, 1997, Second Edition.

WEBSITES:

1. WWW.wikipedia.com

2. WWW.codeguru.com

3. WWW.example-code.com

21

Page 22: Ticket Booking System

TICKET BOOKING SYSTEM

APPENDIX

SCREEN SHOTS

LOGIN FORM:

22

Page 23: Ticket Booking System

TICKET BOOKING SYSTEM

EMPLOYEE DETAILS:

23

Page 24: Ticket Booking System

TICKET BOOKING SYSTEM

TICKET BOOKING FORM:

24

Page 25: Ticket Booking System

TICKET BOOKING SYSTEM

TICKET CANCELLATION:

25

Page 26: Ticket Booking System

TICKET BOOKING SYSTEM

EMPLOYEE DETAILS VIEW:

26

Page 27: Ticket Booking System

TICKET BOOKING SYSTEM

TICKET BOOKING VIEW:

27

Page 28: Ticket Booking System

TICKET BOOKING SYSTEM

DATE WISE REPORT:

28

Page 29: Ticket Booking System

TICKET BOOKING SYSTEM

EMPLOYEE DETAILS REPORT:

29

Page 30: Ticket Booking System

TICKET BOOKING SYSTEM

TICKET BOOKED REPORTS:

30

Page 31: Ticket Booking System

TICKET BOOKING SYSTEM

SAMPLE CODING

Date Wise Report

Dim rs1 As RecordsetDim db As DatabasePrivate Sub Calendar1_Click()Label1.Caption = Format(Calendar1.Value, "DD/MM/YYYY")End Sub

Private Sub Command1_Click()Dim i As IntegerDim total_amount As LongDim d As Dated = Label1.CaptionMSFlexGrid1.ClearMSFlexGrid1.Rows = 3 With MSFlexGrid1 .TextMatrix(.Rows - 3, 0) = "Transaction ID" .TextMatrix(.Rows - 3, 1) = "Child Ticket" .TextMatrix(.Rows - 3, 2) = "Adult Ticket" .TextMatrix(.Rows - 3, 3) = "Total Ticket" .TextMatrix(.Rows - 3, 4) = "Date Of Booking" .TextMatrix(.Rows - 3, 5) = "Amount" .TextMatrix(.Rows - 2, 5) = 0 End Withi = 0

rs1.MoveFirstWhile Not rs1.EOFIf d = rs1.Fields(5) Then

With MSFlexGrid1 .TextMatrix(.Rows - 2, 0) = rs1.Fields("transid") .TextMatrix(.Rows - 2, 1) = rs1.Fields("childtic") .TextMatrix(.Rows - 2, 2) = rs1.Fields("adulttic") .TextMatrix(.Rows - 2, 3) = rs1.Fields("tottic") .TextMatrix(.Rows - 2, 4) = rs1.Fields("dob") .TextMatrix(.Rows - 2, 5) = rs1.Fields("amount") .Rows = .Rows + 1End With

i = 1End If

31

Page 32: Ticket Booking System

TICKET BOOKING SYSTEM

rs1.MoveNextWend

If i = 0 Then MsgBox ("No Such Data Found") Exit SubEnd Iftotal_amount = 0For i = 1 To MSFlexGrid1.Rows - 3 total_amount = total_amount + Val(MSFlexGrid1.TextMatrix(i, 5))Next i

MSFlexGrid1.TextMatrix(MSFlexGrid1.Rows - 1, 5) = total_amountLabel2.Caption = "Rs. "Label2.Caption = Label2.Caption & Val(MSFlexGrid1.TextMatrix(MSFlexGrid1.Rows - 1, 5))Label2.Caption = Label2.Caption & ".00"

End Sub

Private Sub Form_Load()Set db = OpenDatabase("G:\Sujai Completed Project\btticket.mdb") Set rs1 = db.OpenRecordset("Ticket") With MSFlexGrid1 .Rows = .Rows + 1 .TextMatrix(.Rows - 3, 0) = "Transaction ID" .TextMatrix(.Rows - 3, 1) = "Child Ticket" .TextMatrix(.Rows - 3, 2) = "Adult Ticket" .TextMatrix(.Rows - 3, 3) = "Total Tickets" .TextMatrix(.Rows - 3, 4) = "Date Of Booking" .TextMatrix(.Rows - 3, 5) = "Amount" .TextMatrix(.Rows - 2, 5) = 0 End WithEnd Sub

TICKET BOOKING MODULE:Private Sub Command8_Click()Dim bno, temp As Long Data1.Recordset.MoveFirst bno = Data1.Recordset.Fields("transid") Data1.Recordset.MoveNext While Not Data1.Recordset.EOF temp = Data1.Recordset.Fields("transid") If bno < temp Then bno = temp End If Data1.Recordset.MoveNext Wend Label5.Caption = bno + 1

32

Page 33: Ticket Booking System

TICKET BOOKING SYSTEM

End SubPrivate Sub Command1_Click()Label10.Caption = Text7.Text * Label8.CaptionLabel8.Caption = " "Label9.Caption = Text7.TextEnd Sub

Private Sub Command2_Click()Data1.Recordset.AddNewData1.Recordset.Fields(0) = Label5.CaptionData1.Recordset.Fields(1) = Text7.TextData1.Recordset.Fields(2) = Text8.TextData1.Recordset.Fields(3) = Label9.CaptionData1.Recordset.Fields(4) = Label10.CaptionData1.Recordset.Fields(5) = Label4.CaptionData1.Recordset.UpdateMsgBox "Ticket Booked"End Sub

Private Sub Command3_Click()Label10.Caption = Label10.Caption + (Text8.Text * Label8.Caption)Label8.Caption = " "Label9.Caption = Val(Label9.Caption) + Val(Text8.Text)End Sub

Private Sub Command4_Click()Label5.Caption = " "Text7.Text = " "Text8.Text = " "Label9.Caption = " "Label10.Caption = " "End Sub

Private Sub Command5_Click()TicketBooking.PrintFormEnd Sub

Private Sub Command6_Click()Unload MeEnd Sub

Private Sub Command7_Click()Form2.ShowEnd Sub

Private Sub Option1_Click() Label8.Caption = 200End Sub

Private Sub Option2_Click()

33

Page 34: Ticket Booking System

TICKET BOOKING SYSTEM

Label8.Caption = 350End Sub

Private Sub Timer1_Timer()Label4.Caption = Date$End SubTICKET CANCELLATION:

Private Sub Command1_Click()Unload MeEnd Sub

Private Sub Command2_Click()While Not Data1.Recordset.EOF If Text1.Text = Data1.Recordset.Fields(0) Then Label7.Caption = Data1.Recordset.Fields(1) Label8.Caption = Data1.Recordset.Fields(2) Label9.Caption = Data1.Recordset.Fields(3) Label10.Caption = Data1.Recordset.Fields(4) GoTo e End If Data1.Recordset.MoveNextWendMsgBox " Transaction ID does not exist"e:End Sub

Private Sub Command4_Click()confirm = MsgBox("You want to delete", vbYesNo, "Delete conirmation")If confirm = vbYes ThenData1.Recordset.DeleteMsgBox "Ticket Cancelled"Else MsgBox "Ticket Not Cancelled"End IfText1.Text = " "Label7.Caption = " "Label8.Caption = " "Label9.Caption = " "Label10.Caption = " "End Sub

Private Sub Timer1_Timer()Label11.Caption = Date$End Sub

34