Renaming processing method and device based on human-computer interaction

Abstract

The present disclosure provides a renaming processing method and device based on human-computer interaction, the method comprising: when triggering a naming specification component, judging whether a target model currently selected is editable; if editable, determining a model element set to be named according to a model context or a subject domain context associated with the target model. Then, inquiring whether the subject domain to which each element belongs is associated with a subject domain level naming specification; if associated, displaying a corresponding naming specification list in a human-computer interaction interface, and finally, in response to a selection operation of a user on the subject domain level naming specification in the list, determining an effective naming specification of the corresponding model element, and performing renaming processing accordingly. Thus, the consistency of the naming format is realized, while the flexible specification differentiation across subject domains is taken into account, and the specification requirements in different scenarios are met.

Description

Technical Field

[0001] This disclosure relates to the field of human-computer interaction technology, and in particular to a renaming processing method and apparatus based on human-computer interaction. Background Technology

[0002] In the field of data modeling, the English naming of entities (tables), attributes (fields), indexes, and views often relies on the modeler's personal habits, lacking unified and automatically enforceable rules. This leads to the following common problems in actual modeling: inconsistent capitalization (e.g., mixing all uppercase, camelCase, and underscores), inconsistent prefixes, suffixes, or business abbreviations, arbitrary order of semantic units in the naming, fragmented naming rules between different subject areas, and misalignment of naming conventions between logical and physical models.

[0003] However, in scenarios involving continuous model evolution, collaborative design by multiple people, and ongoing maintenance of historical models, the drift in naming styles will gradually accumulate, ultimately directly affecting the readability and standardization of the model, and weakening subsequent automated governance capabilities (such as metadata management, data lineage tracing, and automatic code generation). Therefore, there is an urgent need for a method that can unify and standardize naming in data models to ensure the naming quality of data models throughout their entire lifecycle. Summary of the Invention

[0004] This disclosure provides a renaming processing method and apparatus based on human-computer interaction, to at least partially solve one of the technical problems in related technologies. The technical solution of this disclosure is as follows: According to a first aspect of the present disclosure, a renaming method based on human-computer interaction is provided, comprising: in response to a triggering operation of a naming specification component in a human-computer interaction interface, determining whether a currently selected target model is in an editable state; in response to the target model being in an editable state, determining a set of model elements to be named based on a target context associated with the target model; wherein the target context includes at least one of a model context and a topic domain context; based on a naming specification list, querying whether the topic domain to which each model element in the set of model elements belongs is associated with a topic domain-level naming specification; wherein the topic domain refers to a set of model elements in the target model divided according to business semantics; in response to the topic domain being associated with a topic domain-level naming specification, displaying the topic domain-level naming specification associated with the topic domain in the human-computer interaction interface; in response to a selection operation of the topic domain-level naming specification associated with the topic domain, using the selected topic domain-level naming specification as the effective naming specification for the corresponding model element, and performing renaming processing on the corresponding model element using the effective naming specification.

[0005] According to a second aspect of the present disclosure, a renaming processing apparatus based on human-computer interaction is provided, comprising: a first determining module, configured to determine whether a currently selected target model is in an editable state in response to a triggering operation of a naming specification component in a human-computer interaction interface; a second determining module, configured to determine a set of model elements to be named based on a target context associated with the target model in response to the target model being in an editable state; wherein the target context includes at least one of a model context and a topic domain context; and a querying module, configured to query whether the topic domain to which each model element in the set of model elements belongs is associated with a topic domain-level naming convention based on a naming specification list. Naming conventions; wherein, the subject domain refers to a set of model elements in the target model divided according to business semantics; wherein, the subject domain refers to a set of model elements in the target model divided according to business semantics; a third determining module is used to display the subject domain-level naming convention associated with the subject domain in the human-computer interaction interface in response to the subject domain being associated with a subject domain-level naming convention; a processing module is used to, in response to the selection operation of the subject domain-level naming convention associated with the subject domain, use the selected subject domain-level naming convention as the effective naming convention for the corresponding model element, and perform renaming processing on the corresponding model element using the effective naming convention.

[0006] According to a third aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement a human-computer interaction-based renaming processing method as described in the first aspect of the present disclosure.

[0007] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided that, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, enables the electronic device to perform a human-computer interaction-based renaming processing method as described in the first aspect of the present disclosure.

[0008] According to a fifth aspect of the present disclosure, a computer program product is provided, comprising: a computer program, which, when executed by a processor, implements the human-computer interaction-based renaming processing method as described in the first aspect of the present disclosure.

[0009] The technical solutions provided by the embodiments of this disclosure have at least the following beneficial effects: In this technical solution, when a user triggers the naming convention component, it first verifies whether the target model is in an editable state to avoid performing invalid operations on read-only or locked models, ensuring data integrity and security. When the target model is in an editable state, it determines the set of elements to be named based on the model context or subject domain context, reducing the error rate and complexity of manual selection. Next, it queries whether each model element's subject domain is associated with a subject domain-level naming convention, ensuring accurate matching between the naming and business meaning, improving readability. If associated, the associated subject domain-level naming convention is displayed. After the user selects a subject domain-level naming convention, batch renaming is automatically performed. It ensures consistent formatting while supporting flexible differentiation across subject domains, improving data governance efficiency and team collaboration capabilities. Specifically, when users create new naming conventions, the system displays a configuration interface including an attribute selection area, an assembly rule configuration area, and a preview area, reducing learning costs and the probability of errors. When users select attributes, adjust their order, and format parameters, the system updates the preview in real time without requiring additional submissions, enhancing configuration flexibility and response speed. When determining the set of elements to be named, it first performs a coarse screening of candidate elements based on the target context to avoid traversing all elements; then, it performs a fine screening based on configuration identifiers to accurately identify the elements to be named, improving operational accuracy and security.

