Software instance generation method and software instance generation device

Abstract

The invention provides a software instance generation method and a software instance generation device, and belongs to the technical field of software generation. The service assembly agent analyzes the service demand, generates a corresponding first instance scheme and sends the first instance scheme to the user terminal; receiving a second instance scheme fed back by the user terminal; the business assembly agent obtains a second component for assembling a second instance scheme from a component library; when the business assembly agent judges that the component library is lack of the second component, the component description agent generates a corresponding missing component description; the component generation agent generates a missing component according to the missing component description; the business assembly agent assembles the components in the component library into a software instance based on the second instance scheme; and outputting the software instance. By means of the processing scheme, automatic assembly of the enterprise application software can be achieved only according to the service requirements, the development workload of the enterprise application software is reduced, and the software development efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of software instance generation, and particularly relates to a software instance generation method and a software instance generation device. Background Art

[0002] Currently, the method of using artificial intelligence technology to generate software instances mainly involves programmers writing prompts to generate code. However, due to the inherent uncertainty of large language models themselves, the generated code often requires further confirmation and verification by programmers, and usually needs to be modified and optimized multiple times to meet the actual functional requirements. This greatly affects the overall efficiency of software development, and the development quality largely depends on the professional skill level of programmers. For inexperienced programmers, after introducing artificial intelligence technology, their work efficiency may even be lower than that of the previous traditional development mode.

[0003] In addition, most current software instance generation processes follow the sequence from requirements analysis to design planning and then to coding implementation. Business personnel can only participate in the requirements analysis stage and cannot effectively monitor the subsequent design and coding links. However, in the context of the artificial intelligence era, business personnel also expect to be more deeply involved in the entire process of software instance generation, which not only helps improve development efficiency but also better meets business requirements and service goals. But the actual situation is that business personnel often lack professional knowledge of software instance generation and only rely on simple prompts to generate code, which is only applicable to very simple projects. For projects with a certain degree of business complexity, this method is difficult to achieve effective generation. Summary of the Invention

[0004] Therefore, in order to overcome the above-mentioned drawbacks of the prior art, the present invention provides a software instance generation method and a software instance generation device, which can realize the automatic assembly of enterprise application software only according to business requirements, reduce the development workload of enterprise application software, improve software development efficiency, and also facilitate business personnel to cooperate with developers in software research and development in a timely manner, allowing business personnel to be more deeply involved in software research and development.

[0005] To achieve the above object, the present invention provides a method for generating a software instance, including: receiving an instance generation instruction sent by a user terminal, where the instance generation instruction carries a service requirement, and the service requirement at least includes functions that the software instance needs to implement; using a service assembly agent to analyze the service requirement, generating a corresponding first instance solution and sending the first instance solution to the user terminal, where the first instance solution includes a first architecture and a first component description filling the first architecture, and the first component description includes the function of the component, the deployment environment, the middleware and version it depends on, and the dependent interfaces; using a receiving module to receive a second instance solution fed back by the user terminal, where the second instance solution includes a second architecture and a second component description of a second component filling the second architecture; the service assembly agent obtains the second components for assembling the second instance solution from the component library; when the service assembly agent determines that a second component is missing in the component library, using the component description agent to generate a corresponding missing component description; using the component generation agent to generate a missing component according to the missing component description, and storing the missing component and the corresponding missing component description in the component library; using the service assembly agent to assemble the components in the component library into a software instance based on the second instance solution; when it is determined that the software instance test is completed, using an output module to output the software instance.

[0006] In one embodiment, the using a service assembly agent to analyze the service requirement and generate a corresponding first instance solution includes: using a service assembly agent to analyze the service requirement to determine the target service; when there is an approximate service similar to the target service in the architecture solution library, sending the solution corresponding to the approximate service to the user terminal as the first instance solution.

[0007] In one embodiment, the using the component generation agent to generate a missing component according to the missing component description includes: determining whether there is a first approximate component description similar to the missing component description in the component library; when it is determined that there is a first approximate component description, generating a missing component corresponding to the missing component description from the first approximate component according to the first approximate component description and the missing component description.

[0008] In one embodiment, the using the component generation agent to generate a missing component according to the missing component description includes: determining whether there is a first approximate component description similar to the missing component description in the component library; when it is determined that there is no first approximate component description, the component generation agent generates program code according to the missing component description and encapsulates the program code into a missing component.

[0009] In one embodiment, the use of the component generation agent to generate a missing component based on the missing component description also includes: testing the missing component, and when it is determined that the missing component does not meet expectations, adjusting the missing component description to generate a missing adjustment description; and regenerating a second missing component based on the missing adjustment description.

[0010] In one embodiment, when the business assembly agent determines that a component is missing in the component library, the component description agent is used to generate a corresponding missing component description, including: searching for components with consistent descriptions in the component library one by one according to the second component description, and setting the searched components as corresponding second components; judging whether all the second component descriptions exist in the component library; when it is determined that the second component description does not exist in the component library, the business assembly agent determines that a component is missing in the component library, and outputs the second component description and the second associated component associated with it in the second architecture to the component description agent; the component description agent generates a standardized missing component description based on the second component description and the second associated component associated with it in the second architecture.

