| A | B |
|---|
| input | data that are sent to a computer for processing by a program. Can come in a variety of forms, such as tactile interaction, audio, visuals, or text. |
| output | any data that are sent from a program to a device. Can come in a variety of forms, such as tactile interaction, audio, visuals, or text. |
| User interface | the inputs and outputs that allow a user to interact with a piece of software. User interfaces can include a variety of forms such as buttons, menus, images, text, and graphics. |
| Event-Driven Programming | some program statements run when triggered by an event, like a mouse click or a key press |
| Program | a collection of program statements. Programs run (or “execute”) one command at a time. |
| Program Statement | a command or instruction. Sometimes also referred to as a code statement. |
| Sequential Programming | program statements run in order, from top to bottom |
| Comment | A form of program documentation written into the program to be read by people and which do not affect how a program runs |
| Debugging | Finding and fixing problems in an algorithm or program |
| Documentation | a written description of how a command or piece of code works or was developed |
| Development Process | the steps or phases used to create a piece of software. Typical phases include investigating, designing, prototyping, and testing. |
| Pair Programming | a collaborative programming style in which two programmers switch between the roles of writing code and tracking or planning high-level progress |