[0010] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0011] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0012] Figure 1 This is a flowchart illustrating the renaming process of human-computer interaction as shown in the first embodiment of this disclosure; Figure 2 This is a flowchart illustrating the renaming process of human-computer interaction as shown in the second embodiment of this disclosure; Figure 3 This is a schematic diagram of the interface illustrating the naming conventions shown in this embodiment of the disclosure; Figure 4 This is a flowchart illustrating the renaming process of human-computer interaction as shown in the fourth embodiment of this disclosure; Figure 5 This is a flowchart illustrating the renaming process of human-computer interaction as shown in the fifth embodiment of this disclosure; Figure 6 This is a flowchart illustrating the renaming process of human-computer interaction as shown in the sixth embodiment of this disclosure; Figure 7This is a schematic diagram illustrating the principle of the attribute values ​​of model elements under each attribute item in the embodiments of this disclosure; Figure 8 This is a schematic diagram illustrating the principle of the renaming processing method for human-computer interaction shown in the embodiments of this disclosure; Figure 9 This is a schematic diagram of the structure of the renaming processing device based on human-computer interaction shown in the seventh embodiment of this disclosure; Figure 10 This is a schematic diagram of the structure of an electronic device shown in an exemplary embodiment of the present disclosure. Detailed Implementation

[0013] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0014] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0015] It should be noted that the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved in the technical solution disclosed herein are all carried out with the consent of the user, and all comply with the provisions of relevant laws and regulations, and do not violate public order and good morals.

[0016] In related technologies, only a single naming convention is typically maintained statically, or limited hints are provided only when adding new objects. There is a lack of linkage with model context, subject domain context, and object attributes, as well as a lack of ability to perform batch correction and unified formatting of existing objects during the design process. For physical attributes such as table type, tablespace, library type, and source system in the physical model, as well as business attributes such as primary key, foreign key, distribution key, data item, domain, and fact dimension type on the fields, existing technologies also have difficulty in automatically generating unified English names based on model, subject domain, and object attributes.

[0017] To address any of the above problems, this disclosure proposes a renaming processing method and apparatus based on human-computer interaction.

[0018] The following description, with reference to the accompanying drawings, describes a renaming processing method and apparatus based on human-computer interaction according to embodiments of the present disclosure.

[0019] Figure 1 This is a flowchart illustrating the renaming process based on human-computer interaction as shown in the first embodiment of this disclosure.

[0020] It should be noted that, in this embodiment of the disclosure, the renaming processing method based on human-computer interaction is configured in a renaming processing device based on human-computer interaction as an example. This renaming processing device based on human-computer interaction can be applied to electronic devices so that the electronic devices can perform renaming processing functions based on human-computer interaction.

[0021] like Figure 1 As shown, the renaming processing method based on human-computer interaction includes: Step 110: In response to the triggering operation of the naming convention component in the human-computer interaction interface, determine whether the currently selected target model is in an editable state.

[0022] To prevent accidental renaming operations when the model is locked or the user lacks permissions, one possible implementation is to first check whether the currently selected target model (such as a data model, business model, or physical model) is in an editable state when the user clicks or activates the "Naming Conventions" component (such as a button or menu item) in the human-computer interaction interface. An editable state means that the target model is not locked, the user has modification permissions, and the model is not in published or read-only mode. If the target model is in an uneditable state, all subsequent operations will not be executed, thus avoiding accidental modification or data conflicts to the read-only model.

[0023] Step 120: In response to the target model being in an editable state, determine the set of model elements to be named based on the target context associated with the target model.

[0024] The target context includes at least one of the model context and the topic domain context.

[0025] Furthermore, once the target model is confirmed to be in an editable state, the set of model elements that need to be renamed is determined based on the target context associated with the model. The target context may include at least one of the model context and the subject domain context. The model context may include, but is not limited to, the type of the model itself (logical model, physical model), database type, tablespace, table type (fact table, dimension table), etc. The subject domain context is the business domain to which the model belongs (such as order domain, customer domain, financial domain). The system can rely on one of the contexts alone or combine the two to automatically filter out all model elements (such as tables, fields, views, indexes, etc.) under the current model that need to uniformly apply the naming convention, forming a set of model elements to be named.

[0026] In some embodiments, such as Figure 2 As shown, step 120 may include the following steps: Step 1201: Based on the target context associated with the target model, determine at least one candidate model element.

[0027] To quickly and accurately filter out candidate objects that may need naming from all elements of the target model, one possible approach is to filter based on the target context associated with the target model. The target context can include the model context and the subject domain context. The model context focuses on the technical attributes and state of the target model itself, such as its design pattern (shared or exclusive, which determines which users have access), version number, and structural relationships between elements within the model (e.g., parent-child relationships, reference relationships, etc.). This information helps the system determine whether the current operation is technically feasible. The domain context focuses on the business domain to which the target model belongs, such as the customer domain, order domain, and product domain. It determines which business scope the current naming operation is applied to. The system uses these two types of context information as filtering conditions to remove elements from all elements (such as fields, tables, entities, attributes, etc.) contained in the target model that do not meet the current operation conditions. For example, if the model context indicates that the current model is in read-only mode, then all elements will be excluded; if the subject domain context specifies that only elements of the order domain will be processed, then elements of other domains will be excluded. Finally, the system will obtain a list containing at least one candidate element.

[0028] Step 1202: Based on the configuration identifier of each candidate model element, determine the set of model elements to be named from at least one candidate model element.

[0029] Furthermore, based on the configuration identifiers of each candidate model element, these candidate elements are checked and filtered to ultimately determine which elements truly require naming operations. The configuration identifiers are used to indicate whether the candidate model element is in a nameable state. For example, the configuration identifiers include: a locked identifier (whether the element has been manually locked by a user or administrator, and no modification is allowed in the locked state), a rule association identifier (whether the element has been associated with a specific naming rule; if it has been associated and the rule is still valid, it may not need to be renamed), and a status identifier (whether the element is in a specific state such as "newly created," "pending update," or "deprecated," and different states determine whether a naming operation is required).

[0030] As an example, candidate model elements that are configured to be named are identified as model elements to be named.

[0031] In other words, candidate model elements with configuration identifiers in a nameable state are identified as model elements to be named. The nameable state indicates that the model element is currently allowed and needs to be named. In this embodiment, the configuration identifiers carried by each candidate element can be checked to determine whether it is marked as nameable. It should be noted that a model element must meet the following conditions to be nameable: it is not locked (i.e., the lock identifier is false), it has not been manually excluded from naming operations by the user (i.e., the manual exclusion identifier is false), it is not associated with a naming rule that is already effective and does not need updating (i.e., the rule association identifier indicates "not associated" or "rule expired"), and its status identifier indicates "newly created" or "pending update" (i.e., a name needs to be assigned or modified). Only when all these conditions are met will the configuration identifier of the element be determined by the system to be in a "nameable state".

