Business characteristic management method, apparatus, device, and storage medium

Abstract

The application discloses a service characteristic management method, device and equipment and a storage medium, belongs to the technical field of software development, and is applied to an integrated software system. The method comprises the following steps: obtaining an implementation code corresponding to a to-be-developed service characteristic; determining a characteristic program file of the to-be-developed service characteristic, and writing the implementation code in the characteristic program file, wherein one characteristic program file corresponds to one service characteristic. The application provides a service characteristic management strategy to improve the stability of the integrated software system.

Description

Technical Field

[0001] This application belongs to the field of software development technology, and in particular relates to a business characteristic management method, apparatus, device and storage medium. Background Technology

[0002] With the continuous development of information technology, the scale and business complexity of industrial software are gradually increasing.

[0003] Currently, for industrial control automation software, an integrated software system can include multiple integrated solutions. An integrated solution can include various different devices such as PLC (Programmable Logic Controller), HMI (Human Machine Interface), PAC (Programmable Automation Controller), machine vision, servo drives, and frequency converters. Moreover, the versions of multiple identical devices may be different. However, the business functions provided by each device in each integrated solution are all written in the same program code of the integrated software system. Therefore, when adding a new business feature (business feature refers to the specific implementation method of business function) to a new device version or modifying the business feature of a specific device version, it is usually necessary to introduce new code into an entire program code. This is equivalent to introducing new code into a software environment that has already been tested and stabilized, which will lead to instability of the integrated software system.

[0004] In summary, how to provide a business characteristic management strategy to improve the stability of integrated software systems has become an urgent technical problem to be solved in the field of software development technology. Summary of the Invention

[0005] The primary objective of this application is to provide a business characteristic management method, apparatus, device, and storage medium. The aim is to offer a business characteristic management strategy to improve the stability of integrated software systems.

[0006] To achieve the above objectives, this application provides a business characteristic management method, which is applied to an integrated software system and includes the following steps:

[0007] Obtain the implementation code corresponding to the business features to be developed;

[0008] The feature program file for the business feature is determined, and the implementation code is written into the feature program file, wherein one feature program file corresponds to one business feature.

[0009] Optionally, the step of determining the feature program file of the service feature includes:

[0010] Obtain the development type of the aforementioned business characteristics;

[0011] If the development type is a new feature type, create the feature program file for the business feature;

[0012] When the development type is a feature modification type, the feature program file of the business feature is obtained based on the identity of the business feature.

[0013] Optionally, after the step of writing the implementation code in the feature program file, the method further includes:

[0014] Based on the identity identifier and feature program file of the aforementioned business feature, a first feature instance corresponding to the business feature is created for invocation and execution.

[0015] Optionally, before the step of obtaining the implementation code corresponding to the business feature to be developed, the method further includes:

[0016] Extract the identity identifier and file path of the original business characteristics from the preset configuration file;

[0017] Obtain the feature program file of the original business feature from the file path;

[0018] A second characteristic instance corresponding to the original business characteristic is created based on the identity identifier and characteristic program file of the original business characteristic for invocation and execution.

[0019] Optionally, after the step of writing the implementation code in the feature program file, the method further includes:

[0020] The configuration file is updated based on the identity identifier and feature program file of the aforementioned business characteristics.

[0021] Optionally, the integrated software system includes a user interface, and the method further includes:

[0022] Obtain the device description file of the integrated solution to be loaded, and extract the identity identifier of the service characteristics to be displayed from the device description file;

[0023] Based on the identity identifier of the service characteristic to be displayed, obtain the button element of the service characteristic to be displayed, and display the button element on the user interface.

[0024] Optionally, after the step of displaying the button element on the user interface, the method further includes:

[0025] Upon receiving a call instruction triggered by the user based on the button element, obtain the target identity identifier in the call instruction;

[0026] Based on the target identity, a target feature instance is determined from the first feature instance and the second feature instance, and the interface of the target feature instance is called to execute the target feature instance.

[0027] Furthermore, to achieve the above objectives, this application also provides a business characteristic management device, which is applied to an integrated software system and includes the following steps:

