Define guidelines for the use of syntax-directed testing at the unit level, for integration testing, and at the functional level. Educate the staff regarding syntax testing's applicability and methodology.

Obtain management's and/or the buyer's guidance regarding the degree of garbage intolerance appropriate to each product. Measure that tolerance in terms of consequences, damages, and the severity thereof. Make sure that there is unanimity regarding objectives.

Adopt a standard for the specification of all syntax in the system. Don't invent new notations or make a research project out of it. It doesn't really matter what you use as long as you use something and use it consistently.

Identify all system elements for which syntax-directed testing might prove beneficial.

Obtain or create a formal specification of the appropriate syntax for each such elements. Evaluate the specification for consistency and thoroughness. Obtain buyer concurrence. (This entire step is where most of the action is).

Design appropriate single-error test cases, and far fewer double- and higher-order error combinations. Obtain approval regarding the cut-off level. It can go either way - the powers that be may not want to go far enough, but if they've been burned, they may want to go much too far.

Projected testing costs and duration are useful to set a perspective.

Establish reliable methods for conducting this kind of test and for validating the results.