Answer:
See answer below
Explanation:
He should not encourage his new technicians to document theories that were followed at the end of the troubleshooting process. This because the theory might not add to their knowledge about troubleshooting. What is paramount and needed to be documented for future references are their findings, actions taken by them and the outcome achieved through the whole troubleshooting process.
In trouble shooting, a technician aims at solving problems on computer system by following a set of steps such as establishing theory of probable cause, testing the theory to determine the cause, establishing a plan of action and implementing the solutions; in order to determine and solve the problem.
The theories here are the steps that were followed in determining and solving the observed issues hence should not be documented except the findings, actions taken and the final outcomes that were achieved.
They act like a filter for info a person receives
A company’s technology policy applies only to the Internet usage of employees
I’m not sure if it right so sorry if it wrong!
Can you translate please i’ll help better
The segments of the flowcharts have been recreated such that it does the same processes under the same conditions, but is structured. Their respective pseudo codes have also been created. See the attached pdf.
<h3>What is a pseudo code?</h3>
A pseudo code is a notation used in program design that looks like a simplified computer language.
<h3>Why is it important for flow chart to be structured?</h3>
This preference derives from the fact that such flowcharts are easier to understand and produce less mistakes in human perception.
The organized flowchart primarily aids the mission in the development of new algorithms by encapsulating a variety of data points within an interconnected depiction.
Learn more about flowcharts at;
brainly.com/question/6532130
#SPJ1
