9.event booking final report

A Project Report

On "Event Ticket Booking and Scanning System”

Prepared by Sheekha Girish (12IT032)

Under the guidance of

Mr. Sagar Patel

Assistant Professor

A Report Submitted to

Charotar University of Science and Technology

for Partial Fulfillment of the Requirements for the

Degree of Bachelor of Technology

in Information Technology

(8th Semester Software Project Major-IT407)

Submitted at

DEPARTMENT OF INFORMATION TECHNOLOGY

Chandubhai S. Patel Institute of Technology

At: Changa, Dist: Anand – 388421

April 2016

CANDIDATE’S DECLARATION

I hereby declare that the project entitled “Event Ticket Booking and Scanning System” is my own work conducted under the guidance of Mr. Sagar Patel and Mr. Rohan Amin. I further declare that to the best of my knowledge, the project for B. Tech does not contain any part of the work, which has been submitted for the award of any degree either in this University or in other University without proper citation. Sheekha Girish (12IT032) Mr. Sagar Patel Assistant Professor, Department of Information Technology, Faculty of Technology & Engineering, Changa – 388425.

This is to certify that the report entitled “Event Ticket Booking and Scanning

System” is a bonafied work carried out by Ms. Sheekha Girish (12IT032) under the guidance and supervision of Mr. Sagar Patel & Mr. Rohan Amin for the subject Software Project Major (IT407) of 8th Semester of Bachelor of Technology in Information Technology at Faculty of Technology & Engineering– CHARUSAT, Gujarat. To the best of my knowledge and belief, this work embodies the work of candidate herself, has duly been completed, and fulfills the requirement of the ordinance relating to the B.Tech. Degree of the University and is up to the standard in respect of content, presentation and language for being referred to the examiner. Under supervision of, Mr. Sagar Patel Assistant Professor Dept. of Information Technology CSPIT, Changa, Gujarat.

Mr. Rohan Amin Director R&D Milestone Technoconsulting Pvt. Ltd. Ahmedabad, Gujarat Prof. Parth Shah Head & Associate Professor Department of Information Technology CSPIT, Changa, Gujarat.

Chandubhai S Patel Institute of Technology

At: Changa, Ta. Petlad, Dist. Anand, PIN: 388 421. Gujarat

CERTIFICATE

V

Abstract

Event Ticket Booking and Scanning system is an android application that was developed for any user to filter out events happening in their city or locality with a simple filtering of the city venue and date. This application was developed as a competitor to the already existing application BookMyShow. This application is named Evetic. A web application of Evetic already exists. The application will send a pdf of the ticket via email after the event booking which can be either is downloaded in the device or a printout taken. The scanner part of the application involves scanning the tickets at the time of event entry by the event organizer using a barcode or a QR code returning the result as valid, reentry or invalid. Another feature of the application involves booked ticket history available for the users hence preventing the hassle of recovery in case of transaction failures.

VI

Acknowledgement “When we are motivated by goals that have deep meaning, dreams that need completion, pure dedication that needs expressing, then we truly live.” An idea that had been worked on and developed goes to show it’s possible to achieve the impossible. I express my sincere gratitude to our respectful (Head of Department) Prof. Parth D Shah for making laboratory and library facilities available to me that helped me a long way in carrying out project work successfully. I also express my sincere gratitude to Mr. Rohan Amin from Milestone Technoconsulting Pvt. Ltd. Ahmedabad for constantly guiding and supporting me during the duration of the project. I express my gratitude to the help of Mr. Sagar Patel, for his constant supervision, guidance and co-operation throughout the project and for his constant motivation and valuable help through the project work. I extend my sincere gratitude to my parents who have encouraged me with their blessings to do this project successfully. Finally I would like to thank to all my friends, all the teaching and non-teaching staff members of the Information Technology Department, for all the timely help, ideas and encouragement which helped throughout in the completion of project.

VII

Table of Contents Abstract V Acknowledgement VI 1.0 Introduction………………………………………………………………… 1

1.1 Project Overview……………………………………………………. 1 1.2 Objective…………………………………………………………….. 1 1.3 Scope………………………………………………………………… 1 1.4 Tools & Technology Used…………………………………………… 2

2.0 Project Management……………………………………………………….. 3 2.1 Project Planning……………………………………………………… 3

