Home
ISSUE
Are History Files viewed as a business requirement or an implementation issue?
FUNCTIONAL OVERVIEW
Many systems have implemented separate physical files to store historical records. For example, CUSTOMER and CUSTOMER_HISTORY files. Records may be written to the History files as a result of a scheduled archiving process, or when a particular event has occurred, for example Order Completion.
The attributes of the History File may, or may not be identical to the original file. Should History files be counted?
GENERAL DISCUSSION AND RESOLUTION A separate History file and its associated maintenance functions is counted where the all the following conditions are satisfied: Additional conditions that may indicate that a separate History file should be counted include: But this condition alone is not sufficient. - The file is not user requested or
- The attributes on the History file are identical to the attributes in the current file. or
- The data values can be reproduced from data currently stored within the system or
- The file exists only for performance reasons or
- The History File contains Audit data only.
- The file is user requested and
- The attributes on the History file are different from the attributes in the current file. For example, Summarised data and
- The data values cannot be reproduced from data currently stored within the system.
- The existence of separate maintenance and reporting functions for the History file
A separate History file is not counted where any one of the following conditions exist:
Separate physical files do not result in separate logical files.
|
