7.1 Before Coding RDML Processes and Functions

These guidelines are presented in the form of a checklist as every item should be satisfied before a single RDML process or function is coded. 

• All repository naming standards and guidelines are known by/available to every member of the project team.

• All file definition, naming standards and guidelines are known by/available to every member of the project team.

• All process and function naming standards and guidelines are known by/available to every member of the project team.

• All known repository entries, validation rules and HELP text have been input.

• All known files in the database have been designed, implemented and are understood by all members of the project team. Additionally, all file level validation checks have been implemented and tested.

• Preferably the entire database should be "visualized" in the form of a relational map. Updated versions of this map should be given to all members of the project team.

• The entire application system has been broken down into identifiable processes and functions which will perform all the required business functions (i.e., the whole system is designed before coding is commenced).

• The complete backup and recovery strategy to be used by the application system has been designed.

• All known system variables have been identified, implemented and tested. All members of the project team are aware of their existence and what they can be used for.

• A global exchange list has been designed for all programs in the application system. All members of the project team are aware of its existence and how and why it is used.

• Application Templates are available to automatically generate most common types of online transactions and report production programs. These have been tested and conform to all site standards for "look" and "feel".