Natus Vincere - Code Standards, Sprint Tasksand and Plans

["Natus Vincere"]

Alpha Sprint

Item	Details
Which course does this assignment belong to	2401-MUSE社区-CSDN社区云
Where are the requirements for this assignment	Teamwork——Alpha Sprint-CSDN社区
The goal of this assignment	Team's code standards & current sprint tasks and plans
Team Name	Natus Vincere

目录

• Alpha Sprint
• Code Standards
• Sprint Tasks
• Plans
• Daily Schedule
• Personnel Arrangement
• Testing

Code Standards

Back-end Code Standard

Front-end Code Standards

Sprint Tasks

• Refine the punch card code logic to ensure accurate and efficient time tracking for employees.
• Continue the development of the activity likes and favorites features, enhancing user engagement and interaction within the platform.
• Strengthen the overall stability of the software by addressing potential bugs and performance issues, ensuring a smooth user experience.
• Optimize data handling and storage solutions to improve the application's responsiveness and reliability.
• Add a calendar function on the user side to facilitate users to view the date.

Plans

• Daily Schedule

Day 1:

1. Review and finalize requirements for the punch card code logic.
2. Plan the architecture for the calendar function integration.

Day 2:

1. Begin refining the punch card code logic.
2. Design front and UI frames for the activity likes and favorites features.
3. Start planning the user interface for the calendar function.

Day 3:

1. Complete the initial refinement of the punch card code logic.
2. Develop backend APIs for the activity likes and favorites features.
3. Finalize the design for the calendar function.

Day 4:

1. Implement frontend changes for the punch card functionality.
2. Begin frontend development for the activity likes and favorites features.
3. Start backend development for the calendar function.

Day 5:

1. Conduct initial testing of the punch card code logic.
2. Finalize frontend development for the activity likes and favorites features.
3. Integrate the calendar function with the backend.

Day 6:

1. Address any bugs or performance issues found during testing of the punch card feature.
2. Start user acceptance testing (UAT) for the activity likes and favorites features.
3. Complete the integration of the calendar function.

Day 7:

1. Continue enhancing software stability and fixing bugs in the punch card feature.
2. Optimize data handling and storage solutions for the calendar function.
3. New refresh function in Tasks to Do section

Day 8:

1. Perform comprehensive testing of the punch card feature.
2. Conduct performance testing for the calendar function.
3. Task management function: Added the administrator to send tasks to multiple selected members at a time

Day 9:

1. Finalize any last-minute adjustments based on testing feedback for the punch card feature.
2. The announcement function has been improved, and the announcement management categories have been added
3. Prepare documentation for the new features.

Day 10:

1. Prepare the punch card feature for deployment.
2. Standardize all functions to ensure consistent style on every page
3. Ensure all features are ready for the next phase, including the calendar function, and the system is stable.

• Personnel Arrangement

Specific Tasks	Personnel
Project Management	Liu Ruiyu, Wang Xiaoye
UI Design	Wu Lingyuan, Cao Mingrui
Front-end Development	Liu Ruiyu, Wang Xiaoye, Cai Shaoen
Back-end Development	Lai Zhenpeng, Zhang Zhuorui, Li Yilin, Song Jiazheng, Shi Yisong, Guo Yongzhen

Testing

• ContextLoads Test: Ensures the application context loads correctly.
• Functional Testing: Simulates user behavior to validate feature functionality.
• Unit Testing: Focuses on individual components for accuracy and reliability.