The zeroCode systemaaa has two major components. The initialization and running sequence for the two segments, though not identical, are similar.

This section describes issues specific to the database of the project that will impact zeroCode application generation. For example, it may have been necessary to set up columns in tables in a sequence that is not optimal for zeroCode generation. In such a case, the generated pages will have to be modified to reflect the user-needed ordering of columns.

zeroCode, by default, generates a session variable for the login ID alone. The general design assessment is that reliable, scalable programs use as few session variables as possible. Before adding items to the session, discuss and validate correctly. Using session variables can be decided only if it is not possible to carry the data items as hidden variables, from one UDM to another as parameters. Considerations, like security and server-side modification needs, will decide the use of such variables. Then the necessary session variables, their type (string, integer, etc.) and their use in specific UDMs are listed out.

The major third-party components that zDE uses - the JDBC drivers, FreeMarker, etc.
FreeMarker provides an easy way to get data from Java servlets into Web pages, and helps you keep graphic design separate from application logic. To use this, encapsulate HTML in templates. These get compiled into Template objects, which generate HTML dynamically, using data provided by your servlets. The template language is powerful and intuitive, the compiler is fast, and the output approaches the speed of static HTML pages.