[0032] In summary, by identifying at least one candidate model element based on the target context associated with the target model, the system achieves efficient coarse screening of model elements. Since the target context can quickly lock the operation scope at the global level, it is not necessary to traverse all elements in the target model. Instead, it directly focuses on elements that are relevant to the current operation and meet the technical conditions and business scope, avoiding wasting computing resources on irrelevant model elements and significantly improving the screening efficiency of candidate elements. Secondly, based on the configuration identifier of each candidate model element, a set of model elements to be named is determined from at least one candidate model element, achieving precise fine screening of candidate elements. This enables the system to accurately identify which elements are truly allowed and need to be named, improving the accuracy and security of the operation.

[0033] Step 130: Based on the naming convention list, query whether the subject domain to which each model element in the model element set belongs is associated with a subject domain-level naming convention.

[0034] The subject domain refers to the set of model elements in the target model that are divided according to business semantics.

[0035] It's important to understand that during model building and management, model elements must adhere to certain naming conventions to ensure consistency, understandability, and maintainability. For a given set of model elements to be renamed (i.e., the "model element set"), the system directly queries the naming convention list to check if each topic domain has a pre-configured topic domain-level naming convention. For example, the system may maintain a pre-maintained naming convention list that records the relationships between each topic domain and topic domain-level naming conventions. When processing the set of model elements to be renamed, the system first extracts the topic domains to which all model elements belong (deduplicating them), and then queries the naming convention list for each topic domain to determine if that topic domain is associated with a corresponding topic domain-level naming convention.

[0036] In this context, a subject domain refers to a set of model elements in the target model divided according to business semantics, such as a "customer domain" or an "order domain." A subject domain-level naming convention is a naming rule specifically defined for a particular subject domain. Then, a pre-maintained "subject domain-naming convention" mapping table is accessed to determine whether the subject domain is associated with at least one naming convention. The naming convention can be as follows: Figure 3 As shown.

[0037] Furthermore, it should be noted that this step breaks the limitations of the traditional single global naming convention, allowing different subject domains to have their own independent naming conventions. For example, the customer domain may require fields to start with "cust_", while the order domain may require them to start with "ord_". As a result, model elements can obtain names that are highly consistent with their business semantics, avoiding cross-domain confusion and making the model easier for business personnel to understand and maintain. At the same time, the management granularity of the convention is finer and the extensibility is stronger. When adding a new subject domain, only the convention of that domain needs to be configured.

[0038] In some embodiments, such as Figure 4 As shown, the naming convention list can be updated using the following steps: Step 1301: In response to the triggering operation of the target control in the naming convention management page, display the configuration page associated with the target control.

[0039] As one possible implementation, upon receiving a user's trigger action on a target control in the naming convention management page, a configuration page associated with that target control can be displayed. The target control refers to an interactive element on the page used to trigger a specific function, such as a "Create Naming Convention" button, a "Delete Naming Convention" icon, or a "Modify Naming Convention" link. The trigger action can be a user action such as clicking, double-clicking, or hovering and selecting. The configuration page is an interface designed to perform the specific operation; its content, layout, and interaction methods are all determined by the type of target control that is triggered. For example, clicking the "Delete Naming Convention" icon will display a configuration page containing confirmation information. Thus, by directly displaying the corresponding configuration page by triggering the target control, users can quickly enter the operating environment without manually searching for or memorizing menu paths, reducing the operational threshold and learning cost. Furthermore, the one-to-one correspondence between the configuration page and the target control ensures that users always operate within the correct business context, avoiding operational errors caused by interface jumps or information misalignment.

[0040] Step 1302: In response to the update operation performed on the configuration page, determine the type of the update operation based on the target control to update the naming convention list.

[0041] The update operation types include creating a new naming convention, deleting an existing naming convention, and modifying an existing naming convention.

[0042] Subsequently, the user completes update operations on the configuration page, such as filling out a form and clicking the save button, confirming deletion and clicking the OK button, or modifying fields and clicking the submit button. These operations are collectively referred to as update operations. After receiving the update operation signal, the system accurately determines the specific type of the update operation based on the type of the target control initially triggered by the user. For example, if the user clicks the "Create Naming Convention" button to enter the configuration page, the update operation is determined to be a "Create" type, and the logic of adding a new record to the naming convention list is executed accordingly. If the user clicks the "Delete Naming Convention" icon, the system determines it to be a "Delete" type, and the logic of removing the corresponding record is executed. If the user clicks the "Modify Naming Convention" link, the system determines it to be a "Modify" type, and the logic of updating the corresponding field content is executed. Finally, the system performs the corresponding add, delete, or modify operation on the naming convention list based on the determined operation type.

[0043] In summary, after a user triggers a target control on the naming convention management page, the associated configuration page is displayed first, rather than directly executing the change operation. This provides clear visual feedback and guidance before the user proceeds to the specific operation, reducing the risk of misoperation. Furthermore, the system determines the specific type of update operation performed on the configuration page based on the type of the target control initially triggered by the user. This accurately identifies whether the operation is a creation, deletion, or modification, preventing errors in the naming convention list data due to misjudgment of the operation type. Thus, precise control from user trigger to data change is achieved, improving the smoothness and certainty of user operations while ensuring the consistency and integrity of the naming convention list data, thereby enhancing the overall efficiency and reliability of naming convention management.

[0044] In some embodiments, such as Figure 5 As shown, the new naming convention in step 1302 may include the following steps: Step 13021: In response to the instruction to create a new naming convention triggered by the target control, display the configuration page.

[0045] The naming convention configuration interface includes an attribute selection area, an assembly rule configuration area, and a preview area.

[0046] To help users intuitively understand the entire naming convention construction process, one possible implementation is to have the system immediately respond and display a configuration page when a user issues a command to create a new naming convention by clicking the "Create New Naming Convention" button, selecting the "Create" option in the menu, or pressing a shortcut key. This interface can include three functional areas: an attribute selection area, an assembly rule configuration area, and a preview area. The attribute selection area allows users to choose which attributes from all available metadata attributes should participate in the final name generation. For example, users can select the project code, department name, creation date, etc. The assembly rule configuration area allows users to define the order in which these selected attribute items are arranged and how they are separated. For example, users can put the project code first, the department name last, and add an underscore as a separator between them. The preview area is used to display an example of the naming result under the current configuration in real time, allowing users to intuitively see the final generated name format before saving. This partitioned design makes the entire configuration process clear and orderly, eliminating the need for users to remember complex operation paths and reducing the learning cost.

