Model specification checking method and device, equipment, storage medium and program product
The model specification checking method addresses inefficiencies in existing compliance checks by employing automated, rule-based inspections tailored to user roles, ensuring timely and accurate model compliance verification.
Patent Information
- Application Number
- CN202411249772.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-06
- Publication Date
- 2024-12-13
AI Technical Summary
Existing model-based software development methods lack efficiency and specificity in compliance checks, primarily relying on verifying model outputs without adequate adherence to standards and regulations.
A model specification checking method that performs automated checks using pre-configured rules, including standard model name and hierarchical label data, to generate comprehensive and targeted inspection results, supporting scheduled and manual triggers, and personalized dimension selection based on user roles.
Enhances the efficiency and relevance of model specification checking by ensuring compliance with standards, reducing human error, and providing real-time, accurate feedback for model improvement.
Smart Images
Figure CN119127301A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of software technology, and in particular to a model specification checking method, apparatus, device, storage medium and program product. Background Art
[0002] Today, model-based software development has gradually replaced traditional manual code development in product development across various industries. Building models requires adherence to relevant standards and regulations, necessitating compliance checks. Existing model testing methods primarily verify the functionality of the model under test by passing parameters to the model and then verifying the model's output. However, model compliance checks are inefficient and lack specificity.
[0003] The above content is only used to assist in understanding the technical solution of this application and does not constitute an admission that the above content is prior art. Summary of the Invention
[0004] The main purpose of this application is to provide a model specification checking method, device, equipment, storage medium and program product, aiming to solve the technical problems of low efficiency and poor pertinence of model specification checking.
[0005] To achieve the above objectives, the present application proposes a model specification checking method, which includes:
[0006] In response to the model specification checking task, obtaining specification checking dimension data;
[0007] Based on the pre-configured specification checking rules, a specification checking is performed on the corresponding test design model according to the specification checking dimension data to generate a model specification checking result.
[0008] In one embodiment, before the step of performing a specification check on the corresponding test design model based on the specification check dimension data based on the preconfigured specification check rules and generating the model specification check result, the step further includes:
[0009] Based on a preset standard specification file, the specification checking rules are configured and generated.
[0010] In one embodiment, the standard specification file includes a standard model name list and standard hierarchical label data. The step of configuring and generating the standard checking rule based on the preset standard specification file includes:
[0011] Based on the standard model name list, configure and generate model name checking rules;
[0012] Based on the standard hierarchical label data, configure and generate model label checking rules;
[0013] The specification checking rules are generated according to the model name checking rules, model label checking rules, preset model description checking rules, and baseline library checking rules.
[0014] In one embodiment, the model specification check result is a first model specification check result, and the step of performing a specification check on the corresponding test design model according to the specification check dimension data based on a preconfigured specification check rule to generate the model specification check result includes:
[0015] When the specification check dimension data is test task dimension data, determining that the test design model associated with the test task is a first model according to the test task name data and the production task name data in the test task dimension data;
[0016] Perform a standard check on the first model according to the standard check rule to generate a standard check result of the first model.
[0017] In one embodiment, the model specification check result is a second model specification check result, and the step of performing a specification check on the corresponding test design model according to the specification check dimension data based on a preconfigured specification check rule to generate the model specification check result includes:
[0018] When the specification check dimension data is business product dimension data, determining that the test design model associated with the business product is the second model according to the business product name data in the business product dimension data and the model screening condition;
[0019] Perform a standard check on the second model according to the standard check rule to generate a standard check result for the second model.
[0020] In one embodiment, the model specification checking task is a scheduled checking task / manually triggered checking task. After the step of performing a specification checking on the corresponding test design model based on the specification checking dimension data based on pre-configured specification checking rules and generating a model specification checking result, the following steps are further included:
[0021] When the model specification inspection task is the scheduled inspection task, obtaining authority data of the person in charge;
[0022] Based on the authority data of the person in charge and according to the model specification check result, a prompt message is generated and sent to the preset terminal of the person in charge.
[0023] In addition, to achieve the above-mentioned purpose, the present application also proposes a model specification checking device, which includes:
[0024] a data acquisition module, configured to acquire specification check dimension data in response to a model specification check task;
[0025] The specification checking module is used to perform a specification check on the corresponding test design model based on the pre-configured specification checking rules and the specification checking dimension data, and generate a model specification checking result.
[0026] In addition, to achieve the above-mentioned purpose, the present application also proposes a model specification checking device, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the computer program is configured to implement the steps of the model specification checking method described above.
[0027] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium and stores a computer program. When the computer program is executed by a processor, the steps of the model specification checking method described above are implemented.
[0028] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps of the model specification checking method as described above are implemented.
[0029] The present application provides a model specification checking method, which can perform automated specification checking on the test design model through specification checking rules. By standardizing the checking dimension data, the corresponding dimensions can be selected according to user needs or roles to perform model specification checking, solving the problems of low efficiency and poor pertinence of model specification checking in the existing technology, and improving the efficiency and pertinence of model specification checking. BRIEF DESCRIPTION OF THE DRAWINGS
[0030] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0031] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following is a brief introduction to the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0032] Figure 1 A flowchart of the first embodiment of the model specification checking method of this application is provided;
[0033] Figure 2 A schematic diagram of performing model specification checking on the test task dimension provided in the first embodiment of the model specification checking method of this application;
[0034] Figure 3 A schematic diagram of performing model specification checking on the business product dimension provided in the first embodiment of the model specification checking method of this application;
[0035] Figure 4 A schematic diagram of the first prompt information provided in Example 1 of the model specification checking method of this application;
[0036] Figure 5 A schematic diagram of the second prompt information provided in Example 1 of the model specification checking method of this application;
[0037] Figure 6 A schematic diagram of the third prompt information provided in Example 1 of the model specification checking method of this application;
[0038] Figure 7 A schematic diagram of online query of model specification checking results provided in Example 1 of the model specification checking method of this application;
[0039] Figure 8 A flowchart of the second embodiment of the model specification checking method of this application is provided;
[0040] Figure 9 This is a schematic diagram of the module structure of the model specification checking device according to an embodiment of the present application;
[0041] Figure 10 Schematic diagram of the device structure of the hardware operating environment involved in the model specification checking method in the embodiment of the present application.
[0042] The purpose, features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0043] It should be understood that the specific embodiments described herein are merely used to explain the technical solutions of the present application and are not intended to limit the present application.
[0044] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0045] The main solutions of the embodiments of this application are:
[0046] In response to the model specification checking task, obtaining specification checking dimension data;
[0047] Based on the pre-configured specification checking rules, a specification checking is performed on the corresponding test design model according to the specification checking dimension data to generate a model specification checking result.
[0048] In the prior art, the model testing method mainly verifies the function of the model to be tested by verifying the model output after inputting parameters into the model to be tested. Therefore, the efficiency of model specification checking is low and the pertinence is poor.
[0049] The present application provides a solution that can perform automated specification checking on test design models through specification checking rules. By standardizing and checking dimensional data, corresponding dimensions can be selected according to user needs or roles for model specification checking. This solves the problems of low efficiency and poor pertinence of model specification checking in the existing technology, and improves the efficiency and pertinence of model specification checking.
[0050] It should be noted that the execution subject of this embodiment may be a computing service device with data processing, network communication, and program execution capabilities, such as a tablet computer, personal computer, mobile phone, etc., or an electronic device capable of implementing the aforementioned functions, a model specification checking system, etc. This embodiment and the following embodiments will be described below using the model specification checking system as an example.
[0051] Based on this, the embodiment of the present application provides a model specification checking method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the model specification checking method of this application.
[0052] In this embodiment, the model specification checking method includes steps S10 to S20:
[0053] Step S10, in response to the model specification check task, obtaining specification check dimension data;
[0054] The model specification checking system obtains specification checking dimension data in response to the model specification checking task.
[0055] For example, there are two types of model specification check tasks: scheduled check tasks and manually triggered check tasks. The corresponding methods are scheduled task triggering and manual triggering. The details of the two methods are as follows:
[0056] a) Scheduled task triggering:
[0057] In order to ensure the completeness of all test task checks, this system regularly obtains test tasks of all execution stages through scheduled tasks, and then obtains all associated test design model diagrams based on the test tasks of the execution stage and performs a full specification check.
[0058] b) Manual trigger:
[0059] Since the standard inspection of scheduled tasks is automatically triggered regularly in the background, users cannot obtain the latest real-time inspection results. Therefore, in order to meet real-time requirements, the function of manual triggering of inspections by users is implemented. Users can trigger standard inspections at any time as needed and obtain the latest inspection results.
[0060] Step S20 , based on the pre-configured specification checking rules, a specification checking is performed on the corresponding test design model according to the specification checking dimension data to generate a model specification checking result.
[0061] The model specification checking system is based on pre-configured specification checking rules and performs specification checking on the corresponding test design model according to the specification checking dimension data to check whether it meets the predetermined specification requirements. It generates model specification checking results, indicates whether the model meets the specifications, and lists any parts or problems that do not meet the specifications, providing a basis for subsequent model improvement or correction, ensuring that the model meets the design standards during the implementation or use stage.
[0062] It should be noted that specification checking rules are pre-defined standards or criteria used to evaluate whether the model meets the requirements. These rules may include design standards, technical specifications, industry best practices, etc., which can ensure that the checking process is consistent and systematic and avoid subjectivity.
[0063] For example, the model specification check results can support queries based on product name, task name, model name, and whether all are compliant. The inspection result list includes task name, production, model name, product name, business automation, interface automation, naming check, label check, version check, baseline check, whether all are compliant, and operation link; among them, naming check, label check, version check, and baseline check correspond to the four rules of specification check, business automation and interface automation are statistics on model automation implementation. Click on the model to view to open the specific model request page, and you can quickly adjust the model for non-compliant items.
[0064] In a feasible implementation, the model specification check result is a first model specification check result, and step S20 may include steps S2011 to S2012:
[0065] Step S2011: when the specification check dimension data is test task dimension data, determining that the test design model associated with the test task is a first model based on the test task name data and the production task name data in the test task dimension data;
[0066] Step S2012: Perform a standard check on the first model according to the standard check rule to generate a standard check result of the first model.
[0067] When the specification check dimension data is test task dimension data, the model specification check system determines that the test design model associated with the test task is the first model based on the test task name data and the production task name data in the test task dimension data, and then performs a specification check on the first model according to the specification check rules. The inspection content may include multiple dimensions such as the model's design compliance, implementation details, performance requirements, etc., and generates the first model specification check results, which usually include compliance assessment, existing problems, improvement suggestions, etc.
[0068] In this embodiment, when the specification inspection dimension data is the test task dimension data, the test design model associated with the test task is determined to be the first model based on the test task name data and the production task name data in the test task dimension data; according to the specification inspection rules, the first model is subjected to a specification inspection, and the specification inspection results of the first model are generated. Through accurate model identification and specification inspection, problems in the design or implementation can be discovered in a timely manner to ensure that the model meets the expected standards. The specification inspection helps to improve the design quality of the model, reduce potential risks and defects, and the detailed inspection results provide a basis for improvement, promote model optimization and adjustment, and at the same time, by accurately locating the model from the test task dimension data and combining the specification inspection rules, the model is comprehensively evaluated to ensure the systematicity, comprehensiveness and consistency of the specification inspection.
[0069] In another feasible implementation, the model specification check result is a second model specification check result, and step S20 may include steps S2021 to S2022:
[0070] Step S2021: When the specification check dimension data is business product dimension data, determining that the test design model associated with the business product is a second model based on the business product name data in the business product dimension data and the model screening condition;
[0071] Step S2022: Perform a standard check on the second model according to the standard check rule to generate a standard check result for the second model.
[0072] When the specification check dimension data is business product dimension data, the model specification check system filters the test design model associated with the business product as the second model based on the business product name data and model screening conditions (such as specific business needs or project requirements) in the business product dimension data, and then performs a specification check on the second model according to the specification check rules to generate the second model specification check result.
[0073] In this embodiment, when the specification check dimension data is business product dimension data, the test design model associated with the business product is determined to be the second model based on the business product name data and model screening conditions in the business product dimension data; according to the specification check rules, the second model is subjected to a specification check to generate a specification check result for the second model, and business-related models are screened out through the business product dimension data. The non-compliant parts of the model are identified and improved through systematic specification checks, and the inspection speed is improved through automated tools or efficient screening methods, thereby ensuring that the selected test design model is highly relevant to the business product and ensuring that it complies with the standards through specification checks, thereby improving the efficiency and accuracy of model checks and reducing the workload of manual inspections.
[0074] For example, the dimensions of model specification checking include test task dimension and business product dimension. Users can select appropriate dimensions according to their personal roles or specific needs. Figure 2 and Figure 3 , Figure 2 Schematic diagram of model specification checking for the test task dimension provided in the first embodiment of the model specification checking method of this application, Figure 3 This is a schematic diagram of model specification checking in the business product dimension provided in the first embodiment of the model specification checking method of this application. The specific introduction of model specification checking in the two dimensions is as follows:
[0075] a) Test task dimension:
[0076] Users can trigger a specification check of all associated test design model diagrams under the test production task by entering the test task name and production name. Based on the test task dimension, it supports entering multiple test tasks at the same time to trigger the check synchronously.
[0077] b) Business product dimension:
[0078] This tool also supports business product-based model diagram compliance checking. This method primarily filters model diagrams within a business product based on the business product name and user-entered model filter criteria, and then performs compliance checking on the results. Filter criteria include: model name, model tag, update user, and update time range. This allows compliance checking of models within a specified range within a business product.
[0079] In another feasible implementation, the model specification check task is a scheduled check task / manually triggered check task. After step S20, steps S301 to S302 may be further included:
[0080] Step S301, when the model specification inspection task is the scheduled inspection task, obtaining the authority data of the person in charge;
[0081] Step S302: Based on the authority data of the person in charge and the result of the model specification check, a prompt message is generated and sent to a preset terminal of the person in charge.
[0082] When the model specification check task is a scheduled check task, the model specification check system queries the permission data of the relevant person in charge according to the task settings. This usually involves obtaining data from the permission database or directory service and checking the obtained permission data to ensure that the person in charge has the permission to view or process the results of the scheduled check task, obtain the person in charge's permission data, and then extract key issues, exceptions or important notifications from the model specification check results based on the person in charge's permission data, and summarize the inspection results into concise and clear prompt information, including necessary details and suggestions, and finally send the prompt information to the preset responsible person terminal.
[0083] For example, for the standard inspection results triggered by the scheduled inspection task, the notification will be classified and summarized according to different user permissions. Figure 4 、 Figure 5 and Figure 6 , Figure 4 This is a schematic diagram of the first prompt information provided in Example 1 of the model specification checking method of this application. Figure 5 This is a schematic diagram of the second prompt information provided in Example 1 of the model specification checking method of this application. Figure 6 This is a schematic diagram of the third prompt information provided in Example 1 of the model specification checking method of this application.
[0084] For the test leader, the model specification check results of all execution stages under the test leader's responsibility will be summarized and a prompt message will be sent to the test leader;
[0085] For the test team leader, the model specification check results of all execution phase test tasks of the team will be summarized and notified;
[0086] For the room manager role, the model specification check results of the execution phase test tasks corresponding to each group in the room will be summarized and notified.
[0087] In addition, refer to Figure 7 , Figure 7 This is a schematic diagram of online query of model specification checking results provided in Example 1 of the model specification checking method of this application. When the model specification checking task is a manually triggered checking task, the system supports online query of model specification checking results.
[0088] In this embodiment, when the specification inspection dimension data is business product dimension data, the test design model associated with the business product is determined to be the second model based on the business product name data and model screening conditions in the business product dimension data; according to the specification inspection rules, the second model is subjected to a specification inspection, and the specification inspection results of the second model are generated, ensuring that the model specification inspection results are communicated to relevant personnel in a timely manner, improving processing efficiency, and ensuring information security and compliance by obtaining and verifying authority data. The generated prompt information provides accurate feedback based on the actual inspection results to support improvement measures. At the same time, the automated notification process reduces manual intervention, avoids delays in information transmission, ensures that only appropriate personnel receive sensitive information, reduces the risk of unauthorized access, and improves the efficiency and accuracy of inspection result processing through clear prompt information and multi-channel notifications.
[0089] This embodiment provides a model specification checking method, which can perform automated specification checking on the test design model through specification checking rules. By standardizing the checking dimension data, the corresponding dimensions can be selected according to user needs or roles to perform model specification checking, which solves the problems of low efficiency and poor pertinence of model specification checking in the existing technology, and improves the efficiency and pertinence of model specification checking.
[0090] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above embodiment 1 can be referred to the above introduction and will not be described in detail later. Figure 8 Before step S20, the model specification checking method further includes step S40:
[0091] Step S40: Based on a preset standard specification file, configure and generate the specification checking rules.
[0092] The model specification checking system determines and obtains the standard specification files used for specification checking. The files may include industry standards, internal company standards or other relevant specifications. It then extracts the various requirements and rules of the standard specifications from the files and converts the extracted requirements into specific rules and parameters that can be used for checking. Finally, it obtains the rule configuration, including the rule name, rule description and specific inspection conditions. According to the standards in the specification file, it defines the specific values or ranges of the inspection parameters to obtain the specification checking rules.
[0093] In a feasible implementation, the standard specification file includes a standard model name list and standard hierarchical label data, and step S40 may include steps S401 to S403:
[0094] Step S401, configuring and generating model name checking rules based on the standard model name list;
[0095] Step S402: configuring and generating model label checking rules based on the standard hierarchical label data;
[0096] Step S403 : generating the specification checking rules according to the model name checking rules, the model label checking rules, the preset model description checking rules, and the baseline library checking rules.
[0097] The model specification checking system extracts all relevant specifications from the standard model name list, which may include format requirements, naming conventions or character restrictions. Then, these specifications are converted into checking rules to ensure that each generated model name complies with these standards and generate model name checking rules. Then, all relevant specifications are extracted from the standard hierarchical label data, which may include format requirements and hierarchical structure restrictions and generate model label checking rules. Finally, the model name checking rules, model label checking rules and preset model description checking rules and baseline library checking rules are summarized to distinguish their intersections and potential conflicts, ensuring that all rules can be effectively applied when generating specification checking rules. Priorities are set according to the relative importance and scope of application of the rules to determine which rules should be checked first and generate specification checking rules.
[0098] It should be noted that the standard model name list is a collection of valid model names that comply with specific industry standards or organizational requirements. The list may come from industry standard documents, naming conventions within the organization, or historical data; standard hierarchical label data is a labeling system defined by an organization or industry, in which labels are classified and organized according to a hierarchical relationship. This data usually comes from industry standards, data standard documents within the organization, or labeling systems.
[0099] For example, a feasible implementation of step S402 is as follows:
[0100] 1. Hierarchical consistency:
[0101] Rule definition: Set specific hierarchical relationships, such as "Main Category" must have at least one subcategory.
[0102] Validation logic:
[0103] Main Category Check: Make sure that each Main Category has at least one Sub Category.
[0104] Subcategory Check: Verifies that there is at least one Attribute under each Subcategory.
[0105] Data structure verification: The automated script traverses the tree structure of the tag data to check whether the hierarchy meets the requirements.
[0106] 2. Tag uniqueness:
[0107] Rule definition: Ensure that tag names within the same level are unique.
[0108] Validation logic:
[0109] Uniqueness check: Write a script to find duplicate tags at the same level, for example use a set or hash table to store the tags and detect duplicates.
[0110] Conflict Report: Generate a report listing duplicate labels and their locations for easy correction.
[0111] 3. Format specification:
[0112] Rule definition: specifies format requirements, such as allowed character sets, maximum length, naming rules, etc.
[0113] Validation logic:
[0114] Format validation: Use regular expressions to check whether the label meets the character set and length requirements.
[0115] Naming convention check: Make sure that the tag names follow naming conventions, such as not containing special characters or spaces.
[0116] 4. Implementation rules:
[0117] Rule configuration:
[0118] Rule engine configuration: Enter the defined rules into the rule engine and configure the execution order and conditions of the rules.
[0119] Custom script development: Develop and deploy scripts to implement rule-checking logic, such as using Python or JavaScript.
[0120] System integration: Integrate the rule engine or script into the existing data processing system to ensure that it can automatically perform rule checks.
[0121] 5. Integration testing:
[0122] Test case design: Design test cases, including normal data and abnormal data, to ensure that the rules cover all possible scenarios.
[0123] Test execution: Run test cases to verify that the rule engine or script correctly identifies tags that do and do not meet the specifications.
[0124] Problem fixing: Fix problems found based on test results, adjust rule configuration or script logic, and optimize the accuracy and reliability of rules.
[0125] In this implementation, comprehensive specification checking rules are configured and generated based on the preset standard specification file to ensure that the generated model names and labels meet the preset standards, reduce inconsistencies and errors, and ensure that all aspects of the model are checked by integrating various rules, thereby improving the comprehensiveness and effectiveness of the inspection.
[0126] Exemplarily, the specification checking rules include the following:
[0127] 1. Model name checking rules: The business meaning of the model diagram must be distinguishable, such as: XXX full process, XXX business process, XXX business function XXX business rule, XXX business logic, XXX scheduled task, XXX interface.
[0128] 2. Model label checking rules: at least include labels used to distinguish layers, such as L0, L1, L2, etc.
[0129] 3. Model description check rule: Model version description cannot be empty.
[0130] 4. Baseline library check rules: Each image must have a baseline version.
[0131] Among them, the model description check rules and baseline library check rules are fixed rules, while the model name check rules and model label check rules will be adjusted with the product. In order to meet product adjustment requirements, the model name check rules and model label check rules are managed through standard specification files to ensure that they can be adjusted quickly at any time.
[0132] Accordingly, the logic of model specification checking through specification checking rules is as follows:
[0133] Model naming check: Get the model name and determine whether the model name ends with the standard name in the name_standard list in the configuration file. If it does, it is partially standardized; otherwise, it does not meet the standards.
[0134] Model label check: Get the model label and determine whether the label contains the hierarchical label corresponding to level_tag_standard in the configuration file. If it does, it complies with the standard; otherwise, it does not comply with the standard.
[0135] Model description check: Parse and obtain model description information. If the model description information is empty, it does not comply with the specification; otherwise, it complies with the specification.
[0136] Baseline library check: parse the model information to see if the model has a baseline version. If no baseline version exists, the model does not comply with the specification; otherwise, it complies with the specification.
[0137] In this embodiment, based on the preset standard specification file, the specification inspection rules are configured and generated, and the effective application of the standard specification file is realized. Through systematic rule configuration and verification, the accuracy and consistency of the specification inspection are ensured, which can effectively eliminate human errors in the specification inspection, improve inspection efficiency and accuracy, and ensure that the inspection system meets the latest standard requirements.
[0138] For example, the model specification checking method obtained by combining the first embodiment and the second embodiment has the following advantages over the prior art:
[0139] (2) It provides two dimensions for screening test design models: test tasks and business products. Users can choose appropriate dimensions based on their personal roles or needs, which solves the problem of rapid screening and confirmation of inspection models for different user roles and different inspection scenarios, and effectively improves the efficiency of inspection model range screening.
[0140] (3) Two methods of triggering model specification checks are provided: scheduled tasks and manual triggering. Scheduled tasks will automatically perform specification checks on test tasks in the execution phase on a regular basis, thereby solving the problem of users missing trigger checks or having to manually trigger checks, and avoiding omissions in test task specification checks; manual triggering, as a supplementary method of scheduled task triggering, can support users to manually trigger specification checks, thereby ensuring that users can perform specification checks at any time and obtain real-time specification check results, solving the problem of omissions or non-real-time specification checks.
[0141] (4) The model specification inspection results are summarized and notified to users with different permissions. The inspection results of all test tasks are summarized and notified to the test leader. The inspection results of all test tasks in the group are summarized and notified to the team leader. The inspection results of all test tasks in the room are summarized and notified to the office manager according to the group to which he belongs, thus solving the problem of user management scope inspection with different permissions.
[0142] (5) The standard check of model names is managed through standard specification files, which can be adjusted according to the latest specification requirements, solving the problem of rapid changes in name standard check rules.
[0143] (6) Since the triggering method of the specification check and the notification method of the inspection results are all implemented in a unified logic, the specific dimensions of the model specification check can be added or reduced as needed, thus solving the scalability problem of the specification check dimensions.
[0144] (7) The check result list displays all model records and includes a link to the model address. Clicking the link allows users to quickly jump to the model interface for adjustment, effectively simplifying the steps for users to query based on the model name and then open the model interface.
[0145] It should be noted that the above examples are only used to understand this application and do not constitute a limitation on the model specification checking method of this application. More simple transformations based on this technical concept are all within the scope of protection of this application.
[0146] This application also provides a model specification checking device, please refer to Figure 9 , the model specification checking device includes:
[0147] A data acquisition module 10 is configured to acquire specification check dimension data in response to a model specification check task;
[0148] The specification checking module 20 is used to perform a specification check on the corresponding test design model based on the pre-configured specification checking rules and the specification checking dimension data, and generate a model specification checking result.
[0149] Optionally, before the step of performing a specification check on the corresponding test design model based on the specification check dimension data based on the pre-configured specification check rules and generating the model specification check result, the step further includes:
[0150] Based on a preset standard specification file, the specification checking rules are configured and generated.
[0151] Optionally, the standard specification file includes a standard model name list and standard hierarchical label data, and the step of configuring and generating the standard checking rule based on the preset standard specification file includes:
[0152] Based on the standard model name list, configure and generate model name checking rules;
[0153] Based on the standard hierarchical label data, configure and generate model label checking rules;
[0154] The specification checking rules are generated according to the model name checking rules, model label checking rules, preset model description checking rules, and baseline library checking rules.
[0155] Optionally, the model specification checking result is a first model specification checking result, and the specification checking module 20 is further configured to:
[0156] When the specification check dimension data is test task dimension data, determining that the test design model associated with the test task is a first model according to the test task name data and the production task name data in the test task dimension data;
[0157] Perform a standard check on the first model according to the standard check rule to generate a standard check result of the first model.
[0158] Optionally, the model specification checking result is a second model specification checking result, and the specification checking module 20 is further configured to:
[0159] When the specification check dimension data is business product dimension data, determining that the test design model associated with the business product is the second model according to the business product name data in the business product dimension data and the model screening condition;
[0160] Perform a standard check on the second model according to the standard check rule to generate a standard check result for the second model.
[0161] Optionally, the model specification checking task is a scheduled checking task / manually triggered checking task. After the step of performing a specification checking on the corresponding test design model based on the specification checking dimension data based on pre-configured specification checking rules and generating the model specification checking result, the step further includes:
[0162] When the model specification inspection task is the scheduled inspection task, obtaining authority data of the person in charge;
[0163] Based on the authority data of the person in charge and according to the model specification check result, a prompt message is generated and sent to the preset terminal of the person in charge.
[0164] The model specification checking device provided in this application, which utilizes the model specification checking method of the aforementioned embodiment, can address the technical issues of low efficiency and poor targeting of model specification checking. Compared to the prior art, the beneficial effects of the model specification checking device provided in this application are the same as those of the model specification checking method provided in the aforementioned embodiment, and the other technical features of the model specification checking device are the same as those disclosed in the aforementioned embodiment method, and are not further described here.
[0165] The present application provides a model specification checking device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the model specification checking method in the above-mentioned embodiment one.
[0166] Reference below Figure 10, which shows a schematic diagram of the structure of a model specification checking device suitable for implementing the embodiments of the present application. The model specification checking device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 10 The model specification checking device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.
[0167] like Figure 10 As shown, the model specification checking device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. RAM 1004 also stores various programs and data required for the operation of the model specification checking device. Processing device 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input device 1007 including, for example, a touch screen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output device 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage device 1003 including, for example, a magnetic tape, hard disk, etc.; and communication device 1009. The communication device 1009 can allow the model specification checking device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a model specification checking device with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems may be implemented or have alternatively.
[0168] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0169] The model specification checking device provided in this application, which utilizes the model specification checking method of the aforementioned embodiment, can address the technical issues of low efficiency and poor targeting of model specification checking. Compared to the prior art, the beneficial effects of the model specification checking device provided in this application are the same as those of the model specification checking method provided in the aforementioned embodiment. The other technical features of the model specification checking device are the same as those disclosed in the aforementioned embodiment and are not further elaborated here.
[0170] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any one or more embodiments or examples in a suitable manner.
[0171] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
[0172] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, a computer program) stored thereon, wherein the computer-readable program instructions are used to execute the model specification checking method in the above embodiment.
[0173] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.
[0174] The computer-readable storage medium may be included in the model specification checking device, or may exist independently without being assembled into the model specification checking device.
[0175] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the model specification checking device, the model specification checking device:
[0176] In response to the model specification checking task, obtaining specification checking dimension data;
[0177] Based on the pre-configured specification checking rules, a specification checking is performed on the corresponding test design model according to the specification checking dimension data to generate a model specification checking result.
[0178] Computer program code for performing the operations of the present application may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).
[0179] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, program segment or part of code, and the module, program segment or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, as well as the combination of boxes in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or can be implemented using a combination of dedicated hardware and computer instructions.
[0180] The modules described in the embodiments of the present application may be implemented in software or hardware, wherein the name of a module does not necessarily limit the unit itself.
[0181] The computer-readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the aforementioned model specification checking method. This computer-readable storage medium can address the technical issues of low efficiency and poor targeting of model specification checking. Compared to the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the model specification checking method provided in the aforementioned embodiment, and are not further elaborated here.
[0182] The present application also provides a computer program product, comprising a computer program, which implements the steps of the above-mentioned model specification checking method when executed by a processor.
[0183] The computer program product provided in this application can solve the technical problems of low efficiency and poor pertinence in model specification checking. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the model specification checking method provided in the above embodiment, and will not be repeated here.
[0184] The above description is only part of the embodiments of the present application and does not limit the patent scope of the present application. All equivalent structural transformations made by using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.
Claims
1. A model specification checking method, characterized in that: The method comprises: In response to the model specification checking task, obtaining specification checking dimension data; Based on the pre-configured specification checking rules, a specification checking is performed on the corresponding test design model according to the specification checking dimension data to generate a model specification checking result.
2. The method according to claim 1, characterized in that Before the step of performing a specification check on the corresponding test design model based on the pre-configured specification check rule and the specification check dimension data to generate a model specification check result, the step further includes: Based on a preset standard specification file, the specification checking rules are configured and generated.
3. The method according to claim 2, characterized in that The standard specification file includes a standard model name list and standard hierarchical label data. The step of configuring and generating the specification checking rule based on the preset standard specification file includes: Based on the standard model name list, configure and generate model name checking rules; Based on the standard hierarchical label data, configure and generate model label checking rules; The specification checking rules are generated according to the model name checking rules, model label checking rules, preset model description checking rules, and baseline library checking rules.
4. The method according to claim 1, characterized in that The model specification check result is a first model specification check result. The step of performing a specification check on the corresponding test design model based on the pre-configured specification check rule and the specification check dimension data to generate the model specification check result includes: When the specification check dimension data is test task dimension data, determining that the test design model associated with the test task is a first model according to the test task name data and the production task name data in the test task dimension data; According to the specification checking rule, a specification checking is performed on the first model to generate a specification checking result of the first model.
5. The method according to claim 1, characterized in that The model specification check result is a second model specification check result. The step of performing a specification check on the corresponding test design model based on the pre-configured specification check rule and the specification check dimension data to generate the model specification check result includes: When the specification check dimension data is business product dimension data, determining the test design model associated with the business product as the second model according to the business product name data and the model screening condition in the business product dimension data; According to the specification checking rule, a specification checking is performed on the second model to generate a specification checking result of the second model.
6. The method according to claim 1, characterized in that The model specification checking task is a scheduled checking task / manually triggered checking task. The step of performing a specification checking on the corresponding test design model based on the pre-configured specification checking rule and the specification checking dimension data, and generating the model specification checking result further includes: When the model specification inspection task is the scheduled inspection task, obtaining authority data of the person in charge; Based on the authority data of the responsible person and according to the model specification check result, a prompt message is generated and sent to a preset responsible person terminal.
7. A model specification checking device, characterized in that: The device comprises: A data acquisition module, for acquiring specification checking dimension data in response to a model specification checking task; The specification checking module is used to perform a specification check on the corresponding test design model based on the pre-configured specification checking rules and the specification checking dimension data, and generate a model specification checking result.
8. A model specification checking device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the model specification checking method according to any one of claims 1 to 6.
9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the model specification checking method according to any one of claims 1 to 6 are implemented.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the model specification checking method according to any one of claims 1 to 6 are implemented.