Rule engine-based cloud platform interface design walkthrough method and system

By building a standardized check rule library based on the rule engine, analyzing and matching the interface design files, solving the problems of low efficiency and insufficient accuracy of interface design checks in the existing technology, and realizing the automation of cloud platform interface design and Intelligent, improving interface quality and user experience.

CN119065968APending Publication Date: 2024-12-03CHINA ELECTRONICS CLOUD DIGITAL INTELLIGENCE TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411096720.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-12
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The existing cloud platform interface design check method is inefficient and easy to miss details. It is difficult for automation tools to fully cover design defects, making it difficult to detect and correct user experience problems in a timely manner.

Method used

Using a rule engine-based method, a standardized check rule library is built, and the information to be checked is extracted by analyzing the interface design file, matching it with the rule library, generating a check result report, and realizing automated and intelligent interface design inspection.

Benefits of technology

It significantly improves the efficiency and accuracy of walk-in, reduces the dependence on manual intervention, shortens the design feedback cycle, and improves interface quality and user satisfaction.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119065968A_ABST
    Figure CN119065968A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of interface walkthrough, and provides a cloud platform interface design walkthrough method and system based on a rule engine, and the method comprises the steps: constructing a walkthrough rule according to a category, standardizing the constructed walkthrough rule, and constructing a rule base according to the standardized walkthrough rule and creation information; the method comprises the following steps: collecting a cloud platform interface design file, extracting interface to-be-walked information by analyzing the cloud platform interface design file, and storing the extracted interface to-be-walked information; and matching the extracted interface to-be-walked information with the constructed rule base through a rule engine, and constructing a cloud platform interface design walked result report according to a matching result. According to the rule engine-based cloud platform interface design walkthrough method and system, the walkthrough efficiency and accuracy can be remarkably improved, the design feedback period is remarkably shortened, and powerful support is provided for quality control and iterative optimization of cloud platform interface design.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of interface walkthrough, and in particular to a cloud platform interface design walkthrough method and system based on a rule engine. Background Art

[0002] With the widespread application of cloud products and the increasing requirements of users for interface friendliness and ease of use, the importance of cloud platform interface design walkthrough, as a key link to ensure user experience and interface quality, has become increasingly prominent. Through a comprehensive and detailed walkthrough process, design defects and potential user experience issues can be discovered and corrected in a timely manner before the function is officially launched.

[0003] Currently, although cloud platform interface design walkthroughs have been generally incorporated into the development process, they mainly rely on designers to manually check whether design elements meet specifications. The shortcomings of this method are low efficiency and easy to miss details. On the other hand, although automated walkthrough tools can improve efficiency, they are often limited by the limitations of preset rules and it is difficult to fully cover and accurately identify all design defects.

[0004] Therefore, how to provide a cloud platform interface design walkthrough method that can improve the efficiency and accuracy of the walkthrough while reducing dependence on manual intervention, making the interface design walkthrough more intelligent and automated, and improving the overall competitiveness and user satisfaction of the cloud platform has become a technical problem that needs to be solved urgently. Summary of the invention

[0005] In view of this, in order to overcome the deficiencies of the prior art, the present invention aims to provide a cloud platform interface design walkthrough method and system based on a rule engine.

[0006] According to a first aspect of the present invention, a cloud platform interface design walkthrough method based on a rule engine is provided, the method comprising:

[0007] Construct walkthrough rules by category, standardize the constructed walkthrough rules, and construct a rule base based on the standardized walkthrough rules and creation information;

[0008] Collect cloud platform interface design files, extract interface information to be checked by parsing the cloud platform interface design files, and save the extracted interface information to be checked;

[0009] The extracted interface information to be checked is matched with the constructed rule base through the rule engine, and a cloud platform interface design check result report is constructed based on the matching results.

[0010] Preferably, in the cloud platform interface design walkthrough method based on the rule engine of the present invention, walkthrough rules are constructed by category and the constructed walkthrough rules are standardized, including: constructing layout type walkthrough rules, color type walkthrough rules, text type walkthrough rules and interaction type walkthrough rules, and the walkthrough rules are standardized by setting a unified data format for the walkthrough rules. The walkthrough rules are composed of a rule coding field, a rule classification field, a rule name field, a rule description field, a trigger condition field, a check logic field and an expected result field.