[0047] Step 13022: In response to the attribute selection operation performed in the attribute selection area, determine at least one attribute item to participate in the naming.

[0048] Next, users perform selection operations in the attribute selection area. These operations can include checking checkboxes in the list, clicking attribute item labels, or dragging attribute items from the candidate area to the selected area. The system captures these selection operations in real time and records all attribute items currently selected by the user, serving as the basis for subsequent assembly rule configuration. For example, if a user selects the project code, department name, and creation year from the available attribute list, the system will identify these three attribute items as participating in the naming process. If the user subsequently deselects an attribute item, the system will update the set of participating attribute items accordingly. It should be noted that this process is dynamic; each selection or deselection immediately updates the internally maintained list of selected attribute items and triggers a refresh of the preview area.

[0049] Step 13023: In response to the assembly rule adjustment operation performed in the assembly rule configuration area, adjust the arrangement order of the at least one attribute item in the assembly order, and set the format parameters between the at least one attribute item.

[0050] Furthermore, when a user performs assembly rule adjustment operations in the assembly rule configuration area, the system can respond to these operations in real time, adjust the order of multiple selected attribute items in the final name, and set the format parameters between attribute items. The format parameters include the connector between attribute items, the format of the attribute item name, and at least one of prefix and suffix. The assembly rule adjustment operations cover various methods such as adding, deleting, moving up, moving down, pinning to the top, and pinning to the bottom. For example, users can drag the department name, which was originally in second place, to the first place so that the final name starts with the department name; they can also insert an underscore as a separator between two attribute items, or add a fixed prefix or suffix to the entire name, or convert all attribute items to uppercase letters. Through the above operations, users can flexibly customize naming rules to meet business needs.

[0051] Step 13024: In response to the attribute selection operation and / or assembly rule adjustment operation, calculate and display the naming specification preview result under the current assembly rule in the preview area.

[0052] Furthermore, whenever a user performs a selection operation in the attribute selection area or an adjustment operation in the assembly rule configuration area, whether it occurs alone or simultaneously, the system will immediately trigger the preview area update mechanism. Based on the currently determined attribute items participating in the naming and their order, separators, prefixes, suffixes, capitalization, and other format parameters, the system will calculate a specific name example that conforms to the current assembly rule in real time and display the result in the preview area.

[0053] For example, if a user selects the project code and department name, sets the order to project code first, department name second, separated by an underscore, and sets the project code to uppercase, the preview area will immediately display a similar condition-matching example name after each user action, such as "PROJ-A_Technical Department". This preview result is dynamically updated; the preview result will change with each adjustment made by the user, allowing the user to see the actual effect of each step of the adjustment at any time.

[0054] Step 13025: In response to the received confirmation and save instruction, generate a naming specification object according to the current assembly rules, and add the naming specification object to the naming specification list.

[0055] Finally, after the user selects the attribute items and adjusts the assembly rules, the user will click the "Confirm Save" button or issue a confirmation save command through other means. Upon receiving the command, the system will immediately capture all the current states in the attribute item selection area and assembly rule configuration area, including the list of selected attribute items, the order of the attribute items, and all set format parameters. Then, based on this complete information, a structured naming convention object will be generated. This object is a data entity containing all rule definitions, which can be understood as a complete naming convention configuration record. Finally, the system saves this newly generated naming convention object to persistent storage and adds it to the naming convention list, making the convention visible and usable in the list. Users can then automatically generate filenames, resource names, etc., that conform to the rules based on this convention. For example, if the user previously configured a rule combining project code and department name, after saving, this rule will appear in the naming convention list and can be referenced by other functional modules.

[0056] In summary, after a user triggers the command to create a new naming convention, a configuration interface is displayed, including an attribute selection area, an assembly rule configuration area, and a preview area. This allows users to intuitively understand the entire naming convention construction path, avoiding operational confusion caused by information asymmetry and reducing learning costs and the probability of errors. Furthermore, by performing selection operations in the attribute selection area, the system determines the attributes involved in the naming in real time. Subsequent adjustments to the order and format parameters performed in the assembly rule configuration area are instantly captured and applied by the system, improving configuration flexibility and responsiveness. Simultaneously, whenever a user performs attribute selection or assembly rule adjustment operations, the preview area calculates and displays the naming convention preview results based on the current configuration, allowing users to instantly observe the specific impact of each adjustment on the final name. Finally, when the user issues a confirmation and save command, the system generates a structured naming convention object based on the current complete assembly rules and adds it to the naming convention list, enabling persistent storage and subsequent reuse of the convention. This not only achieves "build once, use multiple times" configuration but also makes naming convention management more centralized and orderly, thereby comprehensively improving the efficiency and reliability of naming convention management.

[0057] Step 140: In response to the topic domain being associated with a topic domain-level naming convention, the topic domain-level naming convention associated with the topic domain is displayed in the human-computer interaction interface.

[0058] As one possible implementation, when the system detects that a topic domain is associated with a topic domain-level naming convention, it presents the user with a list of multiple rule entries contained in that convention (such as "prefixed with cust_", "using underscore naming convention", etc.) in the human-computer interaction interface. These rule entries together constitute a complete topic domain-level naming convention, and each topic domain is associated with only one topic domain-level naming convention. The user can then select the associated topic domain-level naming convention as the basis for renaming the current element. It should be noted that all model elements under the same topic domain should select the same rule to ensure a consistent naming style and avoid convention conflicts.

[0059] As another possible implementation, if the subject domain is not associated with a subject domain-level naming convention, query whether the target model is associated with a model-level naming convention; in response to the target model being associated with a model-level naming convention, use the model-level naming convention as the effective naming convention for the subject domain and all model elements under the subject domain.

