The QA Build Development Cycle

There are three stages to producing a QA Build program:

1. Entering details of the program you want to produce into the Program Editor

2. Compiling your program with the Program Compiler

3. Running your program with the Interpreter

You do all these from the QAB Menu in DP4.

The Program Editor (PROGMAKE)

The Program Editor allows you to create and amend QA Build programs. Running this utility involves entering into a question-and-answer session. Because QA Build has all the resources needed to specify complex programs, there are more questions than a first-time user might expect. However, QA Build always suggests a sensible default answer; you can accept the default with confidence. Moreover, context-sensitive help is available to assist you at every stage. You use its sister screen design utility, the Map Editor, to design the screens (maps) that your program will use. Both these applications use the standard Windows interface.

The Program Compiler (PROGCOMP)

Although you must compile your program before you can run it, QA Build does not generate any code in the traditional sense. The Program Compiler converts your program into a set of instructions that can be interpreted by the Interpreter. It makes a number of checks and, if any errors are detected, it displays a suitable error message.

The Program Interpreter (PROGRUN)

The Interpreter runs your program, notifying you of any run-time errors. Note that QA Build programs can only be run using PROGRUN.