Considerations
Because many of the pieces of an application, such as subschemas, maps, and dialogs, exist in both source and load module format, you must consider the following questions when you migrate from one dictionary to another:
Accessibility of the Source Code
The major benefit of a complete, fully documented application is that the proper source code is accessible when needed for debugging. If a problem arises and the source code resides in a properly controlled production environment, the source code can easily be found and it will correspond exactly to the load module(s) where the problem was encountered.
Availability of Disk Space
A trade-off to migrating a fully documented application is the amount of disk space required. The space may be in one environment, such as production, or may be spread out over a number of environments, such as development, test, and production. Determining exactly how much disk space is necessary depends on whether you decide to copy the application into the production environment or simply move it.
Redundancy
If you choose to maintain separate copies of the application, you must contend with the trade-offs of redundancy. Often, updates to one copy must also be made to the other, and they both must be made within a short period of time to maintain consistency.
Accessibility of Information
If you maintain only one copy of the application, you use a minimum amount of disk space and do not have to contend with redundancy. However, accessibility of information becomes a consideration. If the information is secured so that only one person is able to access it, procedures must be developed that allow maintenance programmers and all members of the staff to obtain reports of component definitions. At the same time, you must ensure that there is ample security so that no one can make accidental or malicious updates that would invalidate production applications.
|
Copyright © 2014 CA.
All rights reserved.
|
|