[0060] In other words, when the system determines that the current topic domain is not associated with any topic domain-level naming convention, it queries whether the target model to which the topic domain belongs is associated with a model-level naming convention. If the target model is associated with a model-level naming convention, the system applies that model-level naming convention to the current topic domain and all model elements under that topic domain, making it the effective naming convention for these model elements. Thus, when a topic domain convention is missing, the system automatically uses a model-level naming convention as a fallback, ensuring that all model elements under that topic domain still have a unified and followable naming rule, and will not cause naming confusion or omissions due to the lack of a convention. At the same time, this mechanism of inheriting model-level conventions to topic domains also avoids users having to manually reconfigure for each topic domain without an independent convention, greatly simplifying the operation process and improving the system's automation level and user experience.

[0061] Step 150: In response to the selection operation of the topic domain-level naming convention associated with the topic domain, the selected topic domain-level naming convention is used as the effective naming convention for the corresponding model element, and the corresponding model element is renamed using the effective naming convention.

[0062] Next, the user selects a subject domain-level naming convention. Upon receiving the user's selection, the system binds the specified subject domain-level naming convention to the model element, making it the unique and effective naming convention for that model element. The system then automatically renames the model element according to the specific rules within that effective convention (such as naming format, prefixes and suffixes, case constraints, etc.), ensuring that the model element's name conforms to the requirements of the selected subject domain-level naming convention. For example, if the convention requires field names to have the prefix "f_" and be all lowercase, the system will automatically change "CustomerName" to "f_customer_name"; if the convention requires table names to begin with "dim_", the system will rename the "Customer" table to "dim_customer". The entire process requires no manual intervention; the system can batch rename all elements to be processed and update the metadata in the model.

[0063] In some embodiments, such as Figure 6 As shown, step 150, which renames the corresponding model element using the effective naming convention, may include the following steps: Step 1501: Extract the attribute values ​​of the corresponding model elements under each attribute item in the order of the attribute items configured in the effective naming specification.

[0064] As one possible implementation, such as Figure 7 As shown, for the target model element to be named (such as a specific field), the actual value of the target model element under each attribute item is obtained one by one according to the attribute item arrangement order configured in the effective naming specification. For example, for the "field name" attribute item, its current field name is read, such as "phone_number".

[0065] Step 1502: Filter the extracted attribute values ​​and perform name format conversion operations on the remaining valid attribute values ​​after filtering to obtain formatted attribute value fragments.

[0066] It's important to understand that after extracting the original attribute values, each value is filtered to remove invalid or harmful data. For example, empty attribute values ​​are filtered out (to avoid generating empty placeholders), and attribute values ​​containing illegal characters are also filtered out. Then, the remaining valid attribute values ​​undergo a uniform format conversion operation to conform to the naming system's syntax requirements. This conversion operation may include, but is not limited to, converting full-width characters to half-width characters, replacing spaces with underscores, and converting all letters to lowercase or camelCase.

[0067] Step 1503: Concatenate the formatted attribute value fragments according to the delimiter configured in the effective naming specification to form an intermediate string.

[0068] Next, based on the order of the attribute items configured in the effective naming convention, the formatted fragments are concatenated sequentially using this delimiter to obtain the intermediate string.

[0069] Step 1504: Append the prefix and suffix configured in the effective naming specification to the beginning and end of the intermediate string respectively to generate the target name of the corresponding model element.

[0070] To enhance the semantic readability and identifiability of names, or to meet the naming requirements of certain systems or platforms, naming conventions may also configure a prefix and a suffix. The prefix can be used to identify the type or domain of an element, for example, "f_" indicates that it is a field, and "t_" indicates that it is a table. The suffix can be used to identify the version, status, or environment of an element, for example, "_v1" indicates version 1, and "_prod" indicates a production environment. The system appends the prefix to the beginning of the middle string and the suffix to the end.

[0071] In summary, following the attribute item arrangement order configured in the effective naming specification, the attribute values ​​of model elements under each attribute item are extracted sequentially. This ensures that the names of all model elements maintain a fixed order and structure in the semantic dimension, thereby avoiding naming ambiguity caused by disordered attribute order and achieving uniformity and predictability of the name structure. Next, the extracted attribute values ​​are filtered and their name formats are converted sequentially, eliminating invalid values ​​and uniformly converting valid values ​​to the standard format. This eliminates naming errors caused by inconsistent quality of the original data. Subsequently, according to the delimiters configured in the specification, the formatted attribute value fragments are concatenated into an intermediate string, making the semantic boundaries of the name clearly distinguishable and facilitating programmatic parsing. This improves the efficiency of manual reading and recognition and supports subsequent reverse attribute restoration through delimiters. Finally, according to the prefix and suffix configured in the specification, they are appended to the beginning and end of the intermediate string, respectively, so that the final name can clearly identify the element's type, version, environment, and other additional information. This enhances the distinctiveness and information capacity of names, enables rapid identification and isolation of elements of different categories and versions, and significantly reduces naming conflicts and the risk of misoperation.

[0072] To ensure consistency in model naming conventions and operational security in multi-user collaborative scenarios, when the system detects that the target model's current design mode is shared, it switches the current user's operating environment to their corresponding personal branch. Shared mode means that the target model allows multiple users to access and edit it simultaneously, while the personal branch is an independent working copy derived from the main branch, used to isolate the current user's modifications to model elements and prevent interference or overwriting between different users' modifications. Subsequently, within the personal branch, users can perform the renaming action in the batch normalization operation on model elements, changing the name of at least one model element. These changes only exist in the personal branch and will not affect the main branch or other users' branches. After the name change is completed, the system merges the changes in the personal branch with the target model's main branch, thus officially writing the user's modifications into the main branch. If a renaming conflict with other users on the same model element is detected during the merging process (i.e., two users have renamed the same element differently), the system handles it according to preset conflict resolution rules. Conflict resolution rules include, for example, rules based on timestamp retention (i.e., retaining changes made by users with later last modification times), rules based on user priority (i.e., retaining changes made by users with higher privileges or roles), or rules prompting users to make manual decisions (i.e., leaving it to the negotiation between users or manual judgment by the administrator). This isolates the modification operations of different users through individual branches, avoiding mutual interference during the editing process. The conflict detection and resolution mechanism during merging ensures the consistency and integrity of naming conventions under multi-user parallel operations. At the same time, the diverse conflict resolution rules provide flexible options for different scenarios, supporting both automated processing to improve efficiency and manual intervention to handle complex situations, thereby minimizing the risks of naming conflicts while ensuring collaborative efficiency.

