Project 11 - Problems Solving Techniques: Translating PDL – Program Design Language into QBASIC Code

Translating PDL – Program Design Language into QBASIC Code in programming

Program Design Language is not really a language at all. It is a method of working out the concept of a program in order to ensure that the program meets the expectation of the developer(s).

The basis of the Program Design Language is that it is fake code that most closely resembles English. The programming languages that best represent Human Language are considered Higher Languages. This is because they are easier to program without requiring much interpretation of the code.

While QBasic (or QuickBasic) is not the most commercially used language for programming, it is a great tool for learning programming, as it is a higher language than other languages. QBasic, however, is not a higher language than Program Design Language (as mentioned, it is basically Human Language). Of course, moving from Program Design Language to QBasic will be much simpler than trying to move to JAVA or even C++.

Why is PDL necessary?

Well, based on a well written article (with the novice in mind), Program Design Language is a great way of mapping out the code in an easily evaluated language. This means that the programmer of his boss can review the code quickly to ensure that what will be coded is, in fact, relevant and on par with the desired goal of the program.

To review my reference, you can go to: http://www.gamedev.net/reference/articles/article1384.asp

Translating PDL – Program Design Language into QBASIC Code Outside of Programming:

Okay. Let's be frank. Outside of programming, I will not be attempting to convert anything to QBasic, or any other programming language for that matter. This doesn't mean that the basic concept of program Design Language has no place in the outside world.

Again, I go back to technical support, because it is something to which I can relate.

One of the hard parts of technical support is explaining, or walking a customer through a process. Most of the time, it is not that the person is stubborn or isn't listening (while that does happen), but rather that they don't understand "Techy Speak".

Take for example the simple process of navigating a customer to the System Properties window or asking them to provide you the amount of Random Access Memory that with which their system is running.

First of all, I locate the System Properties window with the Shortcut keys: Win + Page Break.

I have tried to explain this to customers, and they tend to ask, "What (or where) is a Windows key?"

If on the other hand, I ask them to locate their Start button, within the Windows Task Bar, and right-click on the My Computer icon, they tend to get that far. From there I can explain that they will select Properties.

That is just navigating. I usually have to explain RAM. I can't just call it Random Access Memory and leave it at that. I have to put it in a language easy enough for them to understand. In essence, PDL is the equivalent of Laymen's terms.

If I provide the customer with instructions in these terms, they tend to be able to accomplish the task that I have requested.