Project 11 - Problems Solving Techniques: Solving Simple Problems Using Algorithms and a Program Design Language

Solving Simple Problems Using Algorithms and a Program Design Language

An algorithm is sequence of steps used to accomplish a task, such as solving a problem). The idea around algorithms is that a problem will be addressed based on a series of calculations or logic based tests. In their visual representation, known as Flow Charts, they are usually a series of "Yes or No" or "True or False" questions.

Algorithms are an especially handy tool for problem solving as they tend to map out all possible paths or answers to a solution; especially if there is not a single solution.

Since algorithms tend to be mathematical equations, they do not lend code to be easily read by human eyes. If at all possible, nobody would want to look through a bunch of if-else statements to determine how a program came to the output that was provided, nor would they want to constantly have to re-read the code as they are building the program to remember where they were and of what the next step in the sequence would consist. This is where Program Design Language comes into place. If you consider what a Flow Chart represents, you can determine that it, in essence is the Program Design Language's representation of the programming language.

As I mentioned earlier, a flow chart is nothing more than a display of the algorithm in an easily understood language (with the added bonus of pictures).

Solving Simple Problems Using Algorithms and a Program Design Language

Making things both visually and textually easier one to understand is always a plus.

With both the concepts of using algorithms in the form of flow charts is something that is very common to things such as technical support for things from dealing with lost cable connection to troubleshooting car issues. They can even be in ruling the cause of a rash.

In the aspect of technical support, this in combination with Program Design Language helps users to better support their own issues. I think the best example of this is pertaining to a specific error message that occurs when QuickBooks users attempt to access a data file across a network. If they receive an error message of H202, they have no idea what the program is trying to tell them, nor do they understand what is necessary to fix it.

To explain this in terms that a user could understand, a flow chart was created to help them address the exact cause of the issue, and therefore access a solution. This flowchart can be found here.

Side Note: What is quite interesting about that flow chart is that it was created by one of my peers, who then used this chart to create an algorithm that he then coded into a program. Now, this flow chart is a representation of what the "Network Diagnostic Tool" at the bottom of the article actually performs.