Webxam: Troubleshooting

Top-down methodology is

• starts a a specific line of code

• problems are brought to you from management

• A user has a problem with a button that doesn't work

• Operations calls with a problem and you go for a ride in a convertible until they don't care about the problem anymore.

Implementing a solution is

• writing code for a customer

• putting changes to code into production

• gather and analyze data

• creating documents for the project

Botttom-up methodology is

• lying face-down on the floor weeping uncontrollably

• wher you bring a problem to management's attention to put in the debugging queue.

• operations calls with a problem and says that your code died on line 327

• working the troubleshooting steps backwards. in other words, the first step is to document how you solved the problem.

Spot the differences

• comparing your source code with the source code for another project and listing all the differences between them.

• comparing the output from a program you just modified with the results from the same program before you added the changes.

• comparing the problem with a similar problem in the past and using that problem's solution to fix your program.

• comparing your skills with other programmer's skills

Follow the path is

• following a piece of data from the user's workstation to the database.

• following your program's progress through the logs to determine the problem.

• retracing your route to lunch to try to find your missing phone.

• stepping through the code line-by-line.

Which choice is NOT a troubleshooting methodology?

• spot the differences

• follow the path

• bottom up

• top bottom

Gathering and analyzing the data and investigating the symptoms

• is the same as document the solution

• should only be done if there is time after the problem is solved

• are used by the programmer to determine the solution to the problem.

• are always performed by the customer.

Pick the correct order of steps in the troubleshooting process.

• Identify the problem, Select troubleshooting methodology, Document the problem and solution, Investigate symptoms, Gather and analyze data, Design a solution, Test a solution, Implement the solution

• Identify the problem, Select troubleshooting methodology, Investigate symptoms, Design a solution, Test a solution, Implement the solution, Gather and analyze data, Document the problem and solution

• Identify the problem, Select troubleshooting methodology, Investigate symptoms, Gather and analyze data, Design a solution, Test a solution, Implement the solution, Document the problem and solution

• Identify the problem, Select troubleshooting methodology, Test a solution, Investigate symptoms, Gather and analyze data, Design a solution, Implement the solution, Document the problem and solution