[0011] In one embodiment, the method further includes: when it is determined that the software instance test is completed, storing the second architecture in an architecture solution library, and storing the second component and the corresponding second component description in the component library.

[0012] A software instance generation method includes: obtaining business requirements input through an input interface, generating an instance generation instruction, and sending the instruction to a server, wherein the business requirements include at least functions; receiving a first instance solution sent by the server, wherein the first instance solution includes a first architecture and a first component that populates the first architecture; displaying the first architecture and a first component description of the first component on a display interface, and obtaining adjustment content input through the input interface; modifying the first architecture and the first component description according to the adjustment content to generate a second instance solution, wherein the second instance solution includes a second architecture and a second component description of a second component that populates the second architecture.

[0013] A software instance generation device, the device comprising a receiving module, a business assembly agent, a component description agent, a component generation agent, and an output module: the receiving module receives an instance generation instruction sent by a user terminal, the instance generation instruction carrying a business requirement; the business assembly agent analyzes the business requirement, generates a corresponding first instance solution, and sends the first instance solution to the user terminal, the first instance solution including a first architecture and a first component description that fills the first architecture; the receiving module receives a second instance solution fed back by the user terminal, the second instance solution including a second architecture and a second component description that fills the second architecture; the business assembly agent obtains a second component for assembling the second instance solution from a component library; when the business assembly agent determines that the second component is missing from the component library, the component description agent generates a corresponding missing component description; the component generation agent generates a missing component based on the missing component description, and stores the missing component and the corresponding missing component description in the component library; the business assembly agent is used to assemble the components in the component library into a software instance based on the second instance solution; when it is determined that the software instance test is completed, the output module outputs the software instance.

[0014] Compared with existing technologies, the present invention has the advantage of enabling the automated production and assembly of enterprise application software based solely on business needs, reducing the development workload and improving software development efficiency. Furthermore, components in the component library and architectural solutions in the architectural solution library can be reused to achieve rapid software development, making it easier for business personnel to coordinate with developers to adjust assembly requirements in a timely manner, thereby improving the development efficiency of software with high business complexity. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0016] Figure 1 is a flowchart of a method for generating a software instance in one embodiment of the present invention;

[0017] Figure 2 is a flowchart of a method for generating a software instance in another embodiment of the present invention;

[0018] Figure 3 is a flowchart of a method for generating a software instance in another embodiment of the present invention;

[0019] Figure 4 It is a schematic flowchart of the software instance generation step in an embodiment of the present invention;

[0020] Figure 5 It is a schematic flowchart of the software instance generation method in another embodiment of the present invention;

[0021] Figure 6 It is a schematic flowchart of the software instance generation method in another embodiment of the present invention;

[0022] Figure 7 It is a structural block diagram of the software instance generation device in an embodiment of the present invention. Specific Embodiments

[0023] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0024] The following uses specific specific examples to illustrate the embodiments of the present application. Those skilled in the art can easily understand other advantages and effects of the present application from the content disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The present application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that, without conflict, the following embodiments and the features in the embodiments can be combined with each other. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without making creative efforts belong to the scope of protection of the present application.

[0025] It should be noted that the following describes various aspects of the embodiments within the protection scope of the present invention. It should be obvious that the aspects described herein can be embodied in a wide variety of forms, and any specific structure and / or function described herein is only illustrative. Based on the present application, those skilled in the art should understand that one aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number and aspects described herein can be used to implement the device and / or practice the method. In addition, this device can be implemented and this method can be practiced using other structures and / or functions in addition to one or more of the aspects described herein.

[0026] It should also be noted that the drawings provided in the following embodiments only illustrate the basic concept of the present application in a schematic manner. The drawings only show the components related to the present application and are not drawn according to the number, shape, and size of the components in actual implementation. The type, quantity, and ratio of each component in its actual implementation can be an arbitrary change, and the component layout type may also be more complex.

[0027] In addition, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, those skilled in the art will understand that the described aspects can be practiced without these specific details.

[0028] An embodiment of the present application provides a software instance generation method, which is applied to a server or a terminal. The terminal can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable intelligent devices. The server can be implemented by an independent server or a server cluster composed of multiple servers. The terminal or the server has a component library or is connected to a component library. The component library is a structured data storage system, which can be used to store, retrieve, and manage a large number of components. The terminal or the server can also have an architecture solution library or be connected to an architecture solution library. The architecture solution library can store, retrieve, and manage a large number of architectures. The architectures in the architecture solution library can be obtained by analyzing existing software architectures, or can be software architectures preset by business personnel or programmers according to professional requirements.

[0029] As Figure 1 shown, a software instance generation method applied to the server side includes the following steps:

[0030] Step 101, receive an instance generation instruction sent by a user terminal. The instance generation instruction carries a business requirement, and the business requirement at least includes the functions that the software instance needs to implement.

