[Class Report] Introduction to System Development — Week 32: Semester Wrap-Up and Individual Feedback

Week 32 was the final session of the semester. We looked back on our work, verified final portfolio submissions, ran quick demos, and delivered individual feedback to clarify the “next strengths to grow.”

■ Instructor’s Opening: “A Day to Confirm Small Steps Forward”

At the outset, Professor Tanaka emphasized visualizing growth over perfection. We reviewed the semester’s flow—design → implementation → testing → improvement → operations—and shared the importance of articulating outcomes in words.

■ Practice ①: Final Portfolio Check (Submission Verification)

We collected each student’s portfolio and checked whether the following required items were in place:

• Project overview (purpose & target users)
• Implemented features and tech stack
• Testing and log analysis results (numbers add credibility)
• Improvement history (what changed, when, and why)
• Run instructions (concise steps to actually run it)

Any gaps were addressed on the spot, with students making quick fixes and resubmitting during the session.

■ Practice ②: Short Demos (90 Seconds per Person)

Students gave brief demos based on their portfolios. The time limit trained them to communicate key points concisely. After each talk, classmates and the instructor offered one “what went well” and one “suggestion for improvement.”

• Highlights: UX improvements (input guidance & error messages), presenting quantitative improvements from testing, and clean modularization.
• Suggestions: Lead with the problem in the introduction; show sample input → expected output first; enrich the README.

■ Practice ③: Individual Feedback & Goal Setting for Next Term

We held short one-on-one sessions to advise on technical aspects (debugging skill, test design), communication (documentation, demo structure), and learning goals. Students reflected: “Persevering through debugging boosted my confidence,” “Next term I want to go deeper into design,” and so on.

■ Overall Summary (Instructor’s Feedback)

Professor Tanaka shared class-wide trends.

Strengths

• Students internalized a continuous improvement cycle (test → analyze → improve).
• Many worked with operations in mind, using documentation and runbooks.

Areas to Improve

• Some teams wandered in implementation due to insufficient depth in requirements definition and design.
• Build a habit of writing documentation so that “anyone can reproduce” the results.

For next term, the instructor set priorities: design skills, team role allocation, and better documentation.

■ Notices for Next Term

• Final portfolio submission deadline announced (for those not yet submitted).
• Suggested prep: introductory UML, ER diagrams basics, and a chapter on intro to architecture.
• Shared expectations for next term’s topics: system design, database design, and team development.

■ Closing Message (from the Instructor)

“This semester, we repeatedly practiced build → verify → improve → communicate. Next, let’s deepen how we build—design—to create greater value. Today’s reflection is a solid foundation for that.”

As a capstone to the term, first-year students put their growth into words and renewed their motivation for the coming semester. Great job, everyone!