[0028] The acquisition module is used to acquire the implementation code corresponding to the business features to be developed.

[0029] The writing module is used to determine the feature program file of the business feature and write the implementation code into the feature program file, wherein one feature program file corresponds to one business feature.

[0030] In addition, to achieve the above objectives, this application also provides a service characteristic management device, which includes: a memory, a processor, and a service characteristic management program stored in the memory and executable on the processor. When the service characteristic management program of the service characteristic management device is executed by the processor, it implements the steps of the service characteristic management method as described above.

[0031] In addition, to achieve the above objectives, this application also provides a computer-readable storage medium storing a service feature management program, which, when executed by a processor, implements the steps of the service feature management method described above.

[0032] This application embodiment obtains the implementation code corresponding to the business feature to be developed in the integrated software system and writes the implementation code into the feature program file corresponding to the current business feature. One feature program file corresponds to one business feature. Therefore, compared to the traditional business feature management method of introducing new code into the corresponding overall code block of the system, this application embodiment sets one feature program file to store only the implementation code of one business feature. Thus, when developing a business feature in the integrated software system, only the new code needs to be introduced into the feature program file of the business feature to be developed. This achieves the isolation of the implementation code of each business feature in the system. Developing one business feature will not affect the software environment of other business features in the integrated software system, ensuring that the scope of software changes is controllable and thereby improving the stability of the integrated software system. Attached Figure Description

[0033] Figure 1 This is a schematic diagram of the hardware operating environment of the business characteristic management device involved in the embodiments of this application;

[0034] Figure 2 This is a flowchart illustrating the steps of the first embodiment of the business characteristic management method of this application;

[0035] Figure 3 This is a schematic diagram of the feature registration process involved in one embodiment of the business feature management method of this application;

[0036] Figure 4 This is a schematic diagram of the feature execution flow involved in an embodiment of the business feature management method of this application;

[0037] Figure 5 This is a schematic diagram of the functional modules of an embodiment of the business characteristic management device of this application.

[0038] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0039] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0040] Reference Figure 1 , Figure 1 This is a schematic diagram of the hardware operating environment of the service characteristic management device involved in the embodiments of this application.

[0041] It should be noted that the embodiments of this application relate to a business characteristic management device integrating an integrated software system in the field of software development technology. Specifically, the business characteristic management device can be a smartphone, PC (Personal Computer), tablet computer, portable computer, etc.

[0042] like Figure 1 As shown, the service characteristic management device may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or stable non-volatile memory, such as a disk storage device. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001. For ease of description, the execution entity of the method steps in each embodiment is omitted below.

[0043] Those skilled in the art will understand that Figure 1 The structure of the service characteristic management device shown does not constitute a limitation on the service characteristic management device. It may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0044] like Figure 1 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a service feature management program.

[0045] exist Figure 1 In the terminal shown, network interface 1004 is mainly used to connect to the backend server and communicate with it; user interface 1003 is mainly used to connect to the client and communicate with it; and processor 1001 can be used to call the service feature management program stored in memory 1005 and perform the following operations:

[0046] Obtain the implementation code corresponding to the business features to be developed;

[0047] The feature program file for the business feature is determined, and the implementation code is written into the feature program file, wherein one feature program file corresponds to one business feature.

[0048] Furthermore, the operation of determining the characteristic program file of the business characteristics includes:

[0049] Obtain the development type of the aforementioned business characteristics;

[0050] If the development type is a new feature type, create the feature program file for the business feature;

[0051] When the development type is a feature modification type, the feature program file of the business feature is obtained based on the identity of the business feature.

[0052] Furthermore, after the step of writing the implementation code into the feature program file, the processor 1001 can also be used to call the service feature management program stored in the memory 1005 to perform the following operations:

[0053] Based on the identity identifier and feature program file of the aforementioned business feature, a first feature instance corresponding to the business feature is created for invocation and execution.

