Sprint Summary Report

大智若渔_Smart_Fishpond 团队 2024-12-06 17:09:43

Which course does this assignment belong to	2401_Mu_SE_FZU
Where is the requirement for this assignment	Fifth Assignment——Alpha Sprint
Team name	Smart Fishpond Access
The goal of this assignment	1. To Summarize the Sprint Process 2. To Comment the Insight of the Sprint 3. To Claim the Potential Issues and Future Plan of Beta Sprint
Other references	Alibaba Java Development Manual Ultimate Edition v1.3.0 Huawei Internal Code Standards Huawei Cloud JavaScript coding specification

Content

1. Sprint Process

1.1 Expected Progress

2. Team Member Insights and Division of Labor Overview

2.1 Personal Insights

2.2 Team Responsibilities

3. Future Plans and Outlook

3.1 Current Issues

3.2 Next Sprint Plan (β Sprint)

1. Sprint Process

All work is finished in Alpha Sprint. To summarize the procedure of Alpha Sprint, the development Process is reviewed below.

1.1 Expected Progress

Day 1: November 27th

Development Tasks

Front-end Team
- Initialize Vue3 project and set up the basic page framework.
- Create the login page (Login.vue) and device management page (Devices.vue).
Back-end Team
- Initialize Spring Boot project, complete the database table (Users) for the user module.
- Configure MySQL database connection and complete the registration and login API.

Testing Tasks

Write test cases for user registration and login.

Blog Tasks

Write the blog "Code Standards and Sprint Plan", describing the development tasks, timeline, and objectives.
Create the "Special Blog Collection" page to record subsequent blog links.

Corresponding Teams

Development Team, Testing Team, Blog Team.

Day 2: November 28th

Development Tasks

Front-end Team
- Complete the registration page (Register.vue) and implement input validation.
Back-end Team
- Implement back-end logic for user registration and login, returning JWT.

Testing Tasks

Use Postman to test the registration and login API and verify front-end and back-end interaction.

Blog Tasks

Publish the first sprint blog: Show burndown chart, project initialization progress, and screenshots.

Corresponding Teams

Development Team, Testing Team, Blog Team.

Day 3: November 29th

Development Tasks

Front-end Team
- Develop basic functionality for the device management page, including add and delete buttons for devices.
- Create a multi-device list display page.
Back-end Team
- Implement APIs for adding, deleting, and querying devices.

Testing Tasks

Test the device management module's API functionality.

Blog Tasks

Update "Special Blog Collection."

Corresponding Teams

Development Team, Testing Team.

Day 4: November 30th

Development Tasks

Front-end Team
- Integrate Axios to call the device management API, ensuring device add and delete functions work correctly.
Back-end Team
- Simulate the real-time monitoring data API (GET /monitoring/{deviceId}).

Testing Tasks

Write test cases for the real-time monitoring module to validate data format and stability.

Blog Tasks

Publish the second sprint blog: Show progress of the device management module, with burndown chart and screenshots.

Corresponding Teams

Development Team, Testing Team, Blog Team.

Day 5: December 1st

Development Tasks

Front-end Team
- Develop the real-time monitoring page (Monitoring.vue) and integrate Echarts to display real-time data curves.
Back-end Team
- Integrate water temperature prediction algorithm and provide prediction API (GET /monitoring/predict/{deviceId}).

Testing Tasks

Test the response time and accuracy of the prediction algorithm API.

Blog Tasks

Update "Special Blog Collection".

Corresponding Teams

Development Team, Testing Team.

Day 6: December 2nd

Development Tasks

Front-end Team
- Implement integration of real-time monitoring page and prediction data display.
Back-end Team
- Develop alarm record API.

Testing Tasks

Test the alarm record module to ensure data storage and query functionality.

Blog Tasks

Publish the third sprint blog: Show progress on real-time monitoring and prediction functionality.

Corresponding Teams

Development Team, Testing Team, Blog Team.

Day 7: December 3rd

Development Tasks

Front-end Team
- Develop the intelligent Q&A page (QA.vue), integrating voice input functionality.
Back-end Team
- Complete the intelligent Q&A API, integrating the BERT model and knowledge graph.

Testing Tasks

Test the semantic recognition effect of the intelligent Q&A feature.

Blog Tasks

Update "Special Blog Collection".

Corresponding Teams

Development Team, Testing Team.

Day 8: December 4th

Development Tasks

Front-end Team
- Develop the multi-device location page (Location.vue) and integrate AMap API.
Back-end Team
- Develop the device location API to provide latitude and longitude data.

Testing Tasks

Test the functionality and map loading performance of the device location module.

Blog Tasks

Publish the fourth sprint blog: Show progress on intelligent Q&A and device location modules.

Corresponding Teams

Development Team, Testing Team, Blog Team.

Day 9: December 5th

Development Tasks

Front-end Team
- Integrate all feature pages and optimize the interface layout.
Back-end Team
- Perform database optimization to improve query efficiency.

Testing Tasks

Complete system-wide testing and fix all identified issues.

Blog Tasks

Write a testing blog, describing testing tools, test case design, and results.

Corresponding Teams

Development Team, Testing Team, Blog Team.

Day 10: December 6th

Development Tasks

Front-end Team
- Package the front-end project and prepare for deployment.
Back-end Team
- Deploy the back-end service to Ali and perform final integration testing.

Testing Tasks

Conduct the final regression testing to ensure the system runs stably.

