Our museum is temporarily closed to support the effort to contain the spread of COVID-19. Read a message from our director, and check our website and social media for updates.

Add new comment

I'm sure I am one of many who used these templates, both to do an initial design, and to document software after the fact. At one time, software programs were developed to analyze code and produce flowcharts after the fact, when there was no other documentation available. This form of documentation was better than nothing, but variable names were often limited in length in actual code, so that the resulting flowcharts did not provide any insight into what the variables meant. One of the challenges of flowcharting was figuring out how to show "go-to" statements, which might result in lines crossing, and also deciding what would logically fit on a page of documentation. Flowcharting with templates was pretty much a manual exercise, with minimal guidance/training on how to do it. I found it beneficial to look at the flowcharts created by someone who had done it well, and this was usually someone who also was a good designer. Overly complex flowcharts usually resulted from documenting code after the fact, OR from creating an unnecessarily complex design. New hires, as lowly persons in the organization, were often given the job of creating flowcharts after the fact to produce documentation