[0054] Furthermore, before the step of obtaining the implementation code corresponding to the business feature to be developed, the processor 1001 can also call the business feature management program stored in the memory 1005 to perform the following operations:

[0055] Extract the identity identifier and file path of the original business characteristics from the preset configuration file;

[0056] Obtain the feature program file of the original business feature from the file path;

[0057] A second characteristic instance corresponding to the original business characteristic is created based on the identity identifier and characteristic program file of the original business characteristic for invocation and execution.

[0058] Furthermore, after the step of writing the implementation code into the feature program file, the processor 1001 can also be used to call the service feature management program stored in the memory 1005 to perform the following operations:

[0059] The configuration file is updated based on the identity identifier and feature program file of the aforementioned business characteristics.

[0060] Furthermore, the integrated software system includes a user interface, and the processor 1001 can also be used to call the service feature management program stored in the memory 1005 to perform the following operations:

[0061] Obtain the device description file of the integrated solution to be loaded, and extract the identity identifier of the service characteristics to be displayed from the device description file;

[0062] Based on the identity identifier of the service characteristic to be displayed, obtain the button element of the service characteristic to be displayed, and display the button element on the user interface.

[0063] Furthermore, after the step of displaying the button element on the user interface, the processor 1001 can also be used to call the service feature management program stored in the memory 1005 to perform the following operations:

[0064] Upon receiving a call instruction triggered by the user based on the button element, obtain the target identity identifier in the call instruction;

[0065] Based on the target identity, a target feature instance is determined from the first feature instance and the second feature instance, and the interface of the target feature instance is called to execute the target feature instance.

[0066] Based on the above structure, various embodiments of the business characteristic management method are proposed.

[0067] Currently, when multiple different versions of devices share a certain function, companies often add checks for device versions in the code to ensure software code reuse and compatibility. For example, if the device version matches the characteristics, the logic for that specific version is executed; otherwise, general logic is executed. In the user interface, each device version may also have its own unique data structure and data storage mode. During saving or communication, an adaptation layer or forced conversion is used to unify the data structure and storage mode. Under this current technological model, the scalability of the software code is very poor. Adding support for a new device version or modifying the code of a specific device version will affect the functionality of other versions of that device. It's equivalent to constantly introducing new code for already tested and stable functions, affecting the overall stability of the version. From a programming design principle perspective, this model also violates the "open / closed principle" in object-oriented software development, which states that stable code should be closed to modification but open only to extension. With the continuous emergence of new businesses, the strong dependencies in the code will keep older functions in an unstable state, becoming a constraint on the development of the enterprise's digital ecosystem.

[0068] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of the business characteristic management method of this application. It should be noted that although the logical order is shown in the flowchart, in some cases, the business characteristic management method of this application may execute the steps shown or described in a different order. In this embodiment, the executing entity of the business characteristic management method can be a personal computer, smartphone, or other device, and this is not limited thereto. The business characteristic management method includes S10 to S20:

[0069] Step S10: Obtain the implementation code corresponding to the business feature to be developed.

