Software development method, device, equipment and computer program product

Abstract

The invention discloses a software development method, device and equipment and a computer program product, and relates to the technical field of computer software, and the method comprises the steps: responding to a software development request, and displaying a visual demand management interface; receiving demand input information input by a user in the demand information acquisition sub-interface, and generating demand output data; skipping to a demand record display interface to display demand output data and a synchronization component; synchronizing the to-be-synchronized demand output data to a visual development interface through a synchronization component; and generating a software development code according to the synchronized demand output data. According to the method, the visual demand tool is provided to interact with the user, the multiple pieces of demand input information input by the user are obtained through the sub-interface, the demand output data are generated, and the demand compiling efficiency is improved. In response to the demand synchronization request of the user, the demand related information is synchronized to the visual development interface to automatically generate the development code, manual writing by personnel is avoided, and the software development efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer software, and particularly relates to a software development method and device, equipment and computer program product. BACKGROUND

[0002] In the process of developing a software project, a demand person needs to manually draw a flowchart, design a user interface (UI), manually write input and output descriptions, demand logic descriptions and the like by using multiple tools in the early stage of the project, offline review is adopted for demand review, and a version needs to be controlled manually. Meanwhile, a developer needs to spend a large amount of time reading a demand, and then completes demand page source code writing by typing codes, thereby resulting in low project development efficiency. SUMMARY

[0003] The main purpose of the present application is to provide a software development method, device, equipment and computer program product, and aims to solve the technical problem of low development efficiency caused by manually writing demands and codes by a worker of a software project.

[0004] To achieve the above purpose, the present application provides a software development method, which comprises the following steps:

[0005] In response to a software development request, a visual demand management interface is displayed, wherein the visual demand management interface comprises at least one demand information acquisition sub-interface;

[0006] Receiving demand input information input by a user in the demand information acquisition sub-interface, and generating demand output data according to the demand input information;

[0007] Jumping to a demand record display interface of the visual demand management interface, and displaying the demand output data and a synchronous component corresponding to the demand output data in the demand record display interface;

[0008] When it is detected that the user triggers the synchronous component corresponding to to-be-synchronized demand output data in the demand output data, synchronizing the to-be-synchronized demand output data to a visual development interface to obtain synchronized demand output data;

[0009] Generating software development codes according to the synchronized demand output data through the visual development interface.

[0010] In an embodiment, the demand information acquisition sub-interface comprises a basic information sub-interface, a logic processing sub-interface and a user interface design sub-interface; and the demand output data comprises demand documents, business flowcharts and user interface design information.

[0011] The receiving user input demand information in the demand information acquisition sub-interface, and generating demand output data according to the demand input information, comprising:

[0012] Receiving the demand basic information input by the user in the basic information sub-interface;

[0013] After the user confirms that the demand basic information input is completed, generating a demand document according to the demand basic information, jumping to the logic processing sub-interface, and displaying the logic processing sub-interface;

[0014] Receiving the logic processing information input by the user in the logic processing sub-interface;

[0015] After the user confirms that the logic processing information input is completed, generating a business process diagram according to the logic processing information and the demand basic information, jumping to the user interface design sub-interface, and displaying the user interface design sub-interface;

[0016] Receiving the page element input by the user in the user interface design sub-interface, generating user interface design information according to the page element, integrating the demand document, the business process diagram and the user interface design information, and generating demand output data.

[0017] In an embodiment, the demand information acquisition sub-interface further comprises a flowchart editing sub-interface;

[0018] The step of generating a business process diagram according to the logic processing information and the demand basic information after the user confirms that the logic processing information input is completed, comprising:

[0019] Generating a preview flowchart according to the logic processing information and the demand basic information;

[0020] Displaying the preview flowchart and the flowchart editing component corresponding to the preview flowchart in the logic processing sub-interface;

[0021] When detecting that the user triggers the flowchart editing component, jumping to the flowchart editing sub-interface, and displaying the preview flowchart in the flowchart editing sub-interface;

[0022] In response to the user's editing operation on the preview flowchart, updating the preview flowchart to obtain a business process diagram.

[0023] In an embodiment, the user interface design information comprises a page picture, input / output content description and page abstract syntax tree;

[0024] The step of receiving the page elements input by the user in the user interface design sub-interface and generating user interface design information according to the page elements comprises:

[0025] Receiving table data corresponding to the page elements uploaded by the user in the user interface design sub-interface;

[0026] Generating a page picture and input / output content description according to the table data;

[0027] Converting the table data into a page abstract syntax tree in a preset programming format.

[0028] In an embodiment, the requirement information acquisition sub-interface further comprises a requirement sub-interface; and the requirement output data further comprises requirement common control items and requirement output credential information.

[0029] After the step of receiving the page elements input by the user in the user interface design sub-interface and generating user interface design information according to the page elements, the method further comprises:

[0030] Jumping to the requirement sub-interface and displaying the requirement sub-interface;

[0031] Receiving control item information input by the user in the requirement sub-interface and generating requirement common control items according to the control item information;

[0032] Receiving credential page information input by the user in the requirement sub-interface and generating requirement output credential information according to the credential page information.