[0011] Preferably, in the cloud platform interface design walkthrough method based on the rule engine of the present invention, the walkthrough rules are standardized by setting a unified data format for the walkthrough rules, including: setting the type of the rule coding field to int, setting the types of the rule classification field and the rule name field to varchar, and setting the types of the rule description field, trigger condition field, check logic field, and expected result field to text.

[0012] Preferably, in the cloud platform interface design walkthrough method based on the rule engine of the present invention, a rule base is constructed according to the standardized walkthrough rules and creation information, including: constructing a rule base by storing the standardized walkthrough rules and the creation time, creator, update time and updater field information of the walkthrough rules in a database.

[0013] Preferably, in the cloud platform interface design walkthrough method based on the rule engine of the present invention, cloud platform interface design files are collected, and interface information to be walked through is extracted by parsing the cloud platform interface design files, including: collecting HTML files, CSS files and JavaScript files corresponding to the cloud platform interface, identifying and extracting the layout elements of the interface, the nested relationship between the layout elements and the text elements by parsing the HTML files, extracting the style attributes of the interface elements and the color style attributes of the interface by parsing the CSS files, and extracting the interactive behavior logic of the interface elements by parsing the JavaScript files.

[0014] Preferably, in the rule engine-based cloud platform interface design walkthrough method of the present invention, the extracted interface information to be walked through is saved, including: formatting the extracted interface information to be walked through into a JSON file, and storing the formatted JSON file.

[0015] Preferably, in the cloud platform interface design walkthrough method based on the rule engine of the present invention, the extracted interface information to be walked through is matched with the constructed rule base through the rule engine, including: reading the constructed rule base through the rule engine, loading the read rule base into the memory, using the formatted JSON file as input data of the rule engine, traversing the rule base in the memory, matching the interface information to be walked through of the input data with the walkthrough rules in the rule base, performing a logical check on the successfully matched input data, and recording the input data that fails the logical check.

[0016] Preferably, in the cloud platform interface design walkthrough method based on the rule engine of the present invention, the interface information to be walked through of the input data is matched with the walkthrough rules in the rule library, a logic check is performed on the input data that successfully matches, and the input data that fails the logic check is recorded, including:

[0017] Match the interface information to be checked of the input data with the triggering conditions of the check rules in the rule base;

[0018] When the interface information to be checked meets the triggering condition of the check rule in the rule base, it is determined that the interface information to be checked of the input data successfully matches the check rule in the rule base;

[0019] Use the preset check logic to perform a logic check on the interface information to be checked in the successfully matched input data, and record the input data that fails the logic check.

[0020] Preferably, in the cloud platform interface design walkthrough method based on the rule engine of the present invention, a cloud platform interface design walkthrough result report is constructed according to the matching results, including:

[0021] Traverse the matching results of the rule engine, extract the input data that fails the logic check, record the error information corresponding to the input data that fails the logic check, the error information includes the interface location information, the problem description information and the violated rule coding information, and format the input data that fails the logic check into a JSON file;

[0022] Create an HTML report template, fill the error information and JSON file corresponding to the input data that fails the logic check into the created HTML report template, and generate a cloud platform interface design walkthrough result report.

[0023] According to a second aspect of the present invention, a cloud platform interface design walkthrough system based on a rule engine is provided, the system comprising a design walkthrough server, the design walkthrough server being used to: construct walkthrough rules by category, standardize the constructed walkthrough rules, and construct a rule base according to the standardized walkthrough rules and creation information; collect cloud platform interface design files, extract interface information to be walked through by parsing the cloud platform interface design files, and save the extracted interface information to be walked through; match the extracted interface information to be walked through with the constructed rule base through a rule engine, and construct a cloud platform interface design walkthrough result report according to the match.

[0024] According to a third aspect of the present invention, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in the first aspect of the present invention when executing the program.

[0025] The cloud platform interface design walkthrough method and system based on the rule engine of the present invention realizes the automation and intelligence of the cloud platform interface design walkthrough by building a rule library and parsing, matching and checking the files related to the cloud platform interface based on the rule engine, thereby significantly improving the efficiency and accuracy of the walkthrough; by flexibly configuring the rule library and building the walkthrough report, the design feedback cycle is significantly shortened, providing strong support for the quality control and iterative optimization of the cloud platform interface design. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0027] Figure 1 An example diagram of the architecture of a rule engine-based cloud platform interface design walkthrough system according to an embodiment of the present invention;