[0031] The business requirement can be a general description specification, which can reflect the required software application environment and functions. The business requirement at least includes the functions that the software instance needs to implement. In some embodiments, the business requirement includes functions, deployment environment, dependent middleware and version, and dependent interfaces. In order to more accurately generate the software instance, the software instance can be described from four dimensions: functions, deployment environment, dependent middleware and version, and dependent interfaces. The description of each parameter in the business requirement does not require a very high technical level for business personnel to implement. The server receives the instance generation instruction sent by the user terminal, and the instance generation instruction carries a business requirement.

[0032] Step 102, analyze the business requirement by using a business assembly agent, generate a corresponding first instance solution, and send the first instance solution to the user terminal. The first instance solution includes a first architecture and a first component description that fills the first architecture. The first component description includes the functions, deployment environment, dependent middleware and version, and dependent interfaces of the component.

[0033] The server uses a business assembly agent to analyze the business requirement, generate a corresponding first instance solution, and send the first instance solution to the user terminal. The business assembly agent can retrieve relevant solutions based on the functionality of the business requirement and then adjust the relevant solutions to the first instance solution corresponding to the business requirement; it can also directly generate the first instance solution corresponding to the business requirement. The server can include an architecture asset library and can also communicate with the architecture asset library. The architecture asset library consists of an architecture solution library and a component library.

[0034] The component library stores components, their corresponding component descriptions, and their code. A component is a reusable software unit with a well-defined function. A component can be thought of as a "building block" within a software instance, which can be combined to build complex systems. A component is an independent, reusable software unit that encapsulates specific functionality and data and interacts with other components through well-defined interfaces. A component can be any of the following: a class, a function, a module, or a library. A component can also be a user interface component, a business logic component, a service component, or a utility component, composed of classes, functions, modules, and libraries. Classes, functions, modules, and libraries are all programming definitions and are not explained here.

[0035] User interface components are components used to build user interfaces, such as buttons, text boxes, drop-down menus, etc. These components usually have a visual appearance and interactive behavior. Business logic components encapsulate the business logic of the application, such as user authentication, order processing, data validation, etc. Data access components are components used to interact with databases or other data stores, such as data access objects (DAO), data models, etc. Service components are components that provide specific services, such as network communication services, logging services, security services, etc. Tool components are components that provide general functions, such as string processing, date and time operations, file operations, etc. Different user interface components, business logic components, service components, or tool components will differ according to the functions to be performed.

[0036] The component description defines the component interface (the component interacts with other components through the interface), the functions and operation methods that the component can provide, etc.

[0037] The architecture solution library stores architectures, which consist of components and their corresponding component descriptions. Architectures are used to build and run applications (an application can be a component or a collection of components) to implement the functionality required by business requirements. An instance solution consists of at least one architecture.

[0038] The first instance solution includes a first architecture and a first component that fills the first architecture. The business assembly agent queries the architecture solution library and the component library according to the business requirements in the instance generation instruction, generates the corresponding first instance solution, and sends it to the user terminal.

[0039] In one embodiment, the business assembly agent can query and find an architecture in the architecture solution library that is approximately or identically described according to the business requirements. Then the business assembly agent sets the found architecture as the first architecture and obtains the components associated with the first architecture as the first components. The server sends the first architecture and the first components as the first instance solution to the user terminal. In one embodiment, the business assembly agent can query the vector descriptions in the component library to find a set of feasible candidate components, and then assemble the set of candidate components according to the architecture rules obtained by deep learning on the architectures in the architecture solution library to obtain the first instance solution. The business assembly agent sends the first instance solution to the user terminal. At this time, the first instance solution includes the first architecture and the set of candidate components as the first components. The vector description is a vectorized representation of data features, and the data features can be at least one of function, deployment environment, dependent middleware and version, and dependent interfaces. The business assembly agent can convert the business requirements into corresponding vector descriptions, and then the business assembly agent can screen out a set of feasible candidate components through similarity calculation and the like.

[0040] Step 103, use the receiving module to receive the second instance solution fed back by the user terminal. The second instance solution includes a second architecture and a second component description of the second component that fills the second architecture.

[0041] The server uses the receiving module to receive the second instance solution fed back by the user terminal. The second instance solution includes a second architecture and a second component description of the second component that fills the second architecture. The user terminal displays the first instance solution, and the user (the user can be a business person, a requester, etc.) judges whether the first instance solution is reasonable. When it is determined to be reasonable, the user terminal feeds back the first instance solution and the reasonable determination result as the second instance solution to the business assembly agent; when it is determined to be unreasonable, the user terminal receives the adjustment content input by the user, adjusts the first instance solution based on the adjustment content and displays it until the user inputs a reasonable determination result. The user terminal feeds back the adjusted first instance solution and the reasonable determination result as the second instance solution to the business assembly agent. The user terminal can display a confirmation button. Once the user clicks the confirmation button, the user terminal generates a reasonable determination result. The user can adjust the first instance solution or directly confirm it through the user terminal. Therefore, the architectures and component descriptions in the second instance solution and the first instance solution can be the same or different.