2.1.1 Project Development Approach and Justification ……….. 3 2.1.2 Project Effort and Time, Cost Estimation…………………. 4

2.2 Project Work Scheduling……………………………………………… 5

3.0 System Requirements Study…………………………………………………. 6 3.1 User Characteristics ………………………………………………….. 6

1. Use Case Diagram……………………………………………. 7 3.2 Hardware and Software Requirements……………………………….. 7 3.3 Assumptions and Constraints………………………………………... 9

4.0 System Analysis……………………………………………………………….. 10

4.1 Study of Existing System.…………………………………………… 10 4.2 Limitations of Existing System..…………………………………….. 10 4.3 Requirements of Proposed System…………………………………… 10

VIII

4.3.1 Functional Requirements……………………………………. 10 4.3.2 Non Functional Requirements………………………………. 11

4.4 System Work Flow…………………………………………………… 13 4.5 Class Diagram………………………………………………………… 13 4.6 Activity Diagram……………………………………………………... 14 4.7 Sequence Diagram……………………………………………………. 15 4.8 State Chart Diagram…………………………………………………… 16

5.0 System Design……………………………………………………………….. 18 5.1 Screen layout……………………………………………………………… 18

6.0 System Implementation and Testing………………………………………….. 25 6.1 Coding Standards………………………………………………………….. 25 6.2 Testing Methods………………………………………………………….. 26

7.0 Future Enhancement…………………………………………………………….. 28

8.0 Conclusion……………………………………………………………………… 29

8.1 Self-Analysis of Project Viabilities………………………………………. 29 8.2 Problem Encountered and their Solutions………………………………… 30 8.3 Summary of Project work………………………………………………… 31

References……………………………………………………………………………. 32

IX

List of Figures

Fig. 2.1 Gantt chart……………………………………………………………………. 5 Fig. 3.1 Use Case Diagram……………………………………………………………. 7 Fig. 4.1 System Workflow…………………………………………………………….. 13 Fig. 4.2 Class Diagram………………………………………………………………… 13 Fig. 4.3.1 User Activity Diagram……………………………………………………... 14 Fig. 4.3.2 Event Organizer Activity Diagram ………………………………………… 15 Fig. 4.4 Sequence Diagram…………………………………………………………….. 16 Fig. 4.5 State Chart Diagram…………………………………………………………… 17 Fig. 5.1 Application Icon……………………………………………………………….. 18 Fig. 5.2 Scanner…………………………………………………………………………. 19 Fig. 5.3 QR and Barcode………………………………………………………………… 20 Fig 5.4 Ticket Validation………………………………………………………………... 22 Fig. 5.5 Landing Page…………………………………………………………………… 22 Fig 5.6 Event Listing…………………………………………………………………….. 23 Fig. 5.7 Admin Login……………………………………………………………………… 24

X

List of Tables

Table 6.1 Flags and Exceptions……………………………………………………. 29 Table 8.1 Technical Feasibility of Mobile Application…………………………… 26

PRJ/2016/IT/001 Introduction

CSPIT (IT) 1

1.0 Introduction

1.1 Project Definition The proposed system is a mobile based application. Event ticket booking and scanning system is an application where users can view the events happening in their particular locality, region or country. The users can book the tickets and verification would be sent via email along with the pdf of the ticket. At the day of the event the ticket will be scanned by the organizer using a QR code or a barcode.

1.2 Scope The name of the application is Evetic. A web application of the same already exists. Users can view the events happening in their locality and book the tickets based on it. The application has two parts to it, the users and the event organizer. The ticket is scanned from barcode or QR code and validated as valid, reentry and invalid. The event ticket validation with ticket number is done on the day of the event by the organizer. Booked ticket history will be available for the users and e-tickets could be downloaded. 1.3 Objective The main objective to create this application is to bring about a similar product in the market to increase the competitive nature. BookMyShow is an already existing application used to book events. But BookMyShow is costly for the event organizers. This application aims at providing the platform for the organizers at an affordable range.

PRJ/2016/IT/001 Introduction

CSPIT (IT) 2

At the same time users are able to compare the effectiveness of both the applications and decide which one to opt for. 1.4 Tools & Technology Used

Android Studio (Coding) SQLITE (Database) Android Phone (Application Testing)

PRJ/2016/IT/001 Project Management

CSPIT (IT) 3

