G_Week5,2025‐03‐19 - 24-S2-2-C-EduKATE/EduKATE_flutter GitHub Wiki

Time

19/03/2025

Attendees

Yi Wang
Siyi Liu
Dong-Jhang Wu
Rifang Zhou
Wenhui Shi
Wenjing Qi

add more if needed

Agenda

Team Stand-ups
Documentation Review and Structure
Code Refactoring and Architecture Discussion
Sprint 1 Deliverables Planning

Minutes

Team Stand-ups

Yi Wang What I did previously: Attended tutor, client, and group meetings to discuss project progress and requirements. Reviewed the existing code files and documentation, and participated in recording and adjusting the documentation structure. What I'm going to do next: Organize the current documentation and restructure the wiki to make all files clearer, more readable, and well-organized. Collaborate with the team to complete Sprint 1 deliverables and prepare for the next client meeting by further analyzing the requirements document.
Siyi Liu - What I did previously: Attended client and supervisor meetings to discuss requirements, reviewed and updated the codebase. What I'm going to do next: Organize existing documentation to make the GitHub structure clear and readable, and write the introductory section of the project in the wiki.
Dong-Jhang Wu What I did previously: Review the code and identify which parts may need to be redesigned to meet the sub-functional requirements. What I'm going to do next: Begin thinking and trying to implement some of the redesign method previously considered.
Rifang Zhou What I did previously: Refactoring the document structure of the project interface. What I'm going to do next: Re layer and simplify the current code.
Wenhui Shi What I did previously: Wrote the project personas and scenario, attended the client meeting and received and reviewed client files, joined group discussion and tutor meeting, then we changed user stories based on tutor feedback. I also completed the minutes for week5 client meeting and group meeting, formatted week3 and week4 client and group meeting minutes and moved them to the wiki. What I'm going to do next: start writing code based on our group discussion and assignment.
Wenjing Qi - What I did previously: Attended client and tutor meetings to discuss requirements, participated in writing user stories, personas, and scenarios, reviewed and updated the codebase, and organized user stories for Sprint 1 while planning for Sprint 2. - What I'm going to do next: Revise user stories and scenarios based on client feedback, collaborate with the team to finalize Sprint 1 deliverables, and prepare for the next client meeting by further analyzing the requirements document.

Documentation Review and Structure

The team discussed the need to improve the documentation structure based on tutor feedback. The tutor emphasized that all documentation should be well-organized, clear, and maintainable. The team agreed to divide into two subgroups - one focusing on code improvement and the other on documentation refinement.

Code Refactoring and Architecture Discussion

The team analyzed each part of the code to clarify their functions and identified areas for improvement. Dong-Jhang Wu proposed modifying the basic block_data.class, suggesting that some blocks should be allowed to have sub-sequences through inheritance. Rifang Zhou proposed a three-layer architecture: Model layer (data handling), Interaction layer (business logic), and UI layer (user-facing components).

Tutor Meeting Feedback

Last week the tutor asked the team to complete user stories and scenarios, then provided specific suggestions for changes. The tutor noted that the team had started with "as a little girl" but advised to use "as a user" instead to make the stories more general. The tutor also requested changes to document placement and the issue section organization. The team discussed these changes and agreed to implement all tutor suggestions immediately.

Actions

Action Item	Responsible	Due Date	Status
Reorganize project documentation and GitHub wiki	Yi Wang, Siyi Liu	Week 6	Completed
Refactor code architecture into three-layer structure	Rifang Zhou, Dong-Jhang Wu	Week 6	Completed
Revise user stories based on tutor feedback	Wenhui Shi, Wenjing Qi	Week 5	Completed
Write introductory section for the project in wiki	Siyi Liu	Week 6	Completed
Begin implementation of redesigned block_data.class	Dong-Jhang Wu	Week 6	Completed
Complete detailed meeting minutes and update wiki	Wenhui Shi	Week 5	Completed

8-Hour Work Tracking

Yi Wang

During Week 5, I actively participated in several important meetings that shaped the direction of our project work. First, I attended the tutor meeting, he emphasized the importance of well-structured, clear, and maintainable documentation. He also gave us feedback on our early sprint planning and user story writing. This session helped me better understand the expectations for Sprint 1 deliverables and highlighted areas where our documentation could be improved.

Next, I attended the client meeting, which provided critical updates. The client shared a more detailed requirements document and clarified some ambiguous parts of our earlier understanding, such as the functional scope of virtual vs. physical interactions and the expected user flow. This clarified our project objectives and allowed us to refine our development plan. I took notes during the session and helped communicate the takeaways to the rest of the team.

