Alpha Sprint Summary Article

Which course does this assignment belong to	https://bbs.csdn.net/forums/ssynkqtd-04
Where are the requirements for this assignment	https://bbs.csdn.net/topics/617606376
The goal of this assignment	Documenting the exact process of software creation
Team name	Wizards of Codes
Team Project	Campus course management and check-in system

I. Project expected plan and actual schedule

1.Project Initiation and Definition Phase:

1. Expected Plan: Hold a project kickoff meeting to define project goals and scope, conduct initial requirements analysis.

2. Actual Progress: The project initiation phase proceeded smoothly, but there was a discrepancy in understanding the use of WeChat mini programs during initial requirements analysis. Through in-depth discussions and example cases, we clarified the use of WeChat mini programs.

2.System Design and Planning:

1. Expected Plan: Conduct system design, including frontend interface design, backend system architecture design, and formulate a detailed development plan.

2. Actual Progress: In the system design phase, the frontend team encountered disputes about data transfer formats. Through technical assessments and practical demonstrations, we ultim
   ately established the standard format for data interaction.

3.Frontend Development Phase:

1. Expected Plan: Frontend team to conduct phased development, including the main dashboard, device management interface, etc., ensuring the interface is visually appealing and user-friendly.

2. Actual Progress: During frontend development, compatibility issues arose with different browsers, especially in handling chart library displays. By introducing compatibility libraries and adjusting code, we successfully resolved these issues.

4.Backend Development Phase:

1. Expected Plan: Backend team to commence development of core system functionalities, including data processing, security, and integration with the frontend.

2. Actual Progress: In the backend development phase, the team faced a choice regarding encryption and decryption algorithms. Through detailed risk assessments and performance testing, we selected the algorithm best suited to project requirements.

5.Prototype Design and Testing:

1. Expected Plan: Create a system prototype covering main interfaces and functionalities, and conduct internal testing and corrections.

2. Actual Progress: During prototype testing, users raised a requirement for real-time data refresh. By adjusting frontend data request logic, we met the user’s real-time update needs.

6.Overall System Integration Testing:

1. Expected Plan: Conduct overall integration testing of frontend and backend, identifying and resolving potential system interaction and functionality issues.

2. Actual Progress: In the integration testing phase, there was an inconsistency in data transfer speed between frontend and backend. By optimizing database queries and frontend data processing logic, we achieved more efficient data transmission.

7.User Feedback and Adjustments:

1. Expected Plan: Invite internal and external users to participate in system testing, collect feedback, and make corresponding adjustments.

2. Actual Progress: User feedback included suggestions for optimizing the main interface. Through redesigning main interface interaction logic, we improved the user’s experience with main interface interactions.

8.Final Delivery and Documentation Compilation:

1. Expected Plan: Complete the development of the final system version and simultaneously write user manuals and technical documentation.

2. Actual Progress: Before the final delivery, issues regarding document formatting were discovered. By collaborating and standardizing the document editing process, we ensured document consistency and professionalism.

Below is the interface of our product.
Login interface:

The running interface:

![https://img-blog.csdnimg.cn/direct/40bcad1d4e2741cdb544bd7f8f20c1d3.png)

II. Team members work and gain

Team member	Work	Gain
Liu Qinyang	The design of the product interface	Mastery in utilizing D3.js and similar libraries for creating dynamic and visually appealing data representations.
Liang Weiquan	User Experience	Expertise in user-centric design principles and proficiency in tools like Adobe XD and Sketch
Zhong Ruicheng	Fulfill course interface to update (refresh) courses in real time	Master the real-time system theory knowledge
Yang Zhilin	Interface and device adaptation	Learn aboout interface adaptation knowledge
Gan Tinghan	Interface interactivity test	know how to Interface interactivity test
Chen Sisheng	Front-end test	Efficient tools significantly enhance development efficiency
Zhao Haonan	Front-end Integration	Passed the real machine test bug
Ye Quanhui	Back-end Architect	Expertise in microservices architecture and proficiency in selecting and implementing appropriate technologies
Chen Guanting	Responsive Design	In-depth knowledge of responsive design principles and proficiency in Bootstrap framework
Zhang Hong	Security Specialist	In-depth knowledge of security programming, familiarity with common security vulnerabilities, and implementation of preventive measures
Huang Yicheng	Data Processing	Mastery in data processing techniques and expertise in database design and optimization

III. A vision for the next phase

Our vision is to create an integrated platform that can effectively manage all aspects of an educational institution, from student enrollment, academic management, resource allocation, facility management, to campus security, interactive communication, and administrative operations.

1. Comprehensiveness and integration: The system should be able to cover all key areas of campus operations, as well as all the needs of teachers, students, administrators, and alumni.
2. Ease of use and accessibility: The interface should be intuitive and easy to use, whether through a computer or a mobile device, to ensure that all users can easily access the information and services they need.
3. Data-driven decision-making: Systems should be able to collect critical data and provide insight through advanced analysis to support management decisions.
4. Security and Privacy Protection: Given that school data usually contains sensitive information, the system must meet the highest security and privacy standards.
5. Flexible customization and expansion: Systems should be tailored to the specific needs of different schools and upgraded and expanded as technology evolves and school needs change.
6. Real-time communication and cooperation tools: The system should have internal real-time communication and collaboration tools to promote internal campus communication and cooperation with external organizations.
7. Continuous technical support and training: Suppliers should provide continuous technical support and provide the necessary training for the school staff to ensure the stable operation of the system.
8. Cost-effectiveness: Although the system needs to be advanced and comprehensive, it should also take into account the budget constraints of educational institutions to provide cost-effective solutions.
9. Intelligent automation: Automate routine management tasks, such as class scheduling, exam monitoring, and financial operations, to reduce the administrative burden and allow teachers and staff to focus on teaching and high-value work.
10. Promoting student development: The system should not only manage student information, but also support students’ personal growth and academic progress by tracking learning processes, grades, and other success indicators.

Implementing such a system may require overcoming technical challenges, financial constraints, and changing management and cultural inertia. But with the development of technology, a campus management system that can meet the above vision will greatly improve the efficiency and service quality of educational institutions, so that they can better serve teachers and students.