Summarizing issues in the alpha stage

In the problem summary of the Alpha phase, we deeply recognize the critical role of user experience and functional improvement in ensuring the success of the FitTrack platform. Below are the detailed issues identified regarding the frontend and functional implementation:

1. The preceding segment responds to the problem

(1) Lack of Intuitiveness

The user interface design currently struggles to intuitively reflect users' fitness tracking needs, making it difficult for users to navigate and locate key features such as workout logs, health metrics, and progress tracking.

(2) Insufficient Usability

Some UI components lack user-friendly features, which may result in inconvenience or confusion during interactions, such as accessing fitness plans or logging workouts.

2. Functional Issues

(1) Communication Features

The platform currently lacks a messaging or communication feature for users to interact with fitness trainers, teammates, or community members, limiting collaboration and support within the platform.

(2) Goal-Setting and Progress Feedback

• Inadequate Feedback Mechanism: Users may face difficulty in receiving real-time feedback on their fitness goals or progress, reducing motivation and engagement.
• Limited Customization: The fitness plan customization options are limited, restricting users from tailoring plans to suit their specific health or fitness needs.

3. After-Workout Feedback and Support

Lack of Issue Resolution

The absence of a clear and structured issue resolution mechanism (e.g., support for incorrect fitness data logging) may hinder user trust in the platform.

The following are specific questions and answers:

Are the problems the software needs to solve clearly defined? Are typical users and typical scenarios clearly described?

Answer: Our software is designed to provide a convenient fitness platform for students on campus. Through this platform, students can easily detect their own movements and make corresponding plans. The above description has defined the goal of the software, typical users and typical usage scenarios, and a more detailed description can be found in the PPT.

Are we meeting our goals (how many features were originally planned? Is the delivery schedule on schedule? Has the planned number of users been reached?)

Answer: Our goal is basically achieved. In the original planned functions, the login, motion planning, planning and other modules have been implemented, and the search function has been upgraded accordingly.

Has the quality of the team's software engineering improved compared to the previous phase? Where is the improvement, by how much, and how can it be measured?

Answer: The quality of the team's software engineering improved, mainly in terms of work efficiency, defect rate reduction and functional reliability, and also improved in the final commissioning phase; In the Alpha stage, team members cultivated team spirit, cooperated and communicated with each other, and the work efficiency was doubled. The number of defects found during back-end development is reduced and the reliability of the system is improved.

What is the number of users and the acceptance of important features we expect? Are we any closer? What have we learned? What would we do if history repeated itself?

Answer: During the Beta phase, we will conduct user usage surveys to check the number of users and their acceptance of important features, which is in line with our expectations. Through the experience of the Alpha phase, we came to the conclusion that when it comes to UI design, we need to coordinate with the backend to avoid overly complex designs, while at the same time designing features that do not exceed our capabilities, so that we do not need to modify the UI design later. To ensure that the development process can be more efficient and accurate to meet the needs of users

Is there enough time to plan?

Answer: Our team has plenty of time in the planning phase.

How does the team resolve differences between colleagues during the planning phase?

Answer: Team members fully exchange opinions in the project QQ group, share ideas and try to understand others' perspectives. Through full communication and discussion, and finally through voting to determine the plan.

Have you completed all the planned work? Part of the reason for not finishing?

Answer: Pretty much all done. The Search, motion, and planning modules are complete

Are there clearly defined and measurable deliverables for each task?

Answer: Yes, each task has clearly defined and measurable deliverables that are discussed and reflected in the group.

Is the overall project proceeding according to plan? What surprises have occurred in the project? What risks were not estimated at the time, and why?

Answer: The project as a whole went according to plan, but something unexpected happened. After the UI design is completed, the interactive steps are directly carried out on the real-time design platform, but it is found that the interactive code cannot be exported after the completion. In addition, the UI design does not take into account the technical limitations of the backend, resulting in the need to modify the completed UI design later. The risk of not being able to export interactive code was not assessed, mainly because team members were unfamiliar with the platform and lacked relevant experience and knowledge.