U4: Debugging and Validating Data

Question 1

Trial and Error

Answer 1

• Good for programming as cost of failure is low
• Takes little time and money, low stakes

Question 2

Rule of Ten

Answer 2

• Trial and error cheaper in earlier stages of Software Development Life Cycle
• Error costs x10 more to fix at each next stage

Question 3

Iteration

Answer 3

Continually trying solutions, refining each one, getting closer to end goal

Question 4

Run-Time Error

Answer 4

• Occurs when program crashes
• Can be caused by dividing by 0, opening nonexistent file

Question 5

Syntax Error

Answer 5

• Mistake in writing code
• Ex: Missing variable, forgetting curly bracket
• AKA: Compile Time Errors as they’re caught while compiling

Question 6

Logic Error

Answer 6

• Program runs but output incorrect
• Can cause run-time error as well

Question 7

Top-down Design

Answer 7

Solution where problem broken down into smaller and smaller sub-problems until each can be solved in few steps

Question 8

Variable Inspection

Answer 8

Visualizers inspect values of objects

Question 8

Visualizers

Answer 8

Allow to see how code executes step by step

Question 9

Data Structure Visualization

Answer 9

Visualizers include tools for visualizing data structures (ex: arrays, lists, trees, graphs).

Question 10

Tracing

Answer 10

• Outputting values of variables during program
• Delete output statements when program debugged

Question 11

Test Data

Answer 11

• Should have wide range of input data
• Include different data (ex: 0, decimals instead of strings)

Question 11

Test Plan

Answer 11

• Includes aspects of program tested
• Outcomes of test (positive or negative and details to errors)
• Changes made to program

Question 12

Data Validation

Answer 12

Checking to ensure data entered is expected

Question 12

try… catch command

Answer 12

• “try” command tries algorithm that may cause crash
• “catch” command catches problem, stopping catch