That for small hotel-hosted events, unifying the information is not one feature among several. It is the mechanism through which the others deliver value at all, demonstrated statistically in two independent samples and then expressed as an architecture and tested.

Three parts. First, no study has examined a unified platform combining real-time visibility, multi-resource pre-booking and a centralized organiser dashboard for small hotel-hosted events. Second, nobody has measured whether small Sri Lankan hotel operators would actually adopt such a platform. Third, the operational consequences, over-procurement, under-sold capacity and travellers missing events, have never been quantified in this context.

Each gap maps onto one of my objectives, which is how the objectives were chosen.

I did not. The scope is national, and the target population is hotels, guesthouses and villas across Sri Lanka.

Collection was concentrated in the Southern Province coastal belt for three reasons stated in Section 3.5.1: it has the densest concentration of small and medium coastal accommodation, the event frequency there is high enough to produce a usable sampling frame of organisers who face the problem, and prior research documents an operational profile there that matches small operators nationally, which supports analytical generalisation.

Because the question has two halves that neither a purely behavioural nor a purely technical project would cover. A behavioural study would have explained the coordination problem without producing anything that addresses it. A software project would have produced an artefact with no evidence it addresses the right thing.

Design Science Research requires both, and Peffers' six-phase DSRM gave the execution order, mapped chapter by chapter in Table 3.1.

Because correlation asks whether two things move together, and regression asks what each one contributes once the others are accounted for. My three predictors overlap heavily, with IV2 and IV3 correlating at 0.738 among travellers, so at the bivariate level each one gets credit for variance it shares with the others.

The regression distributes that credit correctly. Reporting only the correlations would have supported all three hypotheses handsomely and would have been misleading, and Section 7.3 says explicitly that the temptation was resisted.

It is not, and it was not accepted. That is the figure before instrument purification. One reverse-coded item, item 20, returned a corrected item-total correlation of minus 0.623 after reverse-scoring. Removing it by the standard 0.30 threshold lifted the scale to 0.690.

Table 4.3 reports both the initial and the final value for every construct, because showing only the final figure would conceal the diagnostic step that made the scale trustworthy.

The rule was fixed in advance rather than chosen afterwards. Items below the conventional 0.30 corrected item-total threshold are removed, worst first, recomputing after each removal, and no scale may drop below 3 items.

Only 2 items in the whole instrument crossed that threshold, and they were exactly the 2 reverse-coded items, in both independent samples. No forward-worded item was touched and no further removals were made. If I had been fishing, the removals would have been scattered across the instrument rather than confined to the two items with a documented failure mode.

It is enough for what the study claims and not enough for what it explicitly does not claim. With 64 cases and 3 predictors there are roughly 21 cases per predictor, which exceeds the commonly applied minimum of 10 to 15 for stable estimates but falls short of the 50 to 100 per predictor recommended for optimal stability.

So the model is adequately powered to detect a large effect and underpowered for small ones. That is exactly why the non-significant coefficients are reported as a failure to detect a unique effect rather than as evidence that no effect exists.

Because the finding is not that they do not matter. Both correlate strongly with the outcome. The finding is that their contribution operates through unified information rather than independently of it.

So the architecture reflects exactly that. Real-time visibility is built as a read surface over the unified record, and pre-booking is built as the write path into it. They exist, but as expressions of the unified layer rather than as separate features beside it.

Because the evidence decided. The principal component analysis showed the 4 surviving items forming a single dimension rather than three separable factors.

It is therefore scored as one unidimensional composite, and the three conceptual sub-dimensions are retained as facets rather than as separately scored subscales. Establishing them as distinct measurable subscales would require a longer instrument, which is a named future recommendation in Chapter 7.

Because they differ in what they represent to a guest but behave identically to the system. Each carries a price, a total quantity and a remaining quantity, and each must be decremented atomically.

One table gives a single query returning the complete resource position for an event, a single realtime subscription keeping every surface consistent, and a single locking discipline governing all concurrent decrements.

Modelling them separately would have fragmented availability across three code paths and reintroduced, inside the system, the same inconsistency between information sources that the research identifies as the primary failure of the arrangements it replaces.

Because a booking must decrement several independent resource counts and either succeed completely or leave no trace, which requires transactional guarantees a document store does not provide by default.

Chapter 2 identifies concurrency control over multi-resource inventory as the central algorithmic problem for platforms of this type, and one reviewed source finds that platforms on eventually consistent stores expose stale availability to users. Stale availability is the exact failure this research exists to eliminate.

Because the test asserts peak overlap as well as outcome, and it recorded 20 requests in flight at once.

That assertion is what makes the rest of the result meaningful. If the requests had been serialised by the runtime rather than held by the database lock, the outcome would have looked identical while proving nothing about the locking.

Two reasons. A defect in the interface then cannot expose one property's booking data to another, because the interface is not what withholds it. And it makes the guarantee testable independently of the interface, which is what TC-09 does by issuing requests directly against the API with one user's credentials against another user's data.

It also answers the data. Security and data protection appeared in 46.7 percent of substantive organiser adoption responses.

The opposite. Two of them would otherwise have produced a false pass. The most instructive is that the responsive test passed against 36 screenshots of an error page, because an error page does not overflow its viewport.

That was caught by opening the images, not by reading the test output, and the capture script now fails the run if any screen rendered an error. An evaluation that reports only its final state conceals the work that made the final state trustworthy.

It is declared out of scope in Section 1.10. The research question concerns information coordination rather than transactions, so a payment gateway would add regulatory and financial complexity without contributing 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.

The artefact reached a testable state too close to the submission deadline to recruit and run a System Usability Scale panel with adequate rigour, and running it badly would have produced a number with no evidential value.

It leaves NFR-06 specified but unverified, which Section 6.6 names as the weakest point in the evaluation and Section 7.5 carries into the future recommendations. The evaluation effort that was available went to the two claims that could not be established any other way, concurrency integrity and access control, rather than being spread thinly.

No, and the thesis does not claim it. The evaluation establishes that the artefact conforms to a specification derived from the evidence, and that the concurrency and access guarantees hold. It does not establish realised coordination effectiveness in the field.

Demonstrating that would require deploying across a season and measuring procurement variance against actual attendance, the proportion of events running under capacity, and advance turnout prediction accuracy, each against a pre-deployment baseline. That is the first future recommendation in Section 7.5.

It bounds them rather than undermining them. The traveller findings generalise to the domestic young-adult traveller segment, not to the international visitor population that Chapter 1 also identified, and the thesis states that explicitly.

Replicating the traveller survey with international visitors is a named future recommendation. The prior expectation is that centralized information matters more for travellers with less local knowledge of a destination, not less, so the direction of the finding is unlikely to reverse.

Four things, all of them already in Chapter 7. Start traveller collection earlier and push much harder on the international segment. Reword the reverse-coded items or replace them with a different attention check. Build the artefact earlier so a usability panel fits inside the window. And use a longer instrument for the outcome so the three sub-dimensions can be scored separately instead of collapsing into one.

That the most valuable result was one I did not expect. I assumed real-time visibility would dominate, because it is the most visible failure to anyone standing in Mirissa on an event night. The data said otherwise, twice, in two independent samples, and learning to treat that as the finding rather than as a problem with the data was the most useful shift in the project.

The second thing is that instrument design, statistical inference and software architecture turned out to be one continuous piece of work. The decision to put three resource kinds in one table is not a technical preference, it is the regression result written as a schema.