[0028] Figure 2 A flowchart of a rule engine-based cloud platform interface design walkthrough method according to an embodiment of the present invention;

[0029] Figure 3 A schematic diagram of the structure of the device provided by the present invention. DETAILED DESCRIPTION

[0030] The embodiments of the present invention are described in detail below with reference to the accompanying drawings.

[0031] It should be noted that the following embodiments and features in the embodiments may be combined with each other in the absence of conflict; and, based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without making any creative work are within the scope of protection of the present disclosure.

[0032] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein may be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on the present disclosure, it should be understood by those skilled in the art that an aspect described herein may be implemented independently of any other aspect, and two or more of these aspects may be combined in various ways. For example, any number of aspects described herein may be used to implement the device and / or practice the method. In addition, other structures and / or functionalities other than one or more of the aspects described herein may be used to implement this device and / or practice this method.

[0033] Figure 1 The following is an example diagram of the architecture of a rule engine-based cloud platform interface design walkthrough system according to an embodiment of the present invention. Figure 1 As shown, the system may include a design walkthrough server 101, a communication network 102 and / or one or more design walkthrough clients 103. Figure 1 The example shown is a plurality of design walkthrough clients 103 .

[0034] The design walkthrough server 101 can be any appropriate server for storing information, data, programs and / or any other suitable type of content. In some embodiments, the design walkthrough server 101 can perform appropriate functions. For example, in some embodiments, the design walkthrough server 101 can be used to perform a design walkthrough on the cloud platform interface based on a rule engine. As an optional example, in some embodiments, the design walkthrough server 101 can be used to implement a design walkthrough on the cloud platform interface based on a rule engine by building a rule base. For example, the design walkthrough server 101 can be used to: construct walkthrough rules by category, standardize the constructed walkthrough rules, and construct a rule base based on the standardized walkthrough rules and creation information; collect cloud platform interface design files, extract interface information to be walked through by parsing the cloud platform interface design files, and save the extracted interface information to be walked through; match the extracted interface information to be walked through with the constructed rule base through the rule engine, and construct a cloud platform interface design walkthrough result report based on the matching results.

[0035] As another example, in some embodiments, the design walkthrough server 101 may send a rule engine-based cloud platform interface design walkthrough method to the design walkthrough client 103 for user use based on a request of the design walkthrough client 103 .

[0036] As an optional example, in some embodiments, the design walkthrough client 103 is used to provide a visual design walkthrough interface, which is used to receive a user's selection input operation for performing a design walkthrough on the cloud platform interface based on a rule engine, and to, in response to the selection input operation, obtain a design walkthrough interface corresponding to the option selected by the selection input operation from the design walkthrough server 101 and display the design walkthrough interface, wherein the design walkthrough interface at least displays information on performing a design walkthrough on the cloud platform interface based on the rule engine and operation options for the information on performing a design walkthrough on the cloud platform interface based on the rule engine.

[0037] In some embodiments, the communication network 102 can be any suitable combination of one or more wired and / or wireless networks. For example, the communication network 102 can include any one or more of the following: the Internet, an intranet, a wide area network (WAN), a local area network (LAN), a wireless network, a digital subscriber line (DSL) network, a frame relay network, an asynchronous transfer mode (ATM) network, a virtual private network (VPN), and / or any other suitable communication network. The design walkthrough client 103 can be connected to the communication network 102 via one or more communication links (e.g., communication link 104), and the communication network 102 can be linked to the design walkthrough server 101 via one or more communication links (e.g., communication link 105). The communication link can be any communication link suitable for transmitting data between the design walkthrough client 103 and the design walkthrough server 101, such as a network link, a dial-up link, a wireless link, a hardwired link, any other suitable communication link, or any suitable combination of such links.

[0038] The design walkthrough client 103 may include any one or more clients that present an interface related to high-speed access to an ORC external table in an appropriate form for use and operation by a user. In some embodiments, the design walkthrough client 103 may include any suitable type of device. For example, in some embodiments, the design walkthrough client 103 may include a mobile device, a tablet computer, a laptop computer, a desktop computer, and / or any other suitable type of client device.

