Writing Clear Indicator Requirements for Algorithmic Trading Developers
Summary
This guide explains how to prepare a requirements specification for a custom trading indicator. It recommends defining the indicator’s purpose first, then describing its calculations and behavior as an ordered sequence of steps. Terms should be explicitly defined, and explanatory images, flowcharts, diagrams, or planned video demonstrations can help make chart patterns and program behavior clear to both the customer and developer.
The suggested specification topics include drawing style and colors, chart placement, symbols and timeframes, input data and parameters, recalculation and redrawing, alerts, control panels, debugging logs, and acceptance testing. Worked examples include a ZigZag built from oscillator-defined zones and rules for coloring its swings. The article also recommends testing the delivered indicator and providing reproducible bug reports with relevant chart and log details. It is a communication and project-definition guide rather than a trading strategy: it presents practical recommendations and examples, but no measured evidence that these practices improve development outcomes.
Key ideas
- Describe the indicator’s purpose and algorithm in a clear, ordered sequence of operations.
- Define specialized terms so the customer and developer share the same interpretation.
- Use annotated images and flowcharts to clarify chart patterns, calculations, and interface behavior.
- Specify display settings, inputs, data sources, alerts, recalculation behavior, and testing expectations.
- Report defects with enough chart, log, symbol, and timeframe detail for the developer to reproduce them.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.