01
Review the existing design
Within one month, Shinetech supplied an architecture analysis and recommendations. These included improving code structure, consolidating two separate MVC models and optimising data searches.
← Back to Travel & hospitality case studies
Case study · Travel & hospitality
Improving a web-based order platform for event services
An event technology provider commissioned an architecture review, then worked with a Scrum team to improve a web system for orders, quotes, billing and inventory.
- Client context
- An event technology provider serving hotels and conference centres
- Architecture review
- 1 month
- Delivery cadence
- 1–2 week sprints
- Scope
- Orders, quotes and inventory
The situation
The business need
The client provided audiovisual, staging, creative and related equipment services for hotels, resorts and conference centres. A new web application was intended to replace a desktop tool with easier access.
Before proceeding, the client needed to assess whether the architecture could meet quality and performance requirements. Maintainability, UI/business-logic dependencies and searches over larger data sets were particular concerns.
The approach
How the team delivered
02
Agree the wider roadmap
Onsite workshops with the CIO team reviewed development processes and the ERP roadmap. The team considered both distributed and non-distributed deployment trade-offs.
03
Deliver the agreed improvements
A Scrum Master, two developers and part-time technical consulting and QA worked with the client’s Product Owner. One- or two-week sprints, weekly reviews, Pivotal Tracker and Microsoft TFS supported delivery and releases.
Project context
Technology and delivery
Technologies and working practices used in this engagement.
Architecture reviewOrder managementScrumMicrosoft TFS
The result
What the engagement delivered
An actionable architecture review
The client received recommendations tied to maintainability, performance and future extension.
An agreed work plan
The architecture recommendations became a development plan and timeline.
A repeatable release process
The team followed short sprints with production releases and regular customer review.
Need to review an application before extending it further?
Tell us about your software, workflows and delivery requirements.
Discuss your project