CS Principles Unit 3 Application Design Concepts

The inputs and outputs that allow a user to interact with a piece of software. They include a variety of forms such as buttons, menus, images, text, and graphics

Data that are sent to the computer for processing by a program. Can come in a variety of forms, such as tactile interaction, audio, visuals, or text.

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.

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

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

Program statements run in order, from top to bottom.

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

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

A form of program documentation written into the program to be read by people and which do not affect how the program runs.

A collaborative programming style in which two programmers switch between the roles of writing code and tracking or planning high level progress.

Finding and fixing problems in an algorithm or program.

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

Associated with an action and supplies input data to a program. Can be generated when a key is presses, a mouse is clicked, a program is started, or by any other defined action that affects the flow of execution.

A design approach that breaks the problem into smaller pieces and makes sure each piece works before adding it to the whole.

A design approach requires refinement and revision based on feedback, testing, or reflection throughout the process. This may require revisiting earlier phases of the process.