Code Standards, Sprint Tasks, and Plans

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

Assignment Details

QuestionAnswer
Which course does this assignment belong to2401_Mu_SE_FZU
Where is the requirement for this assignmentFifth Assignment —— Alpha Sprint
Team nameElectro Boy
The goal of this assignment1. Establish coding guidelines.
2. Sprint tasks and plans.
Other referencesAlibaba Java Development Manual Ultimate Edition v1.3.0
Huawei Internal Code Standards
Huawei Cloud JavaScript coding specification

1. Team's code standards

in here https://github.com/MingqiLi2003/Electro-Boy.git

2. Overview: Development Task Analysis

The core goal of the Electro Boy project is to develop a Dormitory Property Management System, combining front-end and back-end functionality, real-time data management, and efficient user experience tools to provide an easy and effective solution for managing dormitory-related matters.

2.1 Overview of Development Tasks

The development tasks are divided into the following three layers:

Hardware Service Layer

  • Embedded devices have been developed to manage dormitory-related data, including utility bills, maintenance requests, and notifications.
  • The communication module and data transmission system have been set up to support real-time updates of dormitory management.

Data Persistence Layer

  • An IoT middleware based on the Express framework has been developed to ensure smooth communication and data transmission from front-end to back-end.
  • Backend development using MySQL has been completed to support real-time data storage and management for dormitory utilities, maintenance logs, and notifications.
  • A user database has been established to support management of student information, including dormitory assignments and payment history.

Application Display Layer

  • The Android application based on the Vue3 framework and Echarts has been developed to allow students to check utility bills in real-time, pay online, submit maintenance requests, and receive notifications.
  • The Web platform, developed using HTML and CSS, allows administrators to manage dormitory operations, track student requests, and send announcements.

2.2 Work Completed So Far

After the initial development and technical integration, the following tasks have been completed:

Hardware Layer

  • Embedded development is complete, with the sensor network operating stably to monitor dormitory-related data in real time.
  • Devices have been deployed and tested, with the data transmission module functioning properly to update dormitory information.

Data Persistence Layer

  • The MySQL backend database architecture has been completed to store and manage dormitory utility data, maintenance requests, and student information.
  • The user database has been built, and initial user management systems are functioning as expected.
  • Real-time data processing for utility bill updates and maintenance request tracking has been integrated.

Application Display Layer

  • The UI design for the Android app and Web platform has been completed, providing a seamless user experience for students and administrators.

3 Team Division of Labor

Student IDTask DescriptionContribution
832202210 Li MingqiProject Management and Communication - Developing Project Plans, Teamwork, and Progress Monitoring10%
832102217 Chen YuyanFront-end Architecture and UI Design - Building Front-end Framework, Writing Components, and Designing UI10%
832202201 Ding QingYeFront-end Function Development - Implementing Front-end Functions for Student and Administrator Modules10%
832202216 Aoyu ZhangFront-end optimization and debugging - Front-end performance optimization, bug fixing10%
832202220 Chen ShitaoBackend Architecture and API Design - Building a Backend Framework and Designing API Interfaces10%
832202203 Gaozhengyi WangBackend Function Development - Implementing Backend Functions for Student and Administrator Modules10%
832202219 Chen ZeyunBackend Optimization and Database Integration - Backend Performance Optimization, Database Connection Optimization10%
832202228 Zhang YidongDatabase Design and Optimization - Design database table structure, optimize queries10%
832202207 Rui ZhuTest Case Writing - Writing Front-end Test Cases, Front-end Function Testing10%
832202212 Mingxuan XiaoTest Case Execution - Writing Backend Test Cases, Testing Backend Functionality10%
832202211 Qi LiDeployment and Operations - Project Deployment, Monitoring, and Continuous Integration10%

Team Structure

Development Team (6 members)

  • Responsibilities: Responsible for front-end and back-end functionality development and API implementation.

Testing Team (5 members)

  • Responsibilities: Responsible for designing and executing test cases to ensure functionality completeness.

