Method, device and equipment for adaptively converting user demand into achievement

Abstract

The invention discloses a method, device and equipment for adaptively converting a user demand into an achievement, and the method comprises the steps: responding to user input information, employing the user input information to carry out the matching in a template library to obtain a target template file, and the user input information comprises a function module and field information; a specific symbol in the target template file is analyzed, a target code file is generated, and the target code file comprises a plurality of code snippets; integrating the target code file into each directory of the source program to obtain a Java file; the method comprises the following steps: calling an Execute method of an Invoker class through a Maven tool to compile a Java file to obtain an executable Class file; and loading the executable Class file through the Class Loader on the basis of a reflection mechanism. The technical problem that the actual system development efficiency is low due to the fact that an existing user demand conversion process is too complex, time-consuming and labor-consuming can be solved.

Description

Technical Field

[0001] The present application relates to the field of system development technology, and in particular to a method, device and equipment for adaptively converting user needs into results. Background Art

[0002] With the continuous development and popularization of informatization, enterprise information management system has become an indispensable part of enterprise management. Enterprise information management system can effectively realize enterprise informatization and digital management, improve enterprise management efficiency, reduce enterprise management costs, and thus occupy an advantageous position in market competition and obtain more business opportunities and benefits. However, the construction of enterprise information management system is not achieved overnight, and requires a series of processes and links.

[0003] Specifically, it is necessary to analyze user needs. The purpose of demand analysis is to understand user needs and convert them into executable plans to guide system development. It is necessary to consider the completeness, practical feasibility and scalability of user requirements. In this stage, user surveys are required to determine the functions and technical solutions required by the system. Based on the demand analysis, system design is carried out. It is necessary to define the overall architecture of the system, including the front-end, back-end, data storage, etc. R&D personnel and product managers need to work closely together to develop a complete technical document and product design document, including technology selection, coding specifications, database design, etc. After completing the system design, the next step is to enter the coding stage. One or more programming languages ​​are required to implement the program code. While writing the code, it is necessary to develop the program according to the demand documents and system design documents. Developers also need to improve the code according to code comments, version management and document descriptions. After completing the program code, testing is required. Testing includes unit testing, integration testing, system testing, performance testing, etc. It is necessary to set up test plans, test cases, test data, and record test results. Focus on testing the scalability, stability and correctness of the external interface of the system. After testing, the system needs to be deployed. You need to select the server operating environment, configure the necessary system environment, and configure related application services such as Web servers, databases, proxies, and reverse proxies. After deploying the system, you need to optimize the system performance. If you are adding new features to the existing system, you need to make various preparations and upgrade the system.

[0004] Based on the above process, it can be seen that it is a long process from user demand to application, which can take a few days at least, more than ten days or even longer. Even for a simple demand, such as adding a new user module, the whole process is time-consuming and labor-intensive, and the efficiency is very low, which makes it difficult to meet development needs. Summary of the invention

[0005] The present application provides a method, device and equipment for adaptively converting user needs into results, which is used to solve the technical problem that the existing process of converting user needs is too complicated, time-consuming and labor-intensive, resulting in low efficiency in actual system development.

[0006] In view of this, the first aspect of the present application provides a method for adaptively converting user needs into results, including:

[0007] In response to user input information, the target template file is obtained by matching the user input information in the template library, wherein the user input information includes function modules and field information;

[0008] Parsing specific symbols in the target template file to generate a target code file, wherein the target code file includes multiple code fragments;

[0009] Integrate the target code files into various directories of the source program to obtain Java files;

[0010] The Execute method of the Invoker class is called by the Maven tool to compile the Java file to obtain an executable Class file;

[0011] Based on the reflection mechanism, the executable Class file is loaded through ClassLoader.

[0012] Preferably, in response to the user input information, the target template file is obtained by matching the user input information in the template library, and the method further includes:

[0013] In response to a user's new addition request, receiving module information entered by the user, and creating a functional module according to the module information, wherein the module information includes a module level and a module name;

[0014] On the basis of the functional modules, field information entered by the user is received, wherein the field information includes field name, data type, data length and display type.

