The source portfolio describes a complex trading plan and strategy simulator based on Excel and Microsoft Access. The recorded requirements included match setup, bet placement and management, simulator calculations, tracking and trade logs, strategy management, drawdown analysis, and data management.
The web application scope also described user registration, individual accounts, dashboards, settings, billing-related account status, notifications, and an administrative module for managing match and team data. The source references a database with approximately 33 existing tables and data for around 14,000 matches, with further data planned.
This case study focuses on the central modernization problem: moving calculation-heavy desktop workflows into a web application that can support separate user workspaces and centralized data. The source does not provide measured business results, so none are asserted.
Important design considerations
A simulator conversion should document formulas, macros, queries, mappings, hidden-sheet behavior, and existing outputs before implementation. Test cases should compare web results against the original workbook and database logic. If users need separate private strategies, the data model and access controls should reflect that requirement.
If a specialist simulator has outgrown desktop spreadsheets and databases, a structured conversion can provide a path toward shared access and centralized administration while preserving the calculation model.