[0039] Although the design walkthrough server 101 is illustrated as one device, in some embodiments, any appropriate number of devices may be used to perform the functions performed by the design walkthrough server 101. For example, in some embodiments, multiple devices may be used to implement the functions performed by the design walkthrough server 101. Alternatively, a cloud service may be used to implement the functions of the design walkthrough server 101.

[0040] Based on the above system, an embodiment of the present invention provides a cloud platform interface design walkthrough method based on a rule engine, which is described below through the following embodiments.

[0041] Figure 2 The following is a flow chart of the steps of a cloud platform interface design walkthrough method based on a rule engine according to an embodiment of the present invention. The cloud platform interface design walkthrough method based on a rule engine of this embodiment can be executed on a design walkthrough server, and the cloud platform interface design walkthrough method based on a rule engine includes the following steps:

[0042] Step S201: constructing walkthrough rules by category, standardizing the constructed walkthrough rules, and constructing a rule base according to the standardized walkthrough rules and creation information.

[0043] As an optional example, in the embodiment of the present invention, layout-type walkthrough rules, color-type walkthrough rules, text-type walkthrough rules, and interaction-type walkthrough rules are constructed.

[0044] In actual applications, design specifications can be formulated based on existing industry specifications and standards for cloud platform interface design and combined with actual application scenarios as the basis for defining walkthrough rules. Among them, the cloud platform interface design specifications can be broken down into specific design elements of the interface, such as buttons, input boxes, navigation, icons, and pop-up windows. Each design element is configured with clear style specifications, layout requirements, and interaction logic. For example, in this embodiment, the various walkthrough rules can be classified and defined as follows according to the dimensions of layout, color, text, and interaction:

[0045] Layout walkthrough rules: Rules related to the position, size, and spacing of interface elements to ensure a clear interface hierarchy;

[0046] Color walkthrough rules: These include color consistency, contrast, saturation, and other related rules to ensure that the color combination is consistent with the brand image and takes into account the user's visual comfort;

[0047] Text review rules: involving font, font size, font weight, line spacing and other related rules to ensure the readability of text information;

[0048] Interaction walkthrough rules: Rules related to the behavioral logic and feedback mechanism when users interact with interface components, used to ensure the user-friendliness of components.

[0049] After completing the construction of the walkthrough rules, the present embodiment standardizes the walkthrough rules by setting a unified data format for the walkthrough rules. As an optional example, the walkthrough rules of the present embodiment are composed of a rule coding field, a rule classification field, a rule name field, a rule description field, a trigger condition field, a check logic field, and an expected result field. Table 1 is an example of a standardized walkthrough rule field data format for a cloud platform interface design walkthrough method based on a rule engine according to an embodiment of the present invention. As shown in Table 1, the present embodiment sets the type of the rule coding field to int, the type of the rule classification field and the rule name field to varchar, and the type of the rule description field, the trigger condition field, the check logic field, and the expected result field to text. By standardizing the walkthrough rules, the parsability of the walkthrough rules can be ensured.

[0050] Table 1

[0051] name type describe rule_ID int Rule code, primary key rule_Type varchar Rule Classification rule_Name varchar Rule name, unique key rule_Description text Rule Description rule_Trigger text Trigger conditions rule_Check text Check Logic rule_Result text Expected Results

[0052] In this embodiment, the fields of the unified data format include rule code (rule_ID), type int, which is the primary key and is the unique identifier of the rule; rule category (rule_Type), type varchar, which records the category to which the rule belongs; rule name (rule_Name), type varchar, which is the unique key and records the name of the rule, and the name cannot be repeated; rule description (rule_Description), type text, which records the detailed description of the rule; trigger condition (rule_Trigger), type text, which records the condition for the rule to be activated; check logic (rule_Check), type text, which records the specific logic of rule execution; expected result (rule_Result), type text, which records the expected result after the rule is executed.

[0053] After the walkthrough rules are standardized, this embodiment also needs to build a rule base based on the standardized walkthrough rules and creation information. As an optional example, this embodiment builds a rule base by storing the standardized walkthrough rules and the creation time, creator, update time, and updater field information of the walkthrough rules in a database. In actual applications, when there are updates to the walkthrough rules, they can be flexibly configured through operations such as adding, inserting, and deleting database tables to achieve dynamic management of the walkthrough rules.

