Project specifications
- Market
- EURUSD / XAUUSD / US30
- TF
- H1
- Platform
- MT5
- Client type
- Team / company
- Delivery window
- 7 weeks
- Stack
- MQL5, settings files, a version inventory
- Strategy
- Per-run state records + standardisation
- Modules
- Settings inventory + version tags
- Testing
- Reconciliation across six terminals
Who this was for
Parsianrah Financial Holding
- Role
- Technology team
- City
- Tehran
- Project reference
- TBT-1411-39
The client's idea
Parsianrah Financial Holding works EURUSD / XAUUSD / US30 on H1; the opening brief was: We run six terminals on two servers — tell us which setting lives where.
Initial challenge
As the team grew nobody held a complete picture of the live settings, and every execution problem was solved by guessing.
Solution
One inventory of every run with version and setting tags, a consistent naming scheme, and a record of when each change landed on which terminal.
Why this design
Version tags on every run moved problem tracing from asking colleagues to reading one table. It matches how EURUSD / XAUUSD / US30 is actually traded and can be tested against the data already available.
Safeguards and risk control
Every first run happens on a demo account, and the pre-live checklist is filled in before the live connection.
Our next-step proposal
The next step is a quarterly settings review and keeping the documentation current with broker changes.
Portfolio
Measured results
These are the figures the test produced — not a promise about future performance.
- 15 scenarios Scenario test coverage
- 100 % Parity with the previous build
- 99.8 % Runtime stability in test
- 5 Defects fixed
Portfolio
How the delivery ran
Every project moves through these five phases, with the window for each agreed in the specification.
-
Discovery and problem framing
CompletedReviewing the client's environment: terminal build, broker and the account it runs on.
Day 2–5
-
Written specification
CompletedWriting the install checklist and fixing the starting parameters on EURUSD / XAUUSD / US30.
Day 6–13
-
Implementation
CompletedPreparing the handover pack: files, set files and the parameter document.
Day 14–29
-
Testing and validation
CompletedA real run on a demo account, log review and watching the first days of behaviour.
Day 30–39
-
Handover and support
CompletedHandover of the documentation, a short walkthrough and the support path.
Day 40–43