Teamwork—beta Spring

助教_林日臻 2025-12-28 13:20:38

Deadline

The deadline for this assignment is January 6, 2026, 23:59

1. Assignment Requirements

1.Blog Submissions

The following content is basically arranged in chronological order. Please arrange your time reasonably and do not concentrate multiple tasks into a certain period of time to complete intensively.

  • 1 top-of-the-line collection of essays in the Beta stage, including links to all the following content
  • 1 Specific requirements for the alpha phase problem summary essay (published before the start of the beta sprint and added to the collection of essays)
  • 1 essay on "Preparing for Everything" (published before the start of the beta sprint and added to the collection of essays)
  • 1 essay about the team's code standards
  • 5 beta sprint essays.(Arrange a sprint until the end of the assignment during this assignment. Ensure that the essays released by the team are not published on the same day).
  • 1 user usage survey report
  • 1 Beta sprint summary essay
  • Project classroom demonstration and defense
  • Make defense PPT

During the Alpha sprint, many students experienced "learning by doing", learning a new programming language, learning Git, and learning to build a complete project. However, each group did not have a deep understanding of the meaning of "learning by doing" in software engineering and encountered many problems. Stop for a while, hold a summary meeting, and gain hindsight.

2.Improvements and new features are needed in the next phase.

  • Team division of labor needs to be improved (regarding previous deficiencies, team collaboration and division of labor need to be strengthened and improved)
  • Tool processes that need improvement (such as version control, testing tools, etc.)
  • The planning and arrangement of all blogs, as well as the time planning of the sprint.
  • Specific requirements for the sprint essay blog.

2.sprint blogs

The sprint blog is divided into two parts: scrum and PM report

1.SCRUM section

  • Description of each member: achievements from yesterday’s stand-up meeting to the present (which task was completed, how much time was spent, and how much time is left), existing problems/difficulties encountered, and arrangements for the stand-up meeting from now to tomorrow. (can be listed in tabular form)
  • If the team members' work is development work, they must have code check-in, and provide the Issue content and link/picture corresponding to the check-in record. (If missing, deduct 2 point from the sprint log that day)
  • If the work of team members is testing and other work, it must have specific results, such as screenshots, test reports, etc. (If missing, deduct 2 point from the sprint log that day)
  • A photo of the SCRUM meeting. The meeting photo should be real, unstaged photo of the daily sprint meeting. Faces can be covered to protect privacy.(If photos are reused, the sprint log will not be scored on that day.)

PM report

  • Summarize the expected taskof the entire project (the expected time of all work or the total number of issues), the work that has been completed so far (the time it takes to complete the work or the number of issues that have been completed), and the remaining work (the expected time of the remaining work) or the number of remaining issues)
  • Draw a burn-up chart to show the real situation
  • Record the changes in the total amount of tasks, reflect how many things you have discovered during your work that you had not thought of before; (you can draw a chart)
  • Latest running pictures/gifs/videos of appropriate project procedures/modules (If missing, deduct 2 point from the sprint log that day)

3.Beta Sprint Summary Essay Blog Specific Requirements

  • Corresponds to the tasks set before the start of the sprint (functions to be improved and added). Use a table to display the completion status; for items that have not been completed, describe the specific degree of completion.
  • In the "Problem Summary Essay in the Alpha Phase" and "Essay on Preparing for Everything" before the start of the sprint, your team set up some improvement plans. How was the completion of these plans?
  • Runnable project links, project files, program QR codes, etc. If it is a mobile project such as a WeChat applet or APP, please pay attention to the corresponding online review mechanism, required time and other matters, and be sure to understand and prepare in advance.
  • Running pictures, gifs or videos of each function of the project
  • Each member’s experience, gains and insights during the sprint phase
  • To distribute the contribution of each member, you can use the following markdown

Student ID

Task Description

Contribution

3.Scoring Rules for this Assignment

1.Defense Score

  1. Defense Score (consistent with previous scoring rules) = Sum of scores from other groups/(total number of groups-1) * 0.25 + Sum of assistant scores/(number of assistants) * 0.35 + Sum of teacher scores/(number of teachers) * 0.40

