Software modeling method based on software meta-model
Through detailed analysis and optimization of the operation data of the ordering software, the adaptability problem of traditional modeling methods under large-scale systems and dynamic requirements is solved, efficient delivery efficiency and service quality are achieved, and system flexibility and expansion are enhanced. sex.
Patent Information
- Application Number
- CN202411110812.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-14
- Publication Date
- 2024-11-26
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Traditional software modeling methods cannot effectively adapt to system changes when facing large-scale systems and dynamic requirements, and the complexity and high abstraction levels of meta-modeling methods lead to high learning curves and compatibility problems in model design and management.
By obtaining the operation data of the ordering software, extracting the merchant’s food delivery path data, conducting topological structure analysis and abnormal detection, dividing abnormal models, performing order delivery accident correction and sequence optimization, realizing software architecture integration and meta-model optimization, and uploading to the online ordering cloud platform .
It improves delivery efficiency and service quality, reduces the negative impact of abnormal situations on customer experience, enhances the flexibility and scalability of the system, and supports more functions and needs.
Smart Images

Figure CN119026290A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of metamodeling, and in particular to a software modeling method based on software metamodel. Background Art
[0002] In the field of software engineering, traditional software modeling methods, such as data flow diagrams and entity-relationship models, have been widely used in the system analysis and design phase. However, with the increasing complexity of software systems, these methods have gradually exposed their shortcomings. Especially when facing large-scale systems and dynamic requirements, traditional modeling methods often cannot effectively adapt to system changes or provide sufficient levels of abstraction, resulting in flexibility and scalability issues in the modeling process. Although the software metamodel method provides strong abstraction capabilities and flexibility in theory, it also exposes some shortcomings in practical applications. The complexity and high level of abstraction of the metamodeling method lead to a high learning curve in the model design and management process. The standardization and tool support of the metamodel are not yet fully mature, resulting in compatibility issues between different modeling tools. Summary of the invention
[0003] Based on this, it is necessary for the present invention to provide a software modeling method based on a software metamodel to solve at least one of the above technical problems.
[0004] To achieve the above object, a software modeling method based on software metamodel includes the following steps:
[0005] Step S1: Acquire the ordering software operation data, and extract the merchant delivery path data from the ordering software operation data, so as to obtain the merchant delivery path data; perform a delivery topology structure analysis based on the merchant delivery path data, so as to obtain a delivery topology structure model;
[0006] Step S2: performing meal delivery anomaly detection according to the meal ordering software operation data, thereby obtaining meal delivery anomaly data; dividing the meal delivery topology structure model according to the meal delivery anomaly data, thereby obtaining an abnormal meal delivery topology structure model;
[0007] Step S3: extracting order delivery accident timeout data from the abnormal food delivery data, thereby obtaining order delivery accident timeout data; performing order delivery accident timeout correction on the abnormal food delivery topological structure model according to the order delivery accident timeout data, thereby obtaining abnormal delivery sequence data;
[0008] Step S4: clustering the abnormal delivery sequence of the ordering software operation data according to the abnormal delivery sequence data, thereby obtaining the abnormal operation delivery sequence data of the ordering software; optimizing the delivery sequence according to the abnormal operation delivery sequence data of the ordering software, thereby obtaining the ordering delivery sequence optimization data;
[0009] Step S5: Integrate the ordering software architecture according to the ordering delivery sequence optimization data to obtain the ordering software architecture data; optimize the software metamodel architecture according to the ordering software architecture data to obtain the ordering software optimization metamodel, and upload it to the online ordering cloud platform to execute the software metamodel optimization task.
[0010] The present invention can obtain a detailed model of the delivery path by extracting the merchant's delivery path data and performing topological structure analysis. This improves the delivery efficiency, creates a detailed delivery topological structure model to help identify key nodes and potential bottlenecks in the path, facilitates subsequent optimization and adjustment, and is based on real delivery path data rather than theoretical models, which helps to more accurately reflect the actual situation and make more effective decisions. By detecting abnormal delivery data, problems in the delivery process, such as delays, route deviations, etc., can be identified in a timely manner. Analyzing the abnormal data and dividing the abnormal delivery topological structure model can help accurately locate the problem area and cause, provide a basis for improvement measures, and be able to respond quickly when the problem occurs, reducing the negative impact of abnormal situations on customer experience. By extracting the order delivery accident timeout data, it can be found which orders have timeout problems and make targeted improvements. According to the timeout data, the abnormal delivery topological structure model is corrected, which can more accurately reflect the actual delivery situation, improve the reliability of the model, reduce delivery timeouts, and help improve customer satisfaction and service quality. By clustering the abnormal delivery sequence, the commonalities and patterns of abnormal delivery can be identified, which helps to understand the root causes of delivery anomalies. Based on the analysis results of abnormal delivery sequence data, the delivery process can be optimized to reduce the occurrence of abnormal situations. Optimizing the delivery sequence helps to improve overall delivery efficiency, shorten delivery time, and reduce operating costs. By integrating the software architecture based on the delivery sequence optimization data, a more efficient system architecture can be achieved, and the performance and reliability of the software can be improved. The optimized metamodel uploaded to the online ordering cloud platform can achieve continuous model optimization and updating, so that the software system can dynamically adapt to new needs and changes. The optimized metamodel can improve the system's adaptability to changes, enhance the system's flexibility and scalability, and support more functions and needs.
[0011] Optionally, step S1 specifically includes:
[0012] Step S11: Acquire the ordering software operation data, and divide the ordering software operation data into user nodes, thereby obtaining the deliveryman node operation data, the merchant node operation data, and the customer node operation data;
[0013] Step S12: performing spatial path association according to the deliveryman node operation data and the merchant node operation data, thereby obtaining merchant-deliveryman path data;
[0014] Step S13: performing spatial path association according to the customer node operation data and the delivery person node operation data, thereby obtaining customer-delivery person path data;
[0015] Step S14: integrating the merchant-deliveryman path data and the customer-deliveryman path data into delivery area path relationships, thereby obtaining delivery area path connection data;
[0016] Step S15 performs distribution area topology analysis based on the distribution area path connection data, thereby obtaining a meal delivery path topology model.
[0017] The present invention can analyze the operation of each role more accurately by dividing the data according to user nodes (such as delivery personnel, merchants, and customers). This helps to identify the behavior patterns, work efficiency, and potential problems of each node, classify the data of different nodes, and help to optimize the experience of various users in a targeted manner. For example, the delivery route can be optimized according to the operation data of the delivery personnel, and the inventory management and order processing can be improved according to the data of the merchants. Through the detailed division of the node data, the load conditions of different parts of the system can be more clearly understood, which is helpful for improving the performance of the system and diagnosing problems. Through spatial path association, the best delivery path between the delivery personnel and the merchants can be identified, thereby reducing the delivery time and cost. Optimizing the path arrangement can improve the delivery efficiency, reduce empty driving and repeated trips, and thus improve the overall operational efficiency. The work area of the delivery personnel can be reasonably configured according to the actual delivery path data, and the efficiency of resource utilization can be improved. By optimizing the path between the delivery personnel and the customer, the delivery time can be reduced, the customer satisfaction and experience can be improved, and reasonable path planning can reduce the redundant links in the delivery process and improve the delivery efficiency. The most common delivery mode can be found through data analysis, so as to make more reasonable adjustments during peak periods. Integrating different path data can provide a more comprehensive understanding of the needs of the distribution area, optimize the division of the distribution area and resource allocation, and integrate the distribution path data of merchants and customers to achieve collaborative optimization between merchants and customers, improve the overall system operation efficiency, and predict future distribution needs and potential bottlenecks based on integrated data, so as to plan and adjust resources in advance. By analyzing the topological structure of the distribution area, key nodes and paths in the distribution network can be identified and optimized, and the efficiency of the overall distribution network can be improved. Optimizing the topological structure of the distribution area can reduce the redundant parts of the distribution path, thereby reducing transportation costs. Potential weaknesses and risks in the distribution network can be discovered through topological structure analysis, thereby improving the robustness and stability of the system.
[0018] Optionally, step S2 specifically includes:
[0019] Step S21: extracting merchant-side meal delivery data according to the meal ordering software operation data, thereby obtaining merchant-side meal delivery data;
[0020] Step S22: dividing the merchant-side meal delivery data into order process structures, thereby obtaining merchant-side order processing data and merchant-side order delivery data;
[0021] Step S23: performing order printing abnormality analysis according to the merchant-side order processing data, thereby obtaining merchant-side order printing abnormality data;
[0022] Step S24: performing order delivery anomaly analysis based on the merchant-side order delivery data, thereby obtaining merchant-side order delivery anomaly data;
[0023] Step S25: integrating the order abnormality data according to the merchant-side order printing abnormality data and the merchant-side order delivery abnormality data, thereby obtaining the order abnormality data;
[0024] Step S26: dividing the meal delivery topology structure model into abnormal order delivery according to the abnormal order data, thereby obtaining an abnormal meal delivery topology structure model.
[0025] By extracting the meal delivery data from the merchant side, the present invention can fully understand the meal delivery status of the merchant, provide basic data for subsequent abnormal analysis, and ensure the comprehensiveness and accuracy of the data. Structural division of the meal delivery data from the merchant side helps to clearly distinguish between the order processing and delivery links, and facilitates targeted analysis of the performance and potential problems of each link. Analysis of order printing anomalies can reveal specific problems in the printing process, such as printer failure or data transmission errors, so as to take targeted improvement measures. Analysis of order delivery anomaly data helps to identify problems that occur in the delivery process, such as delayed or incorrect delivery, thereby optimizing the delivery process and improving service quality. Integrating printing and delivery anomaly data provides a comprehensive anomaly view, helps identify potential systemic problems, and proposes an overall improvement plan. Re-dividing the meal delivery topology model based on abnormal data can optimize the meal delivery path and strategy, reduce the occurrence of abnormal situations, and improve overall delivery efficiency and accuracy.
[0026] Optionally, step S23 is specifically:
[0027] Step S231: extracting printing order equipment failure data from the merchant-side order processing data, thereby obtaining printing order equipment failure data;
[0028] Step S232: classifying the printing device fault data into fault types, thereby obtaining the printing order device circuit fault data and the printing order device component fault data;
[0029] Step S233: performing control circuit fault type statistics on the circuit fault data of the printing order device, thereby obtaining control circuit abnormality data;
[0030] Step S234: setting a resistance threshold value for the component failure data of the printing order device, thereby obtaining circuit component resistance threshold data;
[0031] Step S235: performing resistance threshold comparison on the printing order equipment component failure data according to the circuit component resistance threshold data, thereby obtaining circuit component resistance abnormality data;
[0032] Step S236: constructing a circuit abnormality detection model according to the control circuit abnormality data and the circuit element resistance abnormality data, thereby obtaining a circuit abnormality detection model;
[0033] Step S237: screening the merchant-side order printing anomaly on the merchant-side order processing data according to the circuit anomaly detection model, thereby obtaining the merchant-side order printing anomaly data.
[0034] The present invention can help the system to fully understand the problems of the equipment in actual operation by extracting the fault data of the printing order equipment. By systematically collecting fault data, a comprehensive fault database can be established to provide basic data for subsequent fault analysis and improvement. The fault data is divided into types, and the faults are divided into circuit faults and component faults, which helps to clarify the source of the problem. This classification can help identify specific fault categories, so that targeted measures can be taken in subsequent analysis and repair. The control circuit fault type statistics of the circuit fault data can be used to understand the various abnormal conditions in the control circuit in detail, which helps to identify common problems in the control circuit and improve the accuracy of fault diagnosis. The resistance threshold is set for circuit element fault analysis to distinguish between normal and abnormal resistance value ranges, which helps to accurately detect the health status of circuit elements, so as to more effectively identify and locate faults. By comparing the resistance threshold to obtain the circuit element resistance abnormality data, it is possible to deeply understand whether the element is in a fault state. Such a comparison can help to timely discover the resistance abnormality in the circuit and prevent potential faults from causing equipment downtime. Constructing a circuit abnormality detection model, combining the control circuit abnormality data and the circuit element resistance abnormality data, can improve the automation level of fault detection. The construction of the model can help to quickly identify abnormalities in complex circuit systems and reduce the time and cost of manual inspection. By screening for order printing anomalies on the merchant side based on the circuit anomaly detection model, anomalies in the order printing process can be identified more accurately. This not only improves the efficiency of fault detection, but also reduces order processing problems caused by printing anomalies and improves the overall service quality.
[0035] Optionally, step S24 is specifically:
[0036] Step S241: extracting the order overtime delivery data from the merchant-side order delivery data, thereby obtaining the order overtime delivery data;
[0037] Step S242: Classifying the delivery timeout types according to the order timeout delivery data, thereby obtaining the order system processing timeout data and the order delivery accident timeout data;
[0038] Step S243: Calculate the system performance bottleneck degree of the order system processing timeout data, thereby obtaining the order system processing bottleneck data;
[0039] Step S244: Obtaining order delivery climate data;
[0040] Step S245: Calculating the delivery rollover probability of the delivery area path connection data according to the order delivery climate data, thereby obtaining the order delivery rollover probability data;
[0041] Step S246: performing accident correlation analysis on the order delivery accident timeout data according to the order delivery rollover probability data, thereby obtaining order delivery rollover accident data;
[0042] Step S247: constructing a delivery anomaly detection model based on the order system processing bottleneck data and the order delivery rollover accident data, thereby obtaining a delivery anomaly detection model;
[0043] Step S248: Screen the merchant-side order delivery data for delivery anomalies according to the delivery anomaly detection model, thereby obtaining the merchant-side order delivery anomaly data.
[0044] The present invention can accurately identify the overtime delivery situation by extracting the order overtime delivery data, which is helpful to understand the current delivery efficiency problem. Through this data, merchants can evaluate the delay points in the delivery process and provide a basis for improvement measures, thereby improving the overall delivery efficiency and customer satisfaction. By classifying the overtime delivery data, the different reasons for system processing timeout and delivery accident timeout can be clearly distinguished. This refinement helps to more accurately analyze the source of the problem and formulate targeted optimization strategies, thereby improving the reliability of order processing and delivery. Calculating the system performance bottleneck degree can reveal the system performance bottleneck in the order processing process. By identifying these bottlenecks, the system administrator can take corresponding optimization measures, such as upgrading hardware or optimizing algorithms, thereby improving the overall performance and processing speed of the system. Obtaining order delivery climate data helps to understand the impact of climate conditions on delivery. By analyzing these data, merchants can predict delivery problems caused by bad weather, thereby reserving extra time or adjusting routes in the delivery plan to reduce the negative impact of climate on delivery. The distribution rollover probability calculation of the distribution area path connection data can evaluate the rollover risk of different paths under specific climate conditions. This analysis helps to optimize the distribution route selection, reduce accidents, and ensure the safety of the distribution process. Accident correlation analysis based on rollover probability data can associate rollover accidents with climate conditions or other factors. Merchants can understand the probability of accidents under different conditions, so as to formulate targeted preventive measures and improve delivery safety. The construction of a delivery anomaly detection model can comprehensively consider system performance bottlenecks and delivery rollover accident data, and automatically identify abnormal situations. This model helps merchants monitor anomalies in the delivery process in real time, so as to adjust and optimize delivery strategies in a timely manner and improve service quality and efficiency. Using the delivery anomaly detection model to screen order delivery data can help to detect delivery anomalies at an early stage. By timely discovering and handling these anomalies, merchants can respond to problems quickly, reduce the negative impact on customer experience, and improve the accuracy and reliability of order delivery.
[0045] Optionally, step S26 is specifically:
[0046] Step S261: extracting abnormal meal delivery path data from the abnormal order data, thereby obtaining abnormal meal delivery path data;
[0047] Step S262: performing meal delivery area frequency statistics on the abnormal meal delivery path data, thereby obtaining high-frequency abnormal meal delivery area data;
[0048] Step S263: performing a regional path spatial intersection operation on the high-frequency abnormal meal delivery area data according to the abnormal meal delivery path data, thereby obtaining the high-frequency abnormal meal delivery space data;
[0049] Step S264: dividing the food delivery topology structure model into abnormal food delivery space structures according to the high-frequency abnormal food delivery space data, thereby obtaining the abnormal food delivery topology structure model.
[0050] The present invention can help identify specific paths with problems in the distribution process by extracting abnormal delivery path data. By understanding which paths frequently have abnormalities, merchants can focus on these areas, optimize delivery routes, reduce future delivery problems, and improve overall delivery efficiency and service quality. Regional frequency statistics of abnormal delivery path data can identify areas where delivery anomalies frequently occur, which enables merchants to accurately locate problem areas and make targeted improvements, such as increasing resources or adjusting delivery strategies, thereby reducing delivery problems in these high-frequency abnormal areas. The regional path spatial intersection operation helps to spatially associate high-frequency abnormal areas with abnormal delivery paths. This analysis can reveal the specific spatial structure of the problem area and help merchants deeply understand the spatial distribution pattern of delivery anomalies, thereby more effectively adjusting delivery routes and strategies. According to the high-frequency abnormal delivery spatial data, the delivery topological structure model is abnormally divided, and a detailed abnormal delivery topological structure model can be established. This model helps to visualize and analyze the spatial structure of distribution anomalies, so that merchants can optimize and improve more targetedly and improve the stability and reliability of the delivery process.
[0051] Optionally, step S4 is specifically:
[0052] Step S41: clustering the abnormal delivery sequence of the ordering software operation data according to the abnormal delivery sequence data, thereby obtaining the abnormal operation delivery sequence data of the ordering software;
[0053] Step S42: Acquire meal delivery sequence data of the delivery person;
[0054] Step S43: performing sequence comparison on the abnormal operation of the ordering software according to the meal delivery sequence data of the delivery personnel, thereby obtaining the abnormal meal delivery sequence data of the delivery personnel;
[0055] Step S44: optimizing the order delivery sequence of the abnormal sequence data of meal delivery by the delivery personnel, thereby obtaining the order delivery sequence optimization data.
[0056] By clustering these abnormal delivery sequence data, the present invention can classify similar abnormal situations into one category, thereby more systematically identifying and analyzing common abnormal patterns. This clustering helps to find potential system failure points or optimization space and provide targeted improvement measures. For example, if it is found that certain delivery routes often have delay problems, the system can focus on these routes for optimization, thereby improving overall delivery efficiency and customer satisfaction. Obtaining the delivery personnel's meal delivery sequence data helps to gain a deeper understanding of the delivery personnel's performance and behavior patterns in actual delivery. These data can reveal specific problems encountered by delivery personnel during the delivery process, such as route selection, delivery time, and customer feedback. By analyzing these data, managers can identify the delivery personnel's work efficiency and existing problems, and take corresponding measures to improve them, such as providing better route planning tools or training to improve the overall delivery quality and efficiency. By comparing the delivery personnel's meal delivery sequence data with the abnormal operation delivery sequence data of the ordering software, the abnormal behavior of the delivery personnel in actual operation or the association with the abnormal sequence of the software can be identified. This comparative analysis helps to reveal whether the delivery personnel are affected by software problems in the process of performing tasks, and whether there are delivery problems caused by system abnormalities. After understanding these correlations, the system can be improved or the delivery personnel's operation process can be optimized in a targeted manner, thereby reducing the occurrence of abnormal situations and improving the stability and reliability of the delivery system. Optimizing the abnormal sequence data of the delivery personnel's meal delivery can improve the delivery process and reduce the occurrence of abnormal situations. By analyzing the abnormal sequence data, the system can identify which delivery links need to be optimized, such as route planning, delivery time management or resource allocation. The optimized delivery sequence can improve delivery efficiency, reduce delay rate, and improve customer experience. At the same time, system optimization can reduce complaints and returns caused by delivery abnormalities, thereby improving overall operational efficiency and customer satisfaction.
[0057] Optionally, step S44 is specifically:
[0058] Step S441: Obtain the delivery personnel's delivery box data, delivery personnel's delivery box data, and delivery personnel's order delivery quantity data;
[0059] Step S442: extracting the delivery box material features from the delivery box data of the delivery person, thereby obtaining the delivery box material data;
[0060] Step S443: Calculate the order delivery loading quantity of the delivery personnel's delivery box data according to the delivery personnel's order delivery quantity data, thereby obtaining the order delivery box loading data;
[0061] Step S444: performing meal delivery simulation according to the delivery box material data and the order delivery box loading data, thereby obtaining meal damage simulation data;
[0062] Step S445: extracting damaged food simulated delivery sequence data from the damaged food simulated data, thereby obtaining damaged food simulated delivery sequence data;
[0063] Step S446: performing sequence comparison on the simulated delivery sequence data of damaged food and the abnormal delivery sequence data of food delivered by the deliveryman, so as to obtain the sequence data of damaged food delivered by the deliveryman;
[0064] Step S447: Optimize the order delivery sequence according to the sequence of damaged food delivered by the delivery personnel, so as to obtain the order delivery sequence optimization data.
[0065] The present invention can fully understand the various resources and operations in the distribution process by obtaining the delivery box data, delivery box data and order delivery volume data of the delivery personnel, which provides a detailed data basis for subsequent analysis and optimization, and ensures that all links of the distribution process can be effectively monitored and managed. Feature extraction of the delivery box material helps to understand the physical properties and material quality of the delivery box. This process can provide data on the durability and protection performance of the delivery box, and provides a scientific basis for reducing food damage and improving packaging design. By calculating the order delivery loading volume, the use and loading efficiency of the delivery box can be accurately grasped, which provides important data support for optimizing the design and configuration of the delivery box, and helps to improve the overall efficiency and resource utilization of the distribution process. Meal delivery simulation based on delivery box material data and order delivery box loading data helps to predict and evaluate the damage of food during the distribution process. This simulation can identify potential problems in advance and provide guidance for optimizing the distribution method and improving food protection measures. Extracting damaged food simulation delivery sequence data from the damage simulation data helps to establish damage patterns and identification rules. This process can provide detailed data support for improving distribution plans and reducing damage, and ensure the safety of food during the distribution process. By comparing the simulated delivery sequence data of damaged food and the abnormal delivery sequence data of the delivery personnel, the problem points in the delivery process can be identified. This comparative analysis helps to find specific problems in the delivery and provide targeted suggestions for improving the delivery process. Optimizing the sequence of damaged food delivered by the delivery personnel can improve the overall efficiency and accuracy of order delivery. The optimized delivery sequence can effectively reduce food damage, improve customer satisfaction, and improve the efficiency of the use of delivery resources.
[0066] Optionally, step S444 is specifically:
[0067] Extracting the hardness characteristics and thickness characteristics of the delivery box material data, thereby obtaining the hardness data and thickness data of the delivery box material data;
[0068] Perform hardness characteristic analysis on the delivery box material data to obtain material hardness characteristic data;
[0069] Perform thickness characteristic analysis on the delivery box material data to obtain material thickness characteristic data;
[0070] Perform pressure resistance analysis based on material hardness characteristic data and material thickness characteristic data to obtain the pressure resistance data of the delivery box material;
[0071] Perform meal delivery simulation based on the pressure resistance data of the delivery box material and the order delivery box loading data, thereby obtaining meal delivery simulation data;
[0072] The meal damage simulation data is extracted from the meal delivery simulation data, thereby obtaining the meal damage simulation data.
[0073] The present invention can obtain the physical property data of the delivery box by extracting the hardness and thickness characteristics, which provides key basic data for subsequent analysis and helps to understand the protection and durability of the material. Through hardness characteristic analysis, the hardness data of the delivery box material can be obtained. This analysis helps to evaluate the compressive resistance and protection performance of the material under different conditions and provide a basis for improving the design. Thickness characteristic analysis can provide thickness data of the delivery box material, which helps to understand the strength and protection effect of the material, thereby optimizing the design of the delivery box to reduce the risk of damage. According to the hardness characteristic data and thickness characteristic data, the pressure resistance analysis can obtain the pressure resistance data of the delivery box material, which helps to evaluate the performance of the delivery box under pressure, thereby optimizing the packaging solution and reducing the damage rate. Using the pressure resistance data and loading data for delivery simulation, the meal delivery simulation data can be obtained, which helps to predict potential problems in actual delivery, so as to make improvements in advance and ensure the safe arrival of the meal. Extracting damage simulation data from the delivery simulation data can clarify the type of damage encountered by the meal during the delivery process, which provides detailed feedback for further optimizing the delivery process and packaging design.
[0074] Optionally, step S5 specifically includes:
[0075] Step S51: Designing a meal ordering software architecture according to the meal ordering processing system optimization data, thereby obtaining meal ordering software architecture data;
[0076] Step S52: performing concurrent user load testing on the ordering software architecture data, thereby obtaining software architecture concurrent user load testing data;
[0077] Step S53: performing error frequency statistics on the software architecture concurrent user load test data, thereby obtaining software architecture load high-frequency error data;
[0078] Step S54: Sorting the severity of the software architecture load high-frequency error data, thereby obtaining architecture high-frequency error severity sorting data;
[0079] Step S55: performing code repair strategy analysis according to the architecture high-frequency error severity ranking data, thereby obtaining an architecture repair strategy;
[0080] Step S56: Optimize the software metamodel architecture according to the architecture repair strategy to obtain an optimized metamodel of the meal ordering software, and upload it to the online meal ordering cloud platform to execute the software metamodel optimization task.
[0081] The present invention can establish an efficient and demand-compliant system framework by optimizing data design ordering software architecture, improve overall system performance and stability, and provide a solid foundation for subsequent optimization. Concurrent load testing of the architecture can evaluate the performance of the system under high user volume conditions, ensure the scalability and stability of the system, and avoid crashes or performance bottlenecks in actual use. Statistical error frequencies in load testing help identify and locate common problems in the system, provide data support for further repairs and optimizations, and improve system reliability. Sorting severity according to high-frequency errors can give priority to errors with the greatest impact, concentrate resources to solve key problems, and significantly improve system stability and user experience. Analyzing repair strategies to deal with serious errors can formulate effective repair plans, optimize code and system architecture, reduce future errors, and improve the overall quality and maintenance efficiency of the system. Optimizing the software metamodel architecture and uploading it to the cloud platform can improve the performance and flexibility of the system, ensure that the ordering software runs efficiently in a cloud environment, and support large-scale user access and operation. BRIEF DESCRIPTION OF THE DRAWINGS
[0082] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments thereof made with reference to the following drawings:
[0083] Figure 1 A schematic diagram of the steps of the software modeling method based on the software metamodel of the present invention;
[0084] Figure 2 Detailed step flow diagram of step S1 in the present invention;
[0085] Figure 3 Detailed step flow diagram of step S2 in the present invention;
[0086] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0087] The following is a clear and complete description of the technical method of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by technicians in this field without creative work are within the scope of protection of the present invention.
[0088] In addition, the accompanying drawings are only schematic illustrations of the present invention and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. The functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor methods and / or microcontroller methods.
[0089] It should be understood that, although the terms "first", "second", etc. may be used herein to describe various units, these units should not be limited by these terms. These terms are used only to distinguish one unit from another unit. For example, without departing from the scope of the exemplary embodiments, the first unit may be referred to as the second unit, and similarly the second unit may be referred to as the first unit. The term "and / or" used herein includes any and all combinations of one or more of the listed associated items.
[0090] To achieve this, please refer to Figures 1 to 3 The present invention provides a software modeling method based on a software metamodel, the method comprising the following steps:
[0091] Step S1: Acquire the ordering software operation data, and extract the merchant delivery path data from the ordering software operation data, so as to obtain the merchant delivery path data; perform a delivery topology structure analysis based on the merchant delivery path data, so as to obtain a delivery topology structure model;
[0092] In this embodiment, operation data is regularly extracted through the API interface of the ordering software, including the GPS location, delivery time, order information, etc. of each delivery person. Assume that the system records 1,000 delivery data every day, and each data includes the delivery person ID, order ID, starting point coordinates, end point coordinates and delivery time. Use geographic information system (GIS) tools to convert GPS coordinates into delivery paths. Linear regression or shortest path algorithm is used to extract delivery path data from the original location data. Use network analysis tools (such as GraphX or NetworkX) to perform topological structure analysis on the extracted delivery path data. Create a delivery topology model, which includes nodes (merchant locations, user locations) and edges (delivery paths) to analyze delivery efficiency and path optimization. Use data processing scripts written in Python, combined with PostGIS database to store spatial data, and visualize and analyze paths through QGIS.
[0093] Step S2: performing meal delivery anomaly detection according to the meal ordering software operation data, thereby obtaining meal delivery anomaly data; dividing the meal delivery topology structure model according to the meal delivery anomaly data, thereby obtaining an abnormal meal delivery topology structure model;
[0094] In this embodiment, based on the running data of the food delivery software (for example, the difference between the actual delivery time and the expected delivery time), anomaly detection algorithms such as Isolation Forest or Support Vector Machine (SVM) are applied for anomaly detection. Assume that 100 abnormal orders are detected, and the delivery time of these orders exceeds twice the expected time. The detected abnormal data is separated from the normal data, and the food delivery topology model is reconstructed. The model is redrawn using the abnormal data to highlight the abnormal delivery area. The Scikit-learn library is used to implement the anomaly detection algorithm, store the abnormal data and model update information in the MongoDB database, and use D3.js for model visualization.
[0095] Step S3: extracting order delivery accident timeout data from the abnormal food delivery data, thereby obtaining order delivery accident timeout data; performing order delivery accident timeout correction on the abnormal food delivery topological structure model according to the order delivery accident timeout data, thereby obtaining abnormal delivery sequence data;
[0096] In this embodiment, timeout data is extracted from abnormal food delivery data. The difference between the actual delivery time of each order and the set delivery time window is calculated. Assume that 20 timeout orders are extracted from 100 abnormal orders. The abnormal food delivery topology model is corrected according to these timeout data, and the delivery path of the timeout area in the model is adjusted. Increase the processing of timeout data, such as optimizing path planning or increasing delivery personnel resources. Use SQL queries to perform statistical analysis on the food delivery records in the database, generate a timeout order report, and adjust the food delivery path through a linear optimization algorithm.
[0097] Step S4: clustering the abnormal delivery sequence of the ordering software operation data according to the abnormal delivery sequence data, thereby obtaining the abnormal operation delivery sequence data of the ordering software; optimizing the delivery sequence according to the abnormal operation delivery sequence data of the ordering software, thereby obtaining the ordering delivery sequence optimization data;
[0098] In this embodiment, the abnormal delivery sequence data (including timeouts and abnormal paths) are clustered and analyzed. The K-means clustering algorithm is applied to divide the data into several groups to identify common abnormal delivery patterns. For example, three main abnormal delivery patterns are found. The delivery sequence is optimized based on the clustering results. The delivery strategy and path planning are adjusted to reduce the occurrence of abnormal patterns. Assume that after optimization, the delivery time is reduced by 15%. K-means clustering is implemented using Python's Sci-kit Learn library, the clustering results are displayed through visualization tools (such as Tableau), and the path planning algorithm is updated to apply the optimization strategy.
[0099] Step S5: Integrate the ordering software architecture according to the ordering delivery sequence optimization data to obtain the ordering software architecture data; optimize the software metamodel architecture according to the ordering software architecture data to obtain the ordering software optimization metamodel, and upload it to the online ordering cloud platform to execute the software metamodel optimization task.
[0100] In this embodiment, the system architecture of the ordering software is redesigned and integrated based on the delivery sequence optimization data. New modules that support optimization algorithms are added, such as dynamic path planning and real-time delivery adjustment. The software metamodel is optimized according to the new architecture design. The model-driven architecture (MDA) method is applied to update the definition of the software metamodel to support new functions. The optimized metamodel is uploaded to the online ordering cloud platform, and the software metamodel optimization task is performed to ensure the effectiveness of the optimized functions in actual applications. Use UML tools for architecture design and metamodel definition, and use AWS or Azure cloud platforms for model deployment and task execution to ensure that the new model can run smoothly in the actual production environment.
[0101] Optionally, step S1 specifically includes:
[0102] Step S11: Acquire the ordering software operation data, and divide the ordering software operation data into user nodes, thereby obtaining the deliveryman node operation data, the merchant node operation data, and the customer node operation data;
[0103] In this embodiment, after obtaining the operation data of the ordering software, the system classifies the user nodes through log records and real-time data streams. The activity data of each user (such as order time, location, delivery status, etc.) is extracted and divided by role: deliveryman node (including the deliveryman's working hours and geographical location), merchant node (including the merchant's business hours and address), customer node (including the customer's order record and location). These node data are stored in the database and identified and organized by data tags. For example, by analyzing the activity data of the deliveryman in a certain period of time, the deliveryman node is identified, and the relevant location and time data are extracted to form the deliveryman node operation data.
[0104] Step S12: performing spatial path association according to the deliveryman node operation data and the merchant node operation data, thereby obtaining merchant-deliveryman path data;
[0105] In this embodiment, the geographic location data of the deliveryman node and the merchant node are used to calculate the optimal path from the merchant to the deliveryman through spatial path association technology (such as geographic information system GIS). The system first calculates the distance between the merchant and the deliveryman through the coordinate points, and then applies the path optimization algorithm (such as Dijkstra algorithm or A* algorithm) to generate the merchant-deliveryman path data. Assuming that the deliveryman receives an order from merchant A, the system records the coordinates of merchant A and the current location of the deliveryman, calculates the driving path between the two points, and integrates the traffic conditions to generate accurate delivery route data.
[0106] Step S13: performing spatial path association according to the customer node operation data and the delivery person node operation data, thereby obtaining customer-delivery person path data;
[0107] In this embodiment, spatial path association is performed through the data of customer nodes and delivery personnel nodes to obtain the path from the customer to the delivery personnel. The system obtains the customer's order address and the current location of the delivery personnel, and uses geographic information system (GIS) technology to calculate the path between the two. Assuming that customer B places an order and selects delivery personnel C, the system inputs the location of customer B and the current location of delivery personnel C into the path calculation model to calculate the shortest path between the two. The system integrates real-time traffic information to generate customer-delivery personnel path data, including estimated delivery time and route.
[0108] Step S14: integrating the merchant-deliveryman path data and the customer-deliveryman path data into delivery area path relationships, thereby obtaining delivery area path connection data;
[0109] In this embodiment, the merchant-deliveryman path data and the customer-deliveryman path data are integrated to form the delivery area path connection data. The system first aggregates all the path data into the same delivery area model, and establishes a path network within the area by analyzing the intersection and connection relationship of the paths. For example, by analyzing the paths from multiple merchants to deliverymen and the paths from customers to deliverymen in a certain delivery area, they are integrated into a connected path network diagram, and the weights of each path (such as distance, traffic conditions) are marked to generate the delivery area path connection data.
[0110] Step S15 performs distribution area topology analysis based on the distribution area path connection data, thereby obtaining a meal delivery path topology model.
[0111] In this embodiment, a topological structure analysis is performed based on the distribution area path connection data to generate a delivery path topological structure model. Graph theory methods are used to analyze the connectivity, node degree, and shortest path of the path network graph. The system uses graph analysis algorithms (such as the shortest path algorithm and the minimum spanning tree algorithm) to identify key paths and distribution centers within the distribution area. For example, the path network within the distribution area is analyzed, the routes with the highest distribution efficiency are identified, and the key distribution nodes are determined. Finally, a topological model describing the structure of the distribution area is generated, which can effectively support the optimization of delivery paths and resource scheduling.
[0112] Optionally, step S2 specifically includes:
[0113] Step S21: extracting merchant-side meal delivery data according to the meal ordering software operation data, thereby obtaining merchant-side meal delivery data;
[0114] In this embodiment, in the background of the ordering software, the system extracts the merchant's meal delivery data through the API interface, including order ID, meal delivery time, dish details, etc. The data source is the database of the merchant system, and the extracted data will be stored in the data warehouse for subsequent analysis. For example, the merchant system's daily order data will be exported to a CSV file, which contains information such as order creation time, meal delivery time, and number of dishes to ensure the integrity and accuracy of the data.
[0115] Step S22: dividing the merchant-side meal delivery data into order process structures, thereby obtaining merchant-side order processing data and merchant-side order delivery data;
[0116] In this embodiment, the merchant-side meal delivery data is structured, first grouping the data by order ID, and then dividing the process structure according to the meal delivery time and processing stage (such as meal preparation, meal delivery, and delivery). For example, the record of order ID 12345 will be divided into the "order processing" stage and the "order delivery" stage, and further subdivided into the "meal preparation", "packaging" and "delivery" sub-stages. Finally, the processed data is organized into two categories: "merchant-side order processing data" and "merchant-side order delivery data".
[0117] Step S23: performing order printing abnormality analysis according to the merchant-side order processing data, thereby obtaining merchant-side order printing abnormality data;
[0118] In this embodiment, the merchant-side order processing data is analyzed for order printing anomalies, and order records with printing failures or printing delays are extracted and marked. For example, if the printing time of order ID 67890 exceeds the set normal time threshold (such as 5 minutes), it is recorded as a printing anomaly. The analysis tool will count the anomaly frequency and identify potential problems, such as printer failure or network problems, to generate an order printing anomaly data report.
[0119] Step S24: performing order delivery anomaly analysis based on the merchant-side order delivery data, thereby obtaining merchant-side order delivery anomaly data;
[0120] In this embodiment, anomaly analysis is performed based on the merchant-side order delivery data to identify orders with delayed or incorrect delivery. For example, by comparing the expected delivery time with the actual delivery time, if the delivery time exceeds the set standard (such as 15 minutes), it is marked as a delivery anomaly. The abnormal data includes the delivery person information, order ID, and delay time, etc. The analysis results help optimize the delivery process.
[0121] Step S25: integrating the order abnormality data according to the merchant-side order printing abnormality data and the merchant-side order delivery abnormality data, thereby obtaining the order abnormality data;
[0122] In this embodiment, the merchant-side order printing exception data and order delivery exception data are integrated to create a comprehensive exception data set. The printing exception and delivery exception information are merged by order ID using data fusion technology to form a comprehensive data set containing all exception information. For example, order ID 34567 has both printing delay and delivery delay. The integrated data set will contain detailed information on these two exceptions for comprehensive analysis.
[0123] Step S26: dividing the meal delivery topology structure model into abnormal order delivery according to the abnormal order data, thereby obtaining an abnormal meal delivery topology structure model.
[0124] In this embodiment, the food delivery topology model is divided according to the order abnormality data to construct the abnormal food delivery topology model. First, based on the order abnormality data, the impact of abnormal points (such as delivery delays, printing errors) in the food delivery path is identified and marked in the topology model. For example, if it is found through analysis that delivery delays frequently occur in a specific area, the area is highlighted in the food delivery topology model to further optimize the delivery route and improve the service quality.
[0125] Optionally, step S23 is specifically:
[0126] Step S231: extracting printing order equipment failure data from the merchant-side order processing data, thereby obtaining printing order equipment failure data;
[0127] In this embodiment, the merchant-side order processing data is subjected to printing order device failure data extraction. This step includes exporting all data related to the printing device from the order processing system, including printing error logs, device status reports, and maintenance records. Technically, a database query tool or data export function can be used to dump this data onto a data analysis platform for further processing. A specific example includes extracting a log file containing a device failure timestamp, error code, and failure description.
[0128] Step S232: classifying the printing device fault data into fault types, thereby obtaining the printing order device circuit fault data and the printing order device component fault data;
[0129] In this embodiment, the printing device fault data is classified into fault types. This step requires that the extracted fault data be classified according to the fault type, usually into circuit faults and component faults. This classification can be achieved using a data classification algorithm (such as a decision tree or a support vector machine). A specific implementation method is to match the error code and description in the fault log to a predefined fault type by setting rules or training a model, thereby separating the circuit fault data and the component fault data.
[0130] Step S233: performing control circuit fault type statistics on the circuit fault data of the printing order device, thereby obtaining control circuit abnormality data;
[0131] In this embodiment, the circuit fault data of the order equipment is printed to perform statistics on the types of control circuit faults. This step includes statistical analysis of various types of faults in the circuit fault data, such as control circuit overheating, short circuit or voltage instability. Use data analysis tools, such as statistical software or programming languages (such as Python), to perform frequency statistics on different types of circuit faults to form control circuit abnormality data. A specific example is to count the number of occurrences of each type of circuit fault and generate a data report
[0132] Step S234: setting a resistance threshold value for the component failure data of the printing order device, thereby obtaining circuit component resistance threshold data;
[0133] In this embodiment, resistance thresholds are set for the fault data of the printing order equipment components. This step requires setting resistance thresholds for the equipment components, usually based on equipment specifications and standards. Reference data or experimental test data provided by electrical engineers can be used to set the resistance thresholds. The specific implementation method includes recording the resistance range of each component and inputting this data into the fault analysis system.
[0134] Step S235: performing resistance threshold comparison on the printing order equipment component failure data according to the circuit component resistance threshold data, thereby obtaining circuit component resistance abnormality data;
[0135] In this embodiment, the resistance threshold comparison is performed on the component failure data of the printing order device according to the circuit component resistance threshold data. This step involves comparing the actually measured resistance value with the set threshold value to identify the component with abnormal resistance value. An electronic measuring instrument (such as a multimeter) is used to perform a resistance test, and then the measurement result is compared with the threshold data to generate circuit component resistance abnormality data.
[0136] Step S236: constructing a circuit abnormality detection model according to the control circuit abnormality data and the circuit element resistance abnormality data, thereby obtaining a circuit abnormality detection model;
[0137] In this embodiment, a circuit anomaly detection model is constructed based on the control circuit abnormality data and the circuit element resistance abnormality data. This step includes using a machine learning algorithm (such as a random forest or a neural network) to train the collected data to build a model that can detect circuit anomalies. The specific implementation method is to input the control circuit abnormality data and the resistance abnormality data into the training model, adjust the parameters to optimize the accuracy of the model, and form a circuit anomaly detection model.
[0138] Step S237: screening the merchant-side order printing anomaly on the merchant-side order processing data according to the circuit anomaly detection model, thereby obtaining the merchant-side order printing anomaly data.
[0139] In this embodiment, the merchant-side order processing data is screened for merchant-side order printing anomalies based on the circuit anomaly detection model. This step includes using the constructed circuit anomaly detection model to analyze the order processing data and identify printing anomalies. The specific implementation method is to input the order processing data into the detection model, and the abnormal data output by the model can be used for further troubleshooting or maintenance suggestions.
[0140] Optionally, step S24 is specifically:
[0141] Step S241: extracting the order overtime delivery data from the merchant-side order delivery data, thereby obtaining the order overtime delivery data;
[0142] In this embodiment, the overdue orders in the merchant-side order delivery data are extracted. First, all orders whose delivery time exceeds the preset threshold are queried from the merchant system database. This can be determined by setting a timestamp (such as the difference between the order creation time and the current time) to determine whether it is overdue. For example, the threshold for order timeout is set to 3 hours, and all order records whose delivery time exceeds the threshold are extracted to generate a list of overdue delivery data.
[0143] Step S242: Classifying the delivery timeout types according to the order timeout delivery data, thereby obtaining the order system processing timeout data and the order delivery accident timeout data;
[0144] In this embodiment, the extracted overtime delivery data is classified. According to the timeout reason, the data is divided into system processing timeout and delivery accident timeout. For example, the system processing timeout is due to excessive server load, and the delivery accident timeout is due to a traffic accident. By analyzing the detailed information of the timeout record and the system log, the timeout type of each order is determined and the corresponding data classification results are generated.
[0145] Step S243: Calculate the system performance bottleneck degree of the order system processing timeout data, thereby obtaining the order system processing bottleneck data;
[0146] In this embodiment, the performance bottleneck of order system processing is calculated. Using system logs and processing time data, processing bottleneck indicators such as response time delay, processing time distribution, etc. are calculated. For example, the average response time and standard deviation of order processing by the statistical system are used to identify orders whose processing time exceeds a set threshold, thereby determining system performance bottleneck data.
[0147] Step S244: Obtaining order delivery climate data;
[0148] In this embodiment, order delivery climate data is obtained. Real-time climate data of the relevant delivery area, such as temperature, humidity, precipitation, etc., is obtained through a weather API or a weather data provider. These data should cover all relevant weather factors in the delivery area for subsequent analysis.
[0149] Step S245: Calculating the delivery rollover probability of the delivery area path connection data according to the order delivery climate data, thereby obtaining the order delivery rollover probability data;
[0150] In this embodiment, the rollover probability of the delivery path is calculated. The stability of different delivery paths is evaluated using climate data and road condition information. For example, by analyzing rainfall and road slope, a statistical model is used to calculate the rollover probability of each delivery path and generate a rollover probability data list.
[0151] Step S246: performing accident correlation analysis on the order delivery accident timeout data according to the order delivery rollover probability data, thereby obtaining order delivery rollover accident data;
[0152] In this embodiment, the rollover probability data is correlated with the order delivery accident overtime data to identify which overtime accidents are related to high rollover probability. For example, a regression analysis model is used to correlate the rollover probability with the overtime accident rate to determine the delivery accident data in the high rollover probability area.
[0153] Step S247: constructing a delivery anomaly detection model based on the order system processing bottleneck data and the order delivery rollover accident data, thereby obtaining a delivery anomaly detection model;
[0154] In this embodiment, a distribution anomaly detection model is constructed. The system processing bottleneck data and distribution rollover accident data are combined to establish an anomaly detection model using a machine learning algorithm (such as a random forest or support vector machine). The labeling and feature selection of abnormal data should be considered during model training in order to detect and predict distribution anomalies.
[0155] Step S248: Screen the merchant-side order delivery data for delivery anomalies according to the delivery anomaly detection model, thereby obtaining the merchant-side order delivery anomaly data.
[0156] In this embodiment, the constructed anomaly detection model is used to screen the merchant-side order delivery data. The model is applied to real-time order data to detect whether there are abnormal delivery situations. For example, the delivery data of each order is analyzed by the model, delivery anomalies are identified, and an abnormal data report is generated for further processing by the merchant.
[0157] Optionally, step S26 is specifically:
[0158] Step S261: extracting abnormal meal delivery path data from the abnormal order data, thereby obtaining abnormal meal delivery path data;
[0159] In this embodiment, the system will filter out orders marked as "abnormal" from historical order data. These abnormal orders are identified due to delays, wrong delivery or other problems. Then, through data mining technology, the delivery paths of these abnormal orders are extracted. Specifically, the system will extract the starting location, end location and path points passed by each abnormal order. These data will be stored in a database, and each abnormal delivery path will include timestamp, location coordinates and route information. For example, if the delivery path of an order shows that it passes through point C from point A to point B, and there is a delay problem, the system will record these path data for subsequent analysis.
[0160] Step S262: performing meal delivery area frequency statistics on the abnormal meal delivery path data, thereby obtaining high-frequency abnormal meal delivery area data;
[0161] In this embodiment, after extracting the abnormal meal delivery path data, the system will divide these paths into regions and divide the meal delivery area into several grids (for example, each grid is 1 square kilometer). The system will count the frequency of abnormal meal delivery events in each area. For example, if an area has had 10 abnormal meal deliveries in the past month, then the frequency statistics of the area is 10. Through these statistics, the system can identify areas with a higher frequency of abnormalities. These data will help managers find problematic areas, for example, some areas have a higher frequency of abnormal meal deliveries due to traffic congestion or other reasons.
[0162] Step S263: performing a regional path spatial intersection operation on the high-frequency abnormal meal delivery area data according to the abnormal meal delivery path data, thereby obtaining the high-frequency abnormal meal delivery space data;
[0163] In this embodiment, after identifying the high-frequency abnormal delivery areas, the system will perform spatial intersection operations on these areas and the abnormal delivery path data. Specifically, the system will calculate the spatial overlap between these high-frequency areas and the abnormal paths. For example, assuming that the high-frequency abnormal area is area X, and the abnormal delivery path passes through a part of area X, the system will calculate the intersection of these paths with area X. This can help determine which high-frequency abnormal areas are most concentrated in the delivery path. Ultimately, the system will generate a data set that lists the spatial intersection of each high-frequency area and the abnormal delivery path.
[0164] Step S264: dividing the food delivery topology structure model into abnormal food delivery space structures according to the high-frequency abnormal food delivery space data, thereby obtaining the abnormal food delivery topology structure model.
[0165] In this embodiment, the system will construct a food delivery topology model using high-frequency abnormal food delivery spatial data. Specific operations include analyzing nodes (such as food delivery sites, customer addresses) and edges (such as food delivery routes) in the food delivery network. The system will use spatial data analysis techniques, such as graph theory algorithms, to divide the abnormal spatial structure of the food delivery network. For example, the system will find that the food delivery paths between certain nodes frequently have abnormalities, and these nodes will be marked as "high-risk areas." By redividing the topology model, the system can identify the paths and nodes that need to be optimized, thereby forming an optimized abnormal food delivery topology model to reduce future abnormalities.
[0166] Optionally, step S4 is specifically:
[0167] Step S41: clustering the abnormal delivery sequence of the ordering software operation data according to the abnormal delivery sequence data, thereby obtaining the abnormal operation delivery sequence data of the ordering software;
[0168] In this embodiment, the delivery data of the ordering software is collected and marked as normal or abnormal. The data is preprocessed, including data cleaning and standardization. Then, the delivery data is clustered using a machine learning algorithm, such as K-means or DBSCAN. An appropriate number of clusters or radius is set to group abnormal delivery sequences and identify delivery sequences with similar abnormal characteristics. For example, if a certain type of abnormal delivery sequence is found to be characterized by long delivery delays or frequent errors, it is classified into a specific abnormal category. Through these categories, the system can be further analyzed and optimized.
[0169] Step S42: Acquire meal delivery sequence data of the delivery person;
[0170] In this embodiment, delivery sequence data is extracted from the deliveryman's work record. This data includes information such as the timestamp of each delivery, the deliveryman ID, the meal ID, and the delivery status. This data is extracted from the order management system using the API, and the deliveryman's historical delivery records are queried from the database. For example, if the deliveryman Zhang San's delivery record on a certain day includes multiple orders from restaurant A to location B, these delivery records can be arranged in time series and stored as structured data.
[0171] Step S43: performing sequence comparison on the abnormal operation of the ordering software according to the meal delivery sequence data of the delivery personnel, thereby obtaining the abnormal meal delivery sequence data of the delivery personnel;
[0172] In this embodiment, the delivery sequence data of the delivery person is compared with the abnormal delivery sequence data. A sequence alignment algorithm such as dynamic time warping (DTW) or long short-term memory network (LSTM) is used for matching. A similarity threshold is determined to distinguish abnormal from normal patterns. For example, if the delivery sequence of delivery person Zhang San is highly similar to a known abnormal sequence (such as frequent delays or errors), the delivery data of the delivery person is marked as abnormal, and the specific abnormal sequence data is extracted for further analysis.
[0173] Step S44: optimizing the order delivery sequence of the abnormal sequence data of meal delivery by the delivery personnel, thereby obtaining the order delivery sequence optimization data.
[0174] In this embodiment, the identified abnormal sequence data of the delivery personnel are analyzed to determine optimization measures. The delivery sequence is adjusted using an optimization algorithm, such as a genetic algorithm or simulated annealing. Factors to be considered include reducing delivery time and avoiding peak delivery periods. For example, for the abnormal delivery sequence of delivery personnel Zhang San, if frequent delays are found on a specific route, the delivery sequence can be rearranged or the route can be adjusted to improve delivery efficiency, and finally the optimized delivery sequence data is generated and improvement measures are implemented.
[0175] Optionally, step S44 is specifically:
[0176] Step S441: Obtain the delivery personnel's delivery box data, delivery personnel's delivery box data, and delivery personnel's order delivery quantity data;
[0177] In this embodiment, the delivery personnel's delivery box data, delivery personnel's delivery box data, and delivery personnel's order delivery quantity data are obtained. During implementation, these data can be automatically extracted from the delivery personnel's electronic device or database through an integrated delivery management system. For example, the system can extract the size, material, and order quantity data of the delivery box for each delivery from the delivery personnel's mobile application.
[0178] Step S442: extracting the delivery box material features from the delivery box data of the delivery person, thereby obtaining the delivery box material data;
[0179] In this embodiment, the delivery box material feature extraction is performed on the delivery box data of the delivery person, so as to obtain the delivery box material data. In this step, image processing technology and material analysis tools can be used to identify the material type of the delivery box, for example, by scanning the barcode or QR code of the box to obtain material information, and further analyze the strength and durability of these materials.
[0180] Step S443: Calculate the order delivery loading quantity of the delivery personnel's delivery box data according to the delivery personnel's order delivery quantity data, thereby obtaining the order delivery box loading data;
[0181] In this embodiment, the order delivery loading volume is calculated for the delivery personnel's delivery box data according to the delivery personnel's order delivery volume data, thereby obtaining the order delivery box loading data. In specific implementation, an algorithm can be used to calculate the actual loading volume of each delivery box according to the size and design of each delivery box, combined with the volume and quantity of the order. For example, if the volume of each box is 10 cubic meters, and the total order volume is 8 cubic meters, the loading volume of the box is 80%.
[0182] Step S444: performing meal delivery simulation according to the delivery box material data and the order delivery box loading data, thereby obtaining meal damage simulation data;
[0183] In this embodiment, meal delivery simulation is performed based on the delivery box material data and the order delivery box loading data to obtain meal damage simulation data. Simulation software can be used to model the performance of meals under different delivery conditions, such as vibration, temperature changes, etc. For example, virtual simulation technology is used to simulate the squeezing and collision of the delivery box during transportation, and the damage of the meal is recorded.
[0184] Step S445: extracting damaged food simulated delivery sequence data from the damaged food simulated data, thereby obtaining damaged food simulated delivery sequence data;
[0185] In this embodiment, damaged food simulated delivery sequence data is extracted from damaged food simulated data, thereby obtaining damaged food simulated delivery sequence data. This step can form a delivery sequence of damaged food by analyzing the damage in the simulated data, extracting the time, location and conditions of the damage. For example, the damage events and their frequencies occurring on a specific road section or under weather conditions are recorded.
[0186] Step S446: performing sequence comparison on the simulated delivery sequence data of damaged food and the abnormal delivery sequence data of food delivered by the deliveryman, so as to obtain the sequence data of damaged food delivered by the deliveryman;
[0187] In this embodiment, the sequence data of simulated delivery of damaged food and the sequence data of abnormal delivery of food by the deliveryman are compared to obtain the sequence of damaged food delivered by the deliveryman. During implementation, data analysis tools can be used to compare the damage simulation data with the actual abnormal delivery data to find common damage patterns and abnormal situations. For example, if a deliveryman frequently damages food in a specific time period, it indicates that the delivery conditions in that time period are poor.
[0188] Step S447: Optimize the order delivery sequence according to the sequence of damaged food delivered by the delivery personnel, so as to obtain the order delivery sequence optimization data.
[0189] In this embodiment, the order delivery sequence is optimized according to the sequence of damaged food delivered by the delivery personnel, so as to obtain the order delivery sequence optimization data. In specific implementation, the optimization algorithm can be used to adjust the delivery route, delivery box configuration and other related parameters to reduce the risk of food damage. For example, the delivery route can be adjusted to avoid severely bumpy roads, and the box loading method can be optimized to improve stability.
[0190] Optionally, step S444 is specifically:
[0191] Extracting the hardness characteristics and thickness characteristics of the delivery box material data, thereby obtaining the hardness data and thickness data of the delivery box material data;
[0192] In this example, a hardness tester is used to measure the hardness of the delivery box material. The hardness value is recorded for each sample, and the thickness of the material is measured using a thickness gauge. Testing can be performed at multiple points to ensure the accuracy and representativeness of the data. A batch of paper delivery boxes is tested, and the hardness (e.g., Brinell hardness) and thickness (e.g., 0.5 mm, 0.7 mm, 1.0 mm) of each box are measured. All measurement data are recorded to obtain hardness data and thickness data.
[0193] Perform hardness characteristic analysis on the delivery box material data to obtain material hardness characteristic data;
[0194] In this embodiment, the collected hardness data is analyzed, and its mean, standard deviation and other statistical characteristics are calculated. Regression analysis or other statistical methods are used to evaluate the effect of hardness on material properties. Statistical analysis of the hardness data of paper delivery boxes shows that the hardness varies significantly among different production batches. Regression analysis is used to understand the effect of hardness on the pressure resistance of delivery boxes.
[0195] Perform thickness characteristic analysis on the delivery box material data to obtain material thickness characteristic data;
[0196] In this example, the thickness data is statistically analyzed, including average thickness, thickness variability, etc. A chart is used to display the thickness distribution, and the effect of thickness variation on material properties is analyzed. The average value of the measured delivery box thickness data is 0.7 mm, and the standard deviation is 0.05 mm. The analysis results show that the thickness has a significant effect on the strength of the box.
[0197] Perform pressure resistance analysis based on material hardness characteristic data and material thickness characteristic data to obtain the pressure resistance data of the delivery box material;
[0198] In this embodiment, the material pressure resistance test is performed in combination with the hardness characteristic data and the thickness characteristic data. The pressure test is performed to measure the bearing capacity of the delivery box under different pressures and record the failure point. The delivery box with a hardness of 7HB is pressure tested and its maximum pressure resistance is found to be 200N. Similar tests are performed on boxes of different thicknesses to obtain pressure resistance data.
[0199] Perform meal delivery simulation based on the pressure resistance data of the delivery box material and the order delivery box loading data, thereby obtaining meal delivery simulation data;
[0200] In this embodiment, the pressure resistance data and the order delivery box loading data are used for simulation to calculate the delivery effect under different delivery conditions. The simulation software is used to generate detailed simulation data of the delivery process. During the transportation process, the box is loaded with 20 meals, and the weight and volume information of each meal is input into the simulation software to analyze the performance of the delivery box under different conditions.
[0201] The meal damage simulation data is extracted from the meal delivery simulation data, thereby obtaining the meal damage simulation data.
[0202] In this embodiment, in the meal delivery simulation, the damage caused by insufficient performance of the packaging material is analyzed. The number and degree of damaged meals are recorded, and a detailed damage data report is generated. During the simulation, it was found that 10% of the delivery boxes were damaged during transportation. The proportion and type of damaged meals were recorded and analyzed to evaluate the protection effect of the materials during the delivery process.
[0203] Optionally, step S5 specifically includes:
[0204] Step S51: Designing a meal ordering software architecture according to the meal ordering processing system optimization data, thereby obtaining meal ordering software architecture data;
[0205] In this embodiment, the data flow and user interaction requirements of the existing ordering system are collected. The UML (Unified Modeling Language) tool is used to create the use case diagram and class diagram of the system, and the functional modules of the system such as user management, menu browsing, order processing, etc. are defined. Using the microservice architecture, the system is divided into independent services, such as user services, order services, payment services, etc. A RESTful API interface is designed for each service, and each microservice is encapsulated using container technology (such as Docker). Finally, the design documents and architecture diagrams are organized into system architecture data to form a complete ordering software architecture design document.
[0206] Step S52: performing concurrent user load testing on the ordering software architecture data, thereby obtaining software architecture concurrent user load testing data;
[0207] In this embodiment, a load testing tool such as JMeter or LoadRunner is used to perform concurrent testing on the ordering system. Virtual users are set to simulate high-concurrency scenarios, such as 5,000 users accessing the system to order food at the same time. During the test, the response time, system throughput, and resource utilization (CPU, memory, network, etc.) of each request are recorded. A load test report is generated, which contains performance data under various concurrent conditions, such as response time distribution, error rate, and system bottlenecks.
[0208] Step S53: performing error frequency statistics on the software architecture concurrent user load test data, thereby obtaining software architecture load high-frequency error data;
[0209] In this embodiment, error information is extracted from the log files obtained from the load test, and the logs are analyzed using a log analysis tool (such as ELK Stack or Splunk). The frequency of occurrence of different types of errors (such as 404 errors and 500 server errors) is counted. An error frequency statistics report is generated, including the frequency of occurrence of each error, time distribution, and number of users affected.
[0210] Step S54: Sorting the severity of the software architecture load high-frequency error data, thereby obtaining architecture high-frequency error severity sorting data;
[0211] In this embodiment, based on the error frequency statistics, a risk assessment method (such as failure mode and effect analysis FMEA) is used to score the severity of each error. The scoring criteria may include the impact of the error on the user experience, the threat to the system stability, and the repair cost. An error severity ranking list is generated, and the high-frequency errors are sorted from high to low in severity to form high-frequency error severity ranking data.
[0212] Step S55: performing code repair strategy analysis according to the architecture high-frequency error severity ranking data, thereby obtaining an architecture repair strategy;
[0213] In this embodiment, the data is sorted according to the severity of high-frequency errors to identify the errors with the highest priority. For each high-priority error, its root cause is analyzed and a repair strategy is developed. For example, if it is found that the system crashes due to excessive load, you can consider optimizing database queries or adding a caching mechanism. Develop a detailed repair plan, including code modification, testing, and deployment strategies.
[0214] Step S56: Optimize the software metamodel architecture according to the architecture repair strategy to obtain an optimized metamodel of the meal ordering software, and upload it to the online meal ordering cloud platform to execute the software metamodel optimization task.
[0215] In this embodiment, according to the repair strategy, code improvements are implemented and the system architecture is optimized. The system metamodel is updated using software modeling tools (such as Enterprise Architect) to reflect the optimized architecture design. After the optimization is completed, the metamodel data is uploaded to the online ordering cloud platform (such as AWS or Azure), and automated testing is performed to verify the optimization effect. Finally, the system operation is monitored to ensure that the optimization goals such as performance improvement and error reduction are achieved.
[0216] Therefore, the embodiments should be regarded as illustrative and non-restrictive from all points, and the scope of the present invention is limited by the appended claims rather than the above description, and it is therefore intended that all changes falling within the meaning and range of equivalent elements of the application documents are included in the present invention.
[0217] The above description is only a specific embodiment of the present invention, so that those skilled in the art can understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but should conform to the widest scope consistent with the principles and novel features invented herein.
Claims
1. A software modeling method based on software metamodel, characterized in that: The following steps are involved: Step S1: Acquire the ordering software operation data, and extract the merchant delivery path data from the ordering software operation data, so as to obtain the merchant delivery path data; Perform a meal delivery topology analysis based on the merchant’s meal delivery path data to obtain a meal delivery topology model; Step S2: performing meal delivery anomaly detection according to the meal ordering software operation data, thereby obtaining meal delivery anomaly data; The meal delivery topology structure model is divided according to the abnormal meal delivery data, so as to obtain the abnormal meal delivery topology structure model; Step S3: extracting order delivery accident timeout data from the abnormal food delivery data, thereby obtaining order delivery accident timeout data; performing order delivery accident timeout correction on the abnormal food delivery topological structure model according to the order delivery accident timeout data, thereby obtaining abnormal delivery sequence data; Step S4: clustering the abnormal delivery sequence of the ordering software operation data according to the abnormal delivery sequence data, thereby obtaining the abnormal operation delivery sequence data of the ordering software; optimizing the delivery sequence according to the abnormal operation delivery sequence data of the ordering software, thereby obtaining the ordering delivery sequence optimization data; Step S5: Integrate the ordering software architecture according to the ordering delivery sequence optimization data to obtain the ordering software architecture data; optimize the software metamodel architecture according to the ordering software architecture data to obtain the ordering software optimization metamodel, and upload it to the online ordering cloud platform to execute the software metamodel optimization task.
2. The software modeling method based on software metamodel according to claim 1, characterized in that: Step S1 is specifically as follows: Step S11: Acquire the ordering software operation data, and divide the ordering software operation data into user nodes, thereby obtaining the deliveryman node operation data, the merchant node operation data, and the customer node operation data; Step S12: performing spatial path association according to the deliveryman node operation data and the merchant node operation data, thereby obtaining merchant-deliveryman path data; Step S13: performing spatial path association according to the customer node operation data and the delivery person node operation data, thereby obtaining customer-delivery person path data; Step S14: integrating the merchant-deliveryman path data and the customer-deliveryman path data into delivery area path relationships, thereby obtaining delivery area path connection data; Step S15 performs distribution area topology analysis based on the distribution area path connection data, thereby obtaining a meal delivery path topology model.
3. The software modeling method based on software metamodel according to claim 1, characterized in that: Step S2 is specifically as follows: Step S21: extracting merchant-side meal delivery data according to the meal ordering software operation data, thereby obtaining merchant-side meal delivery data; Step S22: dividing the merchant-side meal delivery data into order process structures, thereby obtaining merchant-side order processing data and merchant-side order delivery data; Step S23: performing order printing abnormality analysis according to the merchant-side order processing data, thereby obtaining merchant-side order printing abnormality data; Step S24: performing order delivery anomaly analysis based on the merchant-side order delivery data, thereby obtaining merchant-side order delivery anomaly data; Step S25: integrating the order abnormality data according to the merchant-side order printing abnormality data and the merchant-side order delivery abnormality data, thereby obtaining the order abnormality data; Step S26: dividing the meal delivery topology structure model into abnormal order delivery according to the abnormal order data, thereby obtaining an abnormal meal delivery topology structure model.
4. The software modeling method based on software metamodel according to claim 3 is characterized in that: Step S23 is specifically as follows: Step S231: extracting printing order equipment failure data from the merchant-side order processing data, thereby obtaining printing order equipment failure data; Step S232: classifying the printing device fault data into fault types, thereby obtaining the printing order device circuit fault data and the printing order device component fault data; Step S233: performing control circuit fault type statistics on the circuit fault data of the printing order device, thereby obtaining control circuit abnormality data; Step S234: setting a resistance threshold value for the component failure data of the printing order device, thereby obtaining circuit component resistance threshold data; Step S235: performing resistance threshold comparison on the printing order equipment component failure data according to the circuit component resistance threshold data, thereby obtaining circuit component resistance abnormality data; Step S236: constructing a circuit abnormality detection model according to the control circuit abnormality data and the circuit element resistance abnormality data, thereby obtaining a circuit abnormality detection model; Step S237: screening the merchant-side order printing anomaly on the merchant-side order processing data according to the circuit anomaly detection model, thereby obtaining the merchant-side order printing anomaly data.
5. The software modeling method based on software metamodel according to claim 3 is characterized in that: Step S24 is specifically as follows: Step S241: extracting the order overtime delivery data from the merchant-side order delivery data, thereby obtaining the order overtime delivery data; Step S242: Classifying the delivery timeout types according to the order timeout delivery data, thereby obtaining the order system processing timeout data and the order delivery accident timeout data; Step S243: Calculate the system performance bottleneck degree of the order system processing timeout data, thereby obtaining the order system processing bottleneck data; Step S244: Obtain order delivery climate data; Step S245: Calculating the delivery rollover probability of the delivery area path connection data according to the order delivery climate data, thereby obtaining the order delivery rollover probability data; Step S246: performing accident correlation analysis on the order delivery accident timeout data according to the order delivery rollover probability data, thereby obtaining order delivery rollover accident data; Step S247: constructing a delivery anomaly detection model based on the order system processing bottleneck data and the order delivery rollover accident data, thereby obtaining a delivery anomaly detection model; Step S248: Screen the merchant-side order delivery data for delivery anomalies according to the delivery anomaly detection model, thereby obtaining the merchant-side order delivery anomaly data.
6. The software modeling method based on software metamodel according to claim 3 is characterized in that: Step S26 is specifically as follows: Step S261: extracting abnormal meal delivery path data from the abnormal order data, thereby obtaining abnormal meal delivery path data; Step S262: performing meal delivery area frequency statistics on the abnormal meal delivery path data, thereby obtaining high-frequency abnormal meal delivery area data; Step S263: performing a regional path spatial intersection operation on the high-frequency abnormal meal delivery area data according to the abnormal meal delivery path data, thereby obtaining the high-frequency abnormal meal delivery space data; Step S264: dividing the food delivery topology structure model into abnormal food delivery space structures according to the high-frequency abnormal food delivery space data, thereby obtaining the abnormal food delivery topology structure model.
7. The software modeling method based on software metamodel according to claim 1, characterized in that: Step S4 is specifically as follows: Step S41: clustering the abnormal delivery sequence of the ordering software operation data according to the abnormal delivery sequence data, thereby obtaining the abnormal operation delivery sequence data of the ordering software; Step S42: Acquire meal delivery sequence data of the delivery person; Step S43: performing sequence comparison on the abnormal operation of the ordering software according to the meal delivery sequence data of the delivery personnel, thereby obtaining the abnormal meal delivery sequence data of the delivery personnel; Step S44: optimizing the order delivery sequence of the abnormal sequence data of meal delivery by the delivery personnel, thereby obtaining the order delivery sequence optimization data.
8. The software modeling method based on software metamodel according to claim 7, characterized in that: Step S44 is specifically as follows: Step S441: Obtain the delivery personnel's delivery box data, delivery personnel's delivery box data, and delivery personnel's order delivery quantity data; Step S442: extracting the delivery box material features from the delivery box data of the delivery person, thereby obtaining the delivery box material data; Step S443: Calculate the order delivery loading quantity of the delivery personnel's delivery box data according to the delivery personnel's order delivery quantity data, thereby obtaining the order delivery box loading data; Step S444: performing meal delivery simulation according to the delivery box material data and the order delivery box loading data, thereby obtaining meal damage simulation data; Step S445: extracting damaged food simulated delivery sequence data from the damaged food simulated data, thereby obtaining damaged food simulated delivery sequence data; Step S446: performing sequence comparison on the simulated delivery sequence data of damaged food and the abnormal delivery sequence data of food delivered by the deliveryman, so as to obtain the sequence of damaged food delivered by the deliveryman; Step S447: Optimize the order delivery sequence according to the sequence of damaged food delivered by the delivery personnel, so as to obtain the order delivery sequence optimization data.
9. The software modeling method based on software metamodel according to claim 8, characterized in that: Step S444 is specifically as follows: Extracting the hardness characteristics and thickness characteristics of the delivery box material data, thereby obtaining the hardness data and thickness data of the delivery box material data; Perform hardness characteristic analysis on the delivery box material data to obtain material hardness characteristic data; Perform thickness characteristic analysis on the delivery box material data to obtain material thickness characteristic data; Perform pressure resistance analysis based on material hardness characteristic data and material thickness characteristic data to obtain the pressure resistance data of the delivery box material; Perform meal delivery simulation based on the pressure resistance data of the delivery box material and the order delivery box loading data, thereby obtaining meal delivery simulation data; The meal damage simulation data is extracted from the meal delivery simulation data, thereby obtaining the meal damage simulation data.
10. The software modeling method based on software metamodel according to claim 1, characterized in that: Step S5 is specifically as follows: Step S51: Designing a meal ordering software architecture according to the meal ordering processing system optimization data, thereby obtaining meal ordering software architecture data; Step S52: performing concurrent user load testing on the ordering software architecture data, thereby obtaining software architecture concurrent user load testing data; Step S53: performing error frequency statistics on the software architecture concurrent user load test data, thereby obtaining software architecture load high-frequency error data; Step S54: Sorting the severity of the software architecture load high-frequency error data, thereby obtaining architecture high-frequency error severity sorting data; Step S55: performing code repair strategy analysis according to the architecture high-frequency error severity ranking data, thereby obtaining an architecture repair strategy; Step S56: Optimize the software metamodel architecture according to the architecture repair strategy to obtain an optimized metamodel of the meal ordering software, and upload it to the online meal ordering cloud platform to execute the software metamodel optimization task.
Citation Information
Patent Citations
Intelligent restaurant control system and control method
CN112508739A
Abnormal order processing method and device, electronic equipment and storage medium
CN113408783A
Take-out delivery time prediction method based on communication network
CN114819389A
Take-out service AI intelligent prediction method
CN115063164A
Method and apparatus for intelligent operation management of infrastructure
US20220043703A1
