Class 7 · CBSE AI · Strand D — The Architect's Capstone
Iterating on an AI project — fixing what user testing finds
Iteration means fixing the top problems from testing and checking nothing else broke. Regression testing, for Class 7.
What this concept actually says
- Iteration is implementing the highest-priority fixes from user testing and verifying each fix resolves the observed problem
- Regression testing: confirming that a fix doesn't break something that was already working
- The iteration cycle ends when the highest-severity issues are resolved — perfection is not the target, a defensible and improved system is
An analogy your child will recognise
Fixing a leaky pipe
A plumber who patches a leaky pipe and immediately turns the water back on full force — without checking slowly first — risks discovering a new leak created by the increased pressure. Regression testing is checking slowly: making sure the fix holds before you stress-test it, and making sure fixing one leak didn't create another.
Cricket team selection after a loss
A captain who drops a batsman after one bad match because 'I feel like we need a change' isn't iterating — they're guessing. A captain who looks at the data (the batsman struggled against left-arm spin in three consecutive matches), makes a targeted change (bring in a player who plays spin well), and then tests it against a left-arm spin-heavy team — that's iteration.
Common misconceptions to watch for
- Iteration means keep changing things until it feels right — iteration means make targeted changes based on evidence and verify each one
- Once a bug is fixed, you don't need to test that area again — regression testing exists precisely because fixes in one area commonly create bugs in connected areas
Key facts in one breath
- A regression test reruns previously-passing tests after a change to confirm they still pass — it prevents fixes from introducing new breakages
- Iteration is not random experimentation — each change should be traceable to a specific observation from user testing or integration testing
- In professional software, changes made without corresponding tests are called 'untested changes' and are considered engineering debt
- Iteration ends not when the system is perfect but when the most critical issues are resolved and the team can defend the remaining known limitations
How Dhee Learning teaches this — the 3-stage question loop
Every Dhee Learning session for this concept follows three stages. We share the questions Dhee actually asks, so you can hear what a session sounds like.
Stage 1 — Surface
You've fixed three issues from your user test and the system feels better to you. But how do you actually confirm each fix worked — without just hoping it did?
Rote answer
"Child says 'I'll try it again myself' — testing their own fix on themselves, which doesn't reproduce the original conditions"
Understood
"Child describes running the specific scenario that revealed the original problem to confirm it no longer occurs — ideally with the same type of user, or at minimum with the same realistic input that originally failed"
Stage 2 — Reasoning
You changed how the upload button works to fix User 1's confusion. Three days later you discover that this change broke the way the AI receives the uploaded image — an integration bug you didn't notice. What process would have caught this, and what does it tell you about the relationship between fixing and testing?
Follow-up Dhee may use: What is the risk of running out of time in the iteration phase — and what's the responsible thing to do if you can't fix everything before the showcase?
Stage 3 — Application
For each of the three highest-priority issues from your synthesis table, write: (1) the specific change you made to address it, (2) the test you ran to verify it's fixed, and (3) any regression check you performed. How does writing this down make the iteration phase part of your project's evidence, not just its history?
Misconception Dhee watches for: Child makes changes based on intuition or aesthetic preference rather than in direct response to specific observations from user testing — losing the evidence chain from problem to fix
Related concepts
Want your child to actually understand this?
Dhee turns this concept into a 15-minute spoken session — asking, listening, and probing — so your child builds the idea themselves.
Frequently asked questions
What is iteration — explained for kids? +
Iteration means fixing the top problems from testing and checking nothing else broke. Regression testing, for Class 7.
What's the most common mistake children make about this concept? +
Iteration means keep changing things until it feels right — iteration means make targeted changes based on evidence and verify each one
How does Dhee Learning teach this in a Class 7 session? +
Dhee opens with a question — for example: "You've fixed three issues from your user test and the system feels better to you. But how do you actually confirm each fix worked — without just hoping it did?" — listens to your child's answer, then probes the reasoning behind it. The session ends when the child can apply the idea to a brand-new situation, not just recall it.