FZU Meteorological Bureau —— Alpha Sprint Plan
Catelog
1. Code Standards
2. Sprint Tasks
3. Group Division
4. Plans
Day1 (12.12)
Day2 (12.13)
Day3-Day4 (12.14-12.15)
Day5-Day6 (12.16-12.17)
Day7-Day8 (12.18-12.19)
Day9-Day10 (12.20-12.21)
1. Code Standards
1.1 front-end
1. Vue Style guide
2. HTML/CSS Style guide
3. JavaScript Style guide
1.2 backend
1. Refer to Alibaba Java Development Manual Ultimate Edition v1.3.0
2. Springboot Style guide Refer to the CSDN site (please support the original)
2. Sprint task
2.1 Front-end development
- Permission Management Core Page Implementation
- Login page design and development: Implement username/password input forms, login verification interactions, and error prompt feedback
- Main Workbench Layout: Complete the responsive layout of the left navigation menu, top action bar, and core ribbon
- User management page implementation: develop user list display (including search/pagination), add/edit user form, role assignment pop-up window (support multi-role selection)
- Permission Management page implementation: display the list of system initialization permission points (only view, not front-end addition or deletion)
- Interaction and Visualization Optimization
- Unified form validation rules and error prompt styles to ensure visual consistency in the interface
- Added operation confirmation pop-up window (e.g., secondary confirmation when deleting a user/role)
2.2 Backend development
- Database Design and Implementation
- Design a data structure that stores the core data of the project
- Realize data addition, deletion, modification and checking to ensure timely and accurate data
- Interface and Integration Development
- Unified API interface format (request JSON parameters, response JSON structure: code/msg/data)
- Realize joint debugging of front-end and back-end interfaces to ensure consistent data transmission
- Integrated permission verification middleware to block unauthorized access and unauthorized operations
2.3 Testing and Optimization
- Front-end testing
- Responsive Testing: Ensure multi-device, multi-screen adaptation
- Functional Testing: Verifying the Availability of User/Roles/Permissions Management Functions (Added → Assignment → Verification)
- Backend Testing
- Database testing: Verify the accuracy of data additions, deletions, modifications, and checks, the consistency of associated table data, and the validity of field constraints
- API Interface Testing: Test API parameter verification, return format correctness, and exception scenario handling (e.g., invalid IDs, duplicate submissions)
- Permission Verification Test: Simulate the interface called by users with different roles to verify the interception effect of unauthorized operations (such as reading only user calls to delete interfaces).
- Integration Testing
- Conduct full-process testing after front-end and back-end joint debugging
- Simulate the full user usage process for verification
2.4 Documentation and Deployment
- Deployment and go-live
- Complete the packaging and deployment of the front-end and back-end projects
- Configure environment parameters such as database connections and interface access paths
- Internal small-scale testing: Organize team members to simulate real-world scenarios, gather feedback, and fix critical bugs
- Documentation
- Write code documentation (architecture description, front-end and back-end implementation ideas, interface description)
- Document project progress
- Test documentation: Write test scenarios, test tool lists, core functional test cases, problem fix records, and experience summary
3. Group Division
| 学号 | 姓名 | 职责 |
|---|
| 832301213 | Chen Ye | Responsible for the overall planning, schedule management and team coordination of the project; Lead the writing, integration and finalization of all project documents |
| 832301102 | Wang Jiarui | Responsible for front-end routing design and control logic implementation |
| 832301208 | Zhang Shimin | Responsible for page component development and style implementation; Customize system themes and layouts; Complete user interaction features |
| 832301113 | Sun Chenen | Build a Spring Boot multi-module project architecture |
| 832301214 | Chen Xueting | Implement the user login authentication module to complete the permission menu management function |
| 832301205 | Zhang Zhikai | Complete the development of core CRUD functions in the business; Write unit test cases; Ensure code quality |
| 832301109 | Liu Zhongbo | Integrated Redis caching capabilities; Realize file upload and download services; Optimize thread pool configuration |
| 832301210 | Chen Hongyu | Execution functional test cases; track and validate bug fixes; Write test reports |
| 832301228 | Lin Juntian | Conduct system performance testing; organize user acceptance tests; Collect user feedback |
| 832301115 | Li Yuxin | Design database table structure; Maintain a data dictionary |
| 832301225 | Lin Qixuan | Optimize database index configuration; Build a master-slave replication architecture; Develop a data backup strategy |
4. Plans
Day1(2025-12-12)
- Project manager: clarify goals and schedules, hold kick-off meetings, and assign tasks; Complete the first draft of the blog
- UI Design Group: Confirm the details of the prototype and start the core interface design
- Front-end group: Build the development environment and initialize the core page framework
- Backend group: Design the database structure and set up the environment
- Test Team: Develop a testing process and prepare test case documentation
Day2(2025-12-13)
- Project Manager: Follow up on the progress of each module and coordinate resources
- UI Design Group: Outputs high-fidelity UI drafts
- Front-end group: complete the basic layout of the homepage and split the components
- Backend group: Completes the basic interface of the user authentication module
- Test group: Refine test scenarios and boundary conditions
- Architect the basic layout and basic components of the homepage
Day3–Day4(2025-12-14 至 2025-12-15)
- Frontend Group: Develop LLM chat interface and air quality display components
- Backend group: Access to third-party air quality APIs to develop personalized recommendation interfaces
- Front-end code iterations on the air quality display component interface
Day5–Day6(2025-12-16 至 2025-12-17)
- Front-end and back-end joint debugging: Complete the docking of core pages and interfaces
- All members: Iterate on some uncertain and unaesthetically pleasing interfaces and buttons
Day7–Day8(2025-12-18 至 2025-12-19)
- Deploy a test environment
- Optimized the smoothness of front-end interface design and jumps
- Improve the code comment text according to the relevant code specifications (code comments, interface descriptions, etc.)
- Select and apply the appropriate testing tools during the sprint phase, and gradually start automated testing
Day9–Day10(2025-12-20 至 2025-12-21)
- Internal alpha version acceptance
- Continue to conduct software testing
- Prepare presentation materials and presentation PPT
- Submit the final Alpha Sprint outcome package
Note: This plan is based on a 10-day sprint period (2025-12-12 – 2025-12-21) with the goal of delivering a fully functional alpha version of the product with a preliminary overall architecture.