[0033] In an embodiment, the visual requirement management interface further comprises a requirement overall preview interface.

[0034] After the step of receiving requirement input information input by the user in the requirement information acquisition sub-interface and generating requirement output data according to the requirement input information, the method further comprises:

[0035] Jumping to the requirement overall preview interface and displaying the requirement output data, an evaluation component corresponding to the requirement output data and a release component in the requirement overall preview interface;

[0036] When detecting that the user triggers the evaluation component corresponding to the requirement output data to be evaluated in the requirement output data, evaluating the requirement output data to be evaluated to obtain evaluated requirement data;

[0037] When detecting that the user triggers the release component corresponding to the evaluated requirement data, releasing the evaluated requirement data.

[0038] In an embodiment, the requirement record display interface jumping to the visual requirement management interface, and after the step of displaying the requirement output data and the synchronization component corresponding to the requirement output data in the requirement record display interface, further comprises:

[0039] In response to the change operation of the user on the selected requirement output data to be changed in the requirement record display interface, changing the requirement output data to be changed according to the change operation, and obtaining changed requirement data;

[0040] Generating version information, and performing requirement version management according to the version information and the changed requirement data.

[0041] In addition, to achieve the above object, the application further provides a software development device, which comprises:

[0042] The visual interface display module is configured to display a visual requirement management interface in response to a software development request, wherein the visual requirement management interface comprises at least one requirement information acquisition sub-interface;

[0043] The requirement input information receiving module is configured to receive requirement input information input by a user in the requirement information acquisition sub-interface, and generate requirement output data according to the requirement input information;

[0044] The requirement output data display module is configured to jump to a requirement record display interface of the visual requirement management interface, and display the requirement output data and the synchronization component corresponding to the requirement output data in the requirement record display interface;

[0045] The requirement output data to be synchronized synchronization module is configured to synchronize the requirement output data to be synchronized to a visual development interface when it is detected that the user triggers the synchronization component corresponding to the requirement output data to be synchronized in the requirement output data, and obtain synchronized requirement output data;

[0046] The software development code generation module is configured to generate software development code according to the synchronized requirement output data through the visual development interface.

[0047] In addition, to achieve the above object, the application further provides a software development device, which comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the software development method as described above.

[0048] In addition, to achieve the above object, the application further provides a storage medium, which is a computer readable storage medium, and a computer program is stored on the storage medium, and the computer program is executed by a processor to implement the steps of the software development method.

[0049] In addition, to achieve the above object, the application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the steps of the software development method.

[0050] The application provides a software development method, which displays a visual requirement management interface comprising a requirement information acquisition sub-interface in response to a software development request; receives requirement input information input by a user in the requirement information acquisition sub-interface, generates requirement output data; jumps to a requirement record display interface and displays the requirement output data and a synchronization component; synchronizes the to-be-synchronized requirement output data to a visual development interface when it is detected that the user triggers the synchronization component of the to-be-synchronized requirement output data; and generates software development code according to the synchronized requirement output data through the visual development interface. The application provides a visual requirement tool to interact with the user, acquires multiple pieces of requirement input information input by the user through a sub-interface, generates requirement output data, and improves the efficiency of requirement writing. In response to a requirement synchronization request of the user, requirement related information is synchronized to the visual development interface to automatically generate development code, manual writing of personnel is avoided, and the software development efficiency is improved. BRIEF DESCRIPTION OF DRAWINGS

[0051] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and serve to explain the principles of the application together with the specification.

[0052] In order to more clearly illustrate the technical solutions in the embodiments of the application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, for those skilled in the art, other drawings can also be obtained based on these drawings without creative labor.

[0053] Figure 1 A flowchart is provided for the software development method embodiment one of the application;

[0054] Figure 2 A schematic diagram of the visual requirement management interface in the application is provided;

[0055] Figure 3 A schematic diagram of the requirement record display interface in the application is provided;

[0056] Figure 4 A flowchart is provided for the software development method embodiment two of the application;

[0057] Figure 5 Fig. 1 is a schematic diagram of a basic information sub-interface in the present application;

[0058] Figure 6 Fig. 2 is a schematic diagram of a logic processing sub-interface in the present application;

[0059] Figure 7 Fig. 3 is a schematic diagram of a flowchart editing sub-interface in the present application;

[0060] Figure 8 Fig. 4 is a schematic diagram of a user interface design sub-interface in the present application;

[0061] Figure 9 Fig. 5 is a schematic diagram of other requirements sub-interface in the present application;

[0062] Figure 10 Fig. 6 is a schematic diagram of a flowchart of the third embodiment of the software development method in the present application;

[0063] Figure 11 Fig. 7 is a schematic diagram of a requirement overall preview interface in the present application;

[0064] Figure 12 Fig. 8 is a schematic diagram of a module structure of the software development device in the present application;

[0065] Figure 13 Fig. 9 is a schematic diagram of a device structure of a hardware running environment involved in the software development method in the present application.

[0066] The object, function characteristics and advantages of the present application will be further explained in combination with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0067] It should be understood that the specific embodiments described herein are merely intended to explain the technical solutions of the present application, and are not intended to limit the present application.

[0068] In order to better understand the technical solutions of the present application, the following will be described in detail in combination with the accompanying drawings and specific embodiments.