[0015] Preferably, in response to the user input information, the target template file is obtained by matching the user input information in the template library, and the method further includes:

[0016] Multiple types of template files are written in a template generator, and specific symbols are marked to generate a template library, which includes template information.

[0017] Preferably, the process of calling the Execute method of the Invoker class by the Maven tool to compile the Java file to obtain an executable Class file further includes:

[0018] The executable Class file is validated to obtain a validation result.

[0019] Preferably, the loading of the executable Class file through ClassLoader based on the reflection mechanism includes:

[0020] Querying basic file information according to the module information of the functional module, the basic file information including the file name, storage path and full class name;

[0021] Based on the reflection mechanism, the target class is searched through ClassLoader according to the full name of the class;

[0022] Extract class objects according to the target class, match corresponding methods, and obtain executable Class files.

[0023] Preferably, the method of loading the executable Class file through ClassLoader based on the reflection mechanism also includes:

[0024] During the idle time period, the executable Class file is initialized to the system application directory by restarting the system to complete the file loading.

[0025] The second aspect of the present application provides a device for adaptively converting user needs into results, including:

[0026] A template matching unit, configured to respond to user input information and use the user input information to match a target template file in a template library, wherein the user input information includes function modules and field information;

[0027] A code generation unit, used for parsing specific symbols in the target template file to generate a target code file, wherein the target code file includes a plurality of code fragments;

[0028] A directory integration unit, used to integrate the target code file into each directory of the source program to obtain a Java file;

[0029] A file compilation unit, used to compile the Java file by calling the Execute method of the Invoker class through the Maven tool to obtain an executable Class file;

[0030] The file loading unit is used to load the executable Class file through ClassLoader based on the reflection mechanism.

[0031] Preferably, it also includes:

[0032] A module construction unit, for responding to a user's new addition request, receiving module information entered by the user, and creating a function module according to the module information, wherein the module information includes a module level and a module name;

[0033] The field entry unit is used to receive field information entered by the user based on the functional module, and the field information includes field name, data type, data length and display type.

[0034] Preferably, the file loading unit is specifically used for:

[0035] Querying basic file information according to the module information of the functional module, the basic file information including the file name, storage path and full class name;

[0036] Based on the reflection mechanism, the target class is searched through ClassLoader according to the full name of the class;

[0037] Extract class objects according to the target class, match corresponding methods, and obtain executable Class files.

[0038] A third aspect of the present application provides a device for adaptively converting user needs into results, the device comprising a processor and a memory;

[0039] The memory is used to store program code and transmit the program code to the processor;

[0040] The processor is used to execute the method for adaptively converting user needs into results described in the first aspect according to the instructions in the program code.

[0041] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0042] In the present application, a method for adaptively converting user needs into results is provided, including: in response to user input information, using the user input information to match in a template library to obtain a target template file, the user input information includes functional modules and field information; parsing specific symbols in the target template file to generate a target code file, the target code file includes multiple code fragments; integrating the target code file into each directory of the source program to obtain a Java file; calling the Execute method of the Invoker class through the Maven tool to compile the Java file to obtain an executable Class file; based on the reflection mechanism, loading the executable Class file through the ClassLoader.

[0043] The method for adaptively converting user needs into results provided by the present application improves the efficiency of system development based on the adaptive generation mechanism of templates and codes; the template file information corresponding to the user needs can be determined through template matching, and then the target code file can be generated based on the method of parsing specific symbols; then the target code file is compiled and loaded in sequence to generate an executable Class file to complete the conversion of results. This process does not require the participation of R&D personnel. Users can directly realize the conversion from needs to results in the management background as needed, that is, development and use, which greatly improves the efficiency of system development and reduces the time spent on development. Therefore, the present application can solve the technical problem that the existing process of converting user needs is too complicated, time-consuming and labor-intensive, resulting in low efficiency of actual system development. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 A flowchart of a method for adaptively converting user needs into results provided in an embodiment of the present application;

[0045] Figure 2 A schematic diagram of the structure of a device for adaptively converting user needs into results provided in an embodiment of the present application;