[0054] Step S202: Collect the cloud platform interface design file, extract the interface information to be checked by parsing the cloud platform interface design file, and save the extracted interface information to be checked.

[0055] This embodiment parses the design files of the cloud platform interface including HTML, CSS and JavaScript, and extracts the key elements and attributes that need to be checked according to the layout check rules, color check rules, text check rules and interaction check rules in step S201.

[0056] As an optional example, this embodiment collects HTML files, CSS files, and JavaScript files corresponding to the cloud platform interface, identifies and extracts the layout elements of the interface, the nested relationships between the layout elements, and the text elements by parsing the HTML files, extracts the style attributes of the interface elements and the color style attributes of the interface by parsing the CSS files, and extracts the interactive behavior logic of the interface elements by parsing the JavaScript files.

[0057] In actual applications, HTML files define the basic structure of the interface. HTML parsers are used to convert HTML content into DOM (Document Object Model) trees. The DOM tree is a hierarchical representation of HTML documents. Each HTML tag, text node, and attribute is represented as a node in the DOM tree. By traversing the DOM tree, layout and text-related elements are identified through nodes, such as 、 <header> 、 <footer> 、 <nav>etc. for layout elements, 、 、 <h1>etc. for text elements. The CSS file defines the style of the interface. The CSS parser is used to convert the CSS content into CSSOM (CSS Object Model). CSSOM is a mapping of CSS styles. Each node represents a style rule. The style information of each element can be obtained by matching the style rules in CSSOM with the elements in the DOM tree. Such as layout attributes such as width, height, margin, padding, color attributes such as color and background-color. The JavaScript file defines the interactive behavior of the interface. The JavaScript parser is used to convert the JavaScript content into AST (Abstract Syntax Tree). AST is a memory representation of the code structure, which contains all statements and expressions. Traverse the AST to identify code segments related to the interaction, including event types, event handling functions, and DOM operations.

[0058] After the extraction of the interface information to be checked is completed, the extracted interface information to be checked is formatted into a JSON file, and the formatted JSON file is stored. That is, the information extracted from the HTML, CSS and JavaScript parsing files is formatted into a JSON file for storage.

[0059] Step S203: Match the extracted interface information to be checked with the constructed rule base through the rule engine, and construct a cloud platform interface design check result report based on the matching results.

[0060] In this embodiment, by starting the rule engine, all the inspection rules in the rule library constructed in step S201 are read and loaded into the memory, and the JSON file formatted in step S202 is used as the input data of the rule engine. The rule engine traverses the rule library in the memory and matches the element attributes in the input data with the trigger conditions of each rule under the corresponding rule category. If the trigger conditions are met, the match is successful.

[0061] As an optional example, the constructed rule base is read through the rule engine, the read rule base is loaded into the memory, the formatted JSON file is used as the input data of the rule engine, the rule base in the memory is traversed, the interface information to be checked of the input data is matched with the check rules in the rule base, a logical check is performed on the input data that matches successfully, and the input data that fails the logical check is recorded. For example, the interface information to be checked of the input data is matched with the triggering conditions of the check rules in the rule base; when the interface information to be checked meets the triggering conditions of the check rules in the rule base, it is determined that the interface information to be checked of the input data matches the check rules in the rule base successfully; the preset check logic is used to perform a logical check on the interface information to be checked in the input data that matches successfully, and the input data that fails the logical check is recorded.

[0062] For example, in actual applications, this embodiment further determines whether the successfully matched input data satisfies the corresponding rule checking logic. The specific process is as follows:

[0063] Data extraction: Extract content related to the inspection logic from the input data, such as the attributes, values, and states of interface elements;

[0064] Condition evaluation: compare the extracted input data with the conditions in the check logic, including but not limited to comparison, calculation and pattern matching;

[0065] Logical judgment: If the condition evaluation result meets the inspection logic of the rule, it passes; if not, it fails and records the information that the condition is not met.