[0042] Step 104: The business assembly agent obtains a second component for assembling a second instance solution from the component library.

[0043] The business assembly agent obtains the second component for assembling the second instance solution from the component library.

[0044] When the business assembly agent determines that all component descriptions that are consistent with the second component description exist in the component library, the business assembly agent determines that the components in the component library meet the requirements of the second instance solution. When it is determined that the components in the component library meet the requirements of the second instance solution, the business assembly agent assembles the second components based on the second architecture and the second component description to obtain a software instance.

[0045] In one embodiment, the business assembly agent determines whether the components in the component library meet the requirements of the second instance solution, including the following steps: the business assembly agent searches for components with consistent descriptions in the component library one by one according to the second component description, and sets the searched components as corresponding second components; then the business assembly agent determines whether all second component descriptions exist in the component library; when it is determined that all second component descriptions exist in the component library, the business assembly agent determines that the components in the component library meet the requirements of the second instance solution; when it is determined that the second component description does not exist in the component library, the business assembly agent determines that the components in the component library do not meet the requirements of the second instance solution, and then determines that the second component is missing in the component library. In one embodiment, the server can also mark the second component descriptions that have not been searched so that the corresponding second component can be quickly generated later.

[0046] Step 105: When the business assembly agent determines that the second component is missing from the component library, the component description agent is used to generate a corresponding description of the missing component.

[0047] When the business assembly agent determines that there is no component description consistent with the second component description in the component library, the business assembly agent determines that the second component is missing in the component library. In this case, the business assembly agent names the missing second component as a missing component and provides the component description of the second component to the component description agent. The server uses the component description agent to generate a corresponding missing component description based on the component description of the second component.

[0048] In one embodiment, the server may also obtain a second associated component in the second architecture that communicates with the second component, and the component description agent generates a corresponding missing component description based on the component description of the second component and the component description of the second associated component.

[0049] Step 106: Use a component generation agent to generate a missing component according to the missing component description, and store the missing component and the corresponding missing component description in a component library.

[0050] The server can directly use the component generation agent to generate the missing component according to the missing component description, and store the missing component and the corresponding missing component description in the component library.

[0051] In one embodiment, the server may also send the missing component description to the user terminal; the user terminal displays the missing component description, and the user determines whether the missing component description meets expectations; when the user determines that the missing component description meets expectations, the user terminal determines the missing component description as a component normalization description, and feeds it back to the server. The server uses a component generation agent to generate a standard component based on the component normalization description, and stores the standard component and the component normalization description in the component library accordingly.

[0052] Step 107: Use the business assembly agent to assemble the components in the component library into a software instance based on the second instance solution.

[0053] When the server determines that all component descriptions that are consistent with the second component description exist in the component library, the server determines that the components in the component library meet the requirements of the second instance solution. When the server determines that the components in the component library meet the requirements of the second instance solution, the server uses the business assembly agent to assemble the components in the component library into a software instance based on the second instance solution.

[0054] Step 108: When it is determined that the software instance test is completed, the software instance is output using an output module.

[0055] The server tests the assembled software instance, and when it determines that the software instance test is completed, it uses the output module to output the software instance.

[0056] The server can send the assembled software instance directly to the user terminal, or send the assembled software instance to the cloud server so that the customer can obtain the corresponding software instance by logging into the cloud server.

[0057] This method automatically assembles enterprise application software based solely on business needs, reducing the development workload and improving software development efficiency. Furthermore, components in the component library and architectural solutions in the architectural solution library can be reused to achieve rapid software development. This also allows business personnel to promptly coordinate with developers to adjust assembly requirements, thereby improving the development efficiency of highly complex software.

[0058] In one embodiment, a business assembly agent is used to analyze business requirements and generate a corresponding first instance solution, including the following steps:

[0059] Use business assembly agents to analyze business needs and determine target businesses;

[0060] When there is an approximate business similar to the target business in the architecture solution library, the solution corresponding to the approximate business is sent to the user terminal as the first instance solution.

[0061] The server can use a business assembly agent to analyze the business requirements and determine the target business. The business assembly agent can perform text analysis on the business requirements and determine the target business corresponding to the function. The target business not only includes the function carried by the business requirements, but can also include the working environment, dependent interfaces, etc. of the business requirements. For example, if the function is "hailing a taxi", the server needs to clarify "hailing a taxi" for subsequent assembly of different components.

[0062] The business assembly agent retrieves in the architecture solution library according to the target business whether there is an approximate business similar to the target business in the architecture solution library, and the business assembly agent sends the solution corresponding to the approximate business to the user terminal as the first instance solution. The business assembly agent can, according to the semantic analysis of the business content, determine the business in the architecture solution library whose semantics are the same as or synonyms of or in an inclusion relationship with it as an approximate business similar to the target business. The inclusion relationship can be full inclusion or partial inclusion. For example, when there is only "booking a car" in the architecture solution library, the server can determine that the businesses of "booking a car" and "ordering food" are similar. The business assembly agent sends the solution corresponding to the approximate business to the user terminal as the first instance solution.