2.0 Project Management

2.1 Project Planning

The project is approximately calculated to complete within a period of 4 months. First, the layout design was discussed along with the platform on which is to be worked upon. The study of Android Studio and its execution took about a month to complete then it was preceded with the coding and design portion of the project. At the end after careful evaluation, the project was termed successful.

2.1.1 Project Development Approach and Justification

The approach used to develop this application is agile scrum based methodology. Scrum is part of the Agile movement. Agile is a response to the failure of the dominant software development project management paradigms (including waterfall) and borrows many principles from lean manufacturing. In 2001, 17 pioneers of similar methods met at the Snowbird Ski Resort in Utah and wrote the Agile Manifesto, a declaration of four values and twelve principles. These values and principles stand in stark contrast to the traditional Project Manager’s Body of Knowledge (PMBOK).

The Agile Manifesto placed a new emphasis on communication and collaboration, functioning software, team self-organization, and the flexibility to adapt to emerging business realities. Scrum’s early advocates were inspired by empirical inspect and adapt feedback loops to cope with complexity and risk. Scrum emphasizes decision making from real-world results rather than speculation. Time is divided into short work cadences, known as sprints, typically one week or two weeks long. The product is kept in a potentially shippable (properly integrated and tested) state at all times. At the end of each sprint, stakeholders and team members meet to see a demonstrated potentially shippable product increment and plan its next steps.


CSPIT (IT) 4

Scrum is a simple set of roles, responsibilities, and meetings that never change. By removing unnecessary unpredictability, we’re better able to cope with the necessary unpredictability of continuous discovery and learning.

2.1.2 Project Effort and Time, Cost Estimation Now we will calculate Effort, Cost and Project Duration Estimation using The Basic COCOMO Model which is itself a Heuristic Estimation Technique. As our project is an Application Development, so it will come under the Organic Category. Estimation of Line of Code: Line of code = no. of files * avg. no. of line = 100 * 75 = 7500 = 7.5(KLOC) Estimation of Development Effort: Effort= 2.4(KLOC)1.05 PM = 2.4(7.5)1.05 PM = 2.4(8.3) PM = 19.90 PM = 20 PM Estimation of Development Time: Tdev= 2.5(Effort)0.38 Months = 2.5(20)0.38 Months = 2.5(3.12) Months = 7.80 Months = 8 Months


CSPIT (IT) 5

2.2 Project Work Scheduling

Fig 2.1 Gantt chart

PRJ/2016/IT/001 System Requirements Study

CSPIT (IT) 6

3.0 System Requirements Study

3.1 User Characteristics

Users o The user can view events filter events by city, event name and date. o Users have to create an account to book tickets. o They can book tickets up to a limit of 20. o They can proceed to buy tickets using PayPal. o The users can download the pdf of the ticket that is sent via mail or keep the pdf in

the phone. o In case of error regarding email, users can go to their booked history on the

application for the verification mail to be sent again.

Event Organizers o The organizers can create various events in a locality. o They need to have an account in the application. o The event is made available to the users by them describing the event. o They can determine the amount of tickets to be made available. o On the day of the event, the scanner part is made available to them for scanning

tickets.

Administrator o The administrator has the full-fledged rights over the application.. o Can create/delete events. o Can view the accounts and events. o Can change the password.


CSPIT (IT) 7

o Can hide any kind of features from the both of users and event organizers. o Insert/delete/edit the information of available on application. o Can access all the accounts of the users/event organizers.

Fig 3.1 Use Case Diagram

3.2 Hardware and Software Requirements

FRONTEND: Android Studio

Android Studio is the official integrated development environment (IDE) for Android platform development.

Android-specific refactoring and quick fixes. Lint tools to catch performance, usability, version compatibility and other problems. ProGuard integration and app-signing capabilities. Template-based wizards to create common Android designs and components.


CSPIT (IT) 8

A rich layout editor that allows users to drag-and-drop UI components, option to preview layouts on multiple screen configurations.

Support for building Android Wear apps Built-in support for Google Cloud Platform, enabling integration with Google Cloud

Messaging and App Engine.