[0070] It should be noted that an integrated software system can be understood as an integrated software platform. An integrated software system can include the individual business characteristics of each device in multiple integrated solutions; that is, the functions of each business characteristic can be used within the integrated software system. "Business" refers to the functionality that the device can provide (e.g., a camera's photo-taking function), and "business characteristic" refers to the specific implementation method of that function (e.g., a beauty mode or a landscape mode). Each business characteristic in the integrated software system is defined with a globally unique GUID (Globally Unique Identifier). It should be understood that when a new business characteristic is added to the integrated software system, an identity identifier (i.e., the aforementioned globally unique identifier) ​​is predefined for the new business characteristic. This GUID will correspond to the GUID of the characteristic function in the program.

[0071] In an integrated software system, the business features to be developed can be either business features to be further developed or business features to be extended. When the business feature to be developed is a business feature to be further developed, it means that the existing business features in the integrated software system are modified to obtain the business feature to be developed, which usually involves optimizing the existing business features. When the business feature to be developed is a business feature to be created, it means that the business feature to be developed is added to the integrated software system.

[0072] When obtaining the implementation code corresponding to the business feature to be developed, it should be understood that the implementation code is the program code that the developers have developed in advance to implement the business feature to be developed.

[0073] Step S20: Determine the feature program file of the business feature, and write the implementation code into the feature program file, wherein one feature program file corresponds to one business feature.

[0074] Determine the feature program file for the business feature to be developed. One feature program file corresponds to one business feature. Write the implementation code of the business feature to be developed into the feature program file.

[0075] It should be noted that the aforementioned feature program file can also be a feature program assembly (also known as an assembly program assembly), which means that the implementation code of a business feature is stored in at least one file. When the implementation code of a business feature is stored in a feature program assembly, the implementation code can be divided into multiple parts based on the specific logical requirements of the implementation code and stored in the sub-files of the feature program assembly respectively, which can also ensure the controllability of the scope of changes.

[0076] In one feasible implementation, the implementation code of the business feature to be developed is provided by the R&D personnel, the feature program file used to store the implementation code is determined by the integration software system, and the implementation code is written into the feature program file after the implementation code is obtained, so that the business feature to be developed can be used later.

[0077] In this embodiment, step S20 includes steps S201 to S203:

[0078] Step S201: Obtain the development type of the business feature.

[0079] The development type of the business feature to be developed can be either the feature addition type or the feature modification type. It should be noted that the feature addition type corresponds to the business feature to be further developed, and the feature modification type corresponds to the business feature to be extended.

[0080] This application does not restrict the method of obtaining the development type. For example, in one feasible implementation, a development task is pre-set to package the implementation code and development type information corresponding to the business characteristics to be developed. When the integrated software system receives the development task, the development task is unpacked to obtain the implementation code and development type.

[0081] Step S202: If the development type is a new feature type, create the feature program file for the business feature.

[0082] When the development type is a new feature type, a feature program file for the business feature is created at a preset address to store the implementation code of the business feature to be developed.

[0083] In a specific implementation, when the integrated software system needs to add a new business feature (i.e., a business feature to be developed), assuming that the business feature to be developed is a beauty mode feature for camera, a new feature program file is created based on the business feature to be developed. The new feature program file is used to store the implementation code of the beauty mode feature.

[0084] Step S203: If the development type is a feature modification type, obtain the feature program file of the business feature based on the identity identifier of the business feature.

[0085] It should be noted that, assuming the integrated software system includes three integration solutions, namely Solution 1, Solution 2, and Solution 3, Solution 1 includes device A and device B, Solution 2 includes device A and device C, and Solution 3 includes device D and device E. Device A has business characteristic 1, device B has business characteristic 2, device C has business characteristic 3, device D has business characteristics 4 and 5, and device E has business characteristic 6. The identity information of all callable business characteristics (i.e., characteristics 1, 2, 3, 4, and 5) in the current integrated software system and the corresponding file paths of these identities are stored in a configuration file beforehand. When the development type is characteristic modification type, the file path corresponding to the current identity is determined from the configuration file of the integrated software system based on the identity of the business characteristic. The characteristic program file of the current business characteristic is obtained from that file path. That is, the characteristic program file is the existing characteristic program file in the integrated software system used to implement the business characteristic.

[0086] In a specific implementation, when the integrated software system needs to modify a business feature, the modified business feature is referred to as the aforementioned business feature to be developed. Assuming that the business feature to be modified is the device's normal photography feature, and the business feature to be developed is the device's beautification photography feature, then, firstly, based on the unique identifier corresponding to the normal photography feature, the feature program file corresponding to the identifier is determined in the configuration file of the integrated software system. Then, based on the implementation code of the beautification photography feature, the existing code in the feature program file is modified or overwritten, thereby completing the development of the beautification photography feature.

[0087] Thus, this application addresses the iterative integration of multi-device systems (components) with different device versions, business functions, and industries encountered during software development in the industrial control industry through a convenient, secure, efficient, and highly scalable business characteristic technology (framework). It also resolves the impact (on existing business logic) caused by updates or additions to a single device's business function. Specifically, this application obtains the implementation code corresponding to the business characteristic to be developed in the integrated software system and writes this implementation code into the characteristic program file corresponding to the current business characteristic. One characteristic program file corresponds to one business characteristic. Compared to the traditional business characteristic management method of introducing new code into the overall code block of the system, this application's embodiment sets one characteristic program file to store only the implementation code of one business characteristic. Therefore, when developing a business characteristic in the integrated software system, only the new code needs to be introduced into the characteristic program file of the business characteristic to be developed. This achieves the isolation of the implementation code of each business characteristic in the system. Developing one business characteristic will not affect the software environment of other business characteristics in the integrated software system, thus ensuring that the scope of software changes is controllable and improving the stability of the integrated software system.

[0088] Furthermore, based on the first embodiment of the business characteristic management method of this application described above, a second embodiment of the business characteristic management method of this application is proposed.

[0089] In this embodiment, after step S20, step A10 is further included:

[0090] Step A10: Based on the identity identifier and feature program file of the business feature, create a first feature instance corresponding to the business feature for invocation and execution.

[0091] A feature instance can also be called an object instance. An object instance refers to software logic, while a feature instance of a business feature refers to the software logic (which can be understood as program code) that implements the functionality of that business feature. Based on the identity of the business feature to be developed and the feature program file, a feature instance corresponding to the business feature is created (hereinafter referred to as the first feature instance for distinction). This first feature instance is used for subsequent calls and executions to use the business feature.

[0092] In a specific implementation, the integration software system (also known as the integration platform) binds the identity identifier and feature program file of the business feature to be developed to generate a first feature instance corresponding to that business feature. It should be understood that the current identity identifier can also serve as the identity identifier of the first feature instance, so that the first feature instance to be executed can be obtained subsequently based on the identity identifier. After obtaining the first feature instance, it is stored in a container (the container where the integration software system resides) or in a memory dictionary. When storing the first feature instance in a memory dictionary, the key of the dictionary is the identity identifier of the first feature instance, and the value of the dictionary is the feature program file of the first feature instance.

[0093] In this embodiment, before step S10, steps B10 to B30 are also included:

[0094] Step B10: Extract the identity identifier and file path of the original business characteristics from the preset configuration file.

[0095] The aforementioned pre-defined configuration file refers to the configuration file of the integrated software system. When developers are developing the integrated software system, they add an integration solution to the system according to actual needs. Then, the implementation code for the business characteristics of each device available to users in the integrated software system is written into the characteristic program file. There is a one-to-one correspondence between business characteristics and characteristic program files. Furthermore, GUIDs are pre-defined for the business characteristics of each device, and the GUIDs of the business characteristics are associated with the storage path of the characteristic program files and saved in the configuration file. It can be understood that the configuration file includes information on at least one business characteristic.

[0096] When developing an integrated software system for the first time, obtain the configuration file of the integrated software system, and extract the identity identifier of each business characteristic (hereinafter referred to as the original business characteristic for distinction) and the file path corresponding to each identity identifier from the configuration file.

[0097] Step B20: Obtain the feature program file of the original business feature from the file path.

[0098] When there are multiple original business characteristics, the characteristic program files of each original business characteristic are obtained based on each file path.

[0099] Step B30: Create a second characteristic instance corresponding to the original business characteristic based on the identity identifier and characteristic program file of the original business characteristic for invocation and execution.

[0100] Based on the identity identifier and feature program file of the original business feature, a feature instance corresponding to the original business feature is generated (hereinafter referred to as the second feature instance for distinction). The second feature instance is used for subsequent calls and execution.

[0101] In a specific implementation, assuming the configuration file of the current integrated software system includes ordinary camera features, beauty camera features, and landscape camera features for the camera class, and network format A, network format B, and network format C for the call class, then we will use the component-based development framework Prism as an example for explanation. The approach is the same for other component-based frameworks or IOC (Inversion of Control) container frameworks. First, the integrated software system starts and reads the feature registration configuration file (i.e., the aforementioned preset configuration file). The read feature GUID and feature Assembly are registered in the IOC container. If there is no component-based development framework, the read feature GUID and feature Assembly are stored in memory as a dictionary, where the key is the GUID and the value is the address of the Assembly.

[0102] For example, such as Figure 3 The diagram shows the feature registration process. The system obtains the identity identifier and file address from the preset configuration file through the integration platform. Based on the file address, it obtains the device business feature function file (i.e., the feature program file mentioned above). It establishes the association between the identity identifier and the feature program file of each business feature to obtain the feature instance. The feature instance is then injected into a container or memory dictionary for subsequent calls and execution.

[0103] In this embodiment, after step S20, step C10 is further included:

[0104] Step C10: Update the configuration file based on the identity identifier and feature program file of the business characteristics.

[0105] Associate the identity and feature program files of the current business characteristics with them and save them to the configuration file of the integrated software system in order to update the configuration file.

[0106] It should be noted that, in order to achieve graceful compatibility across multiple devices in terms of business operations, this application abstracts the device and its version information into a text description. The application associates the device's business characteristic identifier with the device and generates a device description file. When an integration solution includes multiple devices, the device description information for each device can be stored in the same device description file, or each device's device description information can be stored in a separate device description file; this application does not impose any restrictions on this. Therefore, upon receiving a secondary development task or an extended development task, the identifier of the business characteristic to be developed is associated with the device and stored in the corresponding device description file to update the device description file.

[0107] Therefore, this application develops independent feature plugin programs for the features of different device versions, and physically isolates each version's feature program from the file set, ensuring that the addition and modification of features will not affect other feature program sets. This way, when adding support for a new device version or modifying the code of a specific device version, only the specific code file needs to be added or modified, ensuring that the scope of additions and modifications is controllable. Through dependency decoupling and lazy loading, the features of multi-device services are changed from being hard-coded into the code to being linked to the features and code implementation through configuration. This solves the problem of mutual interference and instability when multiple devices and multiple versions of services are loaded simultaneously. During secondary or extended development, it significantly reduces the investment of full-scale testing resources required to address the impact of new features on previous functions, reducing program development costs. Furthermore, this application's business feature management method is suitable for long-term iterative development and has excellent architectural evolution capabilities, adapting to the needs of different stages in the development of industrial automation software.

[0108] Furthermore, based on the first and / or second embodiments of the business characteristic management method of this application described above, a third embodiment of the business characteristic management method of this application is proposed.

[0109] In this embodiment, the integrated software system includes a user interface, and the business characteristic management method of this application further includes steps D10 to D20:

[0110] Step D10: Obtain the device description file of the integrated solution to be loaded, and extract the identity identifier of the service characteristics to be displayed from the device description file.

[0111] For industrial control automation software, an integrated solution typically includes various devices such as PLCs, HMIs, PACs, machine vision systems, servo drives, and frequency converters. Even within a solution, multiple HMI devices may be different versions. Therefore, to ensure graceful compatibility across multiple devices in terms of business requirements, this application abstracts the device and version information into textual descriptions. Specifically, it establishes an association between each device and its unique business characteristics, storing these associations in a device description file. One integrated solution corresponds to one device description file.

[0112] Obtain the device description file of the integrated solution to be loaded, extract the business characteristics (hereinafter referred to as the business characteristics to be displayed for distinction) from the device description file, and extract the identity identifier of the business characteristics to be displayed.

[0113] Step D20: Obtain the button element of the service characteristic to be displayed based on the identity identifier of the service characteristic to be displayed, and display the button element on the user interface.

[0114] When R&D personnel develop integrated software systems, after determining the identity identifier and feature program files of the device's business characteristics, they will also design the display icon corresponding to the business characteristics, namely the button elements mentioned above, which are displayed on the user interface for users to click and trigger.

[0115] The button element for the business characteristic to be displayed is obtained based on the identity of the business characteristic to be displayed, and then the button element is displayed on the user interface. In other words, the integrated software system can only load the integrated solution serially, and the user interface only displays the button element for the business characteristic corresponding to the currently loaded integrated solution.

[0116] In a specific implementation, when the integrated software system loads the integrated solution, it reads the corresponding device description file according to the device description in the solution, and binds the GUID in the file to the elements on the UI (User Interface).

[0117] In this embodiment, after step D20, steps E10 to E20 are also included:

[0118] Step E10: Upon receiving a call instruction triggered by the user based on the button element, obtain the target identity identifier in the call instruction.

[0119] This allows users to trigger a call instruction by clicking a button element on the user interface. Since the button element is associated with the identity of the business characteristic, the call instruction carries the identity of the business characteristic to be used (hereinafter referred to as the target identity for distinction).

[0120] Step E20: Determine the target feature instance from the first feature instance and the second feature instance based on the target identity, and call the interface of the target feature instance to execute the target feature instance.

[0121] After obtaining the target identity carried in the call instruction, the characteristic instance corresponding to the target identity is determined from the first characteristic instance and the second characteristic instance (hereinafter referred to as the target characteristic instance for distinction) based on the target identity. The interface of the target characteristic instance is called based on the call instruction to execute the target characteristic instance.

[0122] In one feasible implementation, when the program triggers an element on the UI (User Interface) during human-computer interaction, it retrieves the corresponding object instance from the IOC container based on the GUID information bound to the UI element, and then executes the instance's interface methods. In another feasible implementation, when the program triggers an element on the UI during human-computer interaction, it retrieves the address of the corresponding Assembly from a dictionary in memory based on the GUID information bound to the UI element, loads the assembly using reflection, initializes the object, and then executes the instance's interface methods.

[0123] For example, such as Figure 4 The diagram shows the feature execution process. First, the integration platform obtains the GUID of the business feature triggered by the user, performs business scheduling on the execution request, then obtains the feature instance corresponding to the GUID from the container based on the GUID, executes the feature instance, and then receives the result of the business feature execution, thus completing the business feature execution process.

[0124] Thus, this application defines a device description file and a UI interface, and displays elements corresponding to the business characteristics provided by the current integrated solution on the UI interface based on the device description file corresponding to the currently loaded integrated solution, so that users can trigger call commands based on the UI interface to complete the business process.

[0125] In addition, this application embodiment also provides a business characteristic management device, which applies an integrated software system.

[0126] Please refer to Figure 5 , Figure 5 This is a functional module diagram of an embodiment of the business characteristic management device of this application, as shown below. Figure 5 As shown, the service characteristic management device of this application includes:

[0127] Module 10 is used to obtain the implementation code corresponding to the business features to be developed;

[0128] The writing module 20 is used to determine the feature program file of the business feature and write the implementation code into the feature program file, wherein one feature program file corresponds to one business feature.

[0129] Furthermore, the writing module 20 is also used to obtain the development type of the business feature; if the development type is a feature addition type, to create a feature program file for the business feature; if the development type is a feature modification type, to obtain the feature program file for the business feature based on the identity identifier of the business feature.

[0130] Furthermore, the business characteristic management device of this application also includes:

[0131] Based on the identity identifier and feature program file of the aforementioned business feature, a first feature instance corresponding to the business feature is created for invocation and execution.

[0132] Furthermore, the business characteristic management device of this application also includes:

[0133] Extract the identity identifier and file path of the original business characteristics from the preset configuration file;

[0134] Obtain the feature program file of the original business feature from the file path;

[0135] A second characteristic instance corresponding to the original business characteristic is created based on the identity identifier and characteristic program file of the original business characteristic for invocation and execution.

[0136] Furthermore, the business characteristic management device of this application also includes:

[0137] The configuration file is updated based on the identity identifier and feature program file of the aforementioned business characteristics.

[0138] Furthermore, the integrated software system includes a user interface, and the business characteristic management device of this application further includes:

[0139] Obtain the device description file of the integrated solution to be loaded, and extract the identity identifier of the service characteristics to be displayed from the device description file;

[0140] Based on the identity identifier of the service characteristic to be displayed, obtain the button element of the service characteristic to be displayed, and display the button element on the user interface.

[0141] Furthermore, the business characteristic management device of this application also includes:

[0142] Upon receiving a call instruction triggered by the user based on the button element, obtain the target identity identifier in the call instruction;

[0143] Based on the target identity, a target feature instance is determined from the first feature instance and the second feature instance, and the interface of the target feature instance is called to execute the target feature instance.

[0144] This application also provides a computer storage medium storing a service feature management program, which, when executed by a processor, implements the steps of the service feature management program method as described in any of the above embodiments.

[0145] The specific embodiments of the computer storage medium in this application are basically the same as the embodiments of the business characteristic management program method described above, and will not be repeated here.

[0146] This application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the business feature management method of this application as described in any of the above embodiments, which will not be elaborated here.

[0147] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0148] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0149] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a service feature management device (such as TWS earphones) to execute the methods described in the various embodiments of this application.