[0073] To achieve efficiency and consistency in batch processing, persistent storage, and synchronous updates across multiple storage layers, the system divides the renaming result set of the model element set into multiple batches according to a preset batch size. This avoids memory pressure or transaction timeouts caused by processing large amounts of data at once, thereby improving system stability and throughput. Subsequently, the system persists each batch by writing the new and old names and corresponding relationships of all model elements in each batch to a reliable storage medium (such as a database or file system). This ensures that data is not lost even if anomalies occur during subsequent operations, thus guaranteeing the traceability and recoverability of the renaming process. Finally, the system updates the target model... The current design patterns (such as exclusive mode and shared mode) dynamically update the new names in each batch to the corresponding model elements in the storage layer corresponding to the current design pattern. That is, different design patterns may correspond to different storage structures (such as different database tables, different files, or different namespaces). The system can accurately identify and update only the layer that matches the current design pattern without affecting the model elements of other layers. Thus, batch processing avoids system overload, persistent storage ensures data security and rollback, and design pattern-oriented updates achieve synchronous consistency between multiple storage layers. Therefore, while ensuring the stability of large-scale renaming operations, it significantly improves the overall execution efficiency and reliability.

[0074] The renaming method for human-computer interaction in this embodiment verifies whether the target model is in an editable state when the user triggers the naming specification component. This avoids performing invalid operations on read-only or locked models, thereby ensuring the integrity of model data and operational security. When the model is in an editable state, the system automatically determines the set of elements to be named based on the model context or subject domain context, eliminating the need for the user to manually select each element, thus reducing the probability of errors and operational complexity of manual selection. Next, the system queries each model element to see if its subject domain is associated with a subject domain-level naming specification. Since subject domains are divided according to business semantics, subsequent naming specifications can... Precise matching with the actual business meaning of elements improves the business readability of naming. When a subject domain is found to be associated with a subject domain-level naming convention, the naming convention associated with the subject domain is displayed in the human-computer interaction interface. The subject domain-level naming convention selected by the user is used as the effective convention, and batch renaming is automatically performed accordingly. This avoids the tediousness and omissions of manual modification one by one, ensuring strict consistency of naming format while realizing flexible standardization across subject domains and models. It meets the corresponding standardization requirements in different scenarios, effectively improves the overall efficiency of data governance, reduces communication costs caused by naming chaos, and promotes team collaboration and the long-term maintainability of model assets.

[0075] Based on any of the above embodiments, such as Figure 8 As shown, the renaming method based on human-computer interaction in this embodiment may include the following steps: 1. Start and Open Naming Conventions User operation: Model designers click the "Naming Conventions" button on the toolbar; System Response: The system will first perform a verification to check whether the current model is in "design state" (i.e., whether it is being edited in the design process); (1) Branch judgment: If the system judges that the design has not started (no), a prompt will pop up: "Please start the design first", and the process will be blocked or ended here; (2) Normal flow: If the system determines that the design has started (yes), it will allow the user to proceed to the next step, and the user will see the "View Naming Rules pop-up (read-only)"; 2. Rule lookup and application determination System processing: While the pop-up window for personnel viewing appears, the system will query the "currently effective naming conventions" in the background; Association check: The system then determines whether the current environment is "associated with naming conventions"; Branch judgment: If not associated (no), the system will prompt: "Not associated with naming convention"; Normal workflow: If it is already associated (yes), the system will display the specific naming conventions and allow users to perform application operations.

[0076] 3. Execute the application Personnel operation: After seeing the available specifications, personnel click the "Apply Naming Specifications" button; System response: The system receives the instruction and determines the current "application scope" (i.e., which objects need to be renamed). 4. Refresh the closing and ending points. System processing: The system performs a "batch normalization of object names within the current range" operation based on the defined range; Results feedback: After processing is complete, the system will prompt "Success and refresh results", and the data on the interface will be updated with a new name that conforms to the specifications; End: The process eventually reaches the "End" node.

[0077] Corresponding to the renaming processing method based on human-computer interaction provided in the above embodiments, this disclosure also provides a renaming processing device based on human-computer interaction. Since the renaming processing device based on human-computer interaction provided in this disclosure corresponds to the renaming processing method based on human-computer interaction provided in the above embodiments, the implementation of the renaming processing method based on human-computer interaction is also applicable to the renaming processing device based on human-computer interaction provided in this disclosure, and will not be described in detail in this disclosure.

[0078] Figure 9 This is a schematic diagram of the structure of the renaming processing device based on human-computer interaction shown in the seventh embodiment of this disclosure.

[0079] like Figure 9 As shown, the renaming processing device 900 based on human-computer interaction includes: a first determining module 910, a second determining module 920, a query module 930, a third determining module 940, and a processing module 950.

[0080] The system comprises the following modules: a first determining module 910, which determines whether the currently selected target model is in an editable state in response to a trigger operation on the naming convention component in the human-computer interaction interface; a second determining module 920, which determines the set of model elements to be named based on the target context associated with the target model in response to the target model being in an editable state; wherein the target context includes at least one of a model context and a subject domain context; a querying module 930, which queries whether the subject domain to which each model element in the set of model elements belongs is associated with a subject domain-level naming convention based on the naming convention list; wherein a subject domain refers to a set of model elements in the target model divided according to business semantics; a third determining module 940, which displays the subject domain-level naming convention associated with the subject domain in the human-computer interaction interface in response to the subject domain being associated with a subject domain-level naming convention; and a processing module 950, which, in response to a selection operation on the subject domain-level naming convention associated with the subject domain, uses the selected subject domain-level naming convention as the effective naming convention for the corresponding model element and performs renaming processing on the corresponding model element using the effective naming convention.

[0081] As one possible implementation, the renaming processing device 900 based on human-computer interaction further includes: an update module, used to display a configuration page associated with the target control in response to a trigger operation of the target control in the human-computer interaction interface; and to determine the type of update operation based on the target control in response to an update operation performed on the configuration page, so as to update the naming specification list; wherein the type of update operation includes any one of creating a new naming specification, deleting an existing naming specification, and modifying an existing naming specification.

