Description:
A cross reference table or set of tables with the application database tables, arrays, segments and application “master” files as the columns to the cross reference. Then all of the application’s programs or other code components as the rows of the cross reference. An alpha character at the intersection of a row and column indicates that a program accesses that data file or table. The alpha character indicates the type of access – Read, Insert, Delete, etc.
This AKC09 cross reference is in either maintained an EXCEL spreadsheet (simple version) or in a comprehensive MS Access mini-application complete with its own reports and data entry and correction panels to maintain the AKC09 information. This section identifies all major files and DB data structures by fully qualified and English language content description. A data structure inventory.
Also provides a list of component relationships which read or update the data structures. This is necessary if a data structure is changed many programs within the main application, subsystem components which use the structure, or other applications which use the structure. If a change occurs to a structure in one system and components of another system use that structure, they will have to change as well. This section identifies what other components within this or other subsystems would have to change.
Provides understanding of which files and or databases are accessed by which programs (and, therefore, by which subsystems) – allows understanding of those subsystems which could be affected by any planned change. Provides a list of all programs that access any files or databases and the type(s) of Access that the Program(s) allow.
How is it used?
This section identifies all major files and DB data structures by fully qualified and English language content description. A data structure inventory. Also provides a list of components relationship which read or update the data structures. This is necessary if a data structure is changed many programs within the main application, subsystem components which use the structure, or other applications which use the structure. If a change occurs to a structure in one system and components of another system use that structure, they will have to change as well. This section identifies what other components within this or other subsystems would have to change.
Why is it important?
(1) Identifies all data structures within and used by the application, the application components that use them and how the component uses the data structure (read, write, update, insert).
(2) Provides understanding of which files and or databases are accessed by which programs (and, therefore, by which subsystems) – allows understanding of those subsystems which could be affected by any planned change.
(3) Provides a list of all programs that access any files or databases and the type(s) of Access that the Program(s) allow.
IT Support Services Comments