[0063] In one embodiment, the business assembly agent can also calculate the approximate values of the functions of all existing businesses and the target business in the architecture solution library, and determine the business with an approximate value greater than a predetermined threshold as an approximate business; the business assembly agent can also calculate the correlation degree between all existing businesses and the target business in the architecture solution library, and determine the business with a correlation degree greater than a certain specific threshold as an approximate business.

[0064] The above method can quickly generate the first instance solution according to the business and send the first instance solution to the user terminal held by the business personnel. The business personnel can proofread the first instance solution in a timely manner according to the customer requirements. The whole process is fast, efficient and convenient, and there is no need to wait for the program developers to develop the entire architecture additionally, providing more efficient and high-quality services for the customers.

[0065] As Figure 2 shown, in one of the embodiments, a component generation agent is used to generate missing components according to the missing component description, including the following steps:

[0066] Step 201, determine whether there is a first approximate component description in the component library that is similar to the missing component description.

[0067] The component generation agent receives the missing component description generated by the component description agent, and the server determines whether there is a first approximate component description similar to the missing component description in the component library based on the missing component description. For example, the missing component description and all component descriptions in the component library are expressed using vector descriptions. The server can calculate the similarity value between the two component descriptions through similarity. When the similarity value is greater than a predetermined threshold, the server determines that there is a first approximate component description similar to the missing component description in the component library. The server can determine the component with a similarity value greater than a predetermined threshold as a first approximate component. There are a large number of components in the component library, so the server can filter out one or more first approximate components. The server can select a first approximate component based on the working environment of the second component that has already met the second architecture, or it can select the first approximate component with the largest similarity value. The server can also select multiple first approximate components at the same time.

[0068] Step 202: When it is determined that the first approximate component description exists, based on the first approximate component description and the missing component description, the first approximate component is generated into a missing component corresponding to the missing component description.

[0069] When the server determines that the first approximate component description exists, the component generation agent generates the missing component corresponding to the missing component description from the first approximate component description according to the first approximate component description and the missing component description.

[0070] The component generation agent can specifically adjust the code of the first approximate component based on the differences between the missing component description and the first approximate component description, thereby generating the missing component and the component code corresponding to the missing component. For example, if the first approximate component description and the missing component description of the first approximate component differ only in the deployment environment, the component generation agent can add additional deployment environment conversion code to the component code of the first approximate component based on the difference in deployment environment to generate the missing component and the component code corresponding to the missing component.

[0071] The above method can adjust the existing components in the component library and regenerate new components according to the functions implemented by the components carried by business needs, the operating environment constraints, and the interaction constraints with other components, so as to achieve rapid software development. The entire process reduces the insertion of program developers and also reduces the workload of program developers.

[0072] In one embodiment, a component generation agent is used to generate a missing component according to a missing component description, including the following steps:

[0073] Determine whether there is a first approximate component description that is similar to the missing component description in the component library; when it is determined that there is no first approximate component description, the component generation agent generates program code according to the missing component description and encapsulates the program code into the missing component.

[0074] The server can determine whether there is a first approximate component description in the component library that is approximate to the missing component description based on the missing component description. The server can calculate the similarity value between the two component descriptions through similarity. When the similarity values are all less than a predetermined threshold, the server determines that there is no first approximate component description in the component library that is approximate to the missing component description.

[0075] When the server determines that there is no first approximate component description, the component generation agent generates program code according to the missing component description and encapsulates the program code into a missing component.

[0076] As Figure 3 shown, in one embodiment, the software instance generation method further includes the following steps:

[0077] Step 301, test the missing component. When it is determined that the missing component does not meet the expectation, adjust the missing component description to generate a missing adjustment description.

[0078] The server can run and test the missing code of the missing component. When it is determined that the missing component can run normally and can cooperate with the second associated component, the server determines that the missing component meets the expectation, and the missing component corresponds to the marked second component description.

[0079] When it is determined that the missing component cannot run normally or cannot cooperate with the second associated component, the server determines that the missing component does not meet the expectation, and the missing component does not correspond to the marked second component description. The server will first determine whether the missing component can run normally, and then determine whether the missing component fails to cooperate with the second associated component. The server generates a failure message. The component description agent adjusts the missing component description according to the failure message to generate a missing adjustment description.

[0080] For example, when the server determines that the missing component cannot run normally, the component description agent can generate a failure message of code exception. The component description agent adjusts the missing component description according to the failure message to generate a missing adjustment description, which includes the failure message of code exception and also includes the previous missing component description.

[0081] Step 302, regenerate a second missing component according to the missing adjustment description.

[0082] The component generation agent directly regenerates a second missing component corresponding to the missing adjustment description according to the missing adjustment description. When the server runs and tests the missing code of the second missing component and determines that the second missing component can run properly and cooperate with the second associated component, the server determines that the second missing component meets the expectation, and the second missing component corresponds to the marked second component description. The server assembles the second component and the second missing component based on the second architecture and the second component description to obtain a software instance.

