First assignment-- front-end and back-end separation contacts programming

助教-吴可仪 2024-09-27 17:46:11

First assignment-- front-end and back-end separation contacts programming


To avoid missing homework content, here is a checklist for students to quickly review

  • Programming implementation

  • Basic function implementation

  • Deployment

  • Release version released

  • Write a blog and submit a blog before the deadline

  • Include job description and directory

  • Check scoring criteria


Due to the first time using community Posting to submit homework, many students did not submit correctly, the following is a gif demo:

This assignment allows the use of any visualization technology: web, Android, applet of WeChat, etc., but to reflect the front and back end separation to achieve the following functions.

Deadline

The deadline for this assignment is: November 1, 2024 23:59
Note: The blog needs to be reviewed after publication, please remember to publish the blog in advance to avoid affecting the assignment submission.

Part1:Homework content

1. Basic contacts functions

  • Function 1: add
    • Basic operations for adding contacts, including name, phone number, etc. and store contacts information in a back-end database
  • Function 2: modify
    • Modify the contacts information. must be read from the back-end database, can not use the cache.
  • Function 3: delete
    • Requirement as above

2. Other instructions

  • About Extended features
  • You can extend the function you want to extend, the extension function will be recorded as additional points, for the extension function please describe in detail in the blog.
  • About development
  • It is recommended to develop based on Web, using Web frameworks, such as common JSP, Servlet, spring series, flask, php, express and so on. Allows the use of any visualization technology: web, Android, wechat mini program, etc. But the front and back ends should be separated.
  • The technology used should be platform compatible and not dependent on the specific environment.
  • The main objective of this assignment is to achieve functionality, and technical considerations only count for a certain number of points. Do not use the prototype tool to generate code, set 0 points directly who gets caught.

Part2:Coding requirement

1.Use of Github

This assignment will continue to follow Github, which requires the development technology of front end and back end separation. Please submit the front end and back end separately in different warehouses, and the link of code warehouse in the blog is convenient for teaching assistants to check.

Frontend Project Directory Structure

|-Student ID_concacts_frontend|- src
​
​        |- concacts.html/.xml/.wxml
​
​    |- ......other files

|- README.md

|- codestyle.md

Backend Project Directory Structure

|-Student ID_concacts_backend|- src|- ...|- controller |- concacts.java/.go/.py...|- ....other files

|- README.md

|- codestyle.md

2.Code Standards Development

The assignment for this time still requires the creation of a codestyle.md as a code standard document. However, it is required that this code standard be derived from mainstream official standards or those recommended by major companies, and the source should be indicated at the top of the code standard document.

3.Technologies and Frameworks

The current assignment does not restrict the choice of programming language, libraries, or frameworks to be used.


Part3:Blog Writing Requirements

  1. Assignment Description
  2. You can include the Github repository address at the beginning of your article. Here's how you can incorporate it into your blog post's introduction:
  3. Before starting the implementation of the program, record your estimated and actual time spent on the development of various modules of the program in the PSP table. After implementing the program, record the actual time spent in the PSP table.
  4. Provide the access link after deploying the project to the cloud server.
  5. Present your finished product, requiring the provision of 10 or more images, or the use of GIFs or embedded videos to demonstrate the required functionality of the assignment. Each displayed image should be accompanied by a brief text description.
  6. Describe the design and implementation process and provide a functional structure diagram.
  7. Code explanation. Display the key code of the project and explain the thought process.

Part4:Assignment Grading Criteria and Evaluation Rule

The total score for this assignment is 100 points.

  • (30') Basic Requirements [Covering Course Objective 2]

    • (15‘) Blog Formatting, using Markdown formatting; Provide the Github repository link correctly and the code standard link
    • (15‘) Function Analysis and Design of the Implementation Process
  • (70‘) Coding Implementation [Covering Course Objective 4]

    • (20‘) Frontend Page Presentation
    • (50‘) Backend Functionality Implementation
      • (20‘) Feature 1: Add
      • (20‘) Feature 2: Modify
      • (10‘) Feature 2: Delete
  • (Extra Credit: 0' to 10) Additional Features


Part5:Rules & Format

  1. To facilitate readability and assist teaching assistants in grading, please provide a table of contents at the beginning of your blog as a content index. Ensure that the table of contents can navigate correctly!

Be sure to include the following major headings; similar meanings are acceptable, and you can personalize your own titles:

  • Git Repository Link and Code Standards Link
  • PSP Table
  • Presentation of the Finished Product
  • Design and Implementation Process
  • Code Explanation
  • Personal Journey and Learnings
  1. To help teachers or teaching assistants from other schools understand the course situation, please add a format description at the beginning of the assignment:
Course for This Assignment
Assignment Requirements
Objectives of This Assignment
Other References...
  1. Submission Rules
  • The submission time for the blog post is based on the class assignment page; the time of code submission is based on Github.
  • Submitting before the deadline will be graded based on the actual score.
    • If the post is under review (the post shows 404) after publication, you can first submit the link to the assignment page before the deadline and wait for it to be approved.
    • Excuses like upload failure or network issues for late submissions will not be accepted.
  • Late Submission: Submitting within two days after the deadline is considered a late submission, and the score will be 50% of the actual score; forgetting to submit the assignment and late submissions will be penalized equally.
  • Missed Submission: Failing to submit within two days after the deadline will result in a score of 0.
  • Plagiarism: When the teaching assistant finds that two blog posts have text/images/code that are too similar, both blog posts will be considered as plagiarism, and both will receive a -100% score (note that it's negative!).
  • Falsifying Submissions: Although the assignment blog may not be completed, submitting it early to reserve a spot will be considered a falsified submission, and the score will be 0.
    Note: For assignments submitted in advance, if you can actively respond to feedback from teaching assistants and make corresponding revisions before the deadline, these improvements will also be taken into consideration during subsequent grading. Being well-prepared in advance has many benefits~
  1. Notices
  • Class group announcements are also part of the assignment requirements. Please check group announcements in a timely manner. If you need to fill out relevant information in the group and fail to do so before the deadline, you will be penalized by 50% of the actual score. If you have any questions about the assignment, please raise them in the class group three days before the deadline. If there are any changes to the assignment requirements by the teaching assistants, they will be announced in the group, so please be sure to check and improve your assignment according to the new requirements. Please respond promptly to feedback from the teacher or teaching assistant. Even after submitting the assignment, you should pay attention to announcements from teaching assistants in the class group!
  1. Clarifications
  • If you find any unclear or misunderstood parts of the assignment, you can leave a comment below this blog post or directly ask questions in the QQ group or WeChat group.

...全文
3206 回复 打赏 收藏 转发到动态 举报
写回复
用AI写文章
0人已提交
完成率0%
暂无数据
回复
切换为时间正序
请发表友善的回复…
发表回复
内容概要:本文围绕含软开断装置(SOP)的配电网在发生多线路故障情况下的故障重构问题展开研究,提出了一种基于Matlab代码实现的优化重构方法。通过引入SOP这一先进的电力电子设备,充分发挥其对有功和无功功率的灵活独立调节能力,实现对配电网潮流的精确控制。在多点故障发生后,该方法能够快速隔离故障区域,并通过重构网络拓扑,最大限度地恢复健全区域的供电,有效减少停电损失,从而显著提升供电可靠性和系统应对突发事件的韧性。研究建立了以最小化负荷削减量和开关操作次数为目标的混合整数非线性规划模型,并综合考虑了潮流平衡、节点电压、线路容量及辐射状运行等关键约束条件,采用先进的智能优化算法进行求解,并通过标准算例系统进行了Matlab仿真验证,证明了所提方法在恢复能力和运行经济性方面的优越性。; 适合人群:电气工程、电力系统自动化等相关专业的高校师生、科研人员以及从事电网规划、运行与调度的工程技术人员。; 使用场景及目标:①用于研究高比例分布式电源接入背景下,配电网在极端故障事件后的快速恢复与韧性提升策略;②为SOP等新型柔性互联装置的规划配置、运行控制及效益评估提供理论依据和技术支持;③作为电力系统优化、故障恢复算法、智能优化算法教学与科研的综合性案例参考。; 阅读建议:读者应具备一定的电力系统分析、优化建模和Matlab编程基础,建议结合提供的Matlab代码进行实践操作,深入理解故障重构模型的构建逻辑、求解流程及SOP的作用机理,并可根据不同的电网参数或故障场景对模型进行修改和扩展,以适应多样化的研究与应用需求。

173

社区成员

发帖
与我相关
我的任务
社区描述
2401_MU_SE_FZU
软件工程 高校
社区管理员
  • FZU_SE_TeacherL
  • 助教-吴可仪
  • 助教-孔志豪
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

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