Students complete the Unit Assessment and then spend the rest of the class sharing their projects.
Purpose
This lesson provides a bookend to Unit 3 where students demonstrate their learning through their projects and a multiple choice assessment.
NOTE: As of 9/2/2022, your quiz in Formative is open for you to see what you missed.
Unit 3 - Intro to App Design
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.
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.
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.
Program Statement: a command or instruction. Sometimes also referred to as a code statement.
Program: a collection of program statements. Programs run (or “execute”) one command at a time.
Sequential Programming: program statements run in order, from top to bottom.
Event-Driven Programming: some program statements run when triggered by an event, like a mouse click or a key press
Documentation: a written description of how a command or piece of code works or was developed.
Comment: a form of program documentation written into the program to be read by people and which does not affect how a program runs.
Pair Programming: a collaborative programming style in which two programmers switch between the roles of writing code and tracking or planning high-level progress
App Screen Size: the x-axis runs across the page, and the y-axis runs down the page. The origin is NOT in the middle but rather, at the top left of the screen.
CamelCase: a typographical convention in which an initial capital is used on the first letter of the SECOND element name (example: iPhone, redButton, musicPop)
Debugging: Finding and fixing problems in an algorithm or program.
Development process: the steps or phases used to create a piece of software. Typical phases include investigating, designing, prototyping, and testing
Event: associated with an action and supplies input data to a program. Can be generated when a key is pressed, a mouse is clicked, a program is started, or by any other defined action that affects the flow of execution.
Incremental Development Process: a design approach that breaks the problem into smaller pieces and makes sure each piece works before adding it to the whole.
Iterative Development Process: 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.
Plagiarism: The use of material created by someone else without permission and presented as one’s own
Program Requirements: descriptions of how a program functions and may include a description of user interactions that a program must provide.
Program specification: a description of all the requirements for the program.
Syntax Error: a mistake in the program where the rules of the programming language are not followed.
Software: A program or a collection of programs
When designing an app, it must have a
PURPOSE: WHY do you need this app? What problem does it solve? Who benefits from using this app?
FUNCTION: HOW does it work? What steps are needed for your app to run?