[0150] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A business characteristic management method, characterized in that, The business characteristic management method is applied to an integrated software system, and the business characteristic management method includes the following steps: Obtain the implementation code corresponding to the business features to be developed; The feature program file for the business feature is determined, and the implementation code is written into the feature program file, wherein one feature program file corresponds to one business feature; Before the step of obtaining the implementation code corresponding to the business feature to be developed, the method further includes: Extract the identity and file path of the original business characteristics from the preset configuration file; Obtain the feature program file of the original business feature from the file path; A second characteristic instance corresponding to the original business characteristic is created based on the characteristic program file and identity identifier of the original business characteristic for invocation and execution.

2. The business characteristic management method as described in claim 1, characterized in that, The step of determining the feature program file for the business characteristics includes: Obtain the development type of the aforementioned business characteristics; If the development type is a new feature type, create the feature program file for the business feature; When the development type is a feature modification type, the feature program file of the business feature is obtained based on the identity of the business feature.

3. The business characteristic management method as described in claim 1, characterized in that, After the step of writing the implementation code in the feature program file, the method further includes: Based on the identity identifier and feature program file of the aforementioned business feature, a first feature instance corresponding to the business feature is created for invocation and execution.

4. The business characteristic management method as described in claim 1, characterized in that, After the step of writing the implementation code in the feature program file, the method further includes: The configuration file is updated based on the identity identifier and feature program file of the aforementioned business characteristics.