[0046] Figure 3 A schematic diagram of a code generation environment based on user needs provided in an embodiment of the present application;

[0047] Figure 4 A schematic diagram of the interactive process of generating a code file based on user needs provided for the application example of this application;

[0048] Figure 5 A schematic diagram of the module management directory interface of the management backend provided for this application example;

[0049] Figure 6 A schematic diagram of the functional module construction interface provided for the application example of this application;

[0050] Figure 7 An example diagram of setting fields on a page provided for the application example of this application;

[0051] Figure 8 Schematic diagram of the field information display interface provided for the application example of this application;

[0052] Fig. 9 A schematic diagram of the user management authority setting interface for the construction module provided in this application example. DETAILED DESCRIPTION

[0053] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0054] For easier understanding, see Figure 1 , an embodiment of a method for adaptively converting user needs into results provided by the present application includes:

[0055] Step 101: In response to user input information, a target template file is obtained by matching the user input information in a template library. The user input information includes function modules and field information.

[0056] Furthermore, step 101, before that, also includes:

[0057] In response to a user's new addition request, receiving module information entered by the user, and creating a functional module according to the module information, the module information including the module level and the module name;

[0058] Based on the function module, the field information entered by the user is received, and the field information includes field name, data type, data length and display type.

[0059] Furthermore, step 101, before that, also includes:

[0060] Write multiple types of template files in the template generator, mark specific symbols, and generate a template library, which includes template information.

[0061] It should be noted that the user input information is the user's demand information, and the functional module is the module that the user needs to add to the system; based on the user input information, template matching can be performed in the pre-prepared template library to determine the file structure, that is, the target template file. Among them, the user input information includes functional modules and field information; users can select the module management interface according to their needs in the pre-designed user login management platform and enter information in this interface. The input module information includes information such as module hierarchy and module name, where the module hierarchy refers to whether the module is a parent module or a child module, and the module name includes Chinese name and English name. The module hierarchy is used to mark which directory the current module needs to be laid out under, which is convenient for the layout of the management platform and the hierarchical setting of the code; the Chinese name is used for liquid level display; the English name is used to generate the naming of entity classes, persistence layers, service layers, service layer implementation classes, control layers, database tables, and list pages and edit pages; in this way, a functional module can be created, which is a new module that meets user needs.

[0062] If the Chinese name of the above-mentioned function module is User Management, then various field information can be set on the setting list page of the user management module based on the module construction; field information includes but is not limited to field name, data type, data length and display type; field names also include Chinese and English. If the field is added on the list page of the user management module, the fields, classes and various attributes of the table can be generated. Among them, the Chinese name is used for liquid level display and code comments; the English name corresponds to the table field and class attribute; the data type indicates whether the field is a string or integer, date type, etc.; the data length indicates the maximum length that can be input to avoid exceeding the limit; the display type is used to select the type of the field on the page, such as an input box, a radio button, a check box, etc. It can be understood that the field is used to describe the specific information and attributes of the function module, which is more detailed information entered after the function module is built.

[0063] The template library is a collection of template file information generated by the template generator. The template of the template generator pre-writes common methods, logic codes, page codes, calls between the control layer and the service layer, calls between the service layer and the persistence layer, calls between the persistence layer and the xml configuration file, and verification of the control layer method parameters. Template files of different types are marked with various specific symbols for easy calling. Template files can be exemplified by: controller_template.java, dao_template.java, service_template.java, service_impl_template.java, validator_template.java, list_template.jsp, form_template.jsp, generatorConfig.xml, etc. This embodiment only provides examples and is not limited. Other template files can be added as needed. In addition, template files can be divided into back-end files such as xml configuration files, entity classes, persistence layers, service layers, service layer implementation classes, and control layers, as well as front-end pages such as list pages, edit pages, and view pages. During the matching process, various types of template files can be found in the template library according to the user input information, and then matched to obtain the target template file.

[0064] Step 102: parse specific symbols in the target template file to generate a target code file, where the target code file includes multiple code fragments.

