4.1.5 Before You Begin Checklist
Before a single RDML process or function is coded, it is recommended that the following checklist has been satisfied:
- All repository development standards and guidelines are known by/available to every member of the project team.
- All LANSA Object naming standards and guidelines are known by/available to every member of the project team. (Refer to LANSA Object Names in the LANSA Technical Reference Guide.)
- All process and function development standards and guidelines are known by/available to every member of the project team. This should include task tracking procedures. (Refer to Using Task Tracking in LANSA in the Administrator Guide.)
- Principal repository development has been completed:
- All known repository entries, validation rules and HELP text have been input.
- All known system variables have been identified, implemented and tested. All members of the project team are aware of their existence and their use.
- All known files in the database have been designed, implemented and are understood by all members of the project.
- All file level validation checks have been implemented and tested.
- 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 functions. These have been tested and conform to all site standards for "look" and "feel". (Refer to Using Application Templates.)
- The entire application system has been broken down into identifiable processes and functions which will perform all of the required business functions (i.e. the whole system has been designed before coding commences).
- The complete backup and recovery strategy to be used by the application system has been designed.
For details about designing processes and functions, refer to Processes and Functions in the LANSA Application Design Guide.
