Planning Objective Rules for Automated Trading Systems
Summary
This installment explains how to prepare a familiar manual trading model for automation. It argues that the trader should first define observable, unambiguous conditions for entries, exits, and stops, then implement those rules without quietly changing the strategy during coding. Examples use a moving-average close rule, RSI thresholds, and a moving-average exit or stop. It also discusses adding explicit filters, such as checking recent highs before entering, while pointing out that more conditions make the system harder for a trader to supervise.
The article uses flowcharts and step-by-step descriptions to translate an idea into program logic, then relates automation to the series’ EA architecture: manual chart interactions are handled through a mouse class, while automated triggers must take over that role and notify the manager of trade events. The supplied excerpt is incomplete, so it does not provide the full implementation or performance evidence. Its practical focus is process design, not a validated trading strategy; example indicator rules are illustrations and are not presented as proven profitable systems.
Key ideas
- Automate a trading model only after becoming familiar with how it is used.
- Specify entry, exit, and stop conditions in objective terms before coding.
- Keep the EA faithful to the defined model instead of inventing new rules during implementation.
- Additional filters can make behavior more conditional and harder to supervise.
- Flowcharts and event handling help map manual actions to automated EA behavior.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.