AP CSP unit 3

Why should element IDs have meaningful names

It helps humans remember and understand the purpose of various elements.

It makes finding errors easier

It helps other team members understand what is happening

Coding elements that provide the User the ability to INPUT into an app

Text box, button, a link

coding elements that the app uses to OUTPUT to the user

Text Label, image, sound

Output devices

Screen (monitor), speakers, vibration, printer

Input devices

mouse, keyboard, camera, microphone, sensors

Output

Elements and devices that the code or computer uses to send information to the user

Input

Elements and devices that send information to the computer for processing

Good names for elements follow these rules

can’t have spaces, can’t start with a number, capitalization matters

A good user interface

provides seamless and intuitive way for users to interact with a computer

User centered design means

Primarily focus on involving the target user audience throughout the design process to create an interface that meets their needs

The benefit of designing before coding

Guides the coding implementation and testing processes

The purpose of a design specification

Describing the requirements for how a program will work or users will interact with it.

Program statement

a command or instruction

Program

A collection of program statements

The differences between sequential and event-driven programming

Sequential programing: program statements run order, from top to bottom, no user interaction, code runs the same way ever time.

Event driven programming: 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

Documentation

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

Comments

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

Reasons to document

1) Remind ourselves what we want to do and why

2) help our team to figure out what we were doing and why

3) great way to start coding (pseudocode)

4) Can help others who may use our code in the future (including ourselves)

Pseudocode

Instructions in plain english that can later be converted into comments or code

Common documentation myths

once we document it never changes, bc it’s part of the original design it never gets changed, it should only include what’s important, it’s only for really big projects, our code is the only documentation we need.

Bug

A fault or flaw in a computer program or hardware that causes unexpected or desired results, deviating from the intended functionality

Debugging

The systematic process of finding, analyzing, and resolving errors, known as bugs

Debugging process

1) Describe the problem

2) Hunt for bugs

3) try solutions

4) document as you go

Debugging strategies

clean code, organized chunks, using comments, testing often, use console log

Test driven development

Testing after every change to the code to make sure that everything still works and nothing was broken

Resources for debugging

Documentation, partner, other students, internet

describe the flow of information during a fundamental computing cycle?

Input → Processing → Output

A "String" in computer coding is:

Character in coding like words

What is one difference between console.log and setProperty?

Responses

The console log is for debugging

primary purpose of internal documentation (i.e. comments) in a program?

To explain to future developers and maintainers the non-obvious logic, design choices, and flow of the source code.

Pair programming

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