Design and implementation of emergency rescue command and management system based on big data
Summary
The emergency rescue command is the guidance center of the emergency rescue holding. It is responsible for organizing and implementing disease control and prevention plans and on-site handling of public health emergencies. Therefore, it builds a modern, fast and effective emergency response system to minimize the risk of emergencies. The harm of public health events to the public is a pressing concern for emergency rescue command, which requires the government to gradually improve its ability to respond to emergencies in an efficient and reasonable manner under the premise of limited supplies and information.
This article discusses an emergency rescue command emergency system based on JAVA. This system only requires users to access and operate the system through a computer browser. In order to ensure the accuracy and safe data storage of system data, the system uses SqlServer database for system data storage services. Based on in-depth research on emergency rescue work and interviews with emergency rescue workers, the business needs of the overall system are analyzed in detail. The business requirements involved in emergency rescue command are sorted out. The main operation modules covered are: personnel information module, login log module, emergency event module, event search module, and data statistics module. The system design is strictly implemented in accordance with the design standards of software engineering, and system testing is conducted to correct errors in a timely manner to ensure data accuracy. In order to ensure that the emergency rescue command emergency system can operate normally.
Keywords: emergency rescue; command and management; JAVA; SqlServer
Abstract
Emergency rescue command is the guiding center of emergency rescue holding， responsible for the organization and implementation of disease control and prevention plans， responsible for the on-site disposal of public health emergencies， therefore， it is urgent to build a modern， efficient and effective emergency response system to deal with emergencies and minimize the harm of public health events to the public. Under the premise of limited materials and information events， the government's ability to efficiently and reasonably respond to emergency rescue events needs to be gradually improved.
This paper discusses the emergency rescue command system based on JAVA. The system can be accessed and operated by users only through computer browser. In order to ensure the accuracy and security of system data storage， the system uses SqlServer database for system data storage services. Based on the in-depth investigation of the emergency rescue work and the interview survey of the emergency rescue workers， the business needs of the whole system are analyzed in detail. The business requirements involved in emergency rescue command are sorted out， mainly covering five modules: personnel information module， login log module， emergency event module， event search module and data statistics module. The system was designed in strict accordance with the design standards of software engineering， and the system was tested to correct errors in time to ensure the accuracy of data. In order to ensure that the emergency rescue command of the emergency system can operate normally.
Keywords: Emergencyrescue; Commandandmanagement; JAVA; SqlServer
Table of contents
5System test................................................ ............ 32
in conclusion................................................. ............. 36
references................................................ ............ 37
1Introduction _
Since public health emergencies occur suddenly and the situation is relatively urgent, the primary purpose of handling them is to be "quick, accurate and complete".
Demand control measures to be taken quickly. Correctly propose on-site work and take correct measures. Emergencies cannot be limited to a certain professional aspect, and issues such as controlling the situation's expansion and related laws and regulations must be considered.
In recent years, emergencies have occurred frequently in our country, and the losses of life and property caused have become even more painful. The Chinese government has paid considerable attention to emergency management for a long time and established a joint scientific research and teaching group on emergency management. Economic development drives social progress, but it gradually fails to match the construction of informatization. The government's ability to respond to emergencies in an efficient and reasonable manner under the premise of limited supplies and information needs to be gradually improved. It is imperative to apply modern network information technology to design and implement an emergency command system for emergency rescue incidents.
1.1.1 Domestic research status
For a person, life and health have the most fundamental meaning and value, and are the basis of human existence. Since humans got rid of the simple survival instinct of animals and entered civilized society, the pursuit of health and longevity has become the highest ideology and ultimate goal, and has developed with the continuous improvement of human material living conditions. Between life and death, any material possessions lose their meaning. Countless families who "fall into poverty or return to poverty due to illness" interpret this basic rule every day.
my country's economy and society have developed rapidly and sustainably, social and personal wealth has accumulated, people's material living standards have continued to improve, and the basic living costs of food, housing, and transportation have dropped significantly. The "Engel coefficient" of both urban and rural residents is lower than 40%. The main population's food and clothing problem has been solved. The society has entered a relatively wealthy stage, and people are increasingly aware of health. At the same time, the country’s new round of medical and health system reform, increased government health investment, and the development and popularization of new medical substances, equipment and technologies have greatly stimulated demand for medical treatment and promoted medical treatment in terms of medical expenses and medical and health service supply. Development in the health sector. In 2015, my country's total health expenditure reached 6% of GDP and maintained an annual growth trend of 10%. Per capita health expenditure increased from 1,490.1 yuan in 2010 to 2,951.8 yuan, and personal health expenditure has been lower than 30% of the total health expenditure. %. The increased willingness to seek medical treatment and the ability to pay have greatly stimulated medical treatment behavior. In 2016, the number of outpatient visits nationwide reached 7.7 billion, and the number of hospitalizations reached 200 million.
1.1.2 Current status of foreign research
Management information systems developed in the 1960s. Three aspects of management information system design management, sinnaxi and systems. In the system, events can be shared through the transmission of information. Management information system not only involves "theoretical research field", but also belongs to "practical field". Management information systems are constantly being updated and developed. It is information management that uses scientific information management theory, computer, network communication technology and information processing methods. After the introduction of management information system into scientific research management, the concept of scientific research management information system was formed. The scientific research management information system is required to realize the application, project management and online review of scientific research projects. A complete set of design solutions was proposed from various aspects such as application management of scientific research achievement projects, achievement management, and system control. The application of scientific research results management information system can enable a university to maintain advantages and continuous development in today's fierce competition, and can respond quickly and provide effective support to the rapidly changing environment.
1.2 Research purpose and significance
The construction of an emergency command system for emergency rescue incidents can help promptly coordinate the parties involved in the incident and fundamentally reduce the negative impact of the incident. Public health emergencies have a wide range of hazards and complex causes, seriously threatening people's lives and property. How to prevent public health emergencies and manage and control them after they occur is the focus of emergency rescue agencies The work content also poses severe challenges to its emergency response capabilities.
1.2.1 Purpose of emergency rescue command emergency system
The application of this system is expected to improve the handling efficiency of emergency rescue events and the utilization rate of events, and reduce the losses to people's lives and safety caused by emergencies. Today, with the rapid development of science and technology, how to use modern technology to continuously improve the emergency command system for emergency rescue incidents in the handling process so that it can better adapt to the needs of the government and users, improve the ability to respond to emergency rescue incidents, and allow limited incidents to be handled Maximizing utilization and ensuring the safety of people's lives and property to the greatest extent require our continuous exploration and research in the future.
1.2.2 The significance of emergency rescue command emergency system
By drawing lessons from the experience of dealing with the aftermath of emergencies, we can start from the following aspects: First, the government must strengthen its ability to handle crisis events, and it is necessary to set up staff and management agencies specialized in responding to emergencies. For example, if a public health coordinator is established, they are one of the earliest recipients and coordinators of information. They have received special training and have certain sensitivity and processing and response capabilities, so that they can better coordinate events and comprehensive coordination. Secondly, enhance people’s awareness of crisis prevention and cultivate citizens’ emergency response capabilities. Such as publishing emergency prevention publications, holding emergency expos and exhibitions, and providing relevant education to the public through websites, television and other media. Developed countries have accumulated rich experience in this regard. We can refer to their practices and carry out relevant activities to improve people's awareness of crisis prevention. Finally, through volunteer service organizations, the whole society can participate in the handling of emergencies. For example, we should establish an infectious disease supervision system that combines obligations and voluntariness, expand the coverage of emergency rescue supervision, ensure sufficient and smooth information, and better respond to public health emergencies.
1.3 Introduction to related technologies
The emergency system of this emergency rescue command adopts B/S architecture, the database uses SqlServer, and the server uses Tomcat7.0.
1.3.1SSM structural model
Spring is like a big factory that assembles beans in the entire project. In the configuration file, you can specify the use of specific parameters to call the constructor method of the entity class to instantiate the object.
SpringMVC intercepts user requests in the project, and its core Servlet, DispatcherServlet, assumes the responsibility of intermediary or front desk. SpringMVC is equivalent to struts in the SSH framework . Secondly, the MVC design pattern designs the system, giving the subsystem structure and class structure of the system, as well as the design of the table structure of the database . This framework is very powerful and can separate many structures that are convenient for the writing stage. Such separation can make customization and operation control more convenient.
Mybatis is an encapsulation of jdbc, which makes the underlying operations of the database transparent. The operations of mybatis are centered around a sqlSessionFactory instance. Mybatis has the following characteristics:
1. Easy to learn: It is small and simple. There are no third-party dependencies. The simplest installation only requires two jar files + configuring a few sql mapping files. It is easy to learn and use. Through the documentation and source code, you can fully grasp its design ideas and implementation.
2. Flexible: mybatis will not impose any impact on the existing design of the application or database. SQL is written in xml , which facilitates unified management and optimization. All needs for operating the database can be met through sql statements.
3. Decouple SQL from program code: By providing a DAO layer, business logic and data access logic are separated, making the system design clearer, easier to maintain, and easier to unit test. The separation of SQL and code improves maintainability.
4. Provide mapping tags to support ORM field relationship mapping between objects and databases.
5. Provide object relationship mapping tags to support the establishment and maintenance of object relationships.
6. Provide xml tags and support writing dynamic sql .
1.3.2Tomcat server
Tomcat server is a free open source web application server. It is a lightweight application server. It is commonly used in situations where the system and concurrent access users are not many. It is the first choice for developing and debugging JSP programs. Tomcat is actually an extension of the Apache server, but it runs independently when running. When configured correctly, Apache serves HTML pages, while Tomcat actually runs JSP pages and Servlets. The latest version of Tomcat is currently 9.0.41.
1.3.3SqlServer database
SqlServer is currently the most widely used database by Internet companies. The database is very important in application development. It directly determines the upper limit of the program. SqlServer is a relational database management system that can combine multiple data forms to process information and complete data management.
SqlServer is a database that reduces development costs. It is easy to develop, standardized, portable, and can be used simultaneously in the standard SQL language on multiple operating platforms. It has good compatibility with multiple languages (such as PERL, C, JAVA, etc.) and can be customized for use.
The above advantages of SqlServer prompted the selection of SqlServer as the database management tool in this development process. The graduation project I designed, researched and developed uses the very mainstream SqlServer database in the database. Precisely because it can use SQL language for database management, it is loved by most programmers.
1.3.4 Introduction to Java language
The language structure of Java language is close to that of C language. Compared with C++ technology, Java is easier to get started. On the other hand, the Java language has features such as classes, encapsulation, inheritance, and polymorphism that make it more convenient. In the network environment, Java has a security mechanism that can provide security protection for classes downloaded from the network. For example, installed classes are placed in separate namespaces rather than local classes, preventing malicious applets from replacing standard Java classes with their own versions. The Java language also has cross-platform features. There are many interfaces inside it, which are convenient for programmers to use. The reasons for using Java language to develop community management systems are as follows:
(1) Adaptability: The adaptability of the J2EE platform is unquestionable. It can minimize the impact of the operating system on the underlying code.
(2) Maintainability: It has rich internal interfaces and low maintenance costs, and the class inheritance and polymorphism features in Java can ensure that website development is easier.
(3) Security: Java has many internal security algorithms, which can ensure the smooth operation of the underlying layer and protect it from external attacks and intrusions.
1.4 Paper structure
This article first discusses the research background and purpose of the topic, combines the actual needs of the topic, develops according to the standard process of software design, and combines the actual functions of the design to complete the task of writing the paper. The paper mainly analyzes from the following chapters:
The first chapter introduces the current situation of the system at home and abroad, analyzes the current development situation of the system and the core issues faced by the requirements, explains the background and significance of the topic, and finally summarizes the chapter content of the full text.
Chapter 2 mainly introduces the demand analysis of the system, which is analyzed from three perspectives. The three analysis perspectives are the technical perspective, the economic perspective, and the operational perspective to analyze the feasibility of system development.
Chapter 3 mainly introduces the structure of the system and the functional design based on system requirements, which is divided into two aspects: system functional module design and system database structure design.
Chapter 4 focuses on the functions and specific implementation and operation procedures of each module in the system. Through the description of the modules, we can have a clearer understanding of the overall module design of the program.
- System testing, testing the system, finding problems and correcting errors.
2Requirements analysis
Public health emergencies have a wide range of hazards and complex causes, seriously threatening people's lives and property. How to prevent public health emergencies and manage and control them after they occur are key tasks for emergency rescue agencies, which also pose severe challenges to their emergency response capabilities. Based on this, the article analyzes the current situation of emergency response capabilities of emergency rescue agencies in public health emergencies, and puts forward tentative management countermeasures based on actual conditions, hoping to provide meaningful reference for improving the emergency response capabilities of emergency rescue agencies, and also provide guidance for my country's emergencies. Adding strength to the prevention and management of public health incidents.
The emergency system of this emergency rescue command adopts B/S architecture, the database uses SqlServer, the server uses Tomcat7.0, and the front-end page is implemented using JSP+JavaScript technology.
Through the analysis of the emergency work of emergency rescue command at home and abroad, and the study and research of relevant materials, we can understand the needs of emergency rescue and emergency work. For the emergency rescue command, we have the emergency designer information module, login log module, emergency event module, and event search module. , five modules of data statistics module.
2.1 Feasibility study
Feasibility analysis is a necessary step for system development, and it is very important. Feasibility analysis can know whether the system has development value and whether it is worth investing. It is explained from a technical perspective, a value perspective, and an operational perspective; the feasibility analysis link It is essential to be able to clearly understand whether the project is feasible and whether investment is necessary before project development; the specific content of this system analysis is as follows.
2.1.1 Economic feasibility
Economic feasibility mainly analyzes whether the system development cost, development profit and other aspects have investment value. When the investment is greater than the return, then there is no need to invest in the project. On the contrary, development investment can be made. Since this system development is my graduation project, the economic investment is relatively small. The main costs for R&D and operation include:
1. Hardware equipment: Computer. Since I have a computer for development, there is no hardware cost.
2. Software development: All kinds of software used in this system development, such as SqlServer, Tomcat7.0, etc., are all open source software and require no economic cost.
3. Personnel costs: I develop it independently and there is no cost.
2.1.2 Technical feasibility
Technical feasibility can be understood as whether the system is feasible at the technical level of development. For each module of the system, each framework design and other aspects need to be analyzed and compared. This design mainly uses JAVA technology for development, using SSM framework technology. The framework is divided into three layers, namely the control layer Controller, the business processing layer Service, and the persistence layer Dao. It can use multi-level architecture management and development. For each module The design and production have a certain degree of security; the database is mainly developed using SqlServer, which is characterized by good stability, large database storage capacity, and fast processing capabilities; the server uses Tomcat service, which can provide a stable operating platform , to ensure stable operation of the system.
2.1.3 Operational feasibility
As the name suggests, operational feasibility refers to whether the system operation process meets the requirements, whether the operation interface is beautiful and intuitive, whether the user can directly operate it, whether it affects work efficiency, etc.; it mainly measures the operational convenience and practicality of the system after it is online; currently, system development has It is a visual interface with simple module operations, suitable for users of all ages. It is simple and easy to understand, so the operational feasibility can be passed.
2.2 System functional requirements analysis
2.2.1 Establishment of demand model
Use the participant vocabulary to describe, as shown in Table 2-1.
Table 2-1 Participant Vocabulary List
| serial number |
vocabulary |
synonyms |
describe |
| 1 |
operator user |
operator |
Operators receive and process events, log management, event management and data statistics and other functions |
| 2 |
expert user |
expert |
Experts evaluate and summarize log records and incident reports |
| 3 |
Lead user |
lead |
Leaders evaluate and summarize log records and emergency incident reports |
2.2.2 System use case diagram
1. Operator role use case diagram
The operator role mainly completes operations such as personnel processing, log management, event management, and emergency events. The use case diagram of the operator role of the emergency system based on SSM for emergency rescue command is shown in Figure 2-2.
Figure 2-1 Operator use case diagram
2. Expert and leadership role management
The expert and leader roles mainly complete data statistics operations. The use case diagram of the emergency system expert and leader roles of SSM-based emergency rescue command is shown in Figure 2-2.
Figure 2-2 Expert and leader use case diagram
3. The system use case model diagram is shown in Figure 2-3.
Figure 2-3 System use case model diagram
2.2.3 System use case description
According to the division of authority functions of the use case design management system, this section will describe the main functional use case descriptions of the emergency rescue command system, as follows.
The use case description of emergency personnel information management of emergency rescue command based on SSM is shown in Table 2-2.
Table 2-2 Personnel information management use case description table
| use case entry |
output |
| Use case name |
Personnel information management |
| Major business players |
operator |
| other participants |
|
| describe |
The operator receives information, handles police supervision and event search operations |
| Preconditions |
Visitor information management module |
| Postcondition |
The operation of adding, deleting, modifying and checking personnel information management was successful. |
| Basic process |
The operator accesses the corresponding module to select additions, deletions, modifications, and checks, and the operation data is stored in the database in real time. |
| alternative process |
1. Access personnel information management module 2. Data access failed |
| Finish |
Data operation successful |
| Implementation constraints and instructions |
1. Add new information and enter complete data 2. To modify information, you need to obtain the selected row 3. Deleting information requires obtaining the selected row 4. Querying information requires obtaining data sources |
| Other event streams |
none |
The use case description of emergency system log management for SSM-based emergency rescue command is shown in Table 2-3.
Table 2-3 Log management use case description table
| use case entry |
output |
| Use case name |
Log management |
| Major business players |
operator |
| other participants |
|
| describe |
Operators maintain log events, log query, log submission, and log review.
|
| Preconditions |
Access login log module |
| Postcondition |
The operation of adding, deleting, modifying and checking the log management was successful. |
| Basic process |
The operator accesses the corresponding module to select additions, deletions, modifications, and checks, and the operation data is stored in the database in real time. |
| alternative process |
1. Access the login log module 2. Data access failed |
| Finish |
Log management data maintenance successful |
Continued Table 2-3 Log management use case description table
| use case entry |
output |
| Implementation constraints and instructions |
1. Add new information and enter complete data 2. To modify information, you need to obtain the selected row 3. Deleting information requires obtaining the selected row 4. Querying information requires obtaining data sources |
| Other event streams |
none |
The use case description of the emergency system event management function of SSM-based emergency rescue command is shown in Table 2-4.
Table 2-4 Event management use case description table
| use case entry |
output |
| Use case name |
incident management |
| Major business players |
operator |
| other participants |
|
| describe |
Operators perform event type maintenance, event search, data query statistics, event entry, and event configuration. |
| Preconditions |
Access event lookup module |
| Postcondition |
Incident Management Add, Delete, Modify and Check Operation Successfully |
| Basic process |
The user accesses the corresponding module and selects addition, deletion, modification and query operation data to be stored in the database in real time. |
| alternative process |
1. Access the event search module 2. Data access failed |
| Finish |
事件管理数据维护成功 |
| 实现约束和说明 |
1.录入数据要保证数据全面 2.更新操作需要获得选中行信息 3.删除操作需要获得选中行信息 4.所有操作要和数据库进行交互 |
| 其他事件流 |
无 |
基于SSM的应急救援指挥的应急系统应急事件管理功能用例描述如表2-5所示。
表2-5应急事件管理用例描述表
| 用例条目 |
输出 |
| 用例名称 |
应急事件管理 |
| 主要业务参与者 |
操作员 |
| 其他参与者 |
|
| 描述 |
操作员维护推送消息的基本信息 用户可以查看随送消息的相关信息 |
| 前置条件 |
访问推应急事件管理 |
| 后置条件 |
推送消息管理增删改查操作成功 |
| 基本流程 |
管理员访问对应模块选择增删改查操作数据实时入库 |
| 替代流程 |
1.访问推应急事件管理 2.数据访问失败 |
续表2-5应急事件管理用例描述表
| 用例条目 |
输出 |
| 结束 |
数据操作成功 |
| 实现约束和说明 |
1.新增信息录入完整数据 2.修改信息需要获取选中行 3.删除信息需要获取选中行 4.查询信息需要获取数据源 |
| 其他事件流 |
无 |
基于SSM的应急救援指挥的应急系统数据统计功能用例描述如表2-6所示。
表2-6数据统计用例描述表
| 用例条目 |
输出 |
| 用例名称 |
数据统计 |
| 主要业务参与者 |
操作员 |
| 其他参与者 |
专家、领导 |
| 描述 |
操作员进行日志记录生成、日志记录统计、日志记录查询，领导和专家可以对日志记录和应急事件报告进行评估和总结 |
| 前置条件 |
访问数据统计模块 |
| 后置条件 |
数据统计增删改查操作成功 |
| 基本流程 |
用户访问对应模块选择增删改查操作数据实时入库 |
| 替代流程 |
1.访问数据统计模块 2.数据访问失败 |
| 结束 |
数据统计数据维护成功 |
| 实现约束和说明 |
1.录入数据要保证数据全面 2.更新操作需要获得选中行信息 3.删除操作需要获得选中行信息 4.所有操作要和数据库进行交互 |
| 其他事件流 |
无 |
2.3非功能性需求
非功能性需求包括性能、可修改性、可用性、易用性、安全性、环境要求等，在最初的需求方案分析阶段很容易被忽略，而这些内容的考虑往往会影响到产品的实现，包括功能架构、操作方式、界面展现、后台处理方式、数据库设计方式等，所以到产品集成测试甚至回归测试时才考虑性能，往往就为时晚矣，可能就需要大量修改前期已完成的功能。
本文非功能性需求主要考虑了程序的可修改性，需要易于维护。易用性要考虑到用户的操作方便，可以提高用户的使用效率，减少工作量。
2.4本章小结
本章介绍的是应急救援指挥的应急系统的需求分析，从三方面可行性角度出发，分析系统是否值得开发，系统采用的具体技术环境等问题做出说明；系统流程图以及对系统的具体功能进行说明，最后进行用例图的分析。
3系统设计
随着计算机技术的发展，在科技日新月异的今天，如何利用现代科技将突发应急救援事件应急指挥系统在处置流程上不断的完善使其更加适应政府和用户的需求，提高应对突发应急救援事件的能力，让有限事件的利用率达到最大，最大程度的保障人民的生命财产的安全，需要我们在未来不断探索和研究。
3.1模块设计原则
基于基本功能的模块划分方法与其他方法相比比较简单，但也遵循了模块划分的基本原则。首先，尽量减少各模块之间的连接，以保证模块的正常运行。两者独立。每个模块都尽可能地发挥功能，并在逻辑上独立。避免在系统结构中造成混乱。模块接口尽量简单。功能调整，尽量减少对模块的影响和影响。系统按基本功能划分。该模块划分方法能使需求分类清晰划分，功能分解效果较好。
3.2软件结构设计
当系统开发工作通过需求分析阶段后，用户的需求得到了充分的明确，设计模型是说明用例实现的对象模型，是实施模型及其源代码的抽象。设计模型用作实施和测试活动多的基本输入。通常情况，在设计模型的时候基本上是按照都是按照对象的属性都合并在一个模型中。
3.2.1软件结构图
软件体系结构包括构成系统的设计元素的描述，它通常通过分层或时间间隔来说明架构的各种组件的组合关系。由一组组件及其相互作用组成的系统本身可以成为更大系统的组成元素。在结构设计方法中，软件结构图可以分为两种类型：转换软件结构图和事务软件结构图，如图3-1所示。
图3-1系统功能结构图
3.2.2 Division of module functions
After demand analysis, the emergency system functions of SSM-based emergency rescue command can be determined.
Generally divided into five modules: personnel information module, login log module, emergency event module, event search module, and data statistics module.
The specific business process is as follows:
(1) According to the level and emergency situation of the emergency rescue incident, lower-level emergency rescue incidents are handled by the personnel information module, and higher-level or more urgent incidents are handled by the emergency event module.
(2) When an emergency rescue event occurs, call the corresponding log based on the event information submitted by the personnel, and complete the corresponding information, including the configuration of the event and the designation of relevant responsible units.
(3) The relevant responsible units that have received the task will handle the emergency rescue incident according to the task content and actual situation.
(4) The relevant responsible units of the task shall provide timely feedback on the progress of the emergency incident during the handling process and track the situation of the emergency incident.
(5) Emergency incident-related units will reasonably adjust tasks based on incident feedback to ensure the accuracy and efficiency of emergency incidents.
(6) When the emergency rescue incident is under control or the emergency state is lifted, the case can be closed. After all the work on the emergency incident is completed, enter the data statistics module.
(7) Data statistics: Record the handling process and basic information of all major or particularly major incidents handled by the emergency rescue incident emergency management system to facilitate statistics and inquiries.
(8) Leaders and experts can evaluate and summarize log records and emergency incident reports in order to improve the management of log events and improve the efficiency of handling similar or identical emergency rescue incidents.
3.3 Database design
3.3.1 Database ER diagram
User entity and administrator entity are used to store administrator account information, which includes number, user name, password, and identification. The ER of the user entity is shown in Figure 3-3.
Figure 3-3 User entity diagram
|
Figure 3-4 Event type entity diagram
Event entity, which reflects event information, mainly has attributes such as number, event name, event type, and quantity. The ER of the event entity is shown in Figure 3-5.
Figure 3-5 Event entity diagram
Personnel entity is used to store personnel information, including number, name, phone number, reporting time, level, person, person number, etc. The ER diagram of the personnel entity is shown in Figure 3-6.
图3-6人员实体图
事件实体，楼房实体是用来存储事件的信息，包括编号、名称，时间，级别、状态、人员编号、人员人、人员电话、处警人、出警人电话。事件的E-R图如图3-7所示。
图3-7事件实体图
应急事件实体，应急事件实体是用来存储应急事件信息，包括编号、事件编号、事件名称、日志编号、日志名称、事件编号、事件名称、数量、状态等。应急事件实体的E-R如图3-8所示。
图3-8应急事件实体图
根据分析，系统中主要存在以下几个实体：用户、事件类型、事件、人员、事件查找、日志，它们之间的E-R图如图3-10所示。
图3-10数据库实体之间总E-R图
3.3.2数据表设计
系统主要由多个表组成，其表的设计主要根据系统功能来制定，其中包括用户表，事件类型表，事件信息表，日志表，人员表，事件表，处警表等构成，每个表的结构都是比较严谨的，需要根据功能的需求制定字段类型和长度。
用户表：主要是用户的基本信息。用户表作用是保存用的信息内容，当用户登陆时，用户输入信息，系统将用户输入的信息和数据库中的这个表作对比。如果账号密码相同，则用户登陆成功，可以进行下一步的操作，如表3-1所示。
表3-1用户表
| 字段 |
类型 |
长度 |
是否为空 |
主键 |
备注 |
| id |
int |
11 |
否 |
主键 |
编号 |
| username |
varchar |
255 |
否 |
用户名 |
|
| password |
varchar |
255 |
否 |
密码 |
|
| b1 |
varchar |
255 |
否 |
标识 |
事件类型表，记录事件类型的基本信息，这个表作为管理系统中最重要的一个表。事件类型的信息都被记录在这个表中，可以随时调取使用事件的类型信息。如表3-2所示。
表3-2事件类型表
| 字段 |
类型 |
长度 |
是否为空 |
主键 |
备注 |
| id |
int |
11 |
否 |
主键 |
编号 |
| name |
varchar |
255 |
否 |
事件类型名称 |
下图是事件信息表，主要包括了编号、事件名称、事件类型、数量等信息构成，添加、修改、删除、查询都操作这个表来完成的，如表3-3所示。
表3-3事件信息表
| 字段 |
类型 |
长度 |
是否为空 |
主键 |
备注 |
| id |
int |
11 |
否 |
主键 |
编号 |
| name |
varchar |
255 |
否 |
事件名称 |
|
| type |
varchar |
255 |
否 |
事件类型 |
|
| count |
int |
11 |
否 |
数量 |
日志信息表：这个表非常重要。这个表主要存储编号、名称、级别、日志内容、日志类型、状态、审核状态。日志信息表如表3-4所示。
表3-4日志信息表
| 字段 |
类型 |
长度 |
是否为空 |
主键 |
备注 |
| id |
int |
11 |
否 |
主键 |
编号 |
| name |
varchar |
255 |
否 |
名称 |
|
| level |
varchar |
255 |
否 |
级别 |
|
| content |
varchar |
255 |
否 |
日志内容 |
|
| type |
int |
11 |
否 |
日志类型 |
|
| state |
varchar |
255 |
否 |
状态 |
|
| shstate |
varchar |
255 |
否 |
审核状态 |
人员信息表，记录人员的信息、包括编号、名称、接报时间、级别、人员人、人员人电话等信息，如表3-5所示。
表3-5人员信息表
| 字段 |
类型 |
长度 |
是否为空 |
主键 |
备注 |
| id |
int |
11 |
否 |
主键 |
编号 |
| name |
varchar |
255 |
否 |
名称 |
|
| tel |
varchar |
20 |
否 |
人员电话 |
|
| jdtime |
datetime |
否 |
人员时间 |
||
| level |
varchar |
255 |
否 |
级别 |
|
| jjname |
varchar |
255 |
否 |
人员人 |
事件信息表，包括编号、名称、时间、级别、状态、人员编号、人员人、人员电话、处警人、处警人电话等，所有的事件信息都是读取的这个表来完成的。事件信息表，如表3-6所示。
表3-6事件信息表
| 字段 |
类型 |
长度 |
是否为空 |
主键 |
备注 |
| id |
int |
22 |
否 |
主键 |
编号 |
| name |
varchar |
20 |
否 |
名称 |
|
| createtime |
datetime |
否 |
时间 |
||
| level |
varchar |
20 |
否 |
级别 |
|
| state |
varchar |
30 |
否 |
状态 |
|
| jjid |
int |
11 |
否 |
人员编号 |
|
| jjname |
varchar |
20 |
否 |
人员人 |
|
| jjtel |
varchar |
20 |
否 |
人员电话 |
|
| cjname |
varchar |
20 |
否 |
处警人 |
|
| cjtel |
varchar |
20 |
否 |
处警人电话 |
3.4本章小结
基于SSM的应急救援指挥的应急系统论文第三章说明网站的概要设计和详细设计，建立多种设计模型，分别介绍网站的功能模块设计和数据库表的设计。
4系统详细设计与实现
4.1登录功能的实现
下图为登陆模块流程图，详细流程为最开始用户输入账号密码，系统判断是否正确，正确显示登陆成功错误或者用户和密码其一为空则需重新输入账号密码。如图4-1所示。
图4-1登录流程面
下图界面是应急指挥系统的登录管理界面，登录界面主要是用来审核登陆者身份，把控系统安全的首要关口。图中主要包括了用户账户信息，密码信息，如果输入的账号密码用户表里不存在，那么则提示登录失败，需重新输入正确的账号密码。如图4-2所示。
图4-2登录主界面
代码如下：
<%@pagelanguage="java"contentType="text/html;charset=UTF-8"
pageEncoding="UTF-8"%>
<%@taglibprefix="c"uri="http://java.sun.com/jsp/jstl/core"%>
<!DOCTYPEhtmlPUBLIC"-//W3C//DTDXHTML1.0Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<htmlxmlns="http://www.w3.org/1999/xhtml">
<head>
<metahttp-equiv="Content-Type"content="text/html;charset=utf-8"/>
<metahttp-equiv="X-UA-Compatible"content="IE=7"/>
<title>应急指挥</title>
<linkhref="css/main.css"rel="stylesheet"type="text/css"media="all"/>
<scriptsrc="js/jquery-1.4.2.min.js"type="text/javascript"></script>
应急事件查找是针对突发事件的频频发生，减少生命和财产损失的一项重要工作，在物资和信息事件有限的前提下，能够高效、合理的应对突发应急救援事件的能力。所以，应急救援指挥的应急系统应当能够为管理者和教师提供方便、快捷、安全、及时的查询方式以及数据的安全性。
用户登录也是本系统重要的部分，该模块主要是验证用户信息的正确性，与其他各个功能模块有着密不可分的关联，我们无论用哪种身份对系统进行操作时，都需要用身份去完成相应的操作。用户登录时序图如图3-2所示。
图3-2用户登录时序图
4.2人员信息管理功能的实现
以下截图是进行接处警的管理，直接操作的是接处警信息表的信息。页面布局主要包括编号、名称、接报时间、级别、人员人编号、人员人姓名、人员人电话、处警人编号、处警人姓名、处警人电话，同时布局了保存和返回按钮，下面介绍下该模块实现的主要过程和原理：首先，需要构建住户模块，通过页面设计工具Dreamweaver设计好，然后将其复制到开发工具当中，接着就是插入文本框控件和按钮控件，调整好使其显得美观得当。具体实现点击保存按钮时，将页面信息作为输入参数，调用inset接口方法，将入参的信息输入到insert方法，实现插入数据到数据库表中，点击返回按钮返回到接处警列表页面，人员信息管理如图4-6所示。
图4-6人员信息管理界面
代码如下：
<tr>
<tdalign="right">名称：</td>
<tdalign="left"><inputname="name"type="text"class="inputTextNormal"id="textfield"value=""/><spanclass="required">*</span></td>
<tdalign="right">接报时间：</td>
<tdalign="left"><inputname="createtime"type="text"class="inputTextMiddle"id="textfield2"value=""/><spanclass="required">*</span></td>
<tdalign="right">级别：</td>
<tdalign="left"><selectname="level">
<optionvalue="低">低</option>
<optionvalue="高">高</option>
</select><spanclass="required">*</span></td>
</tr>
<tr>
4.3应急事件功能的实现
4.3.1应急事件功能的实现
该图是从登陆界面登陆成功之后，进入到事件查看区域的截图。从截图可以看出，系统设计为以列表的形式展现事件信息，列表头部包含事件名称、创建时间、级别、处理状态、人员人、处警人、操作。下面介绍下该模块实现的主要过程和原理：首先，需要构建住户模块，应用Dreamweaver工具进行页面布局。页面加载事件信息，调用select数据方法接口，将返回数据结果集进行遍历，事件页面进行渲染显示。点击监督处理按钮调用handle方法接口进行事件监督处理。事件查看界面的系统截图如图4-7所示
图4-7应急事件列表界面
代码如下：
<tr>
<tdalign="right">处警人编号：</td>
<tdalign="left"><inputname="cjid"type="text"class="inputTextNormal"id="textfield4"value=""/><spanclass="required">*</span></td>
<tdalign="right">处警人姓名：</td>
<tdalign="left"><inputname="ciname"type="text"class="inputTextMiddle"id="textfield5"value=""/><spanclass="required">*</span></td>
<tdalign="right">处警人电话：</td>
<tdalign="left"><inputname="cjtel"type="text"class="inputTextMiddle"id="textfield6"value=""/><spanclass="required">*</span></td>
4.3.2事件修改功能的实现
根据用户输入的事件查询条件，进行事件信息的查询。事件查询流程图如图4-8所示。
图4-8事件查询流程图
用户在进行事件查询的时候，通过输入事件名称等条件进行事件的查询，页面布局条件搜索框和查询按钮，应用Dreamweaver工具进行页面美化和布局，单击查询按钮，调用按钮事件，然后调用selectWhere数据接口方法，将查询条件作为方法的入参，查询事件数据库，返回查询结果集进行页面渲染。
图4-8事件修改界面
代码如下：
<!--//commonTableSearch-->
<divclass="btnBar">
<ulclass="clearfix">
<%--<li><ahref="yuan-create.jsp"title="新增数据"class="btnNormal">新增</a></li>--%>
<%--<li><aid="excelOut"href="javascript:method5('tableToExcel')"title="打印"class="btnNormal">打印</a></li>--%>
</ul>
</div>
<tableborder="0"cellspacing="1"cellpadding="0"class="commonTable"id="tableToExcel">
<tr>
<th>事件编号</th>
<th>事件名称</th>
<%--<th>内容</th>
<th>类型</th>
<th>状态</th>
<th>审核状态</th>
<thclass="editColM">操作</th>--%>
</tr>
<c:forEachitems="${sjs}"var="sj">
<tr>
<tdalign="center">${sj.sjid}</td>
<tdalign="left">${sj.sjname}</td>
<%--<tdalign="center">${yuan.content}</td>
<tdalign="left">${yuan.type}</td>
<tdalign="center">${yuan.state}</td>
<tdalign="center">${yuan.shstate}</td>
<tdalign="center">
4.4事件查找模块功能的实现
4.4.1事件添加功能的实现
管理员登录系统成功后，在新增事件界面输入事件相应信息，系统验证信息合法性，如不符合要求提示用户重新输入，如果符合数据验证要求将数据插入到数据库中。流程图如图4-9所示。
图4-9新增事件流程图
下面截图是系统事件管理新增模块截图，该模块功主要任务就是让用户通过填写事件名称、事件类型和数量，生成事件信息的过程。从界面截图来看，该住户模块主要包括的事件信息的名称、类型和数量等选项，另外添加了两个按钮，一个是保存按钮，一个是返回按钮。下面介绍下该模块实现的主要过程和原理：首先，需要构建事件查找模块，通过页面设计工具Dreamweaver设计好，然后将其复制到开发工具当中，接着就是插入文本框控件和按钮控件，调整好使其显得美观得当。其次就是设计实现的原理，单击保存按钮，进入按钮事件，然后调用insert数据接口方法，将信息插入到事件数据库表中，返回按钮返回事件管理的列表页面。下图就是事件管理的新增页面，如图4-10所示。
图4-10事件管理新增界面
代码如下：
functiongetExplorer(){
varexplorer=window.navigator.userAgent;
//ie
if(explorer.indexOf("MSIE")>=0){
return'ie';
}
//firefox
elseif(explorer.indexOf("Firefox")>=0){
return'Firefox';
}
//Chrome
elseif(explorer.indexOf("Chrome")>=0){
return'Chrome';
}
4.4.2事件修改功能的实现
事件信息的修改，输入要修改的事件信息项目，进行信息的更新。事件修改流程图如图4-11所示。
图4-11事件修改流程
用户在进行事件信息修改的时候，通过输入事件名称、事件类型和数量，页面布局应用input组件进行布局，同时布局button按钮。实现修改功能构建事件查找模块，应用Dreamweaver工具进行页面美化和布局，单击保存按钮，调用按钮事件，然后调用updateResources数据接口方法，将信息更新到事件数据库表中，返回按钮返回事件管理的列表页面。
图4-11事件信息修改界面
代码如下：
<tdalign="right">处警人编号：</td>
<tdalign="left"><inputname="jjid"type="text"class="inputTextNormal"id="textfield4"value=""/><spanclass="required">*</span></td>
<tdalign="right">处警人姓名：</td>
<tdalign="left"><inputname="jjname"type="text"class="inputTextMiddle"id="textfield5"value=""/><spanclass="required">*</span></td>
<tdalign="right">处警人电话：</td>
<tdalign="left"><inputname="jjtel"type="text"class="inputTextMiddle"id="textfield6"value=""/><spanclass="required">*</span></td>
</tr>--%>
</form>
</table>
<!--//commonTable-->
<divid="formPageButton">
<ul>
<li><ahref="javascript:insertSelective()"title="保存"class="btnShort">保存</a></li>
<li><ahref="javascript:window.history.go(-1)"title="返回"class="btnShort">返回</a></li>
</ul>
</div>
4.5事件统计报表功能的实现
下面截图是系统事件统计报表模块截图，该模块功主要任务就是让用户通过事件导入事件数据。页面布局选择导入文件按钮和导入按钮。点击导入按钮浏览本地填写好数据的事件文件，调用insert接口方法，循环读取事件内数据，插入到数据库中的事件信息表。如图4-12所示。
图4-12事件统计报表界面
代码如下：
<divclass="commonTitle"><h2>>><ahref="#">日志管理</a>-新增日志</h2></div>
<tableborder="0"cellspacing="1"cellpadding="0"class="commonTable">
<formid="institutionCreat"name="institutionCreat"action="insertyuan"method="post">
<tr>
<tdalign="right">日志名称：</td>
<tdalign="left"><inputname="name"type="text"class="inputTextNormal"id="textfield"value=""/><spanclass="required">*</span></td>
<tdalign="right">内容：</td>
<tdalign="left"><inputname="content"type="text"class="inputTextMiddle"id="textfield2"value=""/><spanclass="required">*</span></td>
<tdalign="right">级别：</td>
<tdalign="left"><selectname="level">
<optionvalue="低">低</option>
<optionvalue="高">高</option>
4.6日志记录管理的功能实现
加载日志信息管理列表，查询数据库显示信息列表页，选择一条需要删除的信息，系统提示是否删除选中信息，如果同意删除数据库中当前这条数据，提示删除数据成功，如果不同意返回数据列表。流程图如图4-13所示
图4-13日志信息删除流程图
在日志信息管理列表页，选择一条需要修改的信息，进行数据查询，跳转到日志信息查询界面，输入需要查询的信息项系统提示是否查询信息，如果同意进行数据的提交，查询数据库信息，如果不同意返回查询页面，可重新输入查询信息项目，再重新上面操作。流程图如图4-14所示。
图4-14日志管理修改流程图
下图是日志管理页面，该画面主要是展现日志信息的数据，页面布局列表日志名称、级别、内容、类型、状态、审核状态和操作列，列表右上角布局新增按钮，每行数据的操作列添加两个操作按钮一个是修改按钮，一个是删除按钮。下面介绍下该模块实现的主要过程和原理：需要构建日志管理模块，通过页面设计工具Dreamweaver设计好，然后将其复制到开发工具当中，接着就是插入文本框控件和按钮控件，调整好使其显得美观得当。点击新增按钮，跳转到日志新增页面，新增日志调用insert接口方法，将数据插入到数据库日志表，点击编辑按钮，修改日志信息调用update接口方法，更新数据库中当前日志信息，点击删除按钮，删除日志信息调用delete接口方法，删除数据库中当前日志信息。如图4-15所示。
图4-15日志管理页面
代码如下：
<body>
<divid="header-wrap">
<iframeallowtransparency="true"frameborder="0"id="header-box"scrolling="no"src="inc-header.html"></iframe>
</div>
<divid="main-wrap">
<divid="main-nav">
<iframeframeborder="0"id="siderbar-box"scrolling="no"src="inc-nav.html"></iframe>
</div>
<divid="main-content">
<tableborder="0"cellpadding="0"cellspacing="0"id="main-content-box">
<tr>
<tdclass="toggle"></td>
<tdclass="content-wrap"><iframeframeborder="0"id="content-box"src="welcome.html"scrolling="auto"></iframe></td>
</tr>
</table>
4.7本章小结
基于SSM的应急救援指挥的应急系统论文的第四章主要展示应急救援指挥的应急系统的详细实现过程，理清代码的设计思路，将算法研究和界面展示呈现出来，对系统的功能性和界面的友好性有一个直观的了解。
5系统测试
系统测试是测试员在对系统测试过程中找出开发者没有发现的错误，反馈给开发者然后及时的修改错误信息的过程。系统测试可以提高系统的综合质量和性能。本章重点介绍系统测试的具体环节。
5.1登录测试
系统测试主要是针对系统主要的模块来进行详细的数据测试说明，通过每个模块的多种测试数据来确定模块是否可行，是否存在错误，进而及时更改。
1.登录测试
受篇幅所限此处只列出部分测试，正确管理员账号：1，密码：1。操作员账号：1，密码：1。用户在登录界面可以通过用户名、密码进行登录。如表5-1所示。
表5-1登录界面测试表
| 序号 |
操作 |
预期结果 |
实际结果 |
测试结果 |
| 1 |
不输入账号和密码 |
登录失败，请重新输入 |
登录失败，请重新输入 |
测试成功 |
| 2 |
输入管理员账号1，不输入密码 |
登录失败，请重新输入 |
登录失败，请重新输入 |
测试成功 |
| 3 |
不输入管理员账号， 密码：1 |
登录失败，请重新输入 |
登录失败，请重新输入 |
测试成功 |
| 4 |
输入管理员账号：1，密码：1 |
登录成功，跳转管理员界面 |
登录成功，跳转管理员界面 |
测试成功 |
| 5 |
输入错误的管理员账号：ad，密码：888888 |
登录失败，请重新输入 |
登录失败，请重新输入 |
测试成功 |
| 6 |
输入管理员账号：admin，错误的密码：000000 |
登录失败，请重新输入 |
登录失败，请重新输入 |
测试成功 |
| 7 |
输入用户账号：caozuoyuan，密码:123456 |
登录成功，跳转用户界面 |
登录成功，跳转用户界面 |
测试成功 |
| 8 |
输入未注册用户：WHH，密码：123 |
登录失败，请重新输入 |
登录失败，请重新输入 |
测试成功 |
测试结论：登录界面测试成功，达到预期效果。
5.2人员信息录入测试
人员信息录入测试这里操作员可以进行接处警的信息维护，主要包括编号、名称、接报时间、级别、人员人编号、人员人姓名、人员人电话、处警人编号、处警人姓名、处警人电话。如表5-2所示。
表5-2人员信息录入测试表
| 序号 |
操作 |
预期结果 |
实际结果 |
测试结果 |
| 1 |
编号不输入，其它项目正常数据，进行提交 |
提交失败，编号不允许为空 |
提交失败，系统提示编号不允许为空 |
测试成功 |
| 2 |
名称不输入，其它项目正常数据，进行提交 |
提交失败，名称不允许为空 |
提交失败，系统提示名称不允许为空 |
测试成功 |
| 3 |
接报时间不输入，其它项目正常数据，进行提交 |
提交失败，接报时间不允许为空 |
提交失败，系统提示接报时间不允许为空 |
测试成功 |
| 4 |
级别不选择，其它项目正常数据，进行提交 |
提交失败，必须选择级别 |
提交失败，系统提示请选择级别 |
测试成功 |
续表5-2人员信息录入测试表
| 序号 |
操作 |
预期结果 |
实际结果 |
测试结果 |
| 5 |
编号输入：1201，名称输入：口蹄疫，接报时间输入：2021年 |
提交成功，跳转到接处警列表页 |
提交成功，跳转到接处警列表页 |
测试成功 |
测试结论：人员信息录入测试成功，达到预期效果。
5.3事件管理测试
事件新增这里操作员可以对事件信息进行新增操作，指标主要包括名称、类型、数量。如表5-3所示。
表5-3事件新增测试表
| 序号 |
操作 |
预期结果 |
实际结果 |
测试结果 |
| 1 |
输入名称：手套，输入类型：防护类，输入数量：ac，进行提交 |
提交失败，数量必须为数据字 |
提交失败，系统提示数量必须为数字 |
测试成功 |
| 2 |
名称为空，输入类型：防护类，输入数量：100，进行提交 |
提交失败，名称不允许为空 |
提交失败，系统提示名称必须为空 |
测试成功 |
| 3 |
输入名称：手套，类型为空，输入数量：100，进行提交 |
提交失败，类型不允许为空 |
提交失败，类型不允许为空 |
测试成功 |
| 4 |
输入名称：手套，输入类型：防护类，输入数量：100，进行提交 |
提交成功，跳转到事件信息列表页 |
提交成功，跳转到事件信息列表页 |
测试成功 |
测试结论：事件新增测试成功，达到预期效果。
事件查找这里操作员点击选择导入文件按钮，浏览本机填写好事件数据的事件，点击导入按钮，实现事件的查找。如表5-4所示。
表5-4事件新增测试表
| 序号 |
操作 |
预期结果 |
实际结果 |
测试结果 |
| 1 |
选择导入事件：未填写数据的空事件，进行提交导入 |
导入失败，事件不允许为空 |
导入失败，系统提示事件不允许为空 |
测试成功 |
| 2 |
不选择导入事件，进行提交导入 |
导入失败，必须选择导入事件 |
导入失败，系统提示必须选择导入事件 |
测试成功 |
| 3 |
选择导入事件：已填写数据的事件，进行提交导入 |
导入成功，跳转到事件信息列表页 |
导入成功，跳转到事件信息列表页 |
测试成功 |
测试结论：事件新增测试成功，达到预期效果。
5.4事件新增测试
事件查找这里操作员点击选择导入文件按钮，浏览本机填写好事件数据的事件，点击导入按钮，实现事件的查找。如表5-5所示。
表5-5事件新增测试表
| 序号 |
操作 |
预期结果 |
实际结果 |
测试结果 |
| 1 |
选择导入事件：未填写数据的空事件，进行提交导入 |
导入失败，事件不允许为空 |
导入失败，系统提示事件不允许为空 |
测试成功 |
| 2 |
不选择导入事件，进行提交导入 |
导入失败，必须选择导入事件 |
导入失败，系统提示必须选择导入事件 |
测试成功 |
| 3 |
选择导入事件：已填写数据的事件，进行提交导入 |
导入成功，跳转到事件信息列表页 |
导入成功，跳转到事件信息列表页 |
测试成功 |
5.5本章小结
论文第五章完成软件的测试工作，网站测试主要使用功能测试法配合其他测试手段，保证最终的用例设计可靠，测试结果正确。
结论
应急救援指挥的应急系统的系统设计与开发以及论文撰写在预期内完成。应急救援指挥的应急系统完成了人员信息管理模块、日志记录管理模块、应急事件管理、大数据报表模块。可以实现管理员对应急事件的整体把控，对于各项科研成果都通过数据库查询到，及时更新信息，保证信息有效。本次应急救援指挥的应急系统设计主要特点有系统设计采用的是WEB设计模式，数据库采用了SqlServer作为开发存储数据，保证了系统数据的准确、安全，JavaScript、JSP开发前台页面。社区信息管理系统通过以上等等技术开发完成，拥有我们预期需求的安全性、快捷性、实用性等优点。
系统设计之初，系统考虑的不是很周全，系统模块设定，数据库定位，字段长度定位不够准确。今后也应当丰富自己的技术储备，做出更完善的应急救援指挥的应急系统，缓解科研成果管理工作上的难题，解决时下管理系统不健全，所以存在科研成果信息收集和汇总不及时等问题。
参考文献
- XiaoshuWangOptimizedDevelopmentofWebFront-endDevelopmentTechnology[J]JournalofPhysics:ConferenceSeries,2020.
- KangningZhengandZuopengZhangandBinSong.E-commercelogisticsdistributionmodeinbig-datacontext:AcaseanalysisofJD.COM[J].IndustrialMarketingManagement,2020,86(prepublish):153-162.
- 甘宁.互联网时代B2C电子商城购物网站的应用与测试[J].信息与电脑,2021,33(14):3.
- 顾建伟.电子商城系统的研究与实现[D].电子科技大学,2013
- 邱璐璐,陈俊仁.基于SpringBoot和Vue框架的高校代领系统设计与实现[J].信息技术与信息化.2021,第004期.
- 董葆茗,孟萍莉,周璐璐.社交电商背景下零售企业营销模式研究[J].商业经济研究,2020(06):55-59.
- 孙嘉倪.基于B/S结构的云通信管理平台的设计与实现[D].北京邮电大学,2021.
- 单树倩,任佳勋.基于SpringBoot和Vue框架的数据库原理网站设计与实现[J].电脑知识与技术.2021,第030期
- 刘海,王美妮编著.Vue应用程序开发[M].北京:人民邮电出版社,2021.
- 杨涛.基于Node.js的高并发电商购物系统设计与实现[D].北京邮电大学,2021.
- 李云.基于Vue框架开发的学生管理系统[J].数字通信世界,2022(03):50-53.
- 黎西凌.基于springboot的智能管道检测机器人软件设计[J].电子制作.2019,第019期.
- 王博.基于个性化推荐的居舍优品商城的设计与实现[D].北京交通大学,2020.
- 武秀峰.云店电子商务平台订单子系统的设计与实现[D].南京大学,2021.
- 胡晓宇,方剑.基于天翼云的对象存储行业应用实践探索[J].数字通信世界,2022(02):4-9
- 黄菊华编著.Vue.js入门与商城开发实践[M].北京:机械工业出版社,2020
致谢
四年的读书生活即将划上一个句号，而于我却只是一个逗号，我将面对又一次征程的开始。四年的求学生涯在师长、亲友的大力支持下，走得辛苦却也收获满囊，在论文即将付梓之际，思绪万千，心情久久不能平静。在设计之初，对毕业设计制作没有思路，对于自己能力认知有限，指导老师帮我确定适合自己的题目，并认真分析题目的制作方向，制定需求分析；在制作过程中，付立平老师不断的给我纠正问题，帮助我克服很多大大小小的困难，对我完成设计有很大的帮助；指导老师不厌其烦的讲解和答疑，使我倍受感动。
在课题设计过程中，同学们的帮助和关心让我感受到了同学之间的情谊，他们在我遇到困难的时候可以为我分担难题，纠正我的错误思路；使得我的论文思路能够调整到正确的轨道上来。我的大学时光中，因为有你们的存在而变得更加精彩，谢谢我亲爱的伙伴们。
最后，设计在制作过程中，参考了大量的国内外与课题相关的文献，在指导老师的指导下，我顺利的完成了设计任务，感谢老师。