Teamwork——beta Sprint

promisekoloer promisekoloer 墨衍会员 · AI 创作全网分发 墨衍智能分发 通过墨衍一键同步至各平台 可同步平台 CSDN微信公众号微博知乎掘金百家号博客园抖音小红书 你的文章也可以这样分发 墨衍会员 ¥399起/年,写一次发全网 我也要 + 加入社区

Teamwork—beta Spring

Deadline

The deadline for this assignment is December 15, 2023, 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 essay summarizing issues in the alpha stage

  • 1 essay on predicting everything (published before the start of the beta sprint and added to the collection of essays)

  • 1 essay about the team's code standards

  • 3 beta sprint essays.(Arrange a sprint until the end of the assignment during this assignment.Require the team to publish one sprint essays every 3-4 days).

  • 1 user usage survey report

  • 1 Beta sprint summary essay

  • Project classroom demonstration and defense

  • Make defense PPT

  • Specific requirements for the alpha phase problem summary essay (published before the start of the beta sprint and added to the collection of essays)

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 IDTask DescriptionContribution

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.

...全文
0人已提交
完成率0%
暂无数据

相关推荐

变电站精细化设计施工标准(电气部分)

变电站精细化设计施工标准(电气部分).pdf。文档内容齐全,中间有页码不对,是因为这是两个文档合成的,不影响内容完整,内容为图片,不是源文档。

bigshentu

chromedriver-mac-x64-159.0.8133.0(Canary).zip

chromedriver-mac-x64-159.0.8133.0(Canary).zip

LCG元

YOLO26算法工业车间光伏组件热点与系列故障目标检测+训练好的模型+174张数据集+pyqt可视化界面.zip

附训练好的 YOLO 权重与 PyQt 可视化检测界面,页面底部含可视化效果预览,毕设/课设开箱即用。 【数据集概况】 · 检测类别(中文):[系列故障(Falla serie), 热点(Punto caliente)] · 训练集:153 张 · 验证集:14 张 · 测试集:7 张 · 总计:174 张 该数据集聚焦于工业车间内光伏组件的热成像检测场景,专门针对太阳能电池板在运行过程中出现的局部异常进行精准识别,具有明确的工程诊断价值与质量控制意义。数据采集覆盖多种典型热异常模式,为光伏系统运维中的早期隐患预警提供了高质量视觉样本支撑。... 【训练曲线与评估图】 【模型训练配置】 参数 | 值 模型 | yolo26n 训练轮数 | 100 epochs 输入尺寸 | 640x640 批次大小 | 24 优化器 | auto 初始学习率 | 0.01 训练设备 【关键指标汇总】 训练了 85 个 epoch,最终轮指标: 指标 | 数值 mAP50 | **0.8734** mAP50-95 | 0.3870 Precision | 0.8062 Recall | 0.8306 train/box_loss | 2.1071 train/cls_loss | 0.9683 val/box_loss | 1.9784 val/cls_loss | 0.6732 【训练过程分析】 从数据加载那一刻起,整个训练过程仿佛是在一条崎岖不平的道路上前进。训练初期,模型的收敛速度颇为迅速,loss 值稳步降低,到第 20 轮时,box_loss 从初始值 2.1071 下降到 1.85,但并未显著波动,仿佛遇到了平台期。从第 40 轮到 60 轮,训练过程变得愈发缓慢,loss 下降幅度逐渐减小,尤其是 cls_... 使用场景:毕业设计、课程设计、深度学习入门、工业场景落地验证。

guo_xiao_xiao_

对标Adobe Premiere的专业视频剪辑与后期制作工具:基于原生架构重构,集多轨道剪辑、专业调色、字幕图形与音频处理于一体高效创作利器

大家好,我是大飞哥。在视频剪辑与后期制作领域,许多创作者常被主流剪辑软件高昂的订阅费用、全英文的复杂界面以及庞大的安装体积所困扰。这款对标Adobe Premiere Pro的专业视频剪辑与后期制作工具,正是为打破这一壁垒而生的高性价比替代方案。它并非简单的粗糙拼接,而是基于前沿架构对底层逻辑进行全新重构,完整复刻了专业剪辑的常用工作流。其核心使命是让剪辑、调色、字幕、音频与导出全流程,在一个全中文、免安装、无需联网的高效环境中轻松完成,赋予创作者极致的生产力。 在核心功能模块上,软件实现了对专业剪辑需求的深度覆盖。它支持多轨道时间线编辑,提供剃刀切开、波纹删除、滑移滑动等专业工具;特效系统涵盖视频转场、模糊、变换与风格化,且参数支持关键帧动画;专业调色模块配备亮度、对比度、色温、饱和度、曲线与色轮,并配有波形图与矢量示波器;字幕图形支持中文直接输入与描边动画;音频处理则包含增益、降噪与实时电平表,全面满足从粗剪到精修的各项需求。 在实际应用场景中,这款工具展现出了极强的专业适配能力。对于自媒体创作者与短视频博主,可以通过多轨道时间线与关键帧特效,快速完成Vlog剪辑与片头包装;对于企业宣传与影视后期爱好者,借助专业调色台与字幕动画功能,能够精细打磨宣传片与微电影的视觉质感;对于学生群体与办公人士,其多格式导入导出与代理剪辑功能,让日常课程视频或会议记录的裁剪整理变得轻而易举,真正实现了全场景覆盖。 操作体验上,软件采用了与主流剪辑软件高度一致的界面布局,左侧为项目与媒体浏览器,中间为节目监视器,右侧为属性面板,下方为多轨时间轴,熟手几乎零学习成本即可平滑过渡。软件默认简体中文界面,用户可通过“导入媒体”快速拖入素材,使用剃刀工具精准切割,并在效果面板拖拽应用调色与特效,最后点击右上角一键导出,整个流程清晰流畅,配合内置的帮助说明,让创作得心应手。

大飞哥软件自习室

超全反激式变换器开关电源Mathcad设计书

内容概要:本文档《超全反激式变换器开关电源Mathcad设计书》系统阐述了反激式Flyback开关电源的设计原理与工程实现方法,重点结合Mathcad数学工具完成关键参数的精确计算,并利用Simulink搭建闭环控制系统仿真模型,实现从理论计算到系统验证的完整设计流程。内容涵盖反激变换器的工作原理、双闭环控制结构(电压环与电流环)设计、变压器参数计算、PWM控制策略、稳定性分析及动态响应优化,同时整合大量电力电子前沿技术资源,如三电平逆变器中点电位平衡、虚拟同步发电机(VSG)、模型预测控制(MPC)、孤岛检测、阻抗建模、储能协调控制等,形成覆盖电源设计、新能源并网与智能控制的综合性技术体系。; 适合人群:具备电力电子、自动控制或电气工程等相关专业背景,从事开关电源、新能源发电系统、微电网或电力变换器研发工作的工程师及研究生。; 使用场景及目标:①掌握基于Mathcad的反激式开关电源参数化设计方法,提升计算效率与精度;②深入理解双闭环反馈控制在Flyback电路中的应用机制;③结合Simulink仿真平台完成控制算法验证,并拓展至光伏逆变、储能变流、VSG并网等复杂电力系统场景的建模与分析。; 阅读建议:建议结合文档中提供的Mathcad计算书、Simulink仿真模型与参考文献同步学习,注重理论推导与仿真验证的紧密结合,优先掌握控制环路设计思想,再进行实际参数调节与系统性能优化,以实现从原理到工程落地的全面理解。

yyds_2201
评论
收藏 已收藏
分享
返回顶部
promisekoloer
2301-MUSE 176 成员 431 内容