[0066] As an optional example, after matching the extracted interface information to be checked with the constructed rule base, this embodiment traverses the matching results of the rule engine, extracts the input data that fails the logical check, records the error information corresponding to the input data that fails the logical check, the error information includes interface location information, problem description information, and violated rule coding information, and formats the input data that fails the logical check into a JSON file; then creates an HTML report template, fills the error information corresponding to the input data that fails the logical check and the JSON file into the created HTML report template, and generates a cloud platform interface design walkthrough result report.

[0067] The method of this embodiment is described in detail in a specific scenario below;

[0068] Define the walk-through rules for button color contrast as follows:

[0069] Rule name: Button color contrast accessibility check;

[0070] Rule description: The contrast between the background color and text color of buttons in the cloud platform interface design must meet the barrier-free design standards (i.e., the 4.5:1 contrast ratio required by WCAG AA level) to improve the readability of the text and the accessibility of the interface.

[0071] Trigger condition: When the rule engine recognizes that there is a button element with a text label in the interface design file, this rule is triggered for checking.

[0072] Check logic: Extract the background color (recorded as #bgColor) and text color (recorded as #textColor) of the button, apply the contrast algorithm recommended by WCAG to calculate the contrast ratio of #bgColor and #textColor, and compare the calculated contrast ratio with the preset barrier-free design standard (4.5:1 in this example). Among them, the contrast algorithm of WCAG is contrast C = (L1 + 0.05) / (L2 + 0.05), L1 and L2 represent the relative brightness of the foreground color (#textColor in this example) and the background color (#bgColor in this example), and the relative brightness L = 0.2126*R + 0.7152*G + 0.0722*B, and R, G, and B represent the red, green, and blue component values ​​of the color respectively. When calculating the red, green, and blue component values, first obtain the XsRGB value after the RGB value is normalized, where XsRGB = X8bit / 255, and X8bit represents the values ​​of R, G, and B in 8-bit channels. If XsRGB≤0.03928, use XsRGB / 12.92 as the component value; if XsRGB>0.03928, use [(XsRGB+0.055) / 1.055] 2.4 As component value.

[0073] Expected results: If the color contrast ratio of the checked button element is greater than or equal to the preset accessibility design standard (4.5:1), it is judged that the inspection has passed; if the color contrast ratio of the checked button element is lower than the preset accessibility design standard, it is judged that the inspection has failed and its contrast ratio is recorded.

[0074] In practical applications, the process example of building a cloud platform interface design walkthrough result report in this embodiment is as follows:

[0075] Traverse the matching results of the rule engine, extract all interface elements that fail the rule check and their corresponding rules, and classify the results according to the rule type. For each detected problem, record the specific interface location (such as page, component name), problem description and violated rule code, and format the data into a JSON file;

[0076] Generate HTML report templates using programming languages, with basic contents including report title, creation date, creator and problem list. The fields of the problem list include problem number, problem type, interface location, problem description and violation rule code;

[0077] Use programming language to fill the data in the JSON file into the report template to generate the final cloud platform interface design walkthrough result report.

[0078] According to the cloud platform interface design walkthrough method and system based on the rule engine of the embodiment of the present invention, by building a rule library and parsing, matching and checking the files related to the cloud platform interface based on the rule engine, the automation and intelligence of the cloud platform interface design walkthrough are realized, and the efficiency and accuracy of the walkthrough are significantly improved; by flexibly configuring the rule library and building the walkthrough report, the design feedback cycle is significantly shortened, providing strong support for the quality control and iterative optimization of the cloud platform interface design.

[0079] like Figure 3 As shown, the present invention also provides a device, including a processor 310, a communication interface 320, a memory 330 for storing a computer program executable by the processor, and a communication bus 340. The processor 310, the communication interface 320, and the memory 330 communicate with each other through the communication bus 340. The processor 310 implements the above-mentioned cloud platform interface design walkthrough method based on the rule engine by running the executable computer program.

[0080] Among them, the computer program in the memory 330 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0081] The system embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, i.e., they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected based on actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art may understand and implement it without creative effort.

[0082] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods of each embodiment or some parts of the embodiment.

[0083] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.< / h1> < / nav> < / footer> < / header>

Claims

