APCSP UNIT 3

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/12

encourage image

There's no tags or description

Looks like no tags are added yet.

13 Terms

1
New cards

Input

Data that are sent to a computer for processing by a program. Can come in a variety of forms,

such as tacotile interaction, audio, visuals, or text.

2
New cards

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.

3
New cards

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.

4
New cards

Event Driven Programming

Some program statements run when triggered by an event, like a mouse click or a key press.

5
New cards

Program

A collection of program statements. Programs run (or “execute”) one command at a time.

6
New cards

Program Statement

A command or instruction. Sometimes also referred to as a code statement.

7
New cards

Sequential Programming

program statements run in order, from top to bottom

8
New cards

Comment

Form of program documentation written into the program to be read by people and which do not

affect how a program runs

9
New cards

Fault Tolerant

Can continue to function even in the event of individual component failures. This is important

because elements of complex systems like a computer network fail at unexpected times, often in

groups.

10
New cards

Debugging

Finding and fixing problems in an algorithm or program

11
New cards

Documentation

A written description of how a command or piece of code works or was developed

12
New cards

Development Process

The steps or phases used to create a piece of software. Typical phases include investigating,

designing, prototyping, and testing.

13
New cards

Pair Programming

A collaborative programming style in which two programmers switch between the roles of writing

code and tracking or planning high level progress.