Today’s objectives

• Describe how a development process works — its four phases — and tell iterative from incremental (LO CRD-2.E)
• Explain how a program and its interface are designed: investigation, requirements, specification (LO CRD-2.F)

Bell ringer

Your club is running a bake-sale stand at Friday's game, and you're in charge. List the first six things you would do — in order — between right now and the moment the stand opens.

Now go back and label each step with your own one-word tag for what KIND of step it is: finding-out? planning? building? checking? Keep the list — we'll use it all period.

AP TIP: Iterative = LOOPS (revise, revisit earlier phases). Incremental = PIECES (verify each part before adding it). A process can be both at once.

Stop and think

1. A team builds a chat app one feature at a time — messages first, verified working, then emojis, then photos, each verified before it joins the app. Iterative, incremental, or both? Defend your label with the CED definition.
2. After user testing, a team leaves the code alone but returns to the design phase to rework two screens. Which term describes this — and why is revisiting a phase NOT evidence of failure?
3. A programmer facing a brand-new kind of problem starts experimenting with no fixed plan. Which kind of development process is this, and is it legitimate?

Answer in complete sentences. Then check yourself with the matching CFUs on the Topic 1.3 page.

AP TIP: 'Watching users in their normal routine' = direct observation. 'Watching users try your product' = user testing. Exam items hinge on that difference.

Stop and think

1. A team wants to build an app for the school library but has never spoken to the librarian. Choose TWO investigation methods for them, and say what each would reveal that the other wouldn't.
2. In one sentence each: what do the requirements describe, and what does the specification do to those requirements?
3. A teammate says the design phase is 'just drawing what the app looks like.' List three OTHER design-phase activities from the CED that prove them wrong.

Answer in complete sentences. Then check yourself with the matching CFUs on the Topic 1.3 page.

Today in one box

• A development process can be ordered and intentional or exploratory; four phases are commonly used: investigating and reflecting, designing, prototyping, testing
• Iterative = loops (refine and revise, revisit earlier phases); incremental = pieces (verify each before adding it to the whole)
• Investigation — surveys, user testing, interviews, direct observations — determines requirements
• The specification defines the requirements; the design phase outlines how to accomplish it: brainstorming, storyboarding, modules, UI diagrams, testing strategy

Before next class: Before tomorrow, chew on this: in June you wrote the most brilliant program of your life. In September you open the file — and you can't read your own code. Nothing is broken. Every line still runs. So what, exactly, went wrong?

Today’s objectives

• Describe the purpose of a code segment or program by writing documentation — and explain why comments never affect how a program runs (LO CRD-2.G)
• Acknowledge code segments used from other sources correctly — origin or author's name, in the program documentation (LO CRD-2.H)

Bell ringer

The June mystery, solved by you: in June you wrote a 300-line program — your best ever. In September you open it and find variables named x, temp2, and stuff, no notes of any kind, and you cannot follow your own logic. Every line still runs perfectly.

Write 3–4 sentences: what exactly went wrong, if nothing is broken? Then list three specific things June-you could have left behind that would rescue September-you.

Stop and think

1. Using the word 'documentation,' explain precisely what June-you failed to do — and name the TWO audiences every program has.
2. A teammate wants to delete all comments before submission 'to speed the program up.' In two sentences, explain what will and won't change, citing what comments are for.
3. Your little cousin's block-based coding app has no comment feature. Give two other methods their team could use to document the program — and explain why 'no comments possible' doesn't mean 'no documentation needed.'

Answer in complete sentences. Then check yourself with the matching CFUs on the Topic 1.3 page.

AP TIP: Sufficient acknowledgement = IN the documentation + origin or author's name. Both parts, every time — 'I changed it a little' is not a third option.

Stop and think

1. State the two things a sufficient acknowledgement requires, per the CED — the place it lives and the content it includes.
2. A classmate says: 'The Create PT allows AI now, so I can just have it write my procedures.' What TWO obligations did they skip, and what does each one cost?
3. Your partner wrote half the procedures in your shared program. Nothing was 'copied' from anywhere. Does anything need acknowledging? Exact trigger.

Answer in complete sentences. Then check yourself with the matching CFUs on the Topic 1.3 page.

Exit check — I can…

• ☐  run a development process and tell iterative from incremental (LO CRD-2.E)
• ☐  trace investigation → requirements → specification → design (LO CRD-2.F)
• ☐  write documentation that helps the next person — including future me (LO CRD-2.G)
• ☐  credit borrowed and AI code the way the Create PT requires (LO CRD-2.H)