Organizations should keep system documentation on hand to ensure that the system is properly cared for, that changes are controlled, and that the organization knows what’s on the system. What does not need to be in this type of documentation?

A.
Functionality

B.
Changes

C.
Volume of transactions

D.
Identity of system owner

Explanation:
C: It is not important to have the amount of work that the system carries out included in the system documentation. The number of transactions usually changes
daily and thus is usually captured through some type of automated performance tool if the company needs to keep track of this information.
+ A is incorrect because system documentation should include a description of the system’s functionality. Functionality is the reason we have systems and
software. The functionality of a system and how it interacts with other systems should be fully understood and documented.
+ B is incorrect because changes made to the system should be included in the system documentation. Documentation is very important for data processing and
networked environments. If changes are not properly documented, employees will forget what actually took place with each device. If the environment needs to be
rebuilt, for example, it may be done incorrectly if the procedure was poorly or improperly documented.
+ D is incorrect because the system owner’s identity should be included in the system documentation. The system owner is responsible for the functionality and
availability of the system. If something goes wrong, the system owner needs to be contacted; thus, this information must be documented.