✓ REAL WORK CASE
NewFinTech · Hospitality platform · PMS / Channex / OTA

Reservation & Financial Integration Analysis

Reconstructing how reservation and financial behaviour crossed system boundaries, then converting the result into implementation and verification guidance.

Best fit: System Analyst · Technical BA · Integration Analyst
Quest classIntegration InvestigatorEvidence → boundaries → financial rules → testability
✓ COMPLETED
PMS, Channex and OTA integration analysis diagram
Hiring snapshot

Why this case matters for a team

If current behaviour is distributed across systems, documents and stakeholders, this case shows how I rebuild the truth first — before locking requirements or test scenarios.

01Problem shape

Reservation and financial behaviour crossed PMS, Channex and OTA boundaries while the current state was spread across documentation, interface evidence, integration evidence and discussions.

02What I owned

Reconstructing the AS-IS model, separating confirmed facts from assumptions, clarifying system and financial rules, and mapping dependencies.

03Supported output

Requirements · acceptance criteria · dependency maps · pre-certification QA scenarios.

Use this case to assess: current-state reconstruction · cross-system reasoning · financial-rule analysis · requirements & QA hand-off
Integration Investigator · Case path

How I moved from uncertain current state to testable change

The snapshot above is the fast hiring view. Open a checkpoint only if you want to inspect how the analysis moved from evidence to implementable guidance.

Checkpoint 1 of 4

Reconstruct the current state

What is confirmed behaviour, what is an assumption, and what still needs clarification?

What I looked at

Product documentation, interface behaviour, integration evidence and discussions with Product and Development.

Why it mattered

Requirements built on an uncertain current state can make a cross-system change look consistent on paper while preserving hidden contradictions.

My contribution

Reconstruct the current behaviour and separate confirmed facts, decisions, assumptions and open questions.

What this unlocked

A shared AS-IS model that could be used to reason about boundaries, rules and downstream QA.

★

Supported output

RequirementsBusiness and system behaviour made explicit.
Acceptance criteriaExpected behaviour expressed in a testable form.
Dependency mapsSystem and change dependencies surfaced before delivery.
QA scenariosPre-certification checks for integration-sensitive changes.
Scope guardrail

What I am not claiming

This case demonstrates analysis and delivery support. I do not claim production ownership or certification ownership, and I do not attach a production KPI that was not measured.

Next move

Want the shortest case walkthrough?

Tell me what your team is hiring for and I can start with the closest mission, then show the evidence behind it.