BACKEND: SQLITE SQLite is a relational database management system contained in a C programming library. In contrast to many other database management systems, SQLite is not a client–server database engine. Rather, it is embedded into the end program. SQLite is ACID-compliant and implements most of the SQL standard, using a dynamically and weakly typed SQL syntax that does not guarantee the domain integrity. SQLite is a popular choice as embedded database software for local/client storage in application software such as web browsers. It is arguably the most widely deployed database engine, as it is used today by several widespread browsers, operating systems, and embedded systems, among others. SQLite has bindings to many programming languages.

JSON Restful Web services JavaScript Object Notation is an open standard format that uses human text to transmit data objects consisting of attribute–value pairs. It is the most common data format used for asynchronous browser/server communication (AJAJ), largely replacing XML which is used by AJAX. JSON is a language-independent data format. It derived from JavaScript, but now code to generate and parse JSON-format data is available in many programming languages. The official Internet media type for JSON is application/json. The JSON filename extension is .json.


CSPIT (IT) 9

3.3 Assumptions and Dependencies

All the users of the system that is the user, the event organizer and the administrator need to have their accounts to access the different part of the application.

The user browses and selects the events. Tickets are then booked and purchased through PayPal. The organizer has to undergo event creation and maintaining the demand and sale

of tickets. The administrator and the event organizer work side by side in creating the events

and maintaining them. The administrator takes care of the whole system. The scanner part of the application is made available to the organizer and not the

user.

PRJ/2016/IT/001 System Analysis

CSPIT (IT) 10

4.0 System Analysis

4.1 Study of Existing System BookMyShow is India's biggest online movie and events ticketing brand. The website caters to ticket sales for movies, plays, concerts and sporting events via the online platform. Launched in 1999, it is headquartered in Mumbai, Maharashtra. It also has offices in New Delhi, Bangalore, Hyderabad, Chennai and Kolkata.BookMyShow reaches about 800 to 900 cinemas in 200 cities and towns. About 60 percent of its transactions take place via its mobile app which, say experts, is the most successful mobile ecommerce app in the country. 4.2 Limitations of Existing System BookMyShow is costly for the event organizers. Evetic application aims at providing the platform for the organizers at an affordable range. At the same time users are able to compare the effectiveness of both the applications and decide which one to opt for. When there is no competition there is no platform for growth. 4.3 Requirements of Proposed System

4.3.1 Functional Requirements

The application is an alternate option for the users to view and book events. Only authorized person can access related details. The users will register themselves on the application to book tickets. Organizers can change their information regarding the events. Organizers can scan the tickets at the time of event. Administrator will be responsible for the overall maintenance of the application. The scanning of ticket will be validated as valid, re-entry or invalid.

PRJ/2016/IT/001 Study of Existing System

CSPIT (IT) 11

The ticket will be sent via email which can be downloaded or printed. In case of error in email, the user can go to the booked ticket history and re send

the mail.

4.3.2 Non Functional Requirements

Before Application Development:

Justification for Application Development. o Describe the problem and how the application is useful to solve that

problem. o The app’s focus has a strong connection to the target people. o Is it innovative or already available in store? If available then, how it is

different than available? Justification for the tools and technology used for the Application Development.

o Comparison of different technology available for application development and justification for your choice.

o Specification of tools and technology used for your application development.

Justification for Hardware and Device selection. o Justification and specification of hardware selection like, processor, RAM,

OS version, etc. o List of compatible devices on which the application will run.

At the time of Application Development:

Auto adjustment of GUI. o Usage of proper Layouts for GUI making. It should be in auto adjust GUI

for different cell phone with different OS and also for different tablets. o App offers flexibility to alter content and settings to meet people’s needs.

Coding convention. o Structure of the Application.


CSPIT (IT) 12

Maintain .manifest file, .java files, and .xml files properly. Maintain images in all four packages.

o Naming Conventions. (Class, Objects, Methods, Variables, etc.) o Proper comments (e.g. description of method in comment.) o Study of proper License of Agreements.

Application should be multithreaded. Proper Notification for process/task.

o Proper notification/Confirmation at the time of completion of any task or process.

o Progress-bar while loading. All necessary validation.

o Email Id validation. o Password validation.

Email Verification. Auto-update while connect with internet. Feedback functionality is necessary.

After Application Development:

Application file size should be as minimum as possible. (<50 Mb). Easy installation and Easy availability of application.

o Application should be easily installable in provided list of devices. o Application should be available in store.

List of different test cases. o Application should run on different cell phone with different OS versions