1. A cloud platform interface design walkthrough method based on a rule engine, characterized in that: The method comprises: Construct walkthrough rules by category, standardize the constructed walkthrough rules, and construct a rule base based on the standardized walkthrough rules and creation information; Collect cloud platform interface design files, extract interface information to be checked by parsing the cloud platform interface design files, and save the extracted interface information to be checked; The extracted interface information to be checked is matched with the constructed rule base through the rule engine, and a cloud platform interface design check result report is constructed based on the matching results.

2. The cloud platform interface design walkthrough method based on rule engine according to claim 1 is characterized in that: Construct walkthrough rules by category and standardize the constructed walkthrough rules, including: constructing layout walkthrough rules, color walkthrough rules, text walkthrough rules and interaction walkthrough rules. The walkthrough rules are standardized by setting a unified data format for the walkthrough rules. The walkthrough rules are composed of a rule code field, a rule classification field, a rule name field, a rule description field, a trigger condition field, a check logic field and an expected result field.

3. The rule engine-based cloud platform interface design walkthrough method according to claim 2, characterized in that: The walkthrough rules are standardized by setting a unified data format for the walkthrough rules, including: setting the type of the rule code field to int, setting the type of the rule classification field and the rule name field to varchar, and setting the type of the rule description field, trigger condition field, check logic field, and expected result field to text.

4. The cloud platform interface design walkthrough method based on rule engine according to claim 1, characterized in that: A rule base is constructed according to the standardized walkthrough rules and creation information, including: constructing the rule base by storing the standardized walkthrough rules and the creation time, creator, update time and updater field information of the walkthrough rules in a database.

5. The cloud platform interface design walkthrough method based on rule engine according to claim 1, characterized in that: Collect cloud platform interface design files, and extract interface information to be checked by parsing the cloud platform interface design files, including: collecting HTML files, CSS files, and JavaScript files corresponding to the cloud platform interface, identifying and extracting interface layout elements, nested relationships between layout elements, and text elements by parsing HTML files, extracting interface element style attributes and interface color style attributes by parsing CSS files, and extracting interface element interaction behavior logic by parsing JavaScript files.

6. The cloud platform interface design walkthrough method based on rule engine according to claim 1, characterized in that: Saving the extracted interface information to be checked includes: formatting the extracted interface information to be checked into a JSON file, and storing the formatted JSON file.

7. The cloud platform interface design walkthrough method based on rule engine according to claim 1, characterized in that: The extracted interface information to be checked is matched with the constructed rule base through the rule engine, including: reading the constructed rule base through the rule engine, loading the read rule base into the memory, using the formatted JSON file as input data of the rule engine, traversing the rule base in the memory, matching the interface information to be checked of the input data with the check rules in the rule base, performing a logic check on the input data that has been matched successfully, and recording the input data that has not passed the logic check.

8. The cloud platform interface design walkthrough method based on rule engine according to claim 1, characterized in that: Match the interface information to be checked of the input data with the check rules in the rule base, perform logic check on the input data that successfully matches, and record the input data that fails the logic check, including: Match the interface information to be checked of the input data with the triggering conditions of the check rules in the rule base; When the interface information to be checked meets the triggering condition of the check rule in the rule base, it is determined that the interface information to be checked of the input data successfully matches the check rule in the rule base; Use the preset check logic to perform a logic check on the interface information to be checked in the successfully matched input data, and record the input data that fails the logic check.

9. The cloud platform interface design walkthrough method based on rule engine according to claim 1, characterized in that: Build a cloud platform interface design walkthrough result report based on the matching results, including: Traverse the matching results of the rule engine, extract the input data that fails the logic check, record the error information corresponding to the input data that fails the logic check, the error information includes interface location information, problem description information and violated rule coding information, and format the input data that fails the logic check into a JSON file; Create an HTML report template, fill the error information and JSON file corresponding to the input data that fails the logic check into the created HTML report template, and generate a cloud platform interface design walkthrough result report.

10. A cloud platform interface design walkthrough system based on rule engine, characterized in that: The system includes a design walkthrough server, which is used to: construct walkthrough rules by category, standardize the constructed walkthrough rules, and construct a rule library based on the standardized walkthrough rules and creation information; collect cloud platform interface design files, extract interface information to be walked through by parsing the cloud platform interface design files, and save the extracted interface information to be walked through; match the extracted interface information to be walked through with the constructed rule library through a rule engine, and construct a cloud platform interface design walkthrough result report based on the match.