[0083] The above method can re-adjust the existing components in the component library according to the functions implemented by the components carried by the business requirements, the operating environment constraints, the interaction constraints with other components, etc. to regenerate new components, so as to achieve rapid software development, and the whole process reduces the intervention of programmers and also reduces the workload of programmers.

[0084] In one embodiment, the software instance generation method further includes the following steps: when it is determined that the software instance test is completed, store the second architecture in the architecture solution library, and store the second component and the corresponding second component description in the component library.

[0085] When it is determined that the software instance test is completed, the server stores the second architecture in the architecture solution library and stores the second component and the corresponding second component description in the component library.

[0086] The server stores the missing component and the missing component description as a standard component in the component library, which can not only enrich the component library, but also enable the server to reuse the missing component according to the missing component description in the subsequent software generation method. The server stores the second architecture in the architecture solution library, which also enriches the architecture solution library.

[0087] In one embodiment, as Figure 4 shown, when the business assembly agent determines that a component is missing in the component library, the component description agent is used to generate the corresponding missing component description, including the following steps:

[0088] Step 401, search for components with consistent descriptions in the component library one by one according to the second component description, and set the searched components as the corresponding second components.

[0089] The server searches for components with consistent descriptions in the component library one by one according to the second component description, and sets the searched components as the corresponding second components.

[0090] Step 402, determine whether all the second component descriptions exist in the component library.

[0091] The server determines whether all the second component descriptions exist in the component library.

[0092] Step 403, when it is determined that the second component description does not exist in the component library, the service assembly agent determines that a component is missing from the component library, and outputs the second component description and the second associated component associated with it in the second architecture to the component description agent.

[0093] When the server determines that all second component descriptions exist in the component library, the service assembly agent determines that the components in the component library meet the requirements of the second assembly plan. When the server determines that the second component description does not exist in the component library, the service assembly agent determines that a component is missing from the component library, and outputs the second component description and the second associated component associated with it in the second architecture to the component description agent.

[0094] Step 404, the component description agent generates a standardized missing component description based on the second component description and the second associated component associated with it in the second architecture.

[0095] The component description agent generates a standardized missing component description based on the second component description and the second associated component associated with it in the second architecture.

[0096] In one embodiment, as Figure 5 shown, a method for generating a software instance applied to a user terminal includes the following steps:

[0097] Step 501, obtain the service requirements input through the input interface, and generate an instance generation instruction to send to the server. The service requirements include at least functions.

[0098] The user terminal displays the input interface, obtains the service requirements input by the business personnel through the input interface, and then generates an instance generation instruction to send to the server. The service requirements include at least functions. The input interface may also have a display area with a description specification, so that the business personnel can input service requirements according to the description specification. The description of the function or the middleware and version on which it depends in the service requirements can be a rough version, so that the business personnel can adjust it in a timely manner according to the instructions of the customer.

[0099] Step 502, receive the first instance plan sent by the server. The first instance plan includes the first architecture and the first components that fill the first architecture.

[0100] The user terminal will receive the first instance plan sent by the server. The first instance plan includes the first architecture and the first components that fill the first architecture. At this time, the first instance plan is generated by the service assembly agent according to the component library and the architecture plan library, with a lower accuracy, but it can quickly provide relevant displays and feedback to the customer.

[0101] Step 503, display the first architecture and the first component description of the first components on the display interface, and obtain the input adjustment content on the input interface.

[0102] The user terminal displays the first architecture and the first component description of the first component on the display interface. The business personnel can input adjustment content on the input interface of the user terminal. The adjustment content can be customer feedback or content supplemented by the business personnel based on communication with the customer.

[0103] Step 504 : Modify the first architecture and the first component description according to the adjustment content to generate a second instance solution, where the second instance solution includes a second architecture and a second component description that populates the second architecture.

[0104] The user terminal modifies the first architecture and the first component description according to the adjustment content to generate a second instance solution, where the second instance solution includes a second architecture and a second component description that populates the second architecture.

[0105] The above method can facilitate business personnel to participate in the software instance generation process in a timely manner and adjust the direction of software instance generation in a timely manner. The entire process does not require business personnel to have knowledge of software instance generation, which reduces the difficulty of business personnel's work and is also conducive to reducing the workload of program developers in the future.

[0106] In one embodiment, Figure 6 As shown, a method for generating a software instance applied to multiple terminals includes the following steps:

[0107] The user terminal obtains the business requirements inputted in the input interface, generates an instance generation instruction and sends it to the server. The business requirements at least include functions;

[0108] The server receives an instance generation instruction sent by the user terminal, where the instance generation instruction carries a business requirement;

[0109] The server uses a business assembly agent to analyze the business requirements in the instance generation instruction, generates a corresponding first instance solution, and sends the first instance solution to the user terminal. The first instance solution includes a first architecture and a first component description that fills the first architecture. The first component description includes the function, deployment environment, dependent middleware and version, and dependent interface of the component.

[0110] The user terminal receives the first instance solution sent by the server;