[0082] As one possible implementation, the update module, in response to a command to create a new naming convention triggered by the target control, displays a configuration page. The configuration page includes an attribute selection area, an assembly rule configuration area, and a preview area. In response to an attribute selection operation performed in the attribute selection area, it determines at least one attribute to participate in the naming. In response to an assembly rule adjustment operation performed in the assembly rule configuration area, it adjusts the order of at least one attribute in the assembly sequence and sets format parameters between at least one attribute. In response to the attribute selection operation and / or the assembly rule adjustment operation, it calculates and displays the preview result of the naming convention under the current assembly rule in the preview area. In response to a received confirmation and save command, it generates a naming convention object based on the current assembly rule and adds the naming convention object to the naming convention list.

[0083] As one possible implementation, the second determining module 920 is used to determine at least one candidate model element based on the target context associated with the target model; and to determine a set of model elements to be named from the at least one candidate model element according to the configuration identifier of each candidate model element.

[0084] As one possible implementation, a configuration identifier is used to indicate whether a candidate model element is in a nameable state, and the second determination module 920 is used to determine the candidate model elements whose configuration identifier is in a nameable state as model elements to be named.

[0085] As one possible implementation, the processing module 950 is used to extract the attribute values ​​of the corresponding model elements under each attribute item in the order of the attribute items configured in the effective naming specification; filter the extracted attribute values, and perform name format conversion operations on the remaining valid attribute values ​​to obtain formatted attribute value fragments; concatenate the formatted attribute value fragments according to the delimiter configured in the effective naming specification to form an intermediate string; and append the prefix and suffix configured in the effective naming specification to the beginning and end of the intermediate string respectively to generate the target name of the corresponding model element.

[0086] As one possible implementation, the renaming processing device 900 based on human-computer interaction further includes: a merging module, used to switch to the current user's personal branch in response to the target model's current design mode being shared mode; wherein, the shared mode indicates that the target model can be accessed by multiple users simultaneously, and the personal branch is an independent working copy derived from the target model's main branch, used to isolate the current user's modification operations on model elements; in response to the renaming operation in the batch normalization operation executed within the personal branch, at least one model element in the target model is renamed; after the name change is completed, the changes in the personal branch are merged with the target model's main branch; if a renaming conflict with other users on the same model element is detected during the merging process, the conflict is handled according to a preset conflict resolution rule; wherein, the conflict resolution rule is selected from at least one of the following: a rule based on retaining modifications after timestamp retention, a rule based on user priority retaining modifications made by higher-priority users, or a rule prompting the user to manually decide.

[0087] As one possible implementation, the query module 930 is used to query whether the target model is associated with a model-level naming convention if the subject domain is not associated with a subject domain-level naming convention; in response to the target model being associated with a model-level naming convention, the model-level naming convention is used as the effective naming convention for the subject domain and all model elements under the subject domain.

[0088] As one possible implementation, the renaming processing device 900 based on human-computer interaction further includes: a storage module, used to divide the result set obtained by renaming the model element set into multiple batches according to a preset batch size; to persistently store the multiple batches, and to update the new name in each batch to the corresponding model element in the storage layer corresponding to the current design mode according to the current design mode of the target model.

[0089] The human-computer interaction renaming processing device of this disclosure verifies whether the target model is in an editable state when the user triggers the naming specification component. This avoids performing invalid operations on read-only or locked models, thereby ensuring the integrity of model data and operational security. When the model is in an editable state, the system automatically determines the set of elements to be named based on the model context or subject domain context, eliminating the need for the user to manually select each element, thus reducing the probability of errors and operational complexity of manual selection. Next, it queries whether the subject domain to which each model element belongs is associated with a subject domain-level naming specification. Since the subject domain is divided according to business semantics, subsequent naming specifications can be aligned with... The precise matching of elements' actual business meanings enhances the readability of names. When a subject domain is found to be associated with a subject domain-level naming convention, the naming convention associated with the subject domain is displayed in the human-computer interaction interface. The subject domain-level naming convention selected by the user is then used as the effective convention, and batch renaming is automatically performed accordingly. This avoids the tediousness and omissions of manual modification, ensuring strict consistency in naming formats while enabling flexible standardization across subject domains and models. It meets the corresponding standardization requirements in different scenarios, effectively improves the overall efficiency of data governance, reduces communication costs caused by naming chaos, and promotes team collaboration and the long-term maintainability of model assets.

[0090] In an exemplary embodiment, an electronic device is also proposed.

[0091] The electronic devices include: processor; Memory used to store processor-executable instructions; The processor is configured to execute instructions to implement the human-computer interaction-based renaming processing method as proposed in any of the foregoing embodiments.

[0092] As an example, Figure 10 This is a schematic diagram of the structure of an electronic device 600 as shown in an exemplary embodiment of this disclosure, as follows: Figure 10 As shown, the aforementioned electronic device 1000 may further include: The memory 1010 and processor 1020 are connected by a bus 1030, which connects different components (including the memory 1010 and the processor 1020). The memory 1010 stores a computer program, and when the processor 1020 executes the program, it implements the renaming processing method based on human-computer interaction as described in this embodiment of the disclosure.

[0093] Bus 1030 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. For example, these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0094] Electronic device 1000 typically includes a variety of electronic device readable media. These media can be any available media that can be accessed by electronic device 1000, including volatile and non-volatile media, removable and non-removable media.

[0095] The memory 1010 may also include computer system readable media in the form of volatile memory, such as random access memory (RAM) 1040 and / or cache memory 1050. The electronic device 1000 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 1060 may be used to read and write non-removable, non-volatile magnetic media (…). Figure 10 Not shown; usually referred to as a "hard drive"). Although Figure 10 As not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 1030 via one or more data media interfaces. Memory 1010 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of this disclosure.

[0096] A program / utility 1080 having a set (at least one) of program modules 1070 may be stored in, for example, memory 1010. Such program modules 1070 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 1070 typically perform the functions and / or methods described in the embodiments of this disclosure.

[0097] Electronic device 1000 can also communicate with one or more external devices 1090 (e.g., keyboard, pointing device, display 1091, etc.), one or more devices that enable a user to interact with electronic device 1000, and / or any device that enables electronic device 1000 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via input / output (I / O) interface 1092. Furthermore, electronic device 1000 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 1093. As shown, network adapter 1093 communicates with other modules of electronic device 1000 via bus 1030. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 1000, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0098] The processor 1020 performs various functional applications and data processing by running programs stored in the memory 1010.

