[Class Report] Systems Development (Year 3), Week 53
Final Adjustments & Presentation Preparation: Turning Completion into Something That Communicates
In Week 53, the class moved into the final polishing phase of the project.
Students worked on bug fixes, UI improvements, and documentation updates, focusing on shaping the project into something that would communicate clearly in the final presentation.
The key theme this week was:
From “it works” to “it communicates.”
■ Teacher’s Introduction: “Quality Is Decided by the User’s Perspective”
Mr. Tanaka: “What matters is not whether the developer understands it,
but whether someone using it for the first time can use it smoothly.
Today, we review your systems from that point of view.”
The teacher presented the following review points:
- Can a first-time user operate it without confusion?
- Will users know what to do when an error occurs?
- Is the display clear and easy to understand?
- Is the AI behavior appropriate?
■ Goals for Today
- Make the main use cases run reliably
- Improve the UI so it is easier to understand
- Complete the README and presentation materials
- Create the flow for the presentation demo
■ Practical Exercise 1: Bug Fixing and Stabilization
First, students fixed issues found during integration testing.
Common bugs
- Mismatched API response keys
- AI output exceeding the character limit
- Crashes caused by invalid input
- Fallback processing not working
What they did
- Strengthened validation
- Added exception handling
- Identified causes through logs
Student A: “I’m getting better at fixing things while checking the logs!”
■ Practical Exercise 2: UI Improvements from the User’s Perspective
Next, students thoroughly reviewed the UI.
Improvement points
- Making the operation steps clearer
- Improving the clarity of buttons and input fields
- Improving error messages
- Adding explanations for AI-generated output
Example:
*This text was generated by AI.*
Student B: “Just adding explanations makes it much easier to use.”
■ Practical Exercise 3: Final Documentation Updates
Students completed the README and design documents.
Included content
- System overview
- Feature descriptions
- How to use it (step-by-step)
- What to do when errors occur
- Explanation of the APIs and AI used
- Key points of the safety design
Student C: “It’s hard to write while assuming someone else will read it.”
■ Practical Exercise 4: Designing the Presentation Demo Structure
Each team planned the flow of its final presentation.
Common presentation structure
- System overview
- Use case explanation
- Demo (normal scenario)
- Error handling and fallback
- Key ideas and design highlights (AI and architecture)
Teacher: “What matters in a demo is not just that it succeeds,
but that your intention comes across clearly.”
■ Practical Exercise 5: Rehearsal (Mock Presentation)
Each team practiced a short presentation.
Feedback they received
- The explanation relied too much on technical terminology
- The demo flow was hard to follow
- The AI explanation was not sufficient
- The explanation of error handling was strong
Student D: “When I actually explain it out loud, I notice where my understanding is still weak.”
■ What the Whole Class Realized
- Quality changes depending on how you communicate it
- UI and explanation need to work together
- Error handling is something that will be evaluated in the presentation
- AI features do not come across unless they are clearly explained
■ Final Comment from the Teacher
“You have all gained
the ability to build systems.
What you need now is
the ability to communicate them to others.
A presentation is not the goal itself.
It is an opportunity to put your design thinking into words.”
■ Homework (Before the Final Presentation)
- Create presentation slides
- Do a final check of the demo procedure
- Think of three possible questions you may be asked
■ Preview of Next Week: Final Presentation Day
Next week is finally
the Final Presentation Day.
Students will present one complete system that brings together
everything they have learned over the past three years,
and the class will share the results together.
Week 53 was an important class not only for finishing the system,
but for shaping it into something that communicates clearly.
The students are refining both their technical skills and their ability to express their ideas
as they prepare for the final presentation.