[0111] The user terminal displays the first architecture and the first component description of the first component on the display interface, and obtains the input adjustment content on the input interface;

[0112] The user terminal modifies the first architecture and the first component description according to the adjustment content to generate a second instance solution, where the second instance solution includes a second architecture and a second component description that populates the second architecture;

[0113] The server receives the second instance solution fed back by the user terminal;

[0114] The service assembly agent of the server obtains the second components for assembling the second instance solution from the component library;

[0115] When the service assembly agent determines that there are missing components in the component library, the server uses the component description agent to generate corresponding missing component descriptions;

[0116] The server can directly use the component generation agent to generate missing components according to the missing component descriptions, and store the missing components and the corresponding missing component descriptions in the component library; the server can also send the missing component descriptions to the user terminal, and the user judges whether the missing component descriptions meet the expectations. When it is determined that the missing component descriptions meet the expectations, the user terminal determines the missing component descriptions as component normalization descriptions, and the server uses the component generation agent to generate missing components according to the component normalization descriptions, and stores the missing components and the corresponding component normalization descriptions in the component library;

[0117] Use the service assembly agent to assemble the components in the component library into a software instance based on the second instance solution;

[0118] When it is determined that the software instance test is completed, use the output module to output the software instance. The server can send the software instance to the user terminal, and the user terminal displays the software instance, and the user judges whether it meets the expectations. When the server receives the determination from the user terminal that it meets the expectations, the server stores the corresponding second instance solution in the architecture solution library. When the user judges that it does not meet the expectations, the user terminal redisplay the page describing the business requirements, and the user re-enters the business requirements.

[0119] The above method can automatically assemble components at the component level based on the normative descriptions of the components to generate a software instance, and the whole process is efficient and convenient.

[0120] As Figure 7 shown, a software instance generation device is provided, and the device includes a receiving module 701, a service assembly agent 702, a component description agent 703, a component generation agent 704, and an output module 705.

[0121] The receiving module 701 receives the instance generation instruction sent by the user terminal, and the instance generation instruction carries the business requirements.

[0122] The service assembly agent 702 analyzes the business requirements, generates the corresponding first instance solution and sends the first instance solution to the user terminal. The first instance solution includes the first architecture and the first component descriptions filling the first architecture.

[0123] The receiving module 701 receives the second instance solution fed back by the user terminal. The second instance solution includes a second architecture and a second component description of the second components that populate the second architecture.

[0124] The service assembly agent 702 obtains the second components for assembling the second instance solution from the component library.

[0125] When the service assembly agent 702 determines that a second component is missing from the component library, the component description agent 703 generates a corresponding missing component description.

[0126] The component generation agent 704 generates a missing component according to the missing component description, and stores the missing component and the corresponding missing component description in the component library.

[0127] The service assembly agent 702 assembles the components in the component library into a software instance based on the second instance solution.

[0128] When it is determined that the software instance test is completed, the output module 705 outputs the software instance.

[0129] In one embodiment, the apparatus includes a service analysis unit and a solution sending unit.

[0130] The service analysis unit is configured to analyze business requirements using a service assembly agent to determine a target business.

[0131] The solution sending unit is configured to, when there is an approximate business in the architecture solution library that is similar to the target business, send the solution corresponding to the approximate business to the user terminal as a first instance solution.

[0132] In one embodiment, the apparatus includes:

[0133] A judgment unit, configured to judge whether there is a first approximate component description in the component library that is similar to the missing component description.

[0134] A missing component generation unit, configured to, when it is determined that there is a first approximate component description, generate a missing component corresponding to the missing component description from the first approximate component description and the missing component description.

[0135] In one embodiment, the apparatus includes:

[0136] A judgment unit, configured to judge whether there is a first approximate component description in the component library that is similar to the missing component description.

[0137] A missing component generation unit, configured to, when it is determined that there is no first approximate component description, the component generation agent generates program code according to the missing component description and encapsulates the program code into a missing component.

[0138] In one embodiment, the apparatus comprises:

[0139] The missing adjustment description generating unit is used to test the missing component, and when it is determined that the missing component does not meet expectations, adjust the missing component description to generate a missing adjustment description.

[0140] The missing component generating unit is used to regenerate the second missing component according to the missing adjustment description.

[0141] In one embodiment, the apparatus comprises:

[0142] The search unit is configured to search the component library for components with consistent descriptions one by one according to the second component description, and set the searched components as corresponding second components.

[0143] The judging unit is configured to judge whether all second component descriptions exist in the component library.

[0144] The associated output unit is used to determine that the component is missing in the component library when it is determined that the second component description does not exist in the component library, and output the second component description and the second associated component associated with it in the second architecture to the component description agent.

[0145] A missing component description generating unit is used for the component description agent to generate a standardized missing component description based on the second component description and the second associated component associated with it in the second architecture.

[0146] In one embodiment, the apparatus further comprises:

[0147] The storage module is used to store the second architecture in the architecture solution library and store the second component and the corresponding second component description in the component library when it is determined that the software instance test is completed.

