Troubleshooting

Question 1

Name the 6 Troubleshooting Steps

Answer 1

1. Identify the Problem
2. Plan a solution
3. implement the solution
4. Test the solution
5. Analyse the effects of the solution
6. Documenting throughout the process

Question 2

What are two Troubleshooting problem solving approaches? Explain them

Answer 2

Half-split testing and Linear testing

Half-split is when you split the program into two halves and test it there, if there’s no issues then you know the problem has occurred in the second half of the program which narrows down your problem scope which helps save serious time.

Linear is when you test the program sequentially and can either be done top down or bottom up, this is not useful when applying it to a large project as it will take too much time. Top down is when you test a system from the most complex level and then move onto smaller/simpler parts until the problem is found.

Question 3

What should be done during the Identify the Problem stage?

Answer 3

Identify the source of the problem, the symptoms of the problem, the area affected and any new changes.

Question 4

Name three problem solving tools

Answer 4

1. Debugging tools (comes with most programming software)
2. Internet Resource
3. Desk Checking

Question 5

Explain the ‘Plan a Solution’ & the ‘implementing a solution’ stages

Answer 5

Find a solution to the problem and before implementing it make a plan of action as you shouldn’t be blindly implementing a solution.

Question 6

Explain the ‘Testing a Solution’ stage

Answer 6

The technician should test the program after implementing their solution to test if the problem has been fixed, this can be done by testing to see if the functional requirements are working as expected in the program and documenting your results

Question 7

Explain the ‘Documenting throughout the process’ stage

Answer 7

This should be done by the technician throughout the process of troubleshooting and should show how you’ve ended up where you are now with the program. These documents include a Plan of Action, test cases and outcome of your solution.

Question 8

When should you use the linear troubleshooting method?

Answer 8

When you have a clear understanding of the problem and possible solutions

Question 9

Why should you use the half-split troubleshooting method?

Answer 9

It allows you to narrow down the scope of you problem quicker than Linear.