Blog Team (6 members)

  • Responsibilities: Responsible for writing, publishing, and updating blogs to regularly showcase project progress.

PPT Team (11 members)

  • Responsibilities: Responsible for preparing the final presentation PPT on the last day to showcase the project results.

4. Daily Task Plan

Day 1: November 27th

Development Tasks

Front-end Team

  • Initialize Vue3 project and set up the basic page framework.
  • Create the login page (Login.vue) and device management page (Devices.vue).

Back-end Team

  • Initialize Spring Boot project, complete the database table (Users) for the user module.
  • Configure MySQL database connection and complete the registration and login API.

Testing Tasks

  • Write test cases for user registration and login.

Blog Tasks

  • Write the blog "Code Standards and Sprint Plan", describing the development tasks, timeline, and objectives.
  • Create the "Special Blog Collection" page to record subsequent blog links.

Corresponding Teams

Development Team, Testing Team, Blog Team.


Day 2: November 28th

Development Tasks

Front-end Team

  • Complete the registration page (Register.vue) and implement input validation.

Back-end Team

  • Implement back-end logic for user registration and login, returning JWT.

Testing Tasks

  • Use Postman to test the registration and login API and verify front-end and back-end interaction.

Blog Tasks

  • Publish the first sprint blog: Show burndown chart, project initialization progress, and screenshots.

Corresponding Teams

Development Team, Testing Team, Blog Team.


Day 3: November 29th

Development Tasks

Front-end Team

  • Develop basic functionality for the device management page, including add and delete buttons for devices.
  • Create a multi-device list display page.

Back-end Team

  • Implement APIs for adding, deleting, and querying devices.

Testing Tasks

  • Test the device management module's API functionality.

Blog Tasks

  • Update "Special Blog Collection".

Corresponding Teams

Development Team, Testing Team.


Day 4: November 30th

Development Tasks

Front-end Team

  • Integrate Axios to call the device management API, ensuring device add and delete functions work correctly.

Back-end Team

  • Simulate the real-time monitoring data API (GET /monitoring/{deviceId}).

Testing Tasks

  • Write test cases for the real-time monitoring module to validate data format and stability.

Blog Tasks

  • Publish the second sprint blog: Show progress of the device management module, with burndown chart and screenshots.

Corresponding Teams

Development Team, Testing Team, Blog Team.


Day 5: December 1st

Development Tasks

Front-end Team

  • Develop the real-time monitoring page (Monitoring.vue) and integrate Echarts to display real-time data curves.

Back-end Team

  • Integrate water temperature prediction algorithm and provide prediction API (GET /monitoring/predict/{deviceId}).

Testing Tasks

  • Test the response time and accuracy of the prediction algorithm API.

Blog Tasks

  • Update "Special Blog Collection".

Corresponding Teams

Development Team, Testing Team.


Day 6: December 2nd

Development Tasks

Front-end Team

  • Implement integration of real-time monitoring page and prediction data display.

Back-end Team

  • Develop alarm record API.

Testing Tasks

  • Test the alarm record module to ensure data storage and query functionality.

Blog Tasks

  • Publish the third sprint blog: Show progress on real-time monitoring and prediction functionality.

Corresponding Teams

Development Team, Testing Team, Blog Team.


Day 7: December 3rd

Development Tasks

Front-end Team

  • Develop the intelligent Q&A page (QA.vue), integrating voice input functionality.

Back-end Team

  • Complete the intelligent Q&A API, integrating the BERT model and knowledge graph.

Testing Tasks

  • Test the semantic recognition effect of the intelligent Q&A feature.

Blog Tasks

  • Update "Special Blog Collection".

Corresponding Teams

Development Team, Testing Team.


Day 8: December 4th

Development Tasks

Front-end Team

  • Develop the multi-device location page (Location.vue) and integrate AMap API.

Back-end Team

  • Develop the device location API to provide latitude and longitude data.

Testing Tasks

  • Test the functionality and map loading performance of the device location module.