Blog Tasks

Publish the fifth sprint blog: Summarize the sprint results, including complete screenshots and videos of the system running.

PPT Tasks

Prepare the defense PPT
- Showcase the burndown chart, project functionalities, testing results, and improvement plans.

Corresponding Teams

Development Team, Testing Team, Blog Team, PPT Team.

1.2 Actual Progress

All work is conducted as expected. Furthermore, some of key parts are completed ahead of time. The actual progress is visualized by Gantt Chart and Burnup Chart, shown below.

Gantt chart

Burnup Chart

In this sprint plan, we have successfully completed all the tasks, with some parts finished ahead of schedule, ensuring that each group delivered their tasks on time. Through strict time management and efficient teamwork, the project has progressed smoothly as expected.

2. Team Member Insights and Division of Labor Overview

2.1 Personal Insights

Below is the personal insights of each team member. Taking one member of each Group as an example.

Development Group

As a member of the development team, I was responsible for developing the front-end pages and implementing back-end interfaces. Through this sprint, I deeply understood the challenges posed by changes in requirements, especially with the close collaboration between the testing team and blog team, allowing us to adjust the project direction in a timely manner while maintaining efficient progress. After completing each feature, I performed multiple tests to ensure its stability and compatibility. In future projects, I will place more emphasis on code quality and improving the user experience.

Testing Group

Working in the testing team made me realize the importance of product quality. From writing test cases to executing tests, I learned how to verify the integrity and stability of the product from multiple dimensions. Especially with the implementation of automated testing, I could efficiently and comprehensively test the system’s functionality. These tests not only familiarized me with different testing tools but also improved my ability to detect and quickly locate problems. In the future, I will pay more attention to the details and ensure that each feature runs smoothly in different scenarios.

Blog Group

While writing the blog on "Code Standards and Sprint Task Plans," I delved deeply into the team’s coding conventions, which helped clarify the development process and progress schedule. Each sprint blog update is not only a record of the project's progress but also a testament to our team's hard work. Particularly under time pressure, publishing high-quality blogs on time made me realize the importance of time management. In the future, I hope to further improve the professionalism and readability of the content, allowing more readers to understand our team's achievements and thoughts.

PPT Group

My primary task was to present the project results visually. While creating the defense PPT, I realized the importance of condensing information and combining text and visuals effectively. During presentations, how clearly and concisely key information is conveyed often determines how the audience perceives the project. I learned how to use precise language and visual elements, such as charts and GIFs, to make the PPT more dynamic and help everyone better understand the project’s progress. I hope this sprint will enhance my visual design and project presentation skills.

2.2 Team Responsibilities

The distribution of labor is shown below.

FZU ID	Distribution of Labor	Description
832201109	Front-end and back-end	Project initialization, page framework set up
832201117	Front-end and back-end	Development of login and registration pages, and implementation of validation features
832201110	Front-end and back-end	Development of device management and real-time monitoring
832201111	Front-end and back-end	Development of smart Q&A and device location
832201112	Front-end and back-end	Deployment and interface optimization
832201127	Front-end and back-end	Frontend and backend API integration and debugging
832201318	Testing Team	Frontend and backend API integration and debugging
832201306	Testing Team	Executing frontend and backend interaction, and functional module tests
832201307	Testing Team	Device location and database optimization
832201313	Testing Team	Executing frontend and backend interaction, and functional module tests
832201325	Testing Team	Device location and database optimization
832201116	Blog Team	Writing and publishing the sprint blog
832201114	Blog Team	Writing and publishing the sprint blog
832201120	PPT Team	Make the defense PPT, summarizing project progress and outcomes
832201105	PPT Team	Make the defense PPT, summarizing project progress and outcomes
832201104	PPT Team	Make the defense PPT, summarizing project progress and outcomes

Four teams are shown below.

Development Team (6 members)

Responsible for front-end and back-end functionality development and API implementation.
Testing Team (5 members)

Responsible for designing and executing test cases to ensure functionality completeness.
Blog Team (2 members)

Responsible for writing, publishing, and updating blogs to regularly showcase project progress.
PPT Team (3 members)

Responsible for preparing the final presentation PPT on the last day to showcase the project results.

3. Future Plans and Outlook

3.1 Current Issues

Large Size of BERT Model: The size of BERT model is too large, causing long response times when integrated with cloud servers, which impacts system real-time performance and user experience.
Optimization Potential in Web Stress Testing: The results from web stress testing remain room for improvement. Optimizing code and resource usage is necessary to reduce the server load and speed up response times.
Front-End Application Compatibility: Currently, the front-end application is mainly optimized for the iPhone 8 screen size, and compatibility with other devices is not fully optimized. Further adjustments are needed.

3.2 **Next Sprint Plan (β Sprint)**

BERT Model Lightweight Optimization: We plan to use pruning method to achieve lightweight of algorithm, reducing the size of the BERT model, cutting unnecessary parameters while maintaining accuracy. This will balance computational power consumption and performance, enhancing response speed.
Distributed Server Architecture: To alleviate server load, we will implement a distributed server architecture, deploying API interfaces across multiple servers. This will help distribute the workload and improve overall system performance and stability.
Multi-Device Front-End Compatibility: Aiming to ensure smooth display across a wider range of devices, we will add support for devices like the Xiaomi 12, 13, 14, and other varying screen sizes in addition to further optimizing the iPhone 8 compatibility, continuously updating to meet users' diverse needs.