Software design using diagrams and pseudo code aid in the discovery phases of development based projects. Using these tools can greatly increase the success of the project by allowing communication between the clients and the development team. The created documents can be used in the documentation and test phases of the project giving easy to read visual aids.  As training and code review comes along in the future these documents will often be put back into play as well.

Data flow diagrams when the process is needed to be seen visually. Functions are listed as data is communicated back and forth. Each process or function is displayed as a block while lines connect to each showing the flow of data.

State diagrams are different from data flow diagrams. State diagrams display every possible state of the software and what causes the states to change. State diagrams are far more detailed compared to data flow diagrams.

Flow charts are the most time consuming to create. They contain details and options between each process in great detail. Flow charts are great for explaining the full process of each function from start to finish.

Pseudo code is the technique of writing the application code in comment form in great detail. The code is easier for developers to understand as it sets the ground work for the actual code logic as well as the location of the actual programming code. The use of pseudo code can help with documentation as it can be exported from the application source during the documentation phase for use in the actual solution documentation.

Conclusion

Charts are much easier to understand from a client stand perspective. They are visually appealing and many times very colorful and easy to follow. All charts are hard to maintain due to the disconnect form the actual application code. Every time a change is made in the application the developer has to take the time to update all documentation including charts. Tools like UML can make this process easier but only works well with object oriented programming. Pseudo code is much easier for technical teams. The process of creating this code greatly increases the speed of the actual programming language development phase.

Works Cited

How to describe embedded software design using diagrams and pseudo-code. (n.d.). Retrieved from ScienceProg:

http://www.scienceprog.com/how-to-describe-embedded-software-design-using-diagrams-and-pseudo-code/

Introduction to Developing Computer Programs. (n.d.). Retrieved from The School of Electrical Engineering and Computer Science:

http://www.eecs.wsu.edu/~rwarnick/cs251/intro2program_development.htm

Structured Flowcharts Outperform Pseudocode: An Experimental Comparison. (n.d.). Retrieved from IEEEE:

http://csdl2.computer.org/persagen/DLAbsToc.jsp?resourcePath=/dl/mags/so/&toc=comp/mags/so/1989/05/s5toc.xml&DOI=10.1109/52.35587