[0065] The target template file contains pre-defined specific symbols. By parsing the specific symbols, the corresponding code structure can be generated in the code generator to obtain the target code file. The target code file includes multiple code fragments, which can also be divided into front-end code and back-end code by category.

[0066] It is understandable that both the template generator and the code generator need to arrange the production environment in advance to achieve code generation. For example, deploy JDK, Maven and other development tools in the production environment and configure environment variables; deploy the source program and executable program of the management background in the production environment. The source program is used to compile Java files to generate class files; the executable program is convenient for users to access the management through browsers, mobile phones, etc. For details, please refer to Figure 3 In addition, the pom.xml of the source program must be pre-integrated with the maven-invoker plug-in; the source program writes triggers, uses the InvocationRequest class of the Maven tool, and can complete the compilation process of related codes through the Maven series of commands.

[0067] Step 103: Integrate the target code file into each directory of the source program to obtain a Java file.

[0068] The generated target code file is a source file, so it needs to be integrated into each directory of the source program. For example, the persistence layer is stored in the dao directory. At this time, the file is the generated code file, that is, the Java file.

[0069] Step 104: Call the Execute method of the Invoker class through the Maven tool to compile the Java file to obtain an executable Class file.

[0070] Furthermore, step 104 further includes:

[0071] Perform validity check on the executable Class file and obtain the verification result.

[0072] In the actual compilation and execution process, the listener can be used to notify the code generator to prepare for code compilation. The Invoker class can be called through the Maven tool to generate an instance object of the InvocationRequest class, and the Maven warehouse directory, settings.xml address, and pom.xml address of the source program can be configured. Calling the execute method of the Invoker class can complete the compilation of the Java file and obtain an executable Class file.

[0073] Based on the above process, if the parent module name matches the specific symbol {MYBATIS_MODULE_URL_PREFIX}, system is generated, and the user is generated according to the entity class name managed by the user. The final assembled URL access address is / system / user. The code structure generated by this process is standardized, the comments are clear, and the logic is rigorous, which can ensure the standardization and unification of the code, and is readable and maintainable.

[0074] In order to ensure that the generated and compiled files are valid, this embodiment also arranges a code verification mechanism, that is, to verify whether the executable Class file is valid and whether it is an executable file. If there is a problem, the user will be prompted and an email will be sent to the relevant R&D personnel for follow-up; if there is no problem, the executable Class file will be decompressed and pushed to each directory of the application. For example, the persistence layer is stored in the dao directory, the service layer is integrated into the service directory, and the list page, edit page, and view page are integrated into the web directory. In this way, during the daily idle time period, the application will automatically restart and initialize these class, jsp and other files, and users can use them.

[0075] In addition, the user management module can also be displayed under the "System Management" node of the management platform, because the user management module is built under the system management node; then, the user management module is loaded into the role permissions of the current user so that the user has the permissions of the "User Management" module. So far, through a series of operations, the various module information entered by the user is converted into various Class files and pages.

[0076] Step 105: Based on the reflection mechanism, the executable Class file is loaded through ClassLoader.

[0077] Further, step 105 includes:

[0078] Query the basic file information based on the module information of the functional module. The basic file information includes the file name, storage path and full class name;

[0079] Based on the reflection mechanism, the target class is searched by ClassLoader according to the full class name;

[0080] Extract class objects according to the target class and match the corresponding methods to obtain the executable Class file.

[0081] If users need to use the generated executable Class files before they are initialized to the system, they need to dynamically load these executable files based on the reflection mechanism. Users enter the module on the module management page of the management background, such as user management, and click the Save button to save the file name, storage path, class full name and other information to the module management table of the database. During use, according to the module name selected by the user, such as "User Management", the module management table of the database is queried to find the corresponding file name, storage path, and class full name, and then the file is loaded through ClassLoader to find the corresponding class according to the class full name; then, register the bean through the Spring container and obtain the class object according to the class name; traverse all the methods of the class and match the corresponding method according to the page selected by the user, such as the list page corresponds to the list method, thus completing the code loading process.

[0082] Furthermore, step 105 further includes:

