map the screen sequences as a data structure along the lines of your interpreter. hope you've had a class in automata theory.

each major screen becomes a state and its conditionals can be encoded in an automata language with links to other states via the structure. this allows you to incorporate common processes in each page by utilizing only sentinals in the datastructure for the state.

making sure you have the screen sequences correct is important. i strongly recommend doing a PC simulation for customer approval as later changes and misunderstanding may complicate the data structure and the completion time for the project.

electrical engineering state reduction techniques to analyze and organize your state machine might be useful.

i did this for a navy contract and the results were very advantageous. the man machine interface was demonstrated and approved before the machine was built and coded. that pre-approval helped minimize the delivery time change requests.

i used the intended microcontroller and wrote the datastructures for the menus with dummy operational subroutines. we sequenced through the operator tasks and as changes were discussed during the demo meeting, i could immediately alter the datastructure, assemble and run the changes for review. it was the fastest customer acceptance meeting i have ever attended and the contract turned out very nicely.

its often acceptable to use Microsoft PowerPoint to simulate a man-machine interface. I use that when dealing with less technical people and it has the advantage of portability.

duh