5. The business characteristic management method as described in claim 3, characterized in that, The integrated software system includes a user interface, and the method further includes: Obtain the device description file of the integrated solution to be loaded, and extract the identity identifier of the service characteristics to be displayed from the device description file; Based on the identity identifier of the service characteristic to be displayed, obtain the button element of the service characteristic to be displayed, and display the button element on the user interface.

6. The business characteristic management method as described in claim 5, characterized in that, After the step of displaying the button element on the user interface, the method further includes: Upon receiving a call instruction triggered by the user based on the button element, the target identity identifier in the call instruction is obtained; Based on the target identity, a target feature instance is determined from the first feature instance and the second feature instance, and the interface of the target feature instance is called to execute the target feature instance.

7. A business characteristic management device, characterized in that, The business characteristic management device is applied to an integrated software system, and the business characteristic management device includes the following steps: The acquisition module is used to acquire the implementation code corresponding to the business features to be developed. A writing module is used to determine the feature program file of the business feature and write the implementation code into the feature program file, wherein one feature program file corresponds to one business feature; The service characteristic management device further includes: Extract the identity and file path of the original business characteristics from the preset configuration file; Obtain the feature program file of the original business feature from the file path; A second characteristic instance corresponding to the original business characteristic is created based on the characteristic program file and identity identifier of the original business characteristic for invocation and execution.

8. A business characteristic management device, characterized in that, The service feature management device includes a memory and a processor. The memory stores a service feature management program that can run on the processor. When the service feature management program is executed by the processor, it implements the steps of the service feature management method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a service feature management program, which, when executed by a processor, implements the steps of the service feature management method as described in any one of claims 1 to 6.

Images