[0069] The main solution of the embodiment of the present application is: in response to a software development request, a visual requirement management interface is displayed, the visual requirement management interface includes at least one requirement information acquisition sub-interface; receiving requirement input information input by a user in the requirement information acquisition sub-interface, generating requirement output data according to the requirement input information; jumping to a requirement record display interface of the visual requirement management interface, and displaying the requirement output data and a synchronization component corresponding to the requirement output data in the requirement record display interface; when it is detected that the user triggers the synchronization component corresponding to to-be-synchronized requirement output data in the requirement output data, synchronizing the to-be-synchronized requirement output data to a visual development interface, obtaining synchronized requirement output data; and generating software development code according to the synchronized requirement output data through the visual development interface.

[0070] In the prior art, during the development of a software project, a requirement person needs to manually draw a flowchart, design a user interface (UI), manually write input and output descriptions, requirement logic descriptions and the like by using multiple tools in the early stage of the project, offline review is adopted for requirement review, and a version needs to be manually controlled. Meanwhile, a developer needs to spend a lot of time reading requirements, and then writes requirement page source code by typing codes, thereby resulting in low project development efficiency.

[0071] The present application provides a solution, in response to a software development request, a visual requirement management interface including a requirement information acquisition sub-interface is displayed; requirement input information input by a user in the requirement information acquisition sub-interface is received, and requirement output data is generated; a requirement record display interface is jumped to, and requirement output data and a synchronization component are displayed; when it is detected that a user triggers a synchronization component of to-be-synchronized requirement output data, the to-be-synchronized requirement output data is synchronized to a visual development interface; and software development code is generated according to synchronized requirement output data through the visual development interface. The present application provides a visual requirement tool, interacts with a user, acquires multiple requirement input information input by the user through a sub-interface, generates requirement output data, and improves requirement writing efficiency. In response to a requirement synchronization request of the user, requirement related information is synchronized to a visual development interface to automatically generate development code, manual writing of personnel is avoided, and software development efficiency is improved.

[0072] It should be noted that the execution subject of the method of the embodiment can be a computing service device with software development, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone and the like; or a software development device with the same or similar functions. The embodiment and the following embodiments will be described by taking the software development device as an example.

[0073] Based on this, the embodiment of the present application provides a software development method, which is described with reference toFigure 1 , Figure 1 The flowchart of the first embodiment of the software development method is shown in FIG. 1.

[0074] In this embodiment, the software development method comprises steps S10-S50.

[0075] In step S10, in response to a software development request, a visual requirement management interface is displayed, which comprises at least one requirement information acquisition sub-interface.

[0076] It should be noted that the "source start unified front-end development platform" is a front-end development solution for the financial industry, which aims to improve front-end development efficiency, ensure user experience consistency, and reduce maintenance costs through standardization, componentization, and low-code. The present application extends the visual transaction page requirement tool based on the source start unified front-end development platform. During software project development, requirement personnel and developers use the requirement tool to write requirements and generate code.

[0077] It can be understood that when receiving a user's software development request, the requirement tool displays a visual requirement management interface, which can include at least one requirement information acquisition sub-interface, such as a sub-interface for inputting basic information, a sub-interface for inputting processing logic, etc. Each sub-interface can be typeset and displayed in the form of an HTML tag in the visual requirement management interface. Each requirement information acquisition sub-interface is used to interact with the user to obtain information related to the requirement, such as basic requirement information such as requirement name and function description, and information such as specific processing logic for each requirement. The visual requirement management interface can refer to Figure 2 .

[0078] In step S20, the requirement input information input by the user in the requirement information acquisition sub-interface is received, and requirement output data is generated according to the requirement input information.

[0079] It can be understood that the visual requirement management interface can display a "create requirement" component or button. The requirement personnel clicks the button to create a requirement online and displays the requirement information acquisition sub-interface. The requirement personnel inputs requirement input information in the requirement information acquisition sub-interface. The requirement input information can be requirement name, function description, processing logic, etc. The requirement tool integrates and merges the obtained requirement input information to automatically generate requirement output data, avoiding manual writing of requirement documents by the requirement personnel, and improving the efficiency of requirement writing. An example of requirement output data is: "Requirement number: 100501, requirement name: Large certificate purchase, R&D status: 2-in development, last update date: XXXX year YY month ZZ day, responsible person: administrator one, …".

[0080] Step S30, jump to the requirement record display interface of the visualization requirement management interface, and display the requirement output data and the synchronization component corresponding to the requirement output data in the requirement record display interface.

[0081] It should be understood that after the user completes the input of the requirement input information, jump to the requirement record display interface to display the requirement output data to the user. The requirement output data can be displayed in the form of a data list, and the user confirms the requirement output data one by one. At the same time, the requirement record display interface is also provided with a synchronization component for synchronizing the requirement output data to the visualization development interface, thereby automatically generating software development code. The requirement record display interface can refer to the Figure 3

[0082] Step S40, when detecting that the user triggers the synchronization component corresponding to the to-be-synchronized requirement output data in the requirement output data, synchronizing the to-be-synchronized requirement output data to the visualization development interface to obtain the synchronized requirement output data.