[0083] During the idle time period, the executable Class file is initialized to the system application directory by restarting the system to complete the file loading.

[0084] Due to the daily idle time period, the system will automatically restart and initialize the generated executable file into the system. If the system has been restarted and initialized, there is no need for dynamic loading, which improves performance. In other words, executable Class files can be loaded and used in two ways, one is dynamic loading based on reflection mechanism, and the other is initialization based on system restart.

[0085] If the user builds a user management module under the system management node, the user can click the "User Management" link address under the system management node to request to reach the transfer station of the backend server; the transfer station has two functions: the first function is to store the user's newly added modules or functions in the configuration class to facilitate dynamic loading, that is, the files that need to be dynamically loaded are added to the configuration class, and those that do not need to be dynamically loaded are not needed; the second function is that since the reflection mechanism and dynamic loading are relatively performance-consuming, the management background will automatically restart the system during the idle time period, initialize the newly added modules into the system, and remove the module information from the configuration class. The transfer station receives the request passed by the front end and determines whether the module exists in the configuration class. If not, the request is directly transferred to the control layer corresponding to the module; if it exists, it means that it has not been initialized.

[0086] For ease of understanding, this application provides an application example of a method for adaptively converting user needs into results. Assuming that the user needs to build a user management module, the interaction process between the management backend and the template generator, code generator, and code loader can be found in Figure 4, please refer to the user interface design Figure 5 , you can add other functional modules under the parent node module, such as the user management module; then refer to Figure 6 , Figure 7 and Figure 8 For user permission management of function modules, please refer to Fig. 9 The entire process does not require intervention from R&D personnel. Users can complete the development of their needs and put them online through their own operations, achieving the purpose of plug-and-play, saving manpower, material resources, and time costs, and improving efficiency.

[0087] The method for adaptively converting user needs into results provided in the embodiment of the present application improves the efficiency of system development based on the adaptive generation mechanism of templates and codes; the template file information corresponding to the user needs can be determined through template matching, and then the target code file can be generated based on the method of parsing specific symbols; then the target code file is compiled and loaded in sequence to generate an executable Class file to complete the conversion of results. This process does not require the participation of R&D personnel. Users can directly realize the conversion from needs to results in the management background as needed, that is, development and use, which greatly improves the efficiency of system development and reduces the time consumed in development. Therefore, the embodiment of the present application can solve the technical problem that the existing process of converting user needs is too complicated, time-consuming and labor-intensive, resulting in low efficiency of actual system development.

[0088] For easier understanding, see Figure 2 The present application provides an embodiment of a device for adaptively converting user needs into results, including:

[0089] The template matching unit 201 is used to match the target template file in the template library using the user input information in response to the user input information, and the user input information includes function modules and field information;

[0090] A code generation unit 202 is used to parse a specific symbol in a target template file and generate a target code file, wherein the target code file includes a plurality of code fragments;

[0091] A directory integration unit 203 is used to integrate the target code file into each directory of the source program to obtain a Java file;

[0092] The file compiling unit 204 is used to compile the Java file by calling the Execute method of the Invoker class through the Maven tool to obtain an executable Class file;

[0093] The file loading unit 205 is used to load the executable Class file through ClassLoader based on the reflection mechanism.

[0094] Furthermore, it also includes:

[0095] The module construction unit 206 is used to respond to the user's new addition request, receive the module information entered by the user, and create a functional module according to the module information, the module information includes the module level and the module name;

[0096] The field entry unit 207 is used to receive field information entered by the user based on the function module. The field information includes field name, data type, data length and display type.

[0097] Furthermore, the file loading unit 205 is specifically used for:

[0098] Query the basic file information based on the module information of the functional module. The basic file information includes the file name, storage path and full class name;

[0099] Based on the reflection mechanism, the target class is searched by ClassLoader according to the full class name;

[0100] Extract class objects according to the target class and match the corresponding methods to obtain the executable Class file.

[0101] The present application also provides a device for adaptively converting user needs into results, the device comprising a processor and a memory;

[0102] The memory is used to store the program code and transmit the program code to the processor;

