Requirements spec for the backtesting engine
Engines built without a written scope tend to grow every feature at once and finish none, then quietly disagree with each other in edge cases. One spec naming the asset classes, bar or tick resolution, order types, cost models, run time budget and who will use the engine settles most later arguments before the first line of code.
First tasks
- List the asset classes and data resolutions the first version must handle
- Ask two intended users which questions the engine must answer for them
- Write numeric run time and memory targets for a typical study
- Get the spec reviewed by a researcher and an engineer before coding