1.3 Program design and developmentA loop, not a straight line

A development process is the way a team gets from an idea to a working program. Some processes are ordered and intentional: plan everything, then build, then test. Some are exploratory: try something, see what happens, adjust. Most real projects mix both. Either way, the course names four common phases: investigating and reflecting, designing, prototyping, and testing.
?Wait, what's a prototype?
Investigating and reflecting means finding out what users need and what the program must do, and later, looking back at what you learned. Designing means planning how the program will meet those needs. Prototyping means building a version. Testing means checking whether it works and whether it actually helps people. Then you reflect on the results, and very often you go around again.
Iterative and incremental
Two words describe how that going-around works, and the exam loves to test the difference. A development process that is iterative requires refinement and revision based on feedback, testing or reflection throughout the process. It may mean revisiting earlier phases: testing shows users are confused, so you go back to designing. Iterate means repeat. You keep improving the same work.
A development process that is incremental breaks the problem into smaller pieces and makes sure each piece works before adding it to the whole. Build the login screen, test it. Then add the task list, test it. Then add reminders, test those. Increment means a step added. You grow the program one tested piece at a time.
?Wait, what's the difference between purpose and function again?
I thought about it. Show me
- Weeks 1, 2 and 4 each add a new piece and test it before moving on: that is incremental.
Why?
Incremental = break into pieces, make sure each works, then add it to the whole. - Week 3 revises existing work (search) because of feedback, then retests: that is iterative.
Why?
Iterative = refine and revise based on feedback, testing or reflection, often revisiting design. - Overall, the project is both. That's normal, and exam questions sometimes test exactly that.
Answer: Incremental: weeks 1, 2 and 4. Iterative: week 3. The project as a whole uses both.
Stuck? Get a hint
- For each week, ask: did they add something new, or improve something that already existed?
- Adding a new tested piece is incremental.
- Revising because of feedback is iterative.
- AIterative development, because the developer keeps revising the same procedure
- BIncremental development, because each piece is made to work before it is added to the whole
- CEvent-driven development, because each procedure runs when called
- DExploratory development, because there is no plan
Show the answer
B. Making each piece work before combining is the definition of incremental development. Nothing in the story is revised because of feedback, so "iterative" is the trap, and event-driven describes how a program runs, not how it is built.
- Phases: investigating and reflecting, designing, prototyping, testing. Testing and reflection can send you back to any phase.
- Iterative: refine and revise based on feedback, testing or reflection, often revisiting earlier phases.
- Incremental: break the problem into pieces, and make each piece work before adding it to the whole.
- A process can be ordered and intentional or exploratory, and most real projects use both iterative and incremental steps.