[0103] The processor is used to execute the method of adaptively converting user needs into results in the above method embodiment according to the instructions in the program code.

[0104] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0105] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0106] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0107] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for executing all or part of the steps of the method described in each embodiment of the present application through a computer device (which can be a personal computer, server, or network device, etc.). The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (full name in English: Read-Only Memory, English abbreviation: ROM), random access memory (full name in English: Random Access Memory, English abbreviation: RAM), disk or optical disk and other media that can store program code.

[0108] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for adaptively converting user needs into results, characterized in that: include: In response to user input information, the target template file is obtained by matching the user input information in the template library, wherein the user input information includes function modules and field information; Parsing specific symbols in the target template file to generate a target code file, wherein the target code file includes multiple code fragments; Integrate the target code files into various directories of the source program to obtain Java files; The Execute method of the Invoker class is called by the Maven tool to compile the Java file to obtain an executable Class file; Based on the reflection mechanism, the executable Class file is loaded through ClassLoader.

2. The method for adaptively converting user needs into results according to claim 1, characterized in that: In response to the user input information, the target template file is matched in the template library using the user input information, and the method also includes: In response to a user's new addition request, receiving module information entered by the user, and creating a functional module according to the module information, wherein the module information includes a module level and a module name; On the basis of the functional modules, field information entered by the user is received, wherein the field information includes field name, data type, data length and display type.

3. The method for adaptively converting user needs into results according to claim 1, characterized in that: In response to the user input information, the target template file is matched in the template library using the user input information, and the method also includes: Multiple types of template files are written in a template generator, and specific symbols are marked to generate a template library, which includes template information.

4. The method for adaptively converting user needs into results according to claim 1, characterized in that: The Execute method of the Invoker class is called by the Maven tool to compile the Java file to obtain an executable Class file, and then the following is included: The executable Class file is validated to obtain a validation result.

5. The method for adaptively converting user needs into results according to claim 1, characterized in that: The method of loading the executable Class file through ClassLoader based on the reflection mechanism includes: Querying basic file information according to the module information of the functional module, the basic file information including the file name, storage path and full class name; Based on the reflection mechanism, the target class is searched through ClassLoader according to the full name of the class; Extract class objects according to the target class, match corresponding methods, and obtain executable Class files.

6. The method for adaptively converting user needs into results according to claim 1, characterized in that: The method of loading the executable Class file through ClassLoader based on the reflection mechanism also includes: During the idle time period, the executable Class file is initialized to the system application directory by restarting the system to complete the file loading.

7. A device for adaptively converting user needs into results, characterized in that: include: A template matching unit, configured to respond to user input information and use the user input information to match a target template file in a template library, wherein the user input information includes function modules and field information; A code generation unit, used for parsing specific symbols in the target template file to generate a target code file, wherein the target code file includes a plurality of code fragments; A directory integration unit, used to integrate the target code file into each directory of the source program to obtain a Java file; A file compilation unit, used to compile the Java file by calling the Execute method of the Invoker class through the Maven tool to obtain an executable Class file; The file loading unit is used to load the executable Class file through ClassLoader based on the reflection mechanism.

8. The device for adaptively converting user needs into results according to claim 7, characterized in that: Also includes: A module construction unit, for responding to a user's new addition request, receiving module information entered by the user, and creating a function module according to the module information, wherein the module information includes a module level and a module name; The field entry unit is used to receive field information entered by the user based on the functional module, and the field information includes field name, data type, data length and display type.

9. The device for adaptively converting user needs into results according to claim 7, characterized in that: The file loading unit is specifically used for: Querying basic file information according to the module information of the functional module, the basic file information including the file name, storage path and full class name; Based on the reflection mechanism, the target class is searched through ClassLoader according to the full name of the class; Extract class objects according to the target class, match corresponding methods, and obtain executable Class files.

10. A device for adaptively converting user needs into results, characterized in that: The device comprises a processor and a memory; The memory is used to store program code and transmit the program code to the processor; The processor is used to execute the method for adaptively converting user needs into results as described in any one of claims 1-6 according to the instructions in the program code.

Images