[0099] It should be noted that the implementation process and technical principles of the electronic device in this embodiment are explained in the foregoing description of the renaming processing method based on human-computer interaction in the embodiments of this disclosure, and will not be repeated here.

[0100] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory including instructions, which can be executed by a processor of an electronic device to complete the human-computer interaction-based renaming processing method proposed in any of the above embodiments. Optionally, the computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0101] In an exemplary embodiment, a computer program product is also provided, including a computer program / instruction, characterized in that, when the computer program / instruction is executed by a processor, it implements the human-computer interaction-based renaming processing method proposed in any of the above embodiments.

[0102] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0103] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A renaming processing method based on human-computer interaction, characterized in that, include: In response to a trigger operation on the naming convention component in the human-computer interaction interface, determine whether the currently selected target model is in an editable state; In response to the target model being in an editable state, a set of model elements to be named is determined based on the target context associated with the target model; wherein, the target context includes at least one of a model context and a topic domain context; Based on the naming convention list, query whether the subject domain to which each model element in the model element set belongs is associated with a subject domain-level naming convention; wherein, the subject domain refers to the set of model elements in the target model divided according to business semantics; In response to the topic domain being associated with a topic domain-level naming convention, the topic domain-level naming convention associated with the topic domain is displayed in the human-computer interaction interface; In response to the selection operation of the topic domain-level naming convention associated with the topic domain, the selected topic domain-level naming convention is used as the effective naming convention for the corresponding model element, and the corresponding model element is renamed using the effective naming convention.

2. The method according to claim 1, characterized in that, The naming convention list is updated using the following steps: In response to a trigger operation of a target control in the human-computer interaction interface, a configuration page associated with the target control is displayed; In response to an update operation performed on the configuration page, the type of the update operation is determined based on the target control to update the naming convention list; wherein the type of the update operation includes any one of creating a new naming convention, deleting an existing naming convention, and modifying an existing naming convention.

3. The method according to claim 2, characterized in that, The establishment of a new naming convention includes the following steps: In response to the instruction to create a new naming convention triggered by the target control, the configuration page is displayed; wherein, the configuration page includes an attribute selection area, an assembly rule configuration area, and a preview area; In response to an attribute selection operation performed in the attribute selection area, at least one attribute item is determined to participate in the naming; In response to an assembly rule adjustment operation performed in the assembly rule configuration area, the arrangement order of the at least one attribute item in the assembly order is adjusted, and the format parameters between the at least one attribute item are set; In response to the attribute selection operation and / or the assembly rule adjustment operation, the naming specification preview result under the current assembly rule is calculated and displayed in the preview area; In response to the received confirmation and save command, a naming specification object is generated according to the current assembly rules, and the naming specification object is added to the naming specification list.

4. The method according to claim 1, characterized in that, The step of determining the set of model elements to be named based on the target context associated with the target model includes: Based on the target context associated with the target model, at least one candidate model element is determined; Based on the configuration identifier of each candidate model element, a set of model elements to be named is determined from the at least one candidate model element.

5. The method according to claim 4, characterized in that, The configuration identifier is used to indicate whether the candidate model element is in a nameable state. The step of determining the set of model elements to be named from the at least one candidate model element based on the configuration identifier of each candidate model element includes: Candidate model elements that are configured as being in a nameable state are identified as model elements to be named.

6. The method according to claim 1, characterized in that, The renaming process of the corresponding model element using the effective naming specification includes: According to the attribute item arrangement order configured in the effective naming specification, extract the attribute values ​​of the corresponding model elements under each attribute item in sequence; The extracted attribute values ​​are filtered, and the valid attribute values ​​remaining after filtering are sequentially converted into name format to obtain formatted attribute value fragments. According to the delimiter configured in the effective naming specification, the formatted attribute value fragments are concatenated to form an intermediate string; According to the prefix and suffix configured in the effective naming specification, they are appended to the beginning and end of the intermediate string respectively to generate the target name of the corresponding model element.

7. The method according to claim 1, characterized in that, The method further includes: In response to the target model's current design mode being shared mode, the system switches to the current user's personal branch; wherein, the shared mode indicates that the target model can be accessed by multiple users simultaneously, and the personal branch is an independent working copy derived from the target model's main branch, used to isolate the current user's modification operations on model elements; In response to a rename operation in a batch normalization operation performed within the individual branch, at least one model element in the target model is renamed; After the name change is completed, the changes in the individual branch will be merged with the main branch of the target model; If a renaming conflict is detected with other users for the same model element during the merging process, the conflict is handled according to a preset conflict resolution rule; wherein the conflict resolution rule is selected from at least one of the following: a rule based on retaining the modification after the timestamp, a rule based on user priority to retain the modification by the higher priority user, or a rule that prompts the user to make a manual decision.

8. The method according to claim 1, characterized in that, The method further includes: If the topic domain is not associated with a topic domain-level naming convention, query whether the target model is associated with a model-level naming convention. In response to the target model being associated with a model-level naming convention, the model-level naming convention is adopted as the effective naming convention for the subject domain and all model elements under the subject domain.

9. The method according to claim 1, characterized in that, The method further includes: The result set obtained by renaming the model element set is divided into multiple batches according to a preset batch size; The multiple batches are persistently stored, and according to the current design mode of the target model, the new names in each batch are updated to the corresponding model elements in the storage layer corresponding to the current design mode.

10. A renaming processing device based on human-computer interaction, characterized in that, include: The first determination module is used to determine whether the currently selected target model is in an editable state in response to the trigger operation of the naming convention component in the human-computer interaction interface. The second determining module is configured to, in response to the target model being in an editable state, determine a set of model elements to be named based on the target context associated with the target model; wherein the target context includes at least one of a model context and a topic domain context; The query module is used to query whether the subject domain to which each model element in the model element set belongs is associated with a subject domain-level naming convention, based on the naming convention list; wherein, the subject domain refers to the set of model elements in the target model divided according to business semantics; The third determining module is used to display the topic domain-level naming convention associated with the topic domain in the human-computer interaction interface in response to the topic domain being associated with a topic domain-level naming convention. The processing module is configured to respond to the selection operation of the topic domain-level naming convention associated with the topic domain, use the selected topic domain-level naming convention as the effective naming convention for the corresponding model element, and perform renaming processing on the corresponding model element using the effective naming convention.

Images