[0148] The specific definition of the software instance generation device can be found in the definition of the software instance generation method above and will not be repeated here. Each module in the above-mentioned software instance generation device can be implemented in whole or in part through software, hardware, or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each of the above modules.

[0149] The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any changes or replacements that can be easily thought of by any technician familiar with this technical field within the technical scope disclosed in this application should be covered by the scope of protection of the present application.

Claims

1. A method for generating software instances, characterized in that, Including: Receiving an instance generation instruction sent by a user terminal, where the instance generation instruction carries a service requirement, and the service requirement at least includes the functions that a software instance needs to implement; Analyzing the service requirement by using a service assembly agent, generating a corresponding first instance solution and sending the first instance solution to the user terminal. The first instance solution includes a first architecture and a first component description filling the first architecture. The first component description includes the function of the component, the deployment environment, the middleware and version it depends on, and the dependent interfaces; Receiving a second instance solution fed back by the user terminal by using a receiving module. The second instance solution includes a second architecture and a second component description of a second component filling the second architecture; The service assembly agent obtains second components for assembling the second instance solution from a component library; When the service assembly agent determines that a second component is missing in the component library, using the component description agent to generate a corresponding missing component description; Using the component generation agent to generate a missing component according to the missing component description, and storing the missing component and the corresponding missing component description in the component library; Using the service assembly agent to assemble the components in the component library into a software instance based on the second instance solution; When it is determined that the software instance test is completed, using an output module to output the software instance.

2. The software instance generation method according to claim 1, wherein The using the service assembly agent to analyze the service requirement and generate a corresponding first instance solution includes: Analyzing the service requirement by using a service assembly agent to determine a target service; When there is an approximate service similar to the target service in the architecture solution library, sending the solution corresponding to the approximate service to the user terminal as the first instance solution.

3. The software instance generation method according to claim 1, wherein The using the component generation agent to generate a missing component according to the missing component description includes: Judging whether there is a first approximate component description similar to the missing component description in the component library; When it is determined that there is a first approximate component description, generating a missing component corresponding to the missing component description from the first approximate component according to the first approximate component description and the missing component description.

4. The software instance generation method according to claim 1, wherein The using the component generation agent to generate a missing component according to the missing component description includes: Judging whether there is a first approximate component description similar to the missing component description in the component library; When it is determined that there is no first approximate component description, the component generation agent generates program code according to the missing component description and encapsulates the program code into a missing component.

5. The software instance generation method according to claim 3 or 4, characterized in that, The using the component generation agent to generate a missing component according to the missing component description further includes: Testing the missing component. When it is determined that the missing component does not meet the expectation, adjusting the missing component description to generate a missing adjustment description; Regenerating a second missing component according to the missing adjustment description.

6. The software instance generation method according to claim 1, wherein The when the service assembly agent determines that a component is missing in the component library, using the component description agent to generate a corresponding missing component description includes: Search for components with consistent descriptions in the component library one by one according to the description of the second component, and set the searched components as the corresponding second components; Determine whether all the descriptions of the second components exist in the component library; When it is determined that the description of the second component does not exist in the component library, the service assembly agent determines that a component is missing in the component library, and outputs the description of the second component and the second associated component associated with it in the second architecture to the component description agent; The component description agent generates a standardized missing component description according to the description of the second component and the second associated component associated with it in the second architecture.

7. The software instance generation method according to claim 1, wherein It also includes: When it is determined that the software instance test is completed, store the second architecture in the architecture solution library, and store the second component and the corresponding description of the second component in the component library.

8. A method for generating a software instance, characterized in that It includes: Obtain the service requirements input by the input interface, and generate an instance generation instruction to send to the server, and the service requirements at least include functions; Receive the first instance solution sent by the server, and the first instance solution includes the first architecture and the first components that populate the first architecture; Display the first architecture and the first component description of the first component on the display interface, and obtain the input adjustment content on the input interface; Modify the first architecture and the first component description according to the adjustment content to generate a second instance solution, and the second instance solution includes the second architecture and the second component description of the second components that populate the second architecture.

9. A software instance generation device, characterized in that, The device includes a receiving module, a service assembly agent, a component description agent, a component generation agent, and an output module: The receiving module receives the instance generation instruction sent by the user terminal, and the instance generation instruction carries service requirements; The service assembly agent analyzes the service requirements, generates a corresponding first instance solution and sends the first instance solution to the user terminal, and the first instance solution includes the first architecture and the first component description that populate the first architecture; The receiving module receives the second instance solution fed back by the user terminal, and the second instance solution includes the second architecture and the second component description of the second components that populate the second architecture; The service assembly agent obtains the second components for assembling the second instance solution from the component library; When the service assembly agent determines that a second component is missing in the component library, the component description agent generates a corresponding missing component description; The component generation agent generates a missing component according to the missing component description, and stores the missing component and the corresponding missing component description in the component library; Use the service assembly agent to assemble the components in the component library into a software instance based on the second instance solution; When it is determined that the software instance test is completed, the output module outputs the software instance.

Images