[0083] It can be understood that the requirement output data can be displayed in the form of multiple data, and each data is configured with a synchronization component. The "code synchronization" button can be set as a synchronization component at the last position or the first position of each data. Taking the case of setting the synchronization component at the last position as an example, the format of the requirement output data displayed in the requirement record display interface can be an example: "Requirement number: 100501, requirement name: Large certificate purchase, R&D status: 2-Development, Last update date: XXXX year YY month ZZ day, Responsible person: Administrator one, Code synchronization button". The user confirms the requirement output data one by one, and the to-be-synchronized requirement output data is the data in the requirement output data. After the user confirms that the to-be-synchronized requirement output data is correct, the user triggers the synchronization component corresponding to the to-be-synchronized requirement output data, and synchronizes the to-be-synchronized requirement output data to the visualization development interface. For example, after confirming that the first requirement output data is correct, the user clicks the "code synchronization" button in the first requirement output data list, and the first requirement output data is synchronized to the visualization development interface. After the user confirms all the requirement output data and the synchronization is completed, all the data synchronized to the visualization development interface is the synchronized requirement output data.

[0084] Step S50, generating software development code according to the synchronized requirement output data through the visualization development interface.

[0085] ​It should be understood that the visual development interface calls a data analysis interface in the "source start unified front-end development platform", analyzes the synchronized demand output data, and generates a source code file in a preset coding format (for example, it can be in vue format, etc.), obtains the software development code, thereby reducing the code writing amount and development time of the developer.

[0086] The embodiment provides a software development method, in response to a software development request, a visual demand management interface including a demand information acquisition sub-interface is displayed; receiving demand input information input by a user in the demand information acquisition sub-interface, generating demand output data; jumping to a demand record display interface and displaying the demand output data and a synchronization component; when it is detected that the user triggers the synchronization component of the to-be-synchronized demand output data, synchronizing the to-be-synchronized demand output data to the visual development interface; and generating software development code according to the synchronized demand output data through the visual development interface. The present application provides a visual demand tool to interact with the user, acquires multiple demand input information input by the user through the sub-interface, generates demand output data, and improves the efficiency of demand writing. In response to a demand synchronization request of the user, the demand related information is synchronized to the visual development interface to automatically generate development code, avoids manual writing, and improves the software development efficiency.

[0087] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as the above embodiment one can refer to the above introduction, and will not be repeated hereinafter. On this basis, please refer to Figure 4 , the demand information acquisition sub-interface includes a basic information sub-interface, a logic processing sub-interface and a user interface design sub-interface; the demand output data includes a demand document, a business process diagram and user interface design information; step S20, the software development method further includes steps S201-S205:

[0088] Step S201, receiving demand basic information input by a user in the basic information sub-interface.

[0089] It can be understood that the basic information sub-interface can be provided with input components such as input boxes, drop-down boxes, single selection and multiple selection buttons, etc. The user inputs demand basic information such as demand name, code, function description, etc. through the input components. The basic information sub-interface can refer to Figure 5 as shown.

[0090] Step S202, after the user confirms that the demand basic information input is completed, generating a demand document according to the demand basic information, jumping to the logic processing sub-interface, and displaying the logic processing sub-interface.

[0091] It should be understood that whether the user's demand basic information input is completed can be detected, and a "confirm" button or a "next step" button can be set. When it is detected that the user clicks the button, it indicates that the user confirms that the demand basic information input is completed, the demand tool generates a demand document according to the demand basic information, and jumps to a logical processing sub-interface, at which time the logical processing sub-interface is displayed to the user. The logical processing sub-interface can be referred to as shown in Figure 6

[0092] Step S203 receives the logical processing information input by the user in the logical processing sub-interface.

[0093] It can be understood that input boxes, drop-down boxes and other input components can be set in the logical processing sub-interface, and the user inputs the business system related logical processing information through the input components. For example, a business logic description example is "1. Operation code is hidden from the interface, and 1- subscription is sent by default. 2. After the certificate information is queried, the customer number, customer type and customer name are echoed. (If the query interface is not found, support manual input of the customer number, customer type and customer name) 3. After selecting the product type, the remaining quota and the issuance year are echoed. 4. When submitting, the core service is called. 5. The transaction success interface displays the fields returned by the core."

[0094] In addition, a flowchart upload button can also be set in the logical processing sub-interface to receive the existing flowchart directly uploaded by the user.

[0095] Step S204, after the user confirms that the logical processing information input is completed, generates a business flowchart according to the logical processing information and the demand basic information, jumps to a user interface design sub-interface, and displays the user interface design sub-interface.

[0096] It should be understood that after the user confirms that the logical processing information input is completed, a business flowchart is generated in combination with the logical processing information, the flowchart uploaded by the user and the demand basic information. Jump to the user interface design sub-interface and display the user interface design sub-interface to the user.

[0097] In a possible implementation, the demand information acquisition sub-interface further includes a flowchart editing sub-interface; and step S204 can include steps S2041-S2044:

[0098] Step S2041 generates a preview flowchart according to the logical processing information and the demand basic information.

[0099] It can be understood that in order to facilitate the user to confirm and modify the flowchart generated by the tool, a preview flowchart is first generated according to the logical processing information and the demand basic information for the user to preview and confirm.

