05 Group - Sprint Log 3nd (12.10)

1. Brief Introduction

The Link Your Class	Here
The Link of Requirements of This Assignment	Lab3-2 Requirement
Team Name	RIDS-IoT-Group
Team Project Topic	IoT Garbage Manager
Sprint Collection Link	[Sprint Collection Link]
Sprint Summary Link	[Sprint Summary Link]
Video demo link	Preview Demo and Pervious Oral
GitHub link	Github Repo

目录

---

2. Progress of Sprint

Name	Completed Task	Duration of the Task	Problem Encountered	Solution	Proportion
Hanlin Cai (Leader)	Sprint plan task assignment	5h	Other specialized courses have more exams and homework.	Group time is arranged according to the open test and homework time.	120%
Zheng Li	A summary of the proposal report	3h	The tasks completed before are more scattered	Communicate with students who have completed different functions	110%
Jiaqi Hu	Back end authoring	10h	How to cooperate with the front end to effectively display the data.	Swagger API document is applied to solve communication test problem between front and back ends.	105%
Zhijun Zhao	Front end writing	6h	How to connect the front-end and back-end api interfaces.	Strengthen communication and re-write api encapsulation files in the front end.	105%
Yinheng Lin	Update of prototype	3h	The layout of some pages is not quite right.	Spruce up the finished front page.	100%
Shipei Zhang	Back end testing	2h	The processing of the data is not perfect.	Learn the method of data processing on the Internet.	60%
Youlin Feng	PPT editing	3h	Animation effects are difficult to achieve.	Find tutorials to learn about After Effects(AE).	100%
Shuying Liu	Blog writing and documentation	5h	The sprint documentation requirements are not very clear.	Private chat with members to analyze the specific requirements and related requirements of the sprint document	110%
Jingjie Yu	Document organizing	3h	The usage of some functions is unclear.	Communicate with classmates in the group and complete the writing of functions.	100%

---

3. Minutes of Meeting

3.1 Contents of the Meeting

1. Review the previous proposal and evaluate team members.

2. Divide the tasks for the next sprint.

3. Discussed features that need to be updated.

4. In-depth communication between front end and back end

3.2 Pictures of the Meeting

---

4. Development Process

4.1 Check-in Records of Github

4.2 Screenshots of the Operation

The background picture of the front end is not completely set. Currently, the picture of the prototype is used for display.

4.3 Corresponding UML designs

This week's focus is on implementing the front end, located in the red box section of the general mind map, and based on the UML diagram below.

---

5. Introduction of Progress

5.1 Progress of Development

The back-end has been basically written, the front-end has completed the basic interface connection, the next plan is to complete the front-end administrator mode, and page beautification.

5.2 Burnout Diagram

This blog is written by Hanlin Cai.