Another question ...
What would be the right structure of a coded system?
CV mentioned modules. Well they do have their place; but the broader structure i envisage (& one emerging as a natural outcome of my thought & development processes) is that of a multi-level decision tree with multiple nodes at each level. The decision ('yes-no') at each level will be based on one or more Technical/Fundamental parameter (preferably one main & 2 supporting/confirmatory parameters) implemented through 'plug-in' modules (this will enable me to shift/re-arrange the nodes more easily, if needed).
[This decision tree can hopefully then act as the 'feedstock' for a neural net at a later stage - though i'm not too sure about that due to my paltry knowledge of nu-nets at this stage]
But i'm not satisfied entirely with this structure. What i'd like to achieve is a clean segregation of each level based on the specific function it performs (i have only one such level as of now - the Fundamentals level; the others are kind of 'mixed-up'. While i'm not saying (as of now) that it's unachievable within the current (aforementioned) structure, what's increasingly appearing to be a 'cleaner' design is that of MULTIPLE decision trees each based on a specific function (of the entire decision process) and each with it's own levels & nodes (& sub-levels & sub-nodes, if necessary).
Modules (as mentioned by CV) would be the 'bricks', the building blocks, of such a structure but what would be more important is the 'cementation' - between levels & nodes in the first structure and between decision trees and the levels & nodes within them (not to mention sub-levels & sub-nodes, if needed) in the second structure.
Regards,
Kalyan.