[0100] ​Step S2042, display the preview flowchart and the flowchart editing component corresponding to the preview flowchart in the logic processing sub-interface.

[0101] It can be understood that the preview flowchart can be displayed in the preset flowchart area in the logic processing sub-interface, and for each preview flowchart, a corresponding flowchart editing component is set in the preset flowchart area to meet the user's editing and modification needs of the preview flowchart.

[0102] Step S2043, when it is detected that the user triggers the flowchart editing component, jump to the flowchart editing sub-interface, and display the preview flowchart in the flowchart editing sub-interface.

[0103] It can be understood that if the user views the preview flowchart and needs to edit and modify a certain preview flowchart, the user clicks the flowchart editing component corresponding to the preview flowchart. At this time, the page jumps to the flowchart editing sub-interface, and the preview flowchart is displayed to the user in the flowchart editing sub-interface. At this time, the preview flowchart is in an editable mode, which is convenient for the user to edit. The flowchart editing sub-interface can be referred to as shown in Figure 7

[0104] Step S2044, in response to the user's editing operation on the preview flowchart, updating the preview flowchart to obtain a business flowchart.

[0105] It should be understood that the user can edit the preview flowchart in the flowchart editing sub-interface, for example, adding arrows, modifying text, deleting boxes, and the like. The preview flowchart is updated in real time in response to the user's editing operation, and after the user confirms that the editing is completed, a business flowchart is obtained.

[0106] In the embodiment, by displaying the preview flowchart in the logic processing sub-interface, the user can confirm whether the flowchart needs to be modified after previewing the automatically generated flowchart. By setting the flowchart editing button, the flowchart editing sub-interface is displayed when the user confirms that the flowchart needs to be edited, which is convenient for the user to timely modify and edit the flowchart, and improves the accuracy of the requirement output data.

[0107] Step S205, receiving the page element input by the user in the user interface design sub-interface, generating user interface design information according to the page element, integrating the requirement document, the business flowchart and the user interface design information, and generating requirement output data.

[0108] ​It can be understood that the user can also design the UI in the user interface design sub-interface. The user can input page elements by uploading files or uploading pictures. The demand tool generates user interface design information according to the page elements. Finally, the demand document, the business process diagram and the user interface design information are integrated. Specifically, the business process diagram and the user interface design information can be added to the demand document as a separate project to form the demand document together with the basic demand information. Then, the text information in the demand document is extracted to generate demand output data, which is displayed in the demand record display interface in the form of a text list.

[0109] In the embodiment, the input of the user is obtained through at least one of the basic information sub-interface, the logic processing sub-interface and the user interface design sub-interface, and the demand output data such as the demand document, the business process diagram and the user interface design information is generated, thereby improving the comprehensiveness and efficiency of demand writing.

[0110] In a possible implementation, the user interface design information includes a page picture, input and output content description and a page abstract syntax tree. Step S205 can include steps S2051-S2053.

[0111] In step S2051, the table data corresponding to the page elements uploaded by the user in the user interface design sub-interface is received.

[0112] In step S2052, the page picture and the input and output content description are generated according to the table data.

[0113] In step S2053, the table data is converted into a page abstract syntax tree in a preset programming format.

[0114] It should be noted that reference Figure 8 The user interface design sub-interface is described. The user interface design sub-interface can receive an Excel file uploaded by the user. The page elements in the Excel file can be described by the following fields, such as interface area name, interface area type, group name, group type, field name, display form (text box, drop-down list, etc.), data type, operation type (required item, optional item, etc.).

[0115] It can be understood that the UI picture and the input and output content description are generated according to the Excel file of the page elements. Then, a method of converting Excel data into a JSON format AST page abstract syntax tree is called to convert the Excel file into a JSON format AST page abstract syntax tree and return JSON data. Finally, the data is parsed by calling the "source unified front-end development platform" to render the UI design front-end page and display it in the UI preview interface for the user to preview.

[0116] In the embodiment, the page elements filled in the Excel file can be used to automatically generate the UI page picture, the input and output content description of the UI page elements, and the page AST abstract syntax tree information in JSON format after the requirement tool obtains the Excel data, so as to simplify the requirement UI design and improve the requirement writing efficiency.

[0117] In another possible implementation, the requirement information obtaining sub-interface further includes other requirement sub-interfaces; the requirement output data further includes requirement common control items and requirement output credential information; after step S205, the software development method further includes steps S206-S208:

[0118] In step S206, the other requirement sub-interface is jumped to and displayed.

[0119] In step S207, the control item information input by the user in the other requirement sub-interface is received, and the requirement common control items are generated according to the control item information.

[0120] In step S208, the credential page information input by the user in the other requirement sub-interface is received, and the requirement output credential information is generated according to the credential page information.

[0121] It can be understood that, in order to improve the comprehensiveness and integrity of the requirement information, other requirement sub-interfaces can be further set, for example, a control item sub-interface, an output item sub-interface, etc. The requirement common control items dynamically configurable by the user are received through the control item sub-interface. The credential UI display is generated according to the credential information in the Excel file through the output item sub-interface. The credential UI display can include test titles, first and second level titles, test fields, and other information. The credential preview sub-interface can be set to display the credential UI display for the user to preview. The other requirement sub-interfaces can be referred to Figure 9 .

