Software_clan | Assignment 5 -- Coding Standards, Tasks, and Publication Plan
CS Demo Master Alpha Sprint: Coding Standards, Tasks, and Publication Plan
| Assignment information | Details |
|---|---|
| Course | EE308FZ Software Engineering · 2601_FZU-MU_SE |
| Team | software_clan |
| Assignment requirements | Alpha Sprint assignment on CSDN |
| Objective | Explain the engineering work behind our Alpha release, the coding standards for each module, and the schedule for our four sprint logs. |
| Other references | Live platform · Development repository · Requirements specification and prototype presentation |
In our prototype presentation, a player could click through a sample match report. For the Alpha release, we wanted that player to open a replay from their own match, find a round worth reviewing, and see which events supported the coach’s advice. We also built two features players could use between matches: five browser-based aim games and a campus squad lobby.
We completed the Alpha implementation ahead of the course sprint window. From November 21 to 28, 2026, we will publish one development log every two days. The dates attached to commits below show when the engineering work took place. The dates in our publication schedule show when each account of that work will appear.
Alpha scope
| Workstream | What we built |
|---|---|
| Aim training | Five games cover grid shooting, reaction time, wide flicks, fine adjustments, and smooth tracking. A player can choose a skill, complete a session, and see the result in the browser. Frontend project |
| Player accounts and campus squads | Registration and login give each player a persistent identity. Players can edit a profile card, find friends, respond to friend requests, and recruit teammates. In the lobby, one player can publish a squad and another can claim its team code. Backend routes and services |
| Demo upload and match reports | The platform accepts supported ZIP exports and raw CS2 replay files (.dem). It extracts match, round, and player data and returns structured results for the frontend to display. Players can reopen a report from their match history. Parser · Replay and API design |
| AI coaching | The coaching service supplies the AI API with selected match evidence and presents the returned assessment in the report. For Dust2, our map knowledge and tactical rules provide context about locations, defensive positions, and utility use. AI analysis design · Dust2 knowledge base |
How the release took shape
- October 15–23. We moved the backend to Node.js and connected login, profile cards, the squad lobby, and friend relationships. These changes established the identity that follows a player from a friend request into a squad. Backend change · Profile cards · Player search and friends
- October 24–27. Our first replay backend read ZIP exports. We then added support for the v1.2 export format and paginated the evidence returned to the client. Deploying the frontend also exposed a problem with opening the replay page over HTTP, which we fixed. ZIP analysis · Export compatibility · Deployed replay page fix
- October 28–31. Parsing raw demo files gave the coach access to events from the uploaded match. We connected the frontend to the analysis backend, improved replay history, and capped the size of evidence arrays before validation. Raw demo parsing · Replay history · Evidence validation
- October 31–November 4. We calibrated the Dust2 rules with real demos and brought tactical findings and weapon highlights into the report. A later frontend update corrected grenade throw counts and fixed an update-caching issue. The throw-count change is a good example of why we need to trace a displayed statistic back to the event that produced it. Dust2 calibration · Report integration · Frontend v1.3.1 fixes
Team coding standards
| Area | Our conventions |
|---|---|
| Vue and TypeScript frontend | Use two-space indentation and the frontend formatter. Keep API calls separate from presentation components. When a report field changes, check the upload result, the history view, and the empty state. |
| Node.js and Express backend | Keep routes focused on HTTP requests and put business rules in services. Use a consistent response structure with code, message, and data. When a field changes meaning, review the API documentation, its frontend consumer, and the relevant tests together. |
| Python replay parser | Follow PEP 8, use four-space indentation, and document input and output types. For changes to event counting or round attribution, keep a reproducible sample and its expected result. |
| Tactical rules and AI | Keep the match evidence used for an assessment identifiable. When a map rule or statistic changes, update the example and its expected output so another developer can explain the difference. |
| Git and review | Track development tasks in issues, work on feature branches, and review changes through pull requests. Describe the observable change in the commit message and attach relevant test results. Keep credentials and active team codes out of commits, screenshots, and logs. |
Our shared conventions and module contracts are available in the repository. Team code style · Design and API documents
Eight-day publication plan
| Sprint window | Publication date | Development log and planned demonstration |
|---|---|---|
| Nov 21–22 | Nov 22 | 1. Building Five Aim-Training Games. Show how targets appear or move in each game, what counts as a hit, and how the player earns a score. Follow one session from mode selection to its result screen. |
| Nov 23–24 | Nov 24 | 2. Building Player Login, Profile Cards, Friends, and Campus Squads. Follow two accounts through a friend request and a squad invitation. Pair each player’s view with the operation that changes the shared state. |
| Nov 25–26 | Nov 26 | 3. From Demo Upload to a Match Report. Follow one replay through upload, parsing, and the API response. Take one round from the response and show exactly where its data appears in the frontend. |
| Nov 27–28 | Nov 28 | 4. Integrating the AI API for Match Analysis and Player Feedback. Continue with the same match. Show which evidence enters the request, how the response reaches the coaching tab, and which round supports one recommendation. Identify the contribution of the local Dust2 rules alongside the model’s assessment. |
Each log will include a project burn-up chart showing total scope and cumulative completed tasks, along with screenshots or a recording of the running module. The chart will use completion milestones supported by the development records. We will credit individual contributions with issue and commit links for development work and with concrete outputs such as test cases, reports, or design revisions for other work.
Our separate testing post will describe the tools, cases, recorded results, and lessons from testing. The Alpha summary will compare the original plan with the delivered release and cover each member’s contribution, the distribution of work, and our goals for the next stage. A pinned index will link all seven posts. The class submission deadline is November 29, 2026 at 23:59.
相关推荐
as_extensions_flash_lite_digital_home
and standards.4.
游戏录播技术全解析:从录制到分发的完整处理方案
视频编码技术是现代多媒体处理的核心基础,通过压缩算法将原始视频数据转换为高效存储格式。其原理基于空间和时间冗余消除,利用帧内预测和帧间运动补偿等技术大幅减少数据量。在游戏录播场景中,合理的编码参数设置直接影响视频质量和文件大小,如H.265编码相比H.264能在相同质量下节省50%带宽。结合FFmpeg等开源工具,开发者可以构建自动化处理流水线,实现录制内容的智能分析和质量优化。本文以实际游戏赛事录播项目为例,详细解析视频处理全流程中的关键技术要点和工程实践方案。
SolidWorks AI控制:Claude Code与DeepSeek Harness技术选型指南
在CAD智能化进程中,自然语言驱动设计正从概念走向工程落地。其核心在于将用户意图转化为SolidWorks API调用,而API的进程隔离、线程安全与几何求解器依赖构成硬性边界。Claude Code以Python为媒介,将大模型作为可调试的‘高级代码补全器’,强调工程师对API链路的掌控;DeepSeek Harness则构建内嵌Agent Runtime,通过Operation Token实现指令级编译与实时状态感知,显著提升复杂装配体迭代效率。二者差异本质是‘编程范式’与‘代理范式’之别,适用于标准件
ASAP learn
the design process.5.
IBM Tivoli Storage Manager for Windows-2
**Plan for Scalability**: Consider future growth and plan accordingly.