2.Blog Score(100'):

  • (20')Summary of issues in the alpha phase (with the benefit of hindsight)
  • (14')Answered questions related to assumptions, goals, and plans; answered questions related to design/implementation, testing/release
  • (28')5 beta sprint essays
  • (10')user usage survey report
  • (12')Beta sprint summary essay
  • (10')Project expected plan, degree of completion, improvement plan completion status, project running link and screenshot display, etc.
  • (6')Process experience, team members’ division of labor and collaboration

​ Score for this assignment = Defense score * 60% + Blog score * 40%

Blog Guidelines

1. Submission Rules

  • The blog is subject to the submission time of the class assignment page; the files that need to be submitted are subject to the submission time of github;
  • Submitted before the deadline, the score will be the actual score;
  • If the post is under review after it is published (the post displays 404), you can submit the link to the assignment page before the deadline and wait for the review to pass.
  • Reasons for resubmission such as upload failure and network reasons will not be accepted.
    • Late Submission: Submitting within two days after the deadline is considered a late submission, and the score is the actual score * 50%; writing but forgetting to submit the assignment and late submissions are penalized equally.
    • Missed Deadline: Failing to submit the blog within two days after the deadline is considered a missed assignment, and the score is 0.
    • Assignment Plagiarism: When the teaching assistant finds that two blogs have text/images/code that are too similar, both blogs are considered plagiarized, and both receive a score of -100% (note that this is a negative score!).
    • Forgery of Submission: Although the assignment blog has not been completed, submitting it to occupy a place is considered a forged submission, and the score is 0.
    • Note: For assignments submitted in advance, if you can actively respond to teaching assistant and teacher feedback and make corresponding revisions before the deadline, these improvements will be taken into account in the subsequent grading. Early preparation has many advantages. Please note that editing blog content is not allowed after the deadline.

2.Points to Note

If the class group releases relevant notices, it is also part of the assignment requirements; please check the group notice in time. If you need to fill in related information in the group and fail to complete it before the deadline, deduct 50% of the actual score. If there are any questions about the assignment, please raise them in the class group three days before the deadline. If the assistant makes changes to the assignment requirements, it will be announced in the group; please be sure to check and improve the assignment according to the new requirements. Please respond promptly to the comments from the teacher or assistant and make the corresponding modifications. Even if the assignment is submitted, pay attention to the announcements from the assistant in the class group!

3.Clarifying Doubts

If there are unclear aspects of the assignment or if you don't understand something, you can ask in the QQ or WeChat group.

4.PPT  and Practical Demonstrations

During the defense, you should integrate the PPT with practical demonstrations, and strive to allocate the majority of the defense time to the demonstration of examples.

...全文
854 1 打赏 收藏 举报
写回复
用AI写文章
0人已提交
完成率0%
暂无数据
1 条回复
切换为时间正序
请发表友善的回复…
发表回复
文末附数据集可视化效果图。 【数据集概况】 · 检测类别(中文):[矿石0(0), 矿石1(1), 矿石10(10), 矿石11(11), 矿石2(2), 矿石3(3), 矿石4(4), 矿石7(7), 矿石8(8), 矿石9(9), 模组矿石(modore), 普通矿石(ore)] · 训练集:1383 张 · 验证集:130 张 · 测试集:66 张 · 总计:1579 张 该数据集聚焦于典型游戏内资源采集场景,以俯视角呈现冰雪覆盖的虚拟地形环境,包含多种类型矿石与特殊资源点。数据集中各类矿石分布密集且形态多样,标注清晰,能够有效支持对复杂背景下的小目标识别与分类任务,具备较高的训练价值和实际应用潜力。... 【训练曲线与评估图】 【模型训练配置】 参数 | 值 模型 | yolo26n 训练轮数 | 100 epochs 输入尺寸 | 640x640 批次大小 | 24 优化器 | auto 初始学习率 | 0.01 训练设备 【关键指标汇总】 训练了 100 个 epoch,最终轮指标: 指标 | 数值 mAP50 | **0.9185** mAP50-95 | 0.5810 Precision | 0.9468 Recall | 0.8648 train/box_loss | 1.2381 train/cls_loss | 0.4081 val/box_loss | 1.5489 val/cls_loss | 0.5361 【训练过程分析】 100 轮训练后 mAP50 达到 0.9185,模型收敛良好。Loss 曲线前段快速下降,后段趋于平稳,val_loss 无反弹,没有明显过拟合。但 mAP50-95 为 0.5810,和 mAP50 差距 0.34,定位精度仍有优化空间。 【模型性能评估】 Precision 0.9468、Recall 0.8648...
内容概要:本文提出一种融合细菌觅食优化算法(BFOA)、蚁群算法(ACO)与长短期记忆网络(LSTM)的混合智能算法A-ACO-LSTM,用于解决无人机在复杂三维环境中的路径规划问题。通过三维栅格地图建模,结合LSTM对航段风险的预测能力、BFOA在连续空间中的全局优化能力和ACO在离散栅格路径上的搜索优势,构建了“先学习—再优化—后修正”的协同框架。系统综合考虑路径长度、障碍碰撞、飞行风险、转弯平滑度和垂直爬升等因素,设计多目标归一化代价函数与动态权重机制,在保证飞行安全的前提下提升路径质量。代码基于MATLAB实现,包含环境生成、LSTM训练、BFOA连续优化、ACO离散搜索、路径融合与三维可视化等模块,支持参数配置、结果复现与工程扩展。; 适合人群:具备一定算法基础和MATLAB编程经验,从事无人机路径规划、智能优化算法或人工智能应用研究的研发人员及研究生。; 使用场景及目标:①应对城市楼宇、山地地形等复杂三维障碍环境下的无人机自主导航;②实现低能耗、高安全性、强鲁棒性的飞行路径规划;③为多源算法融合与深度学习辅助优化提供技术参考与实现范例; 阅读建议:建议结合完整代码与GUI界面深入理解各模块交互逻辑,重点关注LSTM风险预测与两种群智能算法的耦合机制,可通过更换训练数据、调整环境参数进行二次开发与性能测试。

165

社区成员

发帖
与我相关
我的任务
社区描述
2501_MU_SE_FZU
软件工程 高校
社区管理员
  • FZU_SE_LQF
  • 助教_林日臻
  • 朱仕君
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