In addition, we held several internal group meetings, where we discussed how to divide the team into subgroups—one focusing on code improvement, and the other on documentation refinement. I contributed to the discussion by summarizing what we had so far in terms of structure and suggesting possible ways to organize the wiki more clearly. I then joined the documentation group.

Based on the outcomes of these meetings, I began reviewing the existing documentation and code files. I contributed to adjusting the structure of our GitHub wiki, focusing on improving readability, reducing redundancy, and creating an intuitive layout for future contributors. I also started drafting a more coherent project home page, with the goal of clearly presenting the project’s purpose, key components, and architecture.

These meetings laid a strong foundation for our Sprint 1 completion and set clear priorities for the next week.

Siyi Liu

During Week 5, I first listened to tutor Erica's explanation regarding the standards for writing user stories, which helped me better understand the expectations and structure.

Then, I attended the client meeting, where we confirmed the feasibility of our user stories and received a more detailed requirements document, helping clarify the direction of our future development.

Following this, I joined team discussions where we analyzed each part of the code to clarify their functions. I also participated in code optimization, aiming to simplify the structure and improve readability.

Later, I attended a tutor meeting, where we emphasized that the documentation should be well-organized and easy to navigate. Based on the feedback, I updated and supplemented the wiki section on GitHub with detailed user stories and the necessary project information.

After the meeting, our team divided into two groups — one focusing on further code refinement, and the other responsible for improving documentation. As a member of the documentation group, I contributed to refining the GitHub wiki, especially enhancing the introduction and overview of the project to make it more accessible and readable for future developers.

Dong-Jhang Wu

At this stage, the first step in redesigning the code should be to modify the basic block_data.class. Currently, the block sequence is processed separately, but since some blocks are allowed to have sub-sequences, combining the two becomes somewhat challenging. However, it should be possible to allow certain blocks to have an additional block sequence through inheritance. The code might get a bit messy, but it should be relatively easy to implement.

Our meeting focused on clarifying the format and requirements of the evaluation documents, as well as determining what additional documents are needed, and briefly dividing our team into frontend and backend groups.

Rifang Zhou

During Week 5, I focused on three main tasks. First, I thoroughly reviewed the existing codebase, mapping out how each module functions and interacts with others. I identified redundant code sections and structural issues, documenting these findings for future optimization. During team discussions about code restructuring, I proposed a three-layer architecture inspired by online design practices: a Model layer for data handling, an Interaction layer for business logic, and a UI layer for user-facing components. After debating the responsibilities of each layer, we finalized interface specifications and communication protocols between modules.

I also reorganized project documentation and the GitHub repository. This involved removing unnecessary backup files, standardizing document naming conventions, and creating dedicated folders for architecture-related materials. To improve workflow management, I adjusted branch management strategies to separate development and production code. Additionally, I broke down user stories into actionable tasks, collaborated with team members to define task completion criteria and priorities, and established a tracking system to link tasks back to original requirements.

Wenhui Shi

First, I wrote project personas and scenario, defined main user roles and features, and described how users will interact with system. Then I attended our client meeting and got client material about the block design, and read these files and analyzed client needs. Also for parts I didn't mask sense, I asked client and wrote down their answers and requirements.

I joined group discussion meeting and shared my understanding of client needs with team members. We discussed code assignment plan and decided each person's responsibilities. We also talked about technical details. After this meeting, we knew what coding tasks each person would do next.

Then I attended tutor meeting. We got feedback on user stories from tutor, and changed them based on tutor suggestions. We also adjusted project plan following tutor advice.

Finally, I completed detailed minutes for week5 client meeting and group meeting. I also organized week3 and week4 meeting minutes, changed format to match wiki requirements, and moved all content to project wiki.

Wenjing Qi

During Week 5, I participated in writing personas and scenarios by collaborating with the team to refine them based on client requirements. I then attended a small meeting to gain a deeper understanding of how to write effective user stories.

Following this, I attended the client meeting, where we successfully received the detailed requirements document, discussed key questions (e.g., "start virtual" vs. "start physical," simultaneous "virtual movement" and "physical movement"), and presented initial user stories and scenarios to the client.

After the meeting, I reviewed Wattle materials to understand the project assessment criteria and Sprint 1 submission requirements. I also participated in team discussions to review Sprint 1 progress, set goals, and plan next steps.

To prepare for front-end improvements, I updated VSCode and reviewed the codebase, planning to simplify the code and enhance the EduKATE landing page. Later, I attended the tutor meeting to clarify the scope of user stories and Sprint 1 deliverables.

Finally, I then improved and finalized user stories for Sprint 1, planned stories for Sprint 2, and documented them in the newly created team wiki. Additionally, I organized documentation by updating the wiki with user stories, personas, and senarios.