Blog Tasks

  • Publish the fourth sprint blog: Show progress on intelligent Q&A and device location modules.

Corresponding Teams

Development Team, Testing Team, Blog Team.


Day 9: December 5th

Development Tasks

Front-end Team

  • Integrate all feature pages and optimize the interface layout.

Back-end Team

  • Perform database optimization to improve query efficiency.

Testing Tasks

  • Complete system-wide testing and fix all identified issues.

Blog Tasks

  • Write a testing blog, describing testing tools, test case design, and results.

Corresponding Teams

Development Team, Testing Team, Blog Team.


Day 10: December 6th

Development Tasks

Front-end Team

  • Package the front-end project and prepare for deployment.

Back-end Team

  • Deploy the back-end service to Ali and perform final integration testing.

Testing Tasks

  • Conduct the final regression testing to ensure the system runs stably.

Blog Tasks

  • Publish the fifth sprint blog: Summarize the sprint results, including complete screenshots and videos of the system running.

PPT Tasks

  • Prepare the defense PPT showcasing the burndown chart, project functionalities, testing results, and improvement plans.

Corresponding Teams

Development Team, Testing Team, Blog Team, PPT Team.

5.PSP Table for "Electro Boy" Project

PhasePlanned HoursActual HoursDeviationComments
Planning45+1The planning phase took longer due to more detailed scope definition and task breakdown.
Design67+1Additional time spent on UI/UX design and system architecture discussions.
Development4045+5Development took longer due to unanticipated integration challenges with backend services and API interactions.
Testing1214+2Extra time needed to test all APIs and conduct integration testing between modules.
Documentation86-2Documentation process was completed ahead of schedule with thorough API and UI documentation.
Code Review440Code review process went smoothly as per the planned timeline.
Deployment65-1Deployment phase was completed faster due to prior testing and fewer deployment issues.
Total8081+1Overall, the project stayed close to the planned timeline with minor deviations.
...全文

相关推荐

弱电网下光伏并网逆变器序阻抗建模仿真复现扫频法【序阻抗判断稳定性】

内容概要:本文聚焦于弱电网条件下光伏并网逆变器的序阻抗建模与稳定性分析,系统阐述了基于扫频法的阻抗特性仿真与复现方法。通过构建正负序阻抗模型,深入剖析逆变器在弱电网环境中的动态响应特性,结合锁相环、电流环等关键控制环节对系统阻抗的影响机制,采用序阻抗稳定性判据评估多机并网或复杂电网条件下的系统稳定裕度。研究在Simulink平台中实现激励信号注入、频率响应采集与阻抗曲线绘制,为高比例新能源接入背景下并网系统的稳定性分析提供了可靠的仿真手段与理论支撑,尤其适用于SCI级别论文成果的复现与拓展验证。; 适合人群:电力电子、新能源并网技术及相关领域的硕士/博士研究生、科研人员,以及从事光伏逆变器、微电网稳定控制开发的工程技术人员。; 使用场景及目标:①掌握扫频法在电力电子装置阻抗建模中的具体实施流程;②理解并应用基于序阻抗的稳定性判据进行系统稳定边界分析;③用于高水平学术论文(如SCI期刊)中阻抗建模与稳定性分析部分的仿真复现与方法验证; 阅读建议:建议读者结合文中所述方法与提供的参考文献,自主搭建Simulink仿真模型,逐步完成扰动信号设计、数据采集、傅里叶分析及阻抗拟合全过程,深入探究控制参数变化对系统阻抗特性和稳定性的具体影响,强化理论与实践的融合能力。

欢多天天写代码

三相并网逆变器虚拟阻抗+统一有源阻尼策略SVPWM+SPWM调制仿真

