Final answer:
Company policies should not be part of system documentation, as they do not describe the technical or functional aspects of the system. Instead, system documentation should include items strictly related to the system and its operation.
Step-by-step explanation:
What Should Not Be Part of System Documentation?
System documentation is an important aspect of project management and serves as a reference guide for users and maintainers of the system. It generally includes detailed descriptions of the system's functionality, maintenance, user interfaces, and code. When considering what should not be part of system documentation, we should ensure the content is strictly related to the actual system and its operation.
Schedules - While they are important for project management, schedules pertaining to the development process are not usually included in system documentation, as they do not describe the system itself.
Adjustment and corrections entry - These may include logs or records of the changes made to the system post-deployment and could be part of the documentation for maintenance purposes.
- Reports - Reports generated by the system or about the system's performance would be a relevant part of documentation to assist users in understanding the output and operation of the system.
- Company policies - Although vital to the functioning of an organization, company policies are not a component of system documentation, as they do not describe the system's technical or functional aspects.
Therefore, the element that should not be part of system documentation is D. Company policies. This information is usually part of the organization’s internal policy documentation but does not directly pertain to the technical or user guidelines of a specific system.