Lecture 5: Creating and Testing Programs, Basic Debugging

Vocabulary flashcards covering key terms and concepts from Lecture 5, including code commenting, program design strategies, testing practices, debugging, and historical computer terminology.

Software Engineering

A subfield of computer science that deals with the processes for constructing large pieces of software.

Comments

Descriptive text placed into code for human benefit that is ignored by the computer during execution.

Python Comment Symbol (#)

The character placed in front of text in Python to mark everything after it on that line as a comment.

Triple-Quoted String

A string delimited by ''' or """ that spans multiple lines and is sometimes used like a multi-line comment when unassigned.

Whitespace

Blank lines and spaces in code used to visually separate sections and make code structure easier to read.

Pseudocode

An informal, high-level description of program steps written in human language or comments before filling in actual code.

Debugging

The process of finding where a program is failing, determining the source of the error, and fixing it.

Typical Cases

Test cases representing common or normal input values to verify that a program functions properly under standard conditions.

Edge Cases

Test cases representing special, boundary, or less common conditions (such as extreme limits or transition points) to ensure robust program behavior.

Incremental Development

A software construction process ("pyramid style") where small pieces of code are written and tested step-by-step to maintain a stable program throughout development.

Arch Development Style

An approach to software construction where testing is delayed until all code is completed, leaving the structure unstable until every piece is in place.

First Actual Computer Bug

A physical moth found stuck in Relay #70 Panel F of the Mark II computer at Harvard University in 1947.

Grace Hopper

Rear Admiral (1906–1992) whose team at Harvard University recorded the first actual computer bug in 1947 while working on the Mark II computer.

Steps to Solve a Programming Problem

The four-stage problem-solving sequence: 1) Understand the problem, 2) Make a plan, 3) Execute the plan, and 4) Review your work.