Teamwork——beta Sprint
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 ID | Task Description | Contribution |
|---|---|---|
3.Scoring Rules for this Assignment
1.Defense Score
- 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.
相关推荐
chrome-headless-shell-win32-159.0.8132.0(Canary).zip
chrome-headless-shell-win32-159.0.8132.0(Canary).zip
惠普150 联想1821 1831 1831W定影清零,转印带清零
惠普150 联想1821 1831 1831W定影清零,转印带清零,报错不打印,通过清零软件可以清除。内附使用说明。
【电液伺服执行器与PI控制器】带有PI控制器的电液伺服执行器的模拟研究(Simulink仿真实现)
内容概要:本文围绕带有PI控制器的电液伺服执行器开展模拟研究,利用Simulink工具构建系统仿真模型,深入分析PI控制器在电液伺服系统中的控制性能与动态响应特性。研究内容涵盖系统建模、PI控制参数整定、仿真结果分析等关键环节,重点探讨PI控制器对系统稳定性、响应速度及抗干扰能力的优化作用,并通过仿真验证控制策略的有效性与实用性; 适合人群:具备自动控制原理、液压传动基础知识及Simulink仿真能力的自动化、机械电子、控制工程等相关专业的高校学生、研究生及工程技术人员; 使用场景及目标:①用于自动控制类课程的教学实验或课程设计,帮助学生深入理解电液伺服系统的工作原理与典型控制方法;②应用于工业高精度执行机构的控制器设计,为实际工程中的系统优化提供理论支撑与仿真验证手段; 阅读建议:文中提供的Simulink模型与仿真流程具备良好的可复现性,建议读者结合具体工况调整PI参数,进一步探究PID或其他先进控制算法的改进效果,以深化对控制系统设计的理解与应用能力。
FYZN PcbDesigner.App.1.0.18.12-win10.rar
打开与保存 常用格式直接读写:打开、编辑、保存 .PcbDoc(含设计规则、层叠等信息)也能打开看结构 原理图文档:打开 / 新建 .SchDoc,和 PCB 文档一起在左侧项目树里管理,双击节点即可重开 另存为通用 ASCII:原理图与 PCB 都能导出为 ASCII 格式,方便文本比对、脚本处理,或交给别的流程 底图参考:需要对着图描的时候,可以给每个图层各放一张参考底图,与文件分开存 JSON,迁移工程时能一起带走 最近文件:最近打开的文件列表里可以直接右键「打开文件位置」 win10版本
软件测试浏览器自动化测试3
内容概要:本文介绍了浏览器自动化测试的三种主流工具——Selenium、Playwright 和 Puppeteer,并重点展示了 Puppeteer 的一个最小可运行代码示例。文章指出,从选型角度看,2026年的技术共识是新项目应优先选择 Playwright,已有 Selenium 框架的项目无需主动替换,而 Puppeteer 更适用于仅针对 Chrome 浏览器且运行环境为 Node.js 的场景。文中提供的 Puppeteer 示例涵盖了启动浏览器、打开页面、设置视口、键盘操作、元素定位与点击等核心操作流程,体现了其作为“浏览器控制库”的定位。同时强调,Puppeteer 本身不包含测试运行器和断言功能,需结合 Jest 等测试框架才能完整实现自动化测试能力,这是它与 Playwright 和 Selenium 的本质区别。; 适合人群:具备一定前端或自动化测试基础,从事 Web 自动化测试相关工作的开发与测试人员,尤其是面临工具选型的技术决策者;; 使用场景及目标:①帮助开发者快速理解 Puppeteer 的基本使用方式及其在实际项目中的应用流程;②为团队在自动化测试工具选型时提供明确的技术方向建议,尤其是在新项目中评估 Playwright 与 Puppeteer 的适用边界;; 阅读建议:在学习本文时,建议结合实际编码环境运行示例代码,并进一步探索 Puppeteer 与 Jest 的集成方案,以构建完整的测试闭环;同时关注 Playwright 相对于 Puppeteer 的优势,如多浏览器支持和内置测试模型,以便做出更合理的工程决策。


