AP CSP Unit 3 Review

0.0(0)
studied byStudied by 0 people
full-widthCall with Kai
GameKnowt Play
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/13

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

14 Terms

1
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.

2
New cards

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.

3
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.

4
New cards

Program Statement:

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

statement.

5
New cards

Program:

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

a time.

6
New cards

Sequential Programming:

program statements

run in order, from top to bottom.

No user interaction

Code runs the same way every time

7
New cards

Event Driven Programming:

some program

statements run when triggered by an event, like a

mouse click or a key press

Programs run differently each time depending

on user interactions

8
New cards

Documentation:

a written description of how a

command or piece of code works or was

developed.

9
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.

10
New cards

Debugging:

the process of finding and fixing problems in code

  • Describe- The problem

  • Hunt- For bugs

  • Try- Solutions

  • Document- As you go

11
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

12
New cards

Event handling

a programming concept where a program waits for an event to occur, such as a user clicking a button or data being input, and then executes a specific function, called a handler or listener, to respond to that event

13
New cards

Event listener

a fundamental concept in event-driven programming, allowing applications to react to various occurrences or "events" within a system. These events can originate from user interactions (like clicks, key presses, or mouse movements), system-level actions (like page loading or network requests), or other programmatically triggered occurrences.

14
New cards

(UI) elements

the interactive and informational building blocks of a digital product's interface