内容概要:本文档系统性地介绍了三相并网逆变器的核心控制技术及其在复杂电网环境下的仿真应用,重点涵盖虚拟阻抗与统一有源阻尼策略在SVPWM和SPWM调制方式下的实现方法,旨在提升逆变器的稳定性与电能质量。内容包括无功功率扰动孤岛检测、中点电位平衡控制、低电压穿越(LVRT)、模型预测控制(MPC)、正负序分离、电网前馈控制等关键技术,并扩展至风储联合调频、微电网下垂控制、虚拟同步发电机(VSG)、构网型逆变器等多种典型电力系统应用场景。所有技术均配有基于Simulink/Matlab平台的完整仿真模型、参考文献及说明文档,强调理论分析与仿真实践的深度融合,突出科研中“借力”与创新思维的重要性。; 适合人群:电气工程、自动化、新能源等相关专业的研究生、科研人员及从事电力电子与可再生能源系统开发的工程师;具备MATLAB/Simulink仿真基础和电力系统专业知识的技术人员。; 使用场景及目标:①开展三相并网逆变器控制策略的研究与优化设计;②复现高水平学术论文中的控制算法;③完成毕业课题、科研项目或工程仿真验证;④掌握虚拟阻抗、有源阻尼、SVPWM/SPWM调制、MPC、VSG等核心技术的建模与实现方法;⑤支撑微电网、构网型变流器等前沿方向的科研攻关。; 阅读建议:建议按照资源目录结构化学习,优先选择与自身研究方向契合的内容模块,结合提供的仿真模型、参考文献和说明材料进行实操演练,注重从理论推导到仿真实现的全过程理解,充分利用共享网盘资源深化技术掌握,提升科研效率与创新能力。

欢多天天写代码

chromedriver-win32-159.0.8133.0(Canary).zip

chromedriver-win32-159.0.8133.0(Canary).zip

LCG元

计算机“101计划”《人工智能引论》教学大纲+课件+实训案例

计算机“101计划”《人工智能引论》教学大纲+课件+实训案例

qq_38220914

语音输入法离线语音输入转文字工具2.0支持双档本地识别模型,中英混说精准转写,纯离线运行保护隐私,让打字更高效.zip

大家好,我是大飞哥。日常打字时,频繁切换输入法、断网无法语音转写、或担心语音数据被传至云端,是许多办公族和内容创作者的共同痛点。这款离线语音输入工具 ,正是为此量身打造的 Windows 桌面语音辅助利器。它的核心使命就是按住快捷键说话,松开文字自动上屏,全程本地离线识别,让您在任何可输入文字的窗口内都能实现高效、私密的语音输入,彻底告别网络依赖与隐私焦虑。 在核心功能上,软件内置了两档本地语音识别模型,通过主界面下拉框即可随时切换。默认的“离线·标准”模式响应极快,支持中英混说且自带标点,非常适合日常聊天与文档撰写;而“离线·精准”模式则对纯中文、方言口音及长段落口述的识别准确度更高。更贴心的是,它具备实时预览与一键取消机制,说话过程中若发现说错,按下 Esc 即可取消,一个字都不会误输入;若目标窗口不支持直接写入,文字会自动存入剪贴板,方便您按 Ctrl+V 粘贴,确保每次发声都不白费。 这款工具在具体场景中的表现十分亮眼。对于办公白领,在填写表格、撰写邮件或使用微信、QQ 沟通时,无需频繁切换窗口,按住右键说话即可快速完成信息录入;对于程序员与文字工作者,在代码编辑器或文档中口述注释与段落,能显著提升创作效率;对于经常出差的商务人士,在飞机、高铁等断网环境下,它依然能稳定工作,不经过任何服务器,真正做到了“说了什么只有自己知道”,私密性极佳。 使用体验方面,软件将极简操作贯彻到底。解压后双击 大飞哥语音输入,右下角托盘出现蓝色话筒图标即代表准备就绪。用户只需将光标点进目标输入框,按住右 Alt说话,说完松开,文字便会自动写入。主界面提供了设置快捷键与开机自动启动选项,方便用户按习惯自定义组合键;关闭主窗口并不会退出程序,而是缩至托盘持续待命,彻底退出只需右键托盘或点击主界面按钮,逻辑清晰,零门槛上手。

大飞哥软件自习室
评论
收藏 已收藏
分享
返回顶部