First Metre - only connect... the people with the purpose
contact | site map | legal
|
Recursion

All elements defining viability at one level of recursion of a system will occur on all other levels of recursion of the system.




To understand recursion, one must recognize the distinction between the statement of a sequence of activities based on a set of rules (i.e an algorithm) and the execution of a sequence (i.e. a process). The distinction is the same as between a generic instruction and a particular implementation. The actual execution of the process involves following the instruction’s ruleset and performing the instruction’s sequence of activities.
 
A procedure is recursive if one of the steps that makes up the activity sequence calls for a new running of the same sequence at a different level. Any recursive process must complete the sequence of sequences in full.
 
Thus, while a director works on a different level and to a different time horizon to a line-worker, both will follow a similar generic sequence as they do their level specific work. They each have to supervise their output, manage local changes to minimise variation in their output and direct their reseource efficiently. Before they do their work they have to satisfy themselves that they have the wherewithal to do the work – in effect they audit the resources they have to depend on.