and at least one tablet.


CSPIT (IT) 13

4.4 System Work Flow

Fig. 4.1 System Workflow

4.5 Class Diagram

Fig. 4.2 Class Diagram


CSPIT (IT) 14

4.6 Activity Diagram

Fig. 4.3.1 User Activity Diagram


CSPIT (IT) 15

Fig. 4.3.2 Event Organizer Activity Diagram


CSPIT (IT) 16

4.7 Sequence Diagram

Fig. 4.4 Sequence Diagram


CSPIT (IT) 17

4.8 State Chart Diagram

Fig. 4.5 State Chart Diagram

PRJ/2016/IT/001 System Design

CSPIT (IT) 18

5.0 System Design 5.1 Screen layout

Fig. 5.1 Application Icon

The icon for the evetic application.


CSPIT (IT) 19

Fig. 5.2 Scanner

The scanner part of the application that is available to the event organizer.


CSPIT (IT) 20

Fig. 5.3 QR and Barcode

The pdf of the ticket contains a barcode and QR code which is used for scanning.


CSPIT (IT) 21

Fig. 5.4 Ticket Validation


CSPIT (IT) 22

The scanner will contact the evetic server to confirm the ticket number and will be validated as valid, re-entry or invalid.

Fig. 5.5 Landing Page


CSPIT (IT) 23

This page shall be the lading page of the application. It shall display the events and their description.

Fig. 5.6 Event Listing

This is the event listing page of the application mostly used by the event organizer.


CSPIT (IT) 24

Fig. 5.7 Admin Login

The page for the admin to login and update the events.

PRJ/2016/IT/001 System Implementation and Testing

CSPIT (IT) 25

6.0 System Implementation and Testing 6.1 Coding Standards

Write short methods – No official limit, but try to keep methods short and focused. Think often about how to refactor your code to break it into smaller and more reusable pieces. This is good advice in any language.

This also shows why overly strict rules on the length of comments can be counterproductive by encouraging developers to write long methods to avoid writing docs. Keep lines short – They have a strict rule of 100 characters except for imports or comments that contain URLs or commands that cannot be broken up. Not sure 100 is the magic number, but short lines are good practice anyhow.

Use JavaDoc from the beginning – Don’t wait until the code is finished. Short comments are fine, but use some. Explain purpose and non-obvious behavior. Don’t explain standard Java constructs. Document every class

/** Represents a collection of Blahs. Used to … **/ public class Foo { … } Document anything public – Methods – Constructors – Instance variables (but

very rare to have public ones) • Use @Override when you override methods from parent class –

Won’t be caught until run time public void oncreate(Bundle savedInstanceState)

{ … } – Will be caught at compile time @Override public void oncreate(Bundle savedInstanceState) { … }


CSPIT (IT) 26

Avoid empty catch blocks – Yes try { … } catch(SomeException se) { doSomethingReal(); } – No try { … } catch(SomeException se) { } – Marty’s opinion • Usually, but not always, a good rule

List each Exception type – Yes try { … } catch(ExceptionType1 et1) { … } catch(ExceptionType2 et2) { … } – No try { … } catch(Exception e) { … }

6.2 Testing Methods Monkey Runner is the tool used for testing. The monkey runner tool provides an API for writing programs that control an Android device or emulator from outside of Android code. With monkey runner, you can write a Python program that installs an Android application or test package, runs it, sends keystrokes to it, takes screenshots of its user interface, and stores screenshots on the workstation. The monkey runner tool is primarily designed to test applications and devices at the functional/framework level and for running unit test suites, but you are free to use it for other purposes. The monkey runner tool is not related to the UI/Application Exerciser Monkey, also known as the monkey tool. The monkey tool runs in an adb shell directly on the device or emulator and generates pseudo-random streams of user and system events. In comparison, the monkey runner tool controls devices and emulators from a workstation by sending specific commands and events from an API.

Argument Description

-plugin <plugin_jar>

(Optional) Specifies a .jar file containing a plugin for monkeyrunner. To learn more about monkeyrunner plugins, see Extending monkeyrunner with plugins. To specify more than one file, include the argument multiple times.


CSPIT (IT) 27

<program_filename> If you provide this argument, the monkeyrunner command runs the contents of the file as a Python program. If the argument is not provided, the command starts an interactive session.

<program_options> (Optional) Flags and arguments for the program in <program_file>.

Table 6.1 Flags and Exceptions

PRJ/2016/IT/001 Future Enhancement

CSPIT (IT) 28

7.0 Future Enhancement

The application has been designed at the maximum possible excellence. Still we accept drawbacks, as it is a human effort. As of now, the application is working as per requirements. The design part of the application is lacking as the android application designer is unavailable at the moment.

PRJ/2016/IT/001 Conclusion

CSPIT (IT) 29

8.0 Conclusion

8.1 Self Analysis of Project Viabilities Technology Issues Market Issues

Performance Ease of learning Ease of deployment Ease of support Operational characteristics (i.e. can it run 7 days a week, 24 hours a day?) Interoperability with your other key technologies Scalability

Vendor viability (i.e. is it likely that they will be in business in two years? In five?) Alternate sources for the technology, if any Third-party support for related products and services Level of support provided by the vendor Industry mindshare of the product (i.e. is the market gravitating toward or away from this technology?)

Table 8.1 Technical Feasibility of Mobile Application.

8.2 Problem Encountered and their Solutions

Problem in User Interface Android does not follow a common UI process during their application development. Google till date has not introduced a common User Interface rule that needs to be followed. This in turn has led to certain applications being incompatible with certain devices. So android developers and designers should make sure they must build applications with responsive layout.

Software Fragmentation Issue Several versions of Android operating system are available on different devices. Timely upgrades change the version of Android OS that runs on the device. This

PRJ/2016/IT/001 Conclusion

CSPIT (IT) 30

implies that the developers can’t just focus on the most recent versions of the OS as not everyone upgrades their devices. It is inconvenient for many users to upgrade their operating systems because manufacturers play a vital role in device configuration.

Usage of Third Party API Certain third party API is device dependent and this restricts the usage of many apps across different devices. The SDK and cross-platform IDE does not allow android developers to use a single API across the range of versions.

Security Issue Recently Android mobile devices are getting affected by malware that is similar to PCs as a result of extensive internet usage. Lack of stringent rules in the area of software fragmentation in Android has led to proliferation of malware threats. To make things worse these security issues are quite difficult to fix and it is often one of the biggest challenges faced by android developers.

Patent Issue

Android is open source so there is a possibility for imitation of applications that already exist. Many a times user interface and scenario of the application vary but the concept would have an obvious similarity with the existing applications. One of the reasons for this issue is there are no prescribed quality check rules for uploading apps in Android play store.

PRJ/2016/IT/001

CSPIT (IT) 31

8.3 Summary of Project work

The project has been planned to complete within a period of 6 months. Event ticket booking and scanning system for android platform was discussed prior January 1st, 2016. The month of January involved the study of android and its tool used for implementation that is android studio. In the month of February, it was preceded with implementation starting with the UI layout. Later on it was preceded with the back end connection to the web server Evetic. The database used is SQLITE. Month of March involved integration of the UI with the backend. Month of April concluded the testing of the application and the various scenarios possible that had to be dealt with before application release in to the market. The duration of the project has been 4 months starting from 1st January,2016 – 29th April, 2016. All aspects regarding the client view and the development team ideas were considered for the successful implementation of this project.

PRJ/2016/IT/001

CSPIT (IT) 32

References

1) Ryan Hodson(2014) Android Programming Succinctly Sync fusion Inc. ,USA 2) TheNewBoston:

https://www.youtube.com/playlist?list=PL6gx4Cwl9DGBsvRxJJOzG4r4k_zLKrnxl

3) www.developer.android.com 4) www.tutorialspoint.com/android 5) [4] Software Requirements Specification for Problem Based Learning Module,

Souman Mandal, 2010. 6) [5] Software Design Specification (SDS) Acropolis Course Management System,

2011 7) [6] IEEE Recommended Practice for Software Requirements Specifications,

Software Engineering Standards Committee of the IEEE Computer Society. 1998 8) [7] Software Requirements Specification for PPDP Contact Management System

(CMS) 9) [8] http://www.ehow.com/facts_5156877_preface-book.html, Sat. 29/10/2011. 10) [9]http://www.sil.org/lingualinks/literacy/referencematerials/glossaryofliteracyter

ms/WhatIsAPreface.htm, Sat. 29/10/2011.

9.event booking final report

Documents