HS

Hasara Research Guide

Your final year research project, explained from the beginning. Enter the password to open it.

Oyage final year research project eka, mul idan therum kara denawa. Password eka denna.

It only asks once on this device.

Start here
SI
Start here

Your research, explained from the beginning

You built something real and you proved something real. This guide walks through all of it in plain language, one page at a time. Nothing here assumes you remember the technical words.

If you only read one box on this whole site

Hotels in Sri Lanka host social events and organise them on chalkboards and WhatsApp. So the hotel never knows how many people are coming, and the traveller never knows what is still available.

You asked 104 people which of three possible fixes would actually help. Only one of them mattered: putting all the information in one single trusted place. The same answer came out of two separate groups of people.

Then you built a working website that does exactly that, and you tested it until you could prove it works.

What you actually did, in six steps

  1. You found a real problem Hotels, guesthouses and beach villas across Sri Lanka host beach parties, live music nights, cultural shows and themed dinners. They announce them badly and they take bookings by phone and WhatsApp. Both sides lose.
  2. You read what other researchers had already done Ticketing systems, tourism platforms, hotel booking systems. You found the exact hole: nobody had studied a system that handles tickets, rooms, meals and parking together for small hotel events, and nobody had asked small Sri Lankan hotel owners whether they would even use one.
  3. You wrote down three guesses before collecting any data Guess one, live visibility would fix it. Guess two, advance booking would fix it. Guess three, one central source of information would fix it. Writing them down first is what makes the study a real test.
  4. You surveyed two separate groups 64 travellers and 40 hotel organisers, with matching questionnaires so the same idea could be tested twice, independently.
  5. The numbers gave a clear answer Only guess three survived. And it survived in both groups. Guesses one and two turned out to work through guess three rather than on their own.
  6. You built the system that the answer demanded A website called EVENTIA. Its whole design comes from that finding, right down to how the database is arranged. Then you tested it and it passed every test.

The four sentences that cover everything

Memorise these

One. The problem is not that there is too little information about hotel events. The problem is that the information that exists cannot be trusted, because it lives in five different places and none of them agree.

Two. Of the three things that could fix that, only unifying the information has a measurable effect of its own, and it came out that way in two independent samples.

Three. So the system was built with one single inventory table, so that tickets, rooms and add-ons share one availability number that everybody reads.

Four. The system was then tested against the exact requirements the survey produced, and all of them passed.

How to use this guide

Read the pages in order the first time. Each one takes 5 to 10 minutes. After that, jump wherever you need to.

Three things repeat on every page, so you learn to look for them:

Plain English boxes

The bordered boxes translate something technical into ordinary words. If a page confuses you, find the nearest one of these.

Word boxes

The grey boxes explain a single term: what it means, and why it is in your thesis specifically. Do not skip them. Examiners want to hear the real word used correctly.

Say this out loud

The dark boxes are written to be spoken. Read them aloud once. They are the answer if someone asks about that page.

Every page on this site

01 The words, from zeroHypothesis, variable, reliability, regression, artefact. Every hard word in one place, explained like you have never heard it before. 02 How it happenedThe project changed twice. Why the old presentation says something different, and which version is the real one. 03 Chapter 1, IntroductionThe problem, who it hurts, your research question, your four objectives, and what is in and out of scope. 04 Chapter 2, Literature ReviewWhat 23 other studies found, and the three gaps they left that your study fills. 05 Chapter 3, MethodologyYour plan, written before you had data. Post-positivism, Design Science Research, sampling and ethics. 06 Chapter 4, RequirementsThe big one. All the statistics, the finding, and how it turns into 14 things the system must do. 07 Chapter 5, ImplementationWhat you built and how it works inside. Six tables, four clever bits, one critical piece of code. 08 Chapter 6, TestingTen tests, six measurements, and seven bugs that testing caught before an examiner could. 09 Chapter 7, ConclusionObjectives assessed, problems admitted, lessons learned, business advice, and what should happen next. 10 Appendices A to EThe surveys, the raw statistics, the extra use cases, the full measurements and the actual source code. 11 EVENTIA, the systemScreen by screen, what it does, how to demo it, and the one moment that proves your whole point. 12 Every numberAll the figures on one page, so you can check yourself before the viva. 13 The vivaWhat happens, what to say first, 18 likely questions with answers, and how to handle the weak spots.

Ask an AI about your own project

There is a file on this site called HANDOVER.md. It contains this entire project written out as plain text: every number, every finding, the whole system, all the limitations.

How to use it

1. Open HANDOVER.md and copy everything, or save it and attach the file.

2. Paste it into Claude or ChatGPT.

3. Start with this message:

This is my final year research project. I am preparing for my viva. Use only the facts in this document. If I ask something that is not in here, tell me it is not in the document rather than guessing. Explain things simply.

That last instruction matters. Without it an AI will invent plausible-sounding numbers, and a wrong figure said confidently in a viva is worse than saying you do not remember.

The facts about your project

Full titleSmart Tourism Event Management System: A Platform for Hotel-Hosted Social Events in Sri Lanka
StudentNanayakkarawasam Mahakapuge Hasara Sathsara, ID 28461
DegreeBSc in Management Information Systems (Special), Faculty of Computing, NSBM Green University
SupervisorMs. Pavithra Subashini
Final thesis165 pages, 7 chapters, 5 appendices, 40 references
Submitted11 September 2026
People surveyed64 travellers and 40 hotel organisers
System builtEVENTIA, a web application, deployed and tested
Tests passed10 of 10 functional, 6 of 6 measured targets

Three rules for talking about it

Do this

Say the real words. Say "standardised beta", "Cronbach's Alpha", "row level security". This guide teaches you what each one means. Using the real word correctly is worth more than explaining around it.

Answer from the evidence, not from what you intended. If you are unsure, say what the data showed. "The regression gave a beta of point six six five" is always a safe answer.

Name your own limitations first. Every weak spot in this project is already written into the thesis. Saying it before an examiner finds it turns an attack into a sign of judgement.

Never do this

Never claim the system improved a real hotel. It has not been deployed at a hotel for a season. Your evaluation proves the system works as specified, not that it changed anyone's business yet. That distinction is in the thesis and you must keep it.

Never say your hypotheses all worked. Two of the three were not supported, and that is the interesting part, not a failure.

Say this out loud

My research is about hotel-hosted social events in Sri Lanka. Right now hotels announce them on chalkboards and WhatsApp, so they cannot predict turnout and travellers cannot find out what is available. I tested three possible fixes with a survey of 64 travellers and 40 organisers. Only one of them mattered: centralising the information. It came out the same way in both groups, independently. So I built a working platform where the event details and the live availability are one single record that both sides read, and I tested it against the requirements the survey produced.