[0122] In the embodiment, the requirement common control items, the requirement output credential information, and other information outside the UI design are generated, so as to further improve the user requirement information.

[0123] Based on the first embodiment of the present application, in the third embodiment of the present application, the same or similar contents as the above embodiment one can be referred to the above description, and will not be repeated hereinafter. On this basis, please refer to Figure 10 , the visual requirement management interface further includes a requirement overall preview interface; after step S20, the software development method further includes steps S21-S23:

[0124] Step S21, jump to the demand overall preview interface, and display the demand output data, the review component corresponding to the demand output data and the publishing component in the demand overall preview interface.

[0125] It can be understood that after determining that the user input demand information has been completed, jump to the demand overall preview interface, and display the demand output data in the form of a list in the demand overall preview interface for the user to preview. In addition, a corresponding review component and a publishing component can be set for each demand output data. The demand overall preview interface can be referred to as shown in Figure 11

[0126] Step S22, when detecting that the user triggers the review component corresponding to the to-be-reviewed demand output data in the demand output data, reviewing the to-be-reviewed demand output data to obtain reviewed demand data.

[0127] It can be understood that the user can preview and confirm the completeness of the demand output data in the demand overall preview interface, and after confirming completion, the demand output data needs to be reviewed, that is, the demand personnel online comments and replies after selecting the demand output data. After the review is completed, the reviewed demand data is obtained.

[0128] Step S23, when detecting that the user triggers the publishing component corresponding to the reviewed demand data, publishing the reviewed demand data.

[0129] It should be understood that after the demand review is passed, the demand can be published. When detecting that the user triggers the publishing component corresponding to the reviewed demand data, the reviewed demand data is published. When publishing, a version number can be specified, and the current version data is saved, the page Excel is automatically submitted to the code management tool (for example, Git, SVN, etc.), the standardized doc format demand document is generated, and the file is automatically submitted to the SVN for version management. After publishing, file export can also be performed, and the published demand can export the doc format demand document consistent with the preview page effect.

[0130] In a feasible implementation, after step S30, steps S31-S32 can also be included:

[0131] Step S31, in response to the change operation of the user on the to-be-changed demand output data selected in the demand record display interface, changing the to-be-changed demand output data according to the change operation to obtain changed demand data.

[0132] Step S32, generating version information, and performing demand version management according to the version information and the changed demand data.

[0133] ​It should be noted that if the user needs to edit and modify the published requirement again, a change operation needs to be performed. In response to a change operation of the user on the selected to-be-changed requirement output data in the requirement record display interface, the to-be-changed requirement output data is changed according to the change operation, the changed requirement data is obtained, and the changed requirement data and version information are recorded, and requirement version management is performed.

[0134] It can be understood that after the change operation is completed, the revision record can also be viewed. The previously published requirement content details can be viewed online, and the historical version detail page can be consistent with the display effect of the preview page.

[0135] In the embodiment, the requirement personnel can modify the requirement online through the tool, and requirement version management is performed according to the version information of each modification, which facilitates subsequent tracing and rollback operations, thereby improving work efficiency. The tool can also be used to perform requirement content writing, review, publishing and other operations online, and automatically generate requirement documents.

[0136] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the software development method of the present application. More forms of simple changes based on the technical concept are within the protection scope of the present application.

[0137] The present application also provides a software development device, please refer to Figure 12 , the software development device comprises:

[0138] The visual interface display module 10 is configured to display a visual requirement management interface in response to a software development request, and the visual requirement management interface comprises at least one requirement information acquisition sub-interface.

[0139] The requirement input information receiving module 20 is configured to receive requirement input information input by the user in the requirement information acquisition sub-interface, and generate requirement output data according to the requirement input information.

[0140] The requirement output data display module 30 is configured to jump to a requirement record display interface of the visual requirement management interface, and display the requirement output data and a synchronization component corresponding to the requirement output data in the requirement record display interface.

[0141] The to-be-synchronized requirement output data synchronization module 40 is configured to synchronize the to-be-synchronized requirement output data to a visual development interface when it is detected that the user triggers the synchronization component corresponding to the to-be-synchronized requirement output data in the requirement output data, and obtain synchronized requirement output data.

[0142] The software development code generation module 50 is configured to generate software development code according to the synchronized requirement output data through the visual development interface.

[0143] The software development device provided by the present application can solve the technical problems by using the software development method in the above embodiments. Compared with the prior art, the software development device provided by the present application has the same beneficial effects as the software development method provided by the above embodiments, and other technical features of the software development device are the same as the features disclosed in the above embodiments, which will not be repeated here.

[0144] The present application provides a software development device, which comprises at least one processor and a memory connected with the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the software development method in the above embodiment one.

