Question
Margaret Hamilton recounts how her experience with these things led her to develop the Universal Systems Language, or USL, in “What [these things] Tell Us.” For 10 points each:
[10m] Name these things that were manually identified by the Augekugel (“OW-gheh-koo-gull”) method. Historically, a specific type of these things was identified by DEADBEEF (“dead-beef”) appearing in a memory dump.
ANSWER: software bugs [or software errors, software faults, software defects, problems in software, flaws in software, or any other synonyms for software errors; accept crashes] (Augekugel means “eyeballing” in German, so the Augekugel method was just a computer operator looking at the code.)
[10h] USL specifies systems to eliminate errors before-the-fact, in contrast with this approach to software development. This approach to software development uses the “red, green, refactor” cycle.
ANSWER: test-driven development [or TDD]
[10e] Nowadays, errors are identified more easily thanks to syntax highlighters and debuggers built into these all-encompassing programs for software development. Visual Studio is one of these programs.
ANSWER: integrated development environments [or IDEs (“I-D-eez”); prompt on code editors; reject “environments”]
Data
| Team | Opponent | Part 1 | Part 2 | Part 3 | Total |
|---|---|---|---|---|---|
| Claremont A | Brown A | 10 | 0 | 10 | 20 |
| Columbia A | McGill A | 0 | 10 | 10 | 20 |
| Florida A | Purdue A | 10 | 0 | 0 | 10 |
| Georgia Tech A | Duke A | 0 | 0 | 10 | 10 |
| Harvard A | Vanderbilt A | 10 | 0 | 0 | 10 |
| MIT A | Florida B | 10 | 0 | 10 | 20 |
| Minnesota A | Penn A | 10 | 0 | 10 | 20 |
| North Carolina A | Johns Hopkins A | 0 | 0 | 10 | 10 |
| Ohio State A | Rutgers B | 10 | 0 | 10 | 20 |
| Penn State A | Illinois A | 0 | 0 | 10 | 10 |
| Rutgers A | Chicago A | 10 | 0 | 0 | 10 |
| Stanford A | Georgia Tech B | 10 | 0 | 10 | 20 |
| UC Berkeley A | Cornell A | 0 | 0 | 10 | 10 |
| WUSTL A | Indiana A | 10 | 0 | 10 | 20 |
| Yale A | WUSTL B | 10 | 10 | 10 | 30 |