The control flow technique for programming

The problem: 
Programs grow larger .. The more code is added the harder the development , requirements tracking etc
The solution: 
Write human readable pseudo code instructions into a spreadsheet , so that each "Control flow point" is a row in the spreadsheet. Add the row in the code as logging entries. Thus after each run of the program by filtering the entries from the log the real control flow is revealed. The - human readability is helping also customers and specifications providers to understand what actually the programmer is writing and add / update / correct existing specifications. By sending back and forth the Control Flow the actual process of requirements gathering , specs creation is shortened and the whole development process improved.
It is important that the Control Flow points are chosen ,so that each Control Flow Point must be tested and verified ( not only by the existence of the log entry ). By searching recursively in the source code for the Control Flow point description the developer could jump straight into the actual part of the source code to be worked on ...