[0145] Reference will be made to the following description of the embodiments of the present application, taken in conjunction with the accompanying drawings, in which Figure 13 which shows a structural diagram of a software development device suitable for implementing the embodiments of the present application. The software development device in the embodiments of the present application can include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle terminals (such as vehicle navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. Figure 13 The software development device shown is only an example and should not impose any limitation on the functions and use range of the embodiments of the present application.

[0146] As Figure 13As shown, the software development device can include a processing apparatus 1001 (e.g., a central processing unit, a graphics processing unit, etc.) that can perform various appropriate actions and processes according to programs stored in a read-only memory 1002 or loaded from a storage apparatus 1003 into a random access memory 1004. Various programs and data required for the operation of the software development device are also stored in the random access memory 1004. The processing apparatus 1001, the read-only memory 1002, and the random access memory 1004 are connected to each other through a bus 1005. An input / output interface 1006 is also connected to the bus. Generally, the following systems can be connected to the input / output interface 1006: input apparatuses 1007 including, for example, a touch panel, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output apparatuses 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; the storage apparatus 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication apparatus 1009. The communication apparatus 1009 can allow the software development device to perform wireless or wired communication with other devices to exchange data. Although the software development device having various systems is shown in the figure, it should be understood that all the shown systems are not required to be implemented or possessed. More or less systems can be alternatively implemented or possessed.

[0147] In particular, according to embodiments of the present disclosure, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network through the communication apparatus, or installed from the storage apparatus 1003, or installed from the ROM 1002. When the computer program is executed by the processing apparatus 1001, the above-mentioned functions defined in the methods of the embodiments of the present disclosure are performed.

[0148] The software development device provided by the present disclosure adopts the software development method in the above-mentioned embodiments, and can solve the technical problems of software development. Compared with the prior art, the software development device provided by the present disclosure has the same beneficial effects as the software development method provided by the above-mentioned embodiments, and other technical features in the software development device are the same as the features disclosed in the previous embodiment method, which will not be repeated here.

[0149] It should be understood that parts of the present disclosure can be realized by hardware, software, firmware, or a combination thereof. In the description of the above-mentioned embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0150] The above merely provides a specific implementation of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the present application, which should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0151] The present application provides a computer readable storage medium having stored thereon computer readable program instructions (i.e. computer programs) for performing the software development method in the above embodiments.

[0152] The computer readable storage medium provided by the present application may, for example, be a U disk, but is not limited to an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system, system or device, or any combination of the above. More specific examples of the computer readable storage medium can include, but are not limited to, an electric connection with one or more conductive wires, a portable computer disk, a hard disk, a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM or flash memory), an optical fiber, a portable compact disk read only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present embodiment, the computer readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer readable storage medium can be transmitted by any suitable medium, including but not limited to an electric wire, an optical cable, an RF (Radio Frequency), etc., or any suitable combination of the above.

[0153] The above computer readable storage medium can be contained in a software development device, or can exist separately without being assembled into the software development device.

[0154] The computer readable storage medium described above carries one or more programs, when the one or more programs are executed by the software development device, cause the software development device to: in response to a software development request, display a visual requirement management interface, the visual requirement management interface comprising at least one requirement information acquisition sub-interface; receive requirement input information input by a user in the requirement information acquisition sub-interface, generate requirement output data according to the requirement input information; jump to a requirement record display interface of the visual requirement management interface, and display the requirement output data and a synchronization component corresponding to the requirement output data in the requirement record display interface; when it is detected that the user triggers the synchronization component corresponding to to-be-synchronized requirement output data in the requirement output data, synchronize the to-be-synchronized requirement output data to a visual development interface, obtain synchronized requirement output data; and generate software development code according to the synchronized requirement output data through the visual development interface.

[0155] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0156] The flowcharts and block diagrams in the drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowcharts or block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flowchart illustrations, and combinations thereof, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or combinations of hardware and software.

[0157] The modules involved in the embodiments of the present application can be implemented in software or in hardware. In some cases, the names of the modules do not limit the modules themselves.

[0158] The readable storage medium provided by the present application is a computer readable storage medium, which stores computer readable program instructions (i.e. computer programs) for executing the above-mentioned software development method, and can solve the technical problems. Compared with the prior art, the computer readable storage medium provided by the present application has the same beneficial effects as the software development method provided by the above-mentioned embodiments, which will not be repeated here.

[0159] The present application also provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the steps of the software development method as described above.

[0160] The computer program product provided by the present application can solve the technical problems. Compared with the prior art, the computer program product provided by the present application has the same beneficial effects as the software development method provided by the above-mentioned embodiments, which will not be repeated here.

[0161] The above only describes some embodiments of the present application, and does not limit the patent scope of the present application. Any equivalent structural transformation made by using the content of the present application specification and drawings, or direct / indirect application in other related technical fields is included in the patent protection scope of the present application.

Claims

1. A software development method characterized by, The method comprises: in response to a software development request, displaying a visual requirement management interface, the visual requirement management interface comprising at least one requirement information acquisition sub-interface; receiving requirement input information input by a user in the requirement information acquisition sub-interface, and generating requirement output data according to the requirement input information; jumping to a requirement record display interface of the visual requirement management interface, and displaying the requirement output data and a synchronization component corresponding to the requirement output data in the requirement record display interface; when it is detected that the user triggers the synchronization component corresponding to to-be-synchronized requirement output data in the requirement output data, synchronizing the to-be-synchronized requirement output data to a visual development interface, and obtaining synchronized requirement output data; generating software development code according to the synchronized requirement output data through the visual development interface.

2. The method of claim 1, wherein, The requirement information acquisition sub-interface comprises a basic information sub-interface, a logic processing sub-interface, and a user interface design sub-interface; and the requirement output data comprises requirement documents, business process diagrams, and user interface design information. The step of receiving requirement input information input by a user in the requirement information acquisition sub-interface, and generating requirement output data according to the requirement input information comprises: receiving requirement basic information input by the user in the basic information sub-interface; after the user confirms that the requirement basic information input is completed, generating requirement documents according to the requirement basic information, jumping to the logic processing sub-interface, and displaying the logic processing sub-interface; receiving logic processing information input by the user in the logic processing sub-interface; after the user confirms that the logic processing information input is completed, generating a business process diagram according to the logic processing information and the requirement basic information, jumping to the user interface design sub-interface, and displaying the user interface design sub-interface; receiving page elements input by the user in the user interface design sub-interface, generating user interface design information according to the page elements, integrating the requirement documents, the business process diagram, and the user interface design information, and generating requirement output data.

3. The method of claim 2, wherein, The requirement information acquisition sub-interface further comprises a process diagram editing sub-interface. The step of, after the user confirms that the logic processing information input is completed, generating a business process diagram according to the logic processing information and the requirement basic information comprises: generating a preview process diagram according to the logic processing information and the requirement basic information; displaying the preview process diagram and a process diagram editing component corresponding to the preview process diagram in the logic processing sub-interface; when it is detected that the user triggers the process diagram editing component, jumping to the process diagram editing sub-interface, and displaying the preview process diagram in the process diagram editing sub-interface; in response to an editing operation of the user on the preview process diagram, updating the preview process diagram, and obtaining a business process diagram.

4. The method of claim 2, wherein, The user interface design information comprises page pictures, input / output content descriptions, and page abstract syntax trees. The step of receiving the page element input by the user in the user interface design sub-interface and generating user interface design information according to the page element comprises: Receiving table data corresponding to the page element uploaded by the user in the user interface design sub-interface; Generating a page picture and input / output content description according to the table data; Converting the table data into a page abstract syntax tree in a preset programming format.

5. The method of claim 2, wherein, The requirement information acquisition sub-interface further comprises other requirement sub-interfaces; and the requirement output data further comprises requirement common control items and requirement output credential information; After the step of receiving the page element input by the user in the user interface design sub-interface and generating user interface design information according to the page element, the method further comprises: Jumping to the other requirement sub-interface and displaying the other requirement sub-interface; Receiving control item information input by the user in the other requirement sub-interface and generating requirement common control items according to the control item information; Receiving credential page information input by the user in the other requirement sub-interface and generating requirement output credential information according to the credential page information.

6. The method of claim 1, wherein, The visual requirement management interface further comprises a requirement overall preview interface; After the step of receiving requirement input information input by the user in the requirement information acquisition sub-interface and generating requirement output data according to the requirement input information, the method further comprises: Jumping to the requirement overall preview interface and displaying the requirement output data, an evaluation component corresponding to the requirement output data and a release component in the requirement overall preview interface; Upon detecting that the user triggers the evaluation component corresponding to the to-be-evaluated requirement output data in the requirement output data, evaluating the to-be-evaluated requirement output data to obtain evaluated requirement data; Upon detecting that the user triggers the release component corresponding to the evaluated requirement data, releasing the evaluated requirement data.

7. The method of claim 6, wherein, After the step of jumping to a requirement record display interface of the visual requirement management interface and displaying the requirement output data and a synchronization component corresponding to the requirement output data in the requirement record display interface, the method further comprises: In response to a change operation of the user on selected to-be-changed requirement output data in the requirement record display interface, changing the to-be-changed requirement output data according to the change operation to obtain changed requirement data; Generating version information and performing requirement version management according to the version information and the changed requirement data.

8. A software development apparatus characterized by comprising: The software development apparatus comprises: A visual interface display module configured to display a visual requirement management interface in response to a software development request, the visual requirement management interface comprising at least one requirement information acquisition sub-interface; A requirement input information receiving module configured to receive requirement input information input by a user in the requirement information acquisition sub-interface and generate requirement output data according to the requirement input information; The requirement output data display module is configured to jump to a requirement record display interface of the visual requirement management interface and display the requirement output data and a corresponding synchronization component of the requirement output data in the requirement record display interface. The to-be-synchronized requirement output data synchronization module is configured to, when detecting that the user triggers the synchronization component corresponding to to-be-synchronized requirement output data in the requirement output data, synchronize the to-be-synchronized requirement output data to a visual development interface to obtain synchronized requirement output data. The software development code generation module is configured to generate software development code according to the synchronized requirement output data through the visual development interface.

9. A software development device, characterized by comprising: The device comprises a memory, a processor, and a computer program stored on the memory and executable on the processor, and the computer program is configured to implement the steps of the software development method according to any one of claims 1 to 7.

10. A computer program product, characterised in that, The computer program product comprises a computer program, and the computer program is executable by a processor to implement the steps of the software development method according to any one of claims 1 to 7.

Images