[Class Report] Systems Development (Year 3), Week 54
~ Final Presentation Day: Communicating Three Years of Learning “as a System” ~
Week 54 was finally the final presentation day.
Everything the students had built up since their first year—
- programming
- system design
- API integration
- generative AI utilization
- secure design
—was brought together in
a culminating class in which they presented their成果 as a single system.
■ Teacher’s Introduction: “Today is the day you stand as engineers”
**Mr. Tanaka: “Today is not a class.
Today is the day you show your成果 as developers.
What matters is not perfection,
but being able to communicate
how you thought and how you designed.”**
The atmosphere in the classroom felt different from usual,
and the session began with a slight sense of tension.
■ Presentation Format
Each group gave a presentation of 7 to 10 minutes.
Structure
- System overview
- The problem it solves
- Use case explanation
- Demo (normal flow + error flow)
- Design innovations (API, AI, security)
- Future improvement ideas
■ Presentation 1: AI Learning Support System
Content
- English sentence input → translation API + AI-assisted explanation
- Difficult expressions explained in simpler language
Key Design Points
- Clearly labeled AI output as “supplementary information”
- Falls back to a dictionary API when errors occur
Teacher’s comment:
“The design is good because AI is limited to a support role for explanation.”
■ Presentation 2: Event Information Summary App
Content
- Retrieves event information through a news API
- Summarizes it with AI
- Displays it in a list-based UI
Key Design Points
- Fast display through asynchronous processing
- Shows the original article if AI fails
Student comment:
“Adding caching made a huge difference in the user experience.”
■ Presentation 3: Library Recommendation System
Content
- Book information API + AI-generated recommendation text
- Displays recommendations based on users’ interests
Key Design Points
- Validates and shortens AI-generated text
- Clearly labels content as “AI recommendation”
Teacher’s comment:
“You’ve done a solid job designing it so users don’t trust AI too blindly.”
■ Presentation 4: Weather-Linked Task Management
Content
- Suggests tasks based on weather API data
- Recommends indoor tasks on rainy days
Key Design Points
- Shows regular task lists even if the API fails
- Designed so the feature blends naturally into the UI
■ Overall Feedback
Strengths
- Nearly all groups maintained separation of responsibilities (UI / Service / API)
- AI was handled appropriately as a supporting feature
- Fallback design was well thought out
- Logging and error design were close to real-world practice
Areas for Improvement
- There were differences in UI clarity across groups
- Some groups did not explain their AI usage well enough
- A few groups had insufficient consideration of error cases
■ Peer Feedback
After the presentations, all students exchanged comments.
Student A: “Seeing other groups’ designs helped me notice areas we could improve.”
Student B: “It was interesting how each group used asynchronous processing differently.”
■ Looking Back on Three Years (Overall)
At the end, the teacher looked back on the flow of the past three years.
Year 1
- Programming fundamentals
- Writing code that works
Year 2
- System design
- Team development
- Separation of responsibilities
Year 3
- API integration
- Generative AI
- Secure design
- Integrated development
■ The Teacher’s Final Words
“You are no longer simply
people who can write programs.
You are now
people who can design systems and explain them.
Technology will continue to change from here on.
But what you have gained up to today—
- the ability to design
- the ability to break problems down
- the ability to think safely and securely
—will continue to serve you for a long time.”
■ Student Reflections (Selected)
- “At first I didn’t even understand code, and now we’ve come this far.”
- “I really felt that design is the most important part.”
- “AI is useful, but I learned that how you use it matters.”
- “Working in a team taught me the most.”
■ Closing the Class
The presentation day ended with applause.
The classroom was filled with faces relieved from tension and a strong sense of accomplishment.
■ Overall Summary
Week 54 was
a class in which students proved their three years of learning in a concrete form.
The students had grown greatly—not just as programmers, but as:
- designers
- implementers
- and communicators
The efforts of this past year, and of these past three years,
will surely become strengths that will help them no matter what field they go on to pursue.