Introduction
What the problem is, who it hurts, and what you set out to do about it.
Chapter 1 has one job: convince the reader that there is a real problem worth spending 165 pages on, and tell them exactly what you are going to do about it.
It runs from page 12 to page 19 of your thesis.
The problem, in ordinary words
Hotels, guesthouses and beach villas in Sri Lanka are not only places to sleep. They are where the nightlife happens. Beach parties, live acoustic music, cultural shows, themed dinners. For a lot of travellers, those events are a reason to stay an extra night, which is money for the local economy.
But the way those events get announced and booked has not changed in years:
- A chalkboard at the front desk
- Printed flyers
- A post on a Facebook page nobody follows
- A WhatsApp group that only current guests are in
And bookings are the same. A phone call, a WhatsApp message, or somebody turning up at the door.
There is no shared place where a hotel can show its event to a traveller who is not already staying there. And there is no single page where a traveller can compare what is on tonight across several hotels.
Which hurts both sides, differently
The hotel loses money
No way to predict how many people will come. So they over-order food and drink, or over-schedule staff, or run out and turn people away. All three cost money.
The traveller loses the experience
They find out about an event after it happened. Or they arrive and the tickets, the drinks package or the parking are already gone.
And the tools that exist do not fix it. Booking.com sells room nights and does not know about tonight's beach party. Eventbrite sells event tickets and does not know whether the hotel has a room left. Neither of them coordinates tickets, rooms, meals and parking together for one hotel's evening.
The scope, which is a question you will be asked
The scope of your study is national. The target population is hotels, guesthouses and villas across Sri Lanka that host social events for tourists.
The Southern Province coastal belt, and specifically the Mirissa and Matara area, is the primary case setting inside that national scope. It is where the data was collected. It is not the limit of what the study claims.
Three reasons that belt was chosen, and you should be able to give all three:
- Density The province holds one of the largest concentrations of registered small and medium coastal accommodation in the country, and among the highest volumes of leisure visitors outside the Western Province.
- Frequency Properties there run an almost continuous calendar of social events, so the coordination problem happens often enough to actually study. A lower-density region would not give you enough organisers who face it.
- Typicality Published research on hospitality operations in the deep south documents an operational profile, limited resources and informal coordination, that matches small and medium operators elsewhere in Sri Lanka. That is what lets you generalise from this setting to the national population.
The research question
How can an integrated, smart tourism event management system improve resource coordination and Coordination Effectiveness for hotel event organisers and tourists in Sri Lanka?
Underneath it sit four sub-questions. Notice that the first three line up exactly with your three independent variables, and the fourth is about whether anyone would actually use the thing.
| No | Sub-question | Links to |
|---|---|---|
| 1 | How does real-time event visibility affect event attendance and Coordination Effectiveness for organisers and tourists? | IV1 / H1 |
| 2 | How do online pre-booking and resource coordination mechanisms affect operational planning accuracy for organisers and booking confidence for tourists? | IV2 / H2 |
| 3 | How does centralized information access affect decision-making and coordination efficiency for both organisers and tourists? | IV3 / H3 |
| 4 | To what extent would hotel event organisers in Sri Lanka adopt a centralized platform for listing events and managing bookings? | Adoption intent |
The aim and the four objectives
The aim is one sentence: to design, develop and evaluate a Smart Tourism Event Management System that streamlines event promotion and resource coordination for hotels in Sri Lanka, while evaluating the adoption intent of both organisers and tourists.
The objectives are the four steps that get you there. Chapter 7 goes back and marks each one, so learn them in order.
| No | Objective | Where it was done | Result |
|---|---|---|---|
| 1 | Identify the current challenges and limitations organisers and tourists face around event discovery, resource booking and operational planning | Chapter 4, surveys and thematic analysis | Done |
| 2 | Analyse the statistical relationships between the three independent variables and the dependent variable | Chapter 4, the full analysis | Done |
| 3 | Design and develop a web-based prototype implementing event listing, multi-resource booking and a centralized organiser dashboard | Chapter 5 | Done |
| 4 | Evaluate the prototype's functional performance through scenario-based testing, and assess adoption intent | Chapter 6 and Chapter 4 | Partly |
Two halves. The adoption intent half is complete and was measured properly. The functional testing half is complete, with 10 of 10 test cases passed.
What was not done is the usability study with real participants. That leaves one requirement, NFR-06, specified but never verified. Your thesis says so openly. Do not try to hide it.
What is in and what is out
| In scope | Out of scope |
|---|---|
| Hotel-hosted events across Sri Lanka, with the Southern coastal belt as the case setting | Events outside Sri Lanka |
| Social events: beach parties, music nights, cultural shows, themed dinners | Public infrastructure events, large conferences, private tours |
| Event listing, multi-resource pre-booking, organiser dashboard | Real payment processing and payment gateway integration |
| Scenario-based prototype testing and survey validation | Production-scale load testing, hardware sensor integration |
Someone will notice your system does not take money. That is deliberate and documented, not a gap. Bookings are recorded with a total and marked as pending payment. Integrating a payment gateway adds regulatory and financial complexity that contributes nothing to testing the research question, which is about information coordination, not transactions.
The words in this chapter
A single informal diagram that shows the whole situation at a glance. Who the people are, what flows between them, where the problems are.
Figure 1.1 in your thesis. It shows organisers publishing events and managing inventory on one side, travellers browsing and booking on the other, and a central database in the middle.
The specific thing nobody has studied yet. Not "nobody has built this app", but "nobody has produced knowledge about this".
Chapter 1 states it briefly and Chapter 2 proves it by going through what other researchers actually did. Your gap has three parts, and they are on the Chapter 2 page.
Numbers from this chapter
If they ask you
Why did you only study Mirissa and Matara?
I did not. The scope of the study is national. The target population is hotels, guesthouses and villas across Sri Lanka that host social events.
Data collection was concentrated in the Southern Province coastal belt for three reasons that are stated in Section 3.5.1: it has the densest concentration of small and medium coastal accommodation, it has a high enough event frequency to produce a usable sampling frame of organisers who actually face the problem, and prior research documents an operational profile there that matches small operators nationally, which supports analytical generalisation.
Why does your system not handle payments?
It is declared out of scope in Section 1.10. The research question is about information coordination, not about transactions, so a payment gateway would add regulatory and financial complexity without contributing anything to the thing being tested.
The system still records the server-computed total and marks the booking as pending payment, so the booking record is complete and a payment step could be added without changing the data model.
Is this not just an Eventbrite clone?
No, and Chapter 2 sets out why. Eventbrite is a strong ticketing engine, but it has no concept of a room allocation or a parking slot, and it cannot tell a traveller whether the hotel has space that night.
The contribution here is not ticketing. It is unifying several different kinds of resource, tickets, rooms and add-ons, into one authoritative availability record that both the traveller and the hotel read at the same time. That is the thing the research found actually matters.
Chapter 1 establishes that hotels across Sri Lanka host social events but coordinate them manually, through chalkboards, flyers and WhatsApp. Organisers cannot predict turnout so they over-order or under-order, and travellers either miss events or arrive to find things sold out. The existing tools do not solve it, because room booking platforms ignore events and ticketing platforms ignore rooms. My main research question asks how an integrated system could improve coordination, and I set four objectives: identify the problems, analyse the statistical relationships, build a prototype, and evaluate it along with adoption intent.