SophonNexus: Beta Sprint Essay 3

[SophonNexus]

Which course does this assignment belong to	Software Engineering
Where are the requirements for this assignment?	https://bbs.csdn.net/topics/617676810
Team Name	SophonNexus
Project Name	Crowdsourced Parking Management System
The objective of this assignment	Beta Sprint Essay 3

This Beta Sprint Essay is about the Frontend development

Catalog

• SCRUM section
• Ⅰ. Team Members and Task Progress
• 陈正一 Chen Zhengyi 832102117
• 吴高源 Wu Gaoyuan 832102113
• 李梓莙 Li Zijun 832102110
• Ⅱ. Check-in
• Ⅲ. Test
• Ⅳ. Meeting Photo
• PM report
• Ⅴ. Project Progress Summary
• Anticipated Tasks
• Current Completed Tasks:
• Remaining Tasks:
• Ⅵ. burn-up chart
• Ⅶ. Beta Testing Task Progress Overview
• Ⅷ. Demo Video

SCRUM section

Ⅰ. Team Members and Task Progress

陈正一 Chen Zhengyi 832102117

1. Implement the introduction and invocation of map interfaces, draw points based on latitude and longitude to display the task heatmap, and enhance the basic functional requirements of the thematic map.
   Duration: 4 days
   Challenges: Utilizing an external API poses significant difficulty, especially when the external component library for the map does not provide the expected API, requiring manual exploration of relevant native code.

2. Implement the display, commenting, and replying functionalities for the comments section in the task details.
   Duration: 2 days
   Challenges: Managing the relationships between comments, replies, and nested replies can be complex, and the logic is prone to errors.

3. Optimize the storage of user data such as tokens using Vuex.
   Duration: 5 hours
   Challenges: Integration with axios configuration is needed, which can be somewhat cumbersome.

4. Complete the relevant basic functionalities of the personal center homepage.
   Challenges: Multiple pages and complex navigation require careful restoration of layout changes.

吴高源 Wu Gaoyuan 832102113

1. Optimize the task details page to implement the retrieval of task areas and transfer textual data of user-marked task locations using latitude and longitude.
   Duration: 5 days
   Challenges: Similar to the first task, it requires utilizing an external API, and the logic for selecting grids can be quite complex.

2. Implement tab switching in the breadcrumb navigation for viewing tasks and functionality to display tasks in a specific order.
   Duration: 3 days
   Challenges: Reconstructing the layout can be challenging, as a 1:1 replication of the design may not be feasible, and the responsive layout might not be ideal.

3. Implement the task favoriting feature on the task details page.
   Duration: 5 hours
   Challenges: None.

4. Optimize the default navigation of user-configured routes after login.
   Duration: 2 hours
   Challenges: Requires calling multiple backend APIs, which may seem simple but can be time-consuming.

李梓莙 Li Zijun 832102110

1. Centralize the management of frontend API interfaces by assigning them to an independent API file.
   Duration: 4 days
   Challenges: Organizing according to the backend's API documentation, with a particular emphasis on writing thorough comments.

2. Optimize some asynchronous functions based on axios Promises, and rewrite blocking methods.
   Duration: 2 days
   Challenges: Understanding the concepts of blocking and the execution order of functions may be somewhat challenging.

3. Implement and refine the functionality for uploading images and files in multiple formats in the task publishing module.
   Duration: 4 days
   Challenges: Requires utilizing the browser's built-in file API and transmitting images as URL or file streams to the backend for storage.

Ⅱ. Check-in

Ⅲ. Test

Firstly, we listed all the front-end functionalities of the software, such as user login, map display, task publishing, and so on. Then, we considered possible usage scenarios to ensure that our software functions properly in various situations.

While coding, we made sure that each functionality is independent to facilitate testing. We also used some automated testing tools, like APIFOX, to simulate user operations and check if the software operates as per our design.

We created a bunch of test cases to assess the software's performance in different scenarios, including potential problem areas. For instance, in cases of invalid user input, we also ensured that the software handles it properly.

We paid special attention to how the software performs on different devices and browsers, ensuring that users can easily access it whether on a computer or a mobile phone.

Regarding security, we conducted tests to ensure that user inputs don't lead to any issues. In conclusion, through these tests, we aimed to make the software more stable and user-friendly.

Ⅳ. Meeting Photo

PM report

Ⅴ. Project Progress Summary

Anticipated Tasks

Complete the basic platform setup, including login and registration, multiple map markers, viewing tasks, task publishing, user personal management, comments, and notifications across multiple fundamental modules.

Current Completed Tasks:

1. Two thematic maps and one nearby hotspot map.
2. Login, registration, and welcome interface.
3. Viewing tasks, task publishing, and the retrieval of tasks related to parking, noise, etc.
4. Commenting and favoriting functionalities.

Remaining Tasks:

1. Personal user center and notifications (not fully completed).
2. Some interfaces that are yet to be implemented (such as more information and recommended tasks).
3. Display of subsequent tasks, including air quality and others.

Ⅵ. burn-up chart

Ⅶ. Beta Testing Task Progress Overview

Day 1 to Day 3: 50%
Progress was relatively slow during this period as the team familiarized themselves with the use of external APIs, which posed a significant challenge as the members had not encountered them before.

Day 4 to Day 6: 72%
Team members optimized API interfaces, leading to a substantial increase in the overall development progress. Surprisingly, this also unexpectedly improved efficiency in collaboration and development.

Day 6 to Day 8: 95%
As the project approached its conclusion, the team's enthusiasm remained high. However, some functionalities were still not implemented, leading to a somewhat regrettable outcome.

Ⅷ. Demo Video