AP Computer Science Principles Big Idea 1

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/29

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.

30 Terms

1
New cards

Collaboration in computing

Working together with others to improve computing innovations and incorporate diverse perspectives./n

2
New cards

Purpose of collaboration

To create better, less biased, and more user-friendly computing innovations./n

3
New cards

Benefits of diverse perspectives

Helps avoid bias and improve program functionality by incorporating different user needs and ideas./n

4
New cards

Effective collaboration

Equal participation, open communication, and early establishment of collaborative norms./n

5
New cards

Iterative development

A process that includes ongoing testing, feedback, and refinement of a program./n

6
New cards

Incremental development

Building a program piece-by-piece, testing each part before combining them into the whole./n

7
New cards

User-focused design

Development that prioritizes the needs, feedback, and experiences of the intended users./n

8
New cards

Development phases

Investigating, designing, prototyping, and testing a program./n

9
New cards

Documentation

Written explanations of how code works and why certain choices were made during development./n

10
New cards

Program inputs

Data received by a program (e.g., user actions, other programs) to produce outputs./n

11
New cards

Program outputs

Data or actions produced by a program based on inputs or internal states./n

12
New cards

Code segment

A specific part of a program that performs a particular function./n

13
New cards

User interface design

Creating the layout and interaction elements of a program to make it easy to use./n

14
New cards

Event-driven programming

Programs that execute based on specific user or system actions, like clicks or key presses./n

15
New cards

Feedback

Input from users or collaborators used to improve a program./n

16
New cards

Abstraction

Hiding complex details to focus on high-level functionality when designing code./n

17
New cards

Program specification

A detailed description of how a program should function and interact with users./n

18
New cards

Planning in development

Using diagrams, storyboards, or other visuals to map out how a program should behave./n

19
New cards

Program behavior

How a program functions and responds to various inputs during execution./n

20
New cards

Program testing

Checking that a program works correctly for all intended inputs and situations./n

21
New cards

Pair programming

A collaborative model where two programmers work together at one workstation./n

22
New cards

Online collaboration tools

Platforms that allow for real-time sharing and feedback during program development./n

23
New cards

Conflict resolution

Working through disagreements to ensure productive collaboration in team projects./n

24
New cards

Acknowledging sources

Giving credit for any code or ideas used that were created by others./n

25
New cards

Comments in code

Notes added to code to explain its purpose and improve readability for others./n

26
New cards

Common planning tools

Flowcharts, pseudocode, and storyboards used to design programs before coding begins./n

27
New cards

Program constraints

Limits or requirements such as hardware, software, or user expectations that influence development./n

28
New cards

Consensus building

Reaching agreement in a group to make collaborative decisions about a project./n

29
New cards

Error identification

Detecting mistakes in code using testing or code review./n

30
New cards

Debugging

Fixing bugs or problems discovered in a program during development or testing./n