In an event-driven interface, most events triggered by the "completion" of a field will present an opportunity to either validate that field, or to guide the choices for entering the next.
In this scenario, the programmer draws the user interface first and then writes the business logic in the automatically created methods.