2023 Anhui Vocational College Skills Competition
Application software system development competition
November 2023
If you need source code competition information, you can send a private message to the blogger
1. Competition name
Competition name: Application software system development
English name: Application Software System Development
Competition Category: Higher Vocational Group
Competition category: Electronic information category
2. Competition Goals
The report of the 20th National Congress of the Communist Party of China clearly pointed out that "it is necessary to promote the development of integrated clusters of strategic emerging industries and build a number of new growth engines such as new generation information technology." The enabling role of the new generation of information technology industry in high-quality economic and social development has become more prominent. , Software is the soul of the new generation of information technology, the foundation for the development of the digital economy, the key support for the construction of a manufacturing power, a network power, and a digital China, and a new driving force for the high-quality development of industries.
This competition aims to implement the national software development strategy, deepen the integration of industry and education, collaboratively promote the innovation and development of the software industry, and empower the high-quality development of the economy, society and modern vocational education. Docking the current new technologies, new business formats, new models, and new requirements in the field of software engineering, through the competition, the contestants will be able to master the development process and implementation process of a real enterprise application software system; the contestants will be trained to carry out database design and simple implementation in the real enterprise project environment. Ability in algorithm analysis and design, software design and development, software deployment testing and operation and maintenance, software project documentation, etc., while cultivating players' abilities in inquiry learning, lifelong learning and sustainable development.
The competition items are designed around the actual needs and requirements of relevant positions in the software industry. Through the competition, leading enterprises, industry-education integrated enterprises, etc. will be deeply involved in various aspects of vocational education such as talent training, technological innovation, social services, employment and entrepreneurship; it will also test vocational colleges. Teaching level, leading the construction of majors and the reform of "three educations", promoting the collaborative education of "job-class competition certificates", and creating a social atmosphere that advocates skills; strengthening the transformation of post-competition resources, transforming competition results into teaching materials, courses and practical training projects, etc. resources, integrated into teaching, service teaching, and provided high-quality technical and technical talents in the field of software engineering for the national development strategy.
3. Competition content
(1) Players must have the ability
This competition is based on real enterprise software system projects and work modules. Through typical software system development tasks such as "requirements analysis - system prototype design - database design - module development - system deployment - system testing", it combines higher vocational software technology and computer applications. The teaching standards for technical majors fully consider the latest demands for students' professional skills in corporate positions, and complete designated competition modules within the specified time. It mainly tests contestants' computer information processing technology, programming, operating systems and other related knowledge, application software system database design , simple algorithm analysis and design, front-end page and back-end business function development, data collection and analysis, system deployment testing and operation and maintenance, software project documentation, etc., to cultivate players' work organization and teamwork skills, communication and interpersonal interactions competencies, problem-solving skills, and self-learning with a commitment to keeping pace with industry developments.
(2) Competition modules and content
1. Competition time
The total competition time for this event is 6 hours (one day). Each participating team must independently complete the competition module specified in the "Competition Content" within the specified time.
2. Competition content
The content of the competition is based on real enterprise software system projects, and based on typical tasks of software system development, three competition modules are set up: "System Requirements Analysis", "Software System Development" and "System Deployment Testing".
Module 1: System Requirements Analysis
This module focuses on testing the contestants' ability to analyze system requirements based on given requirements, including:
(1) System planning and design. According to the given project requirements, sort out and plan the requirements, use standard requirements specifications (templates) to describe the requirements specifications, write a module summary, and draw corresponding business flow charts/activity diagrams, use case diagrams, and class diagrams , timing diagram, ER diagram.
(2) Prototype design drawing. According to the module functional requirements, use prototype drawing software to design the module prototype and realize the interactive functions between prototype pages.
Module 2: Software system development
This module focuses on testing the contestants’ business design, front-end page development and back-end business code writing abilities, including:
(1) Front-end page development. Based on the given system requirements, use the data interface provided by the back-end API, use HTML5, CSS3, JavaScript, Vue.js ( ElementUI , vue -element-admin) and other technologies, follow the MVVM model to complete the front-end page and implement business functions. The coding is required to comply with front-end engineering development technical specifications.
(2) Back-end business development. Based on the given system requirements, use visual development tools to design the database, use the Spring Boot framework to implement back-end business functions, complete the development of the RESTful API interface, and publish and run it. It is required that the design conforms to the Domain/POJO, DAO, Service, and Controller hierarchical architecture patterns of the Spring Boot framework, and the coding conforms to the naming and annotation specifications.
Module Three: System Deployment Test
This module focuses on testing the contestants' system deployment, functional testing, bug troubleshooting and document writing abilities, including:
(1) System deployment. Publish the given project into the integrated deployment tool to ensure proper functioning.
(2) Functional testing and bug repair. Use the given front-end and back-end source codes to formulate testing strategies, design test cases, and complete specified functional tests; record bugs that occur during testing, analyze and repair bugs; and write system test reports based on test report templates.
(3) API interface testing. Use the JMeter tool to perform coding standard testing on the back-end RESTful API interface and output an API interface test report.
(3) Module duration and points
Table 1 List of module names, duration and scores
| module |
main content |
Match duration |
Points |
|
| Module one |
System Requirements Analysis |
Carry out system planning, design and prototype design according to the given demand description. |
6 hours |
25 points |
| Module 2 |
Software system development |
Design the system database and complete the development of front-end pages, back-end business and interactive functions based on the designated development framework. |
55 points |
|
| Module three |
System deployment test |
Carry out system deployment, functional testing and bug repair for a given project, use testing tools to conduct API interface testing, and complete system testing documentation. |
20 points |
|
4. Competition method
(1) Competition format
This competition is an offline competition. All participating teams will complete the competition module in one day based on the given project module on site, and will cooperate with each other within a total of 6 hours to complete the competition module in the form of group cooperation.
(2) Team formation method
This event adopts the team competition method. Each school is limited to 2 teams, and each team is composed of 3 full-time students (those who have won the first prize in this competition in the previous National Vocational College Skills Competition can no longer participate). Participants are not allowed to cross schools. Form a team; each team is limited to 2 instructors, who must be full-time and part-time teachers from the school. During the competition, instructors are not allowed to enter the venue for on-site guidance; contestants and instructors cannot be replaced at will after their registration is confirmed.
- Competition process
(1) Competition flow chart
The competition process of this event is shown in Figure 1.
Figure 1 Schematic diagram of competition process
(2) Competition schedule
Table 2 List of competition times
| date |
time |
matter |
| Reporting day |
Before 15:00 |
Registration of each participating team |
| 15:00—15:30 |
Kick-off ceremony |
|
| 15:30—16:30 |
Team leaders meeting, referee meeting |
|
| 16:30—17:00 |
Teams are familiar with the competition venue |
|
| 17:00—18:00 |
The chief referee conducts a pre-match inspection and closes the arena |
|
| competition day |
07:20—07:30 |
Field inspection |
| 07:30—07:55 |
One-time encryption: participating teams draw entry numbers |
|
| 07:55—08:20 |
Secondary encryption: participating teams draw competition numbers |
|
| 08:20—08:30 |
The participating teams enter the competition position and conduct pre-match equipment and material inspections |
|
| 08:30—11:30 |
player competition |
|
| 11:30—12:30 |
Lunch and break on the field |
|
| 12:30—15:30 |
Players continue to play |
|
| 15:30—17:30 |
Complaint acceptance |
|
| 15:30—22:00 |
Score verification and decryption |
- Contest rules
1. Qualifications of participating teams and contestants. Contestants must be current students at the same school. Contestants in the higher vocational group must be full-time junior college students in ordinary colleges and universities. Full-time students in secondary vocational colleges in undergraduate colleges can register to participate in the higher vocational group competition. Students in five-year higher vocational schools Those who register for the competition, fourth and fifth grade students can participate in the higher vocational competition. The age of contestants in the higher vocational group is generally not more than 25 years old, and the cut-off time for age calculation is May 1, 2023. Each participating team can be assigned 2 instructors, and the instructors must be full-time and part-time teachers in the school.
2. Competition positions are determined by drawing lots. In principle, contestants are not allowed to leave the competition venue during the competition.
3. The hardware, software and auxiliary tools required for the competition are provided uniformly. Teams are not allowed to use any of their own devices with storage and communication functions, such as hard drives, CDs, USB flash drives, mobile phones, Walkmans, smart watches, PDAs, etc.
4. Contestants must receive the competition task 10 minutes before the competition and enter the competition position. Relevant operations can only be carried out after the game officially starts.
5. During the competition, if the contestants have any questions, they should raise their hands and the on-site referee should answer the questions in a timely manner as required. If there is an equipment or software failure, contestants should raise their hands to indicate it, and on-site referees, technical personnel, etc. should resolve it in a timely manner. If it is true that the operation cannot continue due to computer software or hardware failure, the backup equipment will be activated after confirmation by the chief referee.
6. When the competition time is over, all players should stand up and end the operation. Only after the staff have checked and inventoried all documents can they leave the venue. No information is allowed to be taken away when leaving the venue.
7. Competition referees should strictly abide by the rules and regulations of the competition to ensure that the competition is fair, just and open. Starting from 8:00 on the day of the competition, event referees should hand over all communication equipment to the event executive committee for safekeeping, and arrange for event referees to rest or work in designated areas until the end of event score evaluation.
8. After the competition, the scoring referee can enter the venue to judge the results. After the final competition results are reviewed and confirmed by the chief referee, they will be reported to the Department of Education as required.
9. The original materials and final results of each competition link in the competition, such as the original materials and final scores, will be sealed and kept in a bag after being signed by the chief referee. They will be sealed by the school hosting the competition and assigned to a dedicated person for safekeeping.
- specifications
The technical specifications, professional knowledge and technical skills of this competition include: education and teaching requirements, industry, and vocational technical standards for software technology-related majors, as well as the revised teaching standards and specifications for software technology-related professional talent training based on the higher vocational catalog, which will be updated in due course Locally revise the technical specifications followed by this event.
Table 3 List of teaching standards
| serial number |
standard unit |
Chinese standard name |
| 1 |
Ministry of Education |
Introduction to junior college majors in higher vocational education: 51 Electronics and Information Category - 5102 Computer Category - 510201 Computer Application Technology |
| Ministry of Education |
Introduction to junior college majors in higher vocational education: 51 Electronics and Information Category - 5102 Computer Category - 510203 Software Technology |
(2) Industry standards
Table 4 List of industry standards
| serial number |
Standard |
Chinese standard name |
| 1 |
Information Technology Industry Career Skills Part 3: Software Development |
|
| 2 |
||
| 3 |
Computer process control software development procedures |
|
| 4 |
Software product classification |
|
| 5 |
Software engineering software development cost measurement specification |
|
| 6 |
Design Guidelines for Software Security in Programmable Logic Devices |
|
| 7 |
||
| 8 |
GB/T 28174.1-2011 |
Unified Modeling Language (UML) Part 1: Infrastructure |
| 9 |
Information Technology Software Engineering Terminology |
|
| 10 |
||
| 11 |
GB/T 38634.1-2020 |
Systems and Software Engineering Software Testing Part 1: Concepts and Definitions |
| 12 |
Systems and Software Engineering Verification and Validation |
|
| 13 |
Requirements for designers and developers of systems and software engineering user documentation |
|
| 14 |
Systems and Software Engineering Life Cycle Management Process Description Guide |
|
| 15 |
||
| 16 |
||
| 17 |
Systems and Software Engineering System Life Cycle Processes |
|
| 18 |
T/CESA 1154—2021 |
Information Technology Service Practitioner Competency Evaluation Guide Design and Development Services |
| 19 |
T/CESA 1155—2021 |
Competency Evaluation Guide for Information Technology Service Practitioners Integrated Implementation Services |
| 20 |
T/CESA 1156—2021 |
Competency Evaluation Guide for Information Technology Service Practitioners Operation and Maintenance Services |
(3) Professional knowledge and technical skills
Table 5 List of professional knowledge and technical skills
| serial number |
Classification |
Specific requirements |
| 1 |
demand analysis |
Master the methods and techniques of demand analysis, be able to write demand specifications according to user needs, and conduct demand analysis and design. |
| 2 |
software design |
Understand the principles and methods of software design, and be able to design software according to requirements specifications, including architecture design, module design, interface design, etc. |
| 3 |
Coding implementation |
Master the techniques and specifications of coding implementation, and be able to implement coding according to software design, including code writing, debugging, testing, etc. |
| 4 |
software test |
Understand software testing methods and techniques, and be able to conduct software testing, including unit testing, integration testing, system testing, etc., to ensure software quality. |
| 5 |
Software maintenance |
Understand software maintenance methods and techniques, and be able to maintain and upgrade software, including bug fixes, function expansion, etc. |
| 6 |
project management |
Understand project management methods and tools, and be able to carry out project plan formulation, progress control, risk management, etc. to ensure that projects are completed on time and with quality. |
| 7 |
Teamwork |
Have good teamwork skills and be able to communicate and collaborate effectively with team members to complete software development tasks together. |
| 8 |
learning ability |
Have the ability to quickly learn new knowledge and technologies, be able to continuously learn and master new technologies and tools, and improve their professional quality and competitiveness. |
- technical environment
(1) Competition environment
The competition venue includes the contestant competition area, display platform area, referee area, technical support area, inspection area, and service area.
1. Competition area for contestants. Each competition station must be marked with an eye-catching station number. The distance between the stations must be greater than 1.5m. The area of each station must be greater than 8㎡. Each station must have an independent power unit (with a leakage protection switch installed) to ensure that the participating teams do not interfere with each other. The competition venue requires video surveillance throughout the competition process without blind spots, and the surveillance video should be kept for 3 months. Environmental standards require ensuring that the venue has good lighting (more than 500lux), good lighting and ventilation, stable water and electricity, emergency backup power supply, and sufficient dry powder fire-extinguishing equipment.
2. Display platform area. An isolation zone separate from the competition venue is needed for team leaders, instructors and staff to rest and carry out other related activities.
3. Referee area. A place for referees to rest and work. There is a total of 1 server, 20 computers, 20 sets of tables and chairs, 1 A4 laser printer, water dispenser, paper cups, and several stationery supplies.
4. Technical support area. Workplace for technical support personnel.
5. Inspection area. Competitor inspection area.
6. Service area. Equipped with commonly used medicines, disinfectants and other first aid supplies, provide medical and other service guarantees, and isolate them with isolation tapes.
Figure 2 Competition venue network layout diagram
（二）硬件环境与配置
表6 竞赛硬件环境及配置一览表
| 序号 |
设备名称 |
配置要求 |
数量 |
| 1 |
计算机 |
|
4台/每队 （含3台开发机、1台服务器） |
| 2 |
路由器 |
|
1台/每队 |
| 3 |
竞赛服务器 |
|
1台 |
| 4 |
交换机 |
|
3台 |
（三）软件环境与版本
表7 竞赛软件开发环境及版本一览表
| 类别 |
名称 |
版本 |
单位 |
数量 |
| 操作系统 |
Windows10 |
Windows 10专业版 （64位） |
套 |
1 |
| 开发工具 |
Adobe Photoshop |
Version 2019 |
套 |
1 |
| Axure RP |
Version 9.0 |
套 |
1 |
|
| IntelliJ IDEA |
Version 2023.1 |
套 |
1 |
|
| Visual Studio Code |
Version 1.77及以上 |
套 |
1 |
|
| HBuilder X |
Version 3.1.22 |
套 |
1 |
|
| 前端开发 |
clipboard |
Version 2.0.6及以上 |
套 |
1 |
| core-js |
Version 3.8.1及以上 |
套 |
1 |
|
| file-saver |
Version 2.0.4及以上 |
套 |
1 |
|
| js-cookie |
Version 2.2.1及以上 |
套 |
1 |
|
| jsencrypt |
Version 3.0.0-rc.1及以上 |
套 |
1 |
|
| screenfull |
Version 5.0.2及以上 |
套 |
1 |
|
| axios |
Version 0.21.0及以上 |
套 |
1 |
|
| vue-router |
Version 3.4.9及以上 |
套 |
1 |
|
| vuex |
Version 3.6.0及以上 |
套 |
1 |
|
| connect |
Version 3.6.6及以上 |
套 |
1 |
|
| sass |
Version 1.32.0及以上 |
套 |
1 |
|
| Node.js |
Version 14.18及以上 |
套 |
1 |
|
| Vue |
Version 2.6.12及以上 |
套 |
1 |
|
| Element-ui |
Version 2.14.1及以上 |
套 |
1 |
|
| Echarts |
Version 5.3.3及以上 |
套 |
1 |
|
| vue-element-admin |
Version 4.4.0及以上 |
套 |
1 |
|
| 后端开发 |
SpringBoot |
Version 2.2.12及以上 |
套 |
1 |
| Tomcat （内嵌至Spring） |
Version 9 |
套 |
1 |
|
| Mybatis |
Version 3及以上 |
套 |
1 |
|
| Spring Security |
Version 5.2.X及以上 |
套 |
1 |
|
| JDK |
Version 8及以上 |
套 |
1 |
|
| JJwt |
Version 0.9.1及以上 |
套 |
1 |
|
| 数据库及管理工具 |
MySQL |
Version 8.0 |
套 |
1 |
| Redis |
Version 3.0及以上 |
套 |
1 |
|
| Navicat Premium |
Version 11.0及以上 |
套 |
1 |
|
| MySQL Workbench |
Version 8.0及以上 |
套 |
1 |
|
| 浏览器 |
Firefox |
Version 112及以上 |
套 |
1 |
| Chrome |
Version 113及以上 |
套 |
1 |
|
| 其他辅助软件 |
WPS |
Version 11.1.0 |
套 |
1 |
| GitStack |
Version 2.3.11 |
套 |
1 |
|
| Postman |
Version 10.5 |
套 |
1 |
|
| Office Visio |
Version 2021 |
套 |
1 |
|
| WinRAR |
Version 6.0.2 |
套 |
1 |
|
| phpstudy |
Version 8.0 |
套 |
1 |
|
| JMeter |
Version 5.5 |
套 |
1 |
|
| Nginx |
Version 1.5.1及以上 |
套 |
1 |
- 赛项安全
（一）组织机构
1.成立由赛项执委会主任为组长的赛项安全保障小组，成员包括承办院校及合作企业等相关人员。
2.与地方相关部门建立协调机制，制定应急预案，及时处置突发事件，保证比赛安全进行。
（二）比赛环境安全管理要求
1.保证各通道口畅通，并配备专门人员看守，控制人员流量和赛场观众饱和度，张贴安全指示标识。
2.赛场周围设立警戒线，无关人员不得入内。所有参赛人员必须凭赛项执委会印发的有效证件进入场地。
3.配备必要的医护人员和医疗药品，有应急抢救预案。
4.设置突发事件应急疏散示意图。如遇特殊情况，服从大赛统一指挥。
（三）生活条件保障
1.原则上由执委会统一安排参赛队食宿。承办院校须尊重少数民族参赛人员的宗教信仰及文化习俗，安排好少数民族参赛选手和教师的饮食起居。
2.竞赛期间安排的住宿地应具有经营许可资质。以学校宿舍作为住宿地的，大赛期间的住宿、饮食安全等由执委会和提供宿舍的学校共同负责。
（四）组队责任
1.各学校组织代表队时，须安排为参赛选手购买大赛期间的人身意外伤害保险。
2.各学校代表队组成后，须制定相关管理制度，并对所有选手、指导教师进行安全教育，实现与赛场安全管理的对接。
（五）应急处理
比赛期间发生意外事故时，发现者应在第一时间上报，同时采取措施，避免事态扩大。赛项执委会应立即启动预案予以解决并向赛区执委会报告。出现重大安全问题的赛项可以停赛，是否停赛由赛区组委会决定。事后，赛区执委会应向大赛执委会报告详细情况。
- 成绩评定
（一）评分原则
1.结果评分原则
评分裁判对参赛选手提交的竞赛成果物，依据赛项评价标准进行评分。
2.独立评分原则
根据裁判分工，负责相同模块评分工作的不同裁判采取随机抽签独立评分，确保成绩评定严谨、客观、准确。
（1）裁判进行随机抽签分组，杜绝主观意愿组队，各自完全独立评分，裁判员间互不干涉。
（2）裁判统一安排在一间工作室评分，比赛监督人员可随机监督。
3.错误不传递原则
各环节分别计算得分，错误不传递，按规定比例计入总分。
4.抽查复核原则
（1）为保障成绩评判的准确性，监督组对赛项总成绩排名前30%的所有参赛队伍（选手）的成绩进行复核；对其余成绩进行抽检复核，抽检覆盖率不得低于15%。
（2）监督组需将复检中发现的错误以书面方式及时告知裁判长，由裁判长更正成绩并签字确认。复核、抽检错误率超过5%的，则认定为非小概率事件，裁判组需对所有成绩进行复核。
（二）评分标准
本次竞赛评分采用裁判分工协作，按子模块设置若干个评分小组，2名裁判为一个小组，各自给出该子模块的分值，2名裁判取平均值作为该项子模块得分；若2名裁判评分偏差大于30%，需要在裁判长监督下重新评分。
表11-1 评分样例一览表
| 模块 |
任务 |
评分项编号 |
评分项描述 |
分值 |
评分 |
| 模块一：系统需求分析 |
任务1：固定碳排放 |
1-1-1 |
原型绘制： 进入双碳管理系统主界面，点击左侧智造双碳—双碳配置内的固定碳排放标签，进入固定碳排放页面，实现固定碳排放管理数据列表显示，数据列表显示内容应包括：编号、能耗项、项目类型、时间类型、能耗数、预警阙值、【修改】和【删除】按钮。 |
0.4 |
|
| 1-1-2 |
原型绘制： 点击【修改】按钮后弹出【修改固定碳排放】对话框，对话框中可修改内容包括：能耗项（*必填项）、项目类型、时间类型、能耗数、预警阙值、备注，修改完成后点击【确定】按钮可保存修改内容并刷新数据列表，若点击【取消】按钮可关闭对话框。点击【删除】按钮可删除项目信息数据并提示“删除成功”字样。 |
0.5 |
|||
| 1-1-3 |
原型绘制： 数据列表上方搜索框中输入能耗项、项目类型、时间类型后点击【搜索】按钮，可实现按搜索条件模糊查询的功能并刷新列表数据，若点击【重置】按钮可清空输入的查询条件。 |
0.4 |
|||
| 1-1-4 |
原型绘制： 数据列表上方显示【新建】按钮，点击【新建】按钮后，在弹出的【添加固定碳排放】对话框中输入能耗项（*必填项）、项目类型、时间类型、能耗数、预警阙值、备注后点击【确定】按钮可新建固定碳排放数据并提示“新建成功”字样，若点击【取消】按钮可关闭对话框。 |
0.5 |
|||
| 1-1-5 |
需求说明：概要简述。 |
0.2 |
|||
| 1-1-6 |
需求说明：流程图/活动图。 |
0.2 |
|||
| 1-1-7 |
需求说明：用例图。 |
0.2 |
|||
| 1-1-8 |
需求说明：类图。 |
0.2 |
|||
| 1-1-9 |
需求说明：时序图。 |
0.2 |
|||
| 1-1-10 |
需求说明：E-R图。 |
0.2 |
（三）评分方式
1.竞赛满分为100分。
2.选手比赛的评分成绩=模块一得分+模块二得分+模块三得分。
3.本竞赛参与赛项成绩管理的组织机构包括裁判组、监督仲裁组。
4.竞赛对参赛队伍提交的成果物采取分步得分、累计总分的计分方式。各子模块分别计算得分，错误不传递，按规定比例计入团队总分。
5.监督组在复检中发现错误，需以书面形式及时告知裁判长，由裁判长更正成绩并签字确认。如复核、抽检错误率超过5%，裁判组需对所有成绩进行复核。
6.在竞赛过程中，参赛选手如有不服从裁判裁决、扰乱赛场秩序、舞弊等行为的，由裁判长按照规定扣减相应分数，情节严重的将取消比赛资格，比赛成绩计0分。
7.赛项成绩解密审核无误后，经裁判长签字后，向全体参赛队进行公布，再将竞赛成绩上传到竞赛平台。比赛成绩以省教育厅最终公布结果为准。
- 奖项设置
本赛项奖项设团体奖。设奖比例是以赛项实际参赛队总数为基数，一、二、三等奖获奖比例分别为 10%、20%、30%（小数点后四舍五入）。
如出现参赛队总分相同情况，按照模块分值权重顺序的得分高低排序，即总成绩相同的情况下比较模块二的成绩，模块二成绩高的排名优先；如果模块二成绩也相同，则按模块一、模块三的成绩进行排名，以此类推完成相同成绩的排序。如果所有模块分值相同，则查看文档撰写规范分值进行排序。
- 赛项预案
1.竞赛软硬件环境和电脑在比赛前进行压力测试，验证功能正常。
2.赛场提供占总参赛队伍10%的备用工位，占总参赛队伍10%的备用服务器。
4.竞赛过程中出现设备掉电、故障等意外时，现场裁判需及时确认情况，安排赛场技术支持人员进行处理，现场裁判登记详细情况，填写补时登记表，报裁判长批准后，可安排延长补足相应选手的比赛时间。
5.本赛项竞赛过程中各个竞赛工位为独立供电且各个参赛队均采用独立网络进行竞赛，如在竞赛时某工位参赛队出现意外境况不会影响其它工位正常比赛，不会由此对成绩产生影响。
6.比赛期间发生大规模意外事故和安全问题（如发病、中毒等），发现者应第一时间报告赛项执委会，赛项执委会应采取终止比赛、快速疏散人群等措施避免事态扩大，并第一时间报告赛区执委会。赛项出现重大安全问题可以停赛，是否停赛由赛区执委会决定。事后，赛区执委会应向大赛执委会报告详细情况。
7.因参赛队伍原因形成事故隐患或造成事故的，视情节警告或取消其获奖资格；赛事工作人员违规的，按照相应的制度追究责任。
- 竞赛须知
（一）参赛队须知
1.在赛事期间，参赛队成员不得私自接触裁判，凡发现有弄虚作假者，取消其参赛资格，成绩无效。
2.所有参赛人员须按照赛项规程要求按照完成赛项评价工作。
3.参赛队认为存在不符合竞赛规定的设备、工具、软件，有失公正的评判、奖励，以及工作人员的违规行为等情况时，须在该赛项竞赛结束后2小时内，向赛项仲裁组提交书面申诉材料。各参赛队应服从和执行申诉的最终仲裁结果。
4.各学校组织代表队时，须安排为参赛选手购买大赛期间的人身意外伤害保险。
（二）指导教师须知
1.各参赛代表队要发扬良好道德风尚，听从指挥，服从裁判，不弄虚作假。如发现弄虚作假者，取消参赛资格，名次无效。
2.各代表队领队要坚决执行竞赛的各项规定，加强对参赛人员的管理，做好赛前准备工作，督促选手带好证件等竞赛相关材料。
3.竞赛过程中，除参加当场次竞赛的选手、执行裁判员、现场工作人员和经批准的人员外，领队、指导教师及其他人员一律不得进入竞赛现场。
4.参赛代表队若对竞赛过程有异议，在规定的时间内由领队向赛项仲裁工作组提出书面报告。
5.对申诉的仲裁结果，领队要带头服从和执行，并做好选手工作。参赛选手不得因申诉或对处理意见不服而停止竞赛，否则以弃权处理。
6.指导老师应及时查看大赛专用网页有关赛项的通知和内容，认真研究和掌握本赛项竞赛的规程、技术规范和赛场要求，指导选手做好赛前的一切技术准备和竞赛准备。
（三）参赛选手须知
1.参赛选手应严格遵守赛场规章、操作规程和工艺准则，保证人身及设备安全，接受裁判员的监督和警示，文明竞赛。
2.参赛选手应按照规定时间抵达赛场，凭身份证、学生证，以及统一发放的参赛证，完成入场检录、抽签确定竞赛工位号，不得迟到早退。
3.参赛选手进入赛场前，须将身份证、学生证、参赛证交由检录人员统一保管，不得带入场内。
4.参赛选手凭竞赛工位号进入赛场，不允许携带任何电子设备及其他资料、用品。
5.参赛选手应在规定的时间段进入赛场，认真核对竞赛工位号，在指定位置就座。
6.参赛选手入场后，迅速确认竞赛设备状况，填写相关确认文件，并由参赛队长确认签字（竞赛工位号）。
7.参赛选手在收到开赛信号前不得启动操作。在竞赛过程中，确因计算机软件或硬件故障，致使操作无法继续的，经裁判长确认，予以启用备用计算机。
8. Contestants should complete the contents of the task book within the time specified in the competition, and save work records as required in a timely manner to prevent data loss caused by operating system abnormalities and other equipment abnormalities. Contestants are solely responsible for data loss due to various reasons.
9. The answer sheet submitted by the participating team shall be marked as required, and information such as place name, school name, name, participation certificate number, etc. shall not appear, otherwise the competition results will be cancelled.
10. During the competition, if the competition cannot be carried out due to serious operating errors or safety accidents (for example, a short circuit due to operational reasons, resulting in a power outage in the stadium, causing the equipment to not work properly), the on-site referee has the right to terminate the game of the team.
11. Players must work continuously during each competition, and food, drinking water, etc. will be provided by the venue. During each game, players’ resting, eating or toileting time will be included in the game time.
12. If there is an equipment failure caused by non-human factors during the game, after confirmation by the referee, you can apply to the chief referee to make up for the time to troubleshoot the fault.
13. Contestants are not allowed to end the competition early for various reasons. If you really need to leave the field due to force majeure, you must raise your hand to the on-site referee. You can only leave after obtaining the referee's permission and completing the record.
14. Each competition team shall submit competition results in accordance with the requirements of the competition and the competition questions. It is prohibited to make any marks on the competition results that are not related to the competition. After the competition operation is completed, the participating teams must confirm the successful submission of the documents required by the competition. The referee will mark the specified position of the competition results and sign and confirm with the participating teams.
15. When the competition time is over, all players should stand up and end the operation. Players may leave the venue after being inspected by staff. No materials or equipment may be taken away when leaving the venue.
16. During the competition, contestants are not allowed to accept interviews related to the content of the competition from other units and individuals without the approval of the Executive Committee. Contestants are not allowed to publish competition-related information privately.
(4) Instructions for staff
1. The competition venue staff are uniformly hired by the competition executive committee and divided into tasks. When entering the competition site, they must wear a hangtag provided by the organizing committee.
2. The competition venue staff must obey the management of the competition executive committee, strictly implement the competition rules formulated by the competition executive committee, implement the work arrangements of the competition executive committee, actively maintain the order of the competition venue, stick to their posts, and serve the competition venue. Provide orderly service.
3. When entering the venue, venue staff are not allowed to bring any communication tools or items unrelated to the competition.
4. When a team enters the venue, on-site referees and venue staff should review the items brought into the venue by the contestants in accordance with regulations. If any items that are not allowed to be brought into the venue are found, they should be handed over to the team's accompanying personnel for safekeeping. The venue does not provide storage services.
5. The venue staff will not answer any technical questions raised by the players during the competition. If there are any disputes, they should report them to the chief referee in a timely manner.
- Grievances and Arbitration
1. Each participating team shall be responsible for any instruments, equipment, tooling, materials, objects, computer software and hardware, competition tools and supplies that do not comply with the regulations of the competition and competition events, competition referees, competition venue management, competition results, as well as inappropriate behavior of staff. Standardize behavior, etc., and appeal to the competition arbitration panel.
2. The subject of the appeal is the team leader.
3. When an appeal is initiated, the participating team shall submit a written report signed and agreed by the team's players to the event arbitration panel. The report should provide a full and factual description of the phenomenon, time of occurrence, persons involved, basis for the complaint, etc. of the complaint incident. Unwritten appeals will not be accepted.
4. Appeals should be submitted within no more than 2 hours after the end of the event. Applications exceeding the time limit will not be accepted.
5. The event arbitration working group will organize a review within 2 hours after receiving the appeal report, and promptly notify the complaining party of the review results in writing. If the complaining party still has objections to the reconsideration result, the provincial (municipal) team leader can appeal to the competition area arbitration committee. The arbitration results of the competition area arbitration committee are final.
6. The complaining party shall not refuse to accept the arbitration result for any reason; shall not take excessive actions to disrupt the order of the competition venue for any reason; the arbitration result shall be signed by the complainant and cannot be collected on behalf of the complainant; if the complainant leaves at the agreed time and place, it shall be deemed to have given up the appeal on its own initiative. .
7. The complaining party may give up the appeal at any time.
- Competition observation
This competition will design an observation area and use a large screen to broadcast the live action in real time. The competition environment is designed based on competition needs and professional characteristics, and some venues can be safely opened without interference to the competition. On-site observation should abide by the following disciplines:
1. Observers must be approved by the competition executive committee, wear observation certificates, and go to the scene to watch the competition along the designated route and in the designated area under the leadership of the staff;
2. Watch the game in a civilized manner, do not make loud noises, obey the instructions of the stadium staff, and eliminate all kinds of uncivilized behaviors that violate the order of the stadium;
3. Observers may not communicate with contestants or referees, pass on information, collect on-site competition data, or affect the normal progress of the competition;
4. Staff have the right to remind and stop any uncivilized behavior that violates the order of the stadium.