Software development method, apparatus, device, and computer program product

Abstract

This application discloses a software development method, apparatus, device, and computer program product, relating to the field of computer software technology. The method includes: responding to a software development request by displaying a visual requirements management interface; receiving requirement input information entered by the user in a requirement information acquisition sub-interface and generating requirement output data; redirecting to a requirement record display interface to display the requirement output data and a synchronization component; synchronizing the requirement output data to be synchronized to the visual development interface via the synchronization component; and generating software development code based on the synchronized requirement output data. This application improves the efficiency of requirement writing by providing a visual requirements tool for user interaction, acquiring multiple requirement inputs from the user through a sub-interface, and generating requirement output data. Responding to the user's requirement synchronization request, the requirement-related information is synchronized to the visual development interface to automatically generate development code, avoiding manual coding and improving software development efficiency.

Description

Technical Field

[0001] This application relates to the field of computer software technology, and in particular to a software development method, apparatus, device, and computer program product. Background Technology

[0002] During software project development, in the early stages, requirements analysts need to manually draw flowcharts and design user interfaces (UIs) using multiple tools, and manually write input / output descriptions and requirement logic descriptions. Requirements reviews are conducted offline, and version control is required. Meanwhile, developers spend a significant amount of time reading requirements and then writing the source code for the required pages, leading to low project development efficiency. Summary of the Invention

[0003] The main purpose of this application is to provide a software development method, apparatus, device, and computer program product, which aims to solve the technical problem of low development efficiency caused by software project staff manually writing requirements and code.

[0004] To achieve the above objectives, this application proposes a software development method, which includes:

[0005] In response to a software development request, a visual requirements management interface is displayed, which includes at least one requirement information acquisition sub-interface.

[0006] Receive the demand input information entered by the user in the demand information acquisition sub-interface, and generate demand output data based on the demand input information;

[0007] Jump to the requirement record display interface of the visual requirement management interface, and display the requirement output data and the corresponding synchronization component in the requirement record display interface;

[0008] When the user triggers the synchronization component corresponding to the demand output data to be synchronized in the demand output data, the demand output data to be synchronized is synchronized to the visual development interface to obtain the synchronized demand output data.

[0009] The software development code is generated by outputting data based on the synchronized requirements through the visual development interface.

[0010] In one embodiment, the requirement information acquisition sub-interface includes a basic information sub-interface, a logic processing sub-interface, and a user interface design sub-interface; the requirement output data includes requirement documents, business process diagrams, and user interface design information.

[0011] The step of receiving demand input information input by the user in the demand information acquisition sub-interface and generating demand output data based on the demand input information includes:

[0012] Receive basic information about your needs from the user in the basic information sub-interface;

[0013] After the user confirms the input of the basic requirement information, a requirement document is generated based on the basic requirement information, and the user is redirected to the logic processing sub-interface and the logic processing sub-interface is displayed.

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

[0015] After the user confirms the input of the logical processing information, a business process diagram is generated based on the logical processing information and the basic requirement information, and the user interface design sub-interface is redirected and displayed.

[0016] The system receives page elements input by the user in the user interface design sub-interface, generates user interface design information based on the page elements, and integrates the requirement document, the business process diagram, and the user interface design information to generate requirement output data.

[0017] In one embodiment, the requirement information acquisition sub-interface further includes a flowchart editing sub-interface;

[0018] The step of generating a business process diagram based on the logical processing information and the basic requirement information after the user confirms the input of the logical processing information includes:

[0019] A preview flowchart is generated based on the logical processing information and the basic requirement information;

[0020] The logic processing sub-interface displays the preview flowchart and the corresponding flowchart editing component.

[0021] When the user triggers the flowchart editing component, the user is redirected to the flowchart editing sub-interface, and the preview flowchart is displayed in the flowchart editing sub-interface.

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

[0023] In one embodiment, the user interface design information includes page images, input / output content descriptions, and a page abstract syntax tree;

[0024] The step of receiving page elements input by the user in the user interface design sub-interface and generating user interface design information based on the page elements includes:

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

[0026] Generate page images and input / output content descriptions based on the table data;

[0027] The table data is converted into a page abstract syntax tree in a preset programming format.

[0028] In one embodiment, the requirement information acquisition sub-interface further includes other requirement sub-interfaces; the requirement output data further includes requirement common control items and requirement output voucher information;

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

[0030] Jump to the other requirements sub-interface and display the other requirements sub-interface;

[0031] Receive control item information input by the user in the other requirements sub-interface, and generate common requirements control items based on the control item information;

[0032] Receive the voucher page information entered by the user in the other requirements sub-interface, and generate the required output voucher information based on the voucher page information.

[0033] In one embodiment, the visual requirements management interface further includes an overall requirements preview interface;

[0034] After the step of receiving the user's requirement input information in the requirement information acquisition sub-interface and generating requirement output data based on the requirement input information, the method further includes:

[0035] Jump to the overall requirement preview interface, and display the requirement output data, the corresponding review component and release component on the overall requirement preview interface;

[0036] When the user triggers the review component corresponding to the requirement output data to be reviewed in the requirement output data, the requirement output data to be reviewed is reviewed to obtain the reviewed requirement data.

[0037] When the user triggers the release component corresponding to the reviewed requirement data, the reviewed requirement data is released.

[0038] In one embodiment, after the step of navigating to the requirement record display interface of the visual requirement management interface and displaying the requirement output data and the corresponding synchronization component in the requirement record display interface, the method further includes:

[0039] In response to the user's change operation on the selected requirement output data to be changed in the requirement record display interface, the requirement output data to be changed is changed according to the change operation to obtain the changed requirement data;

[0040] Generate version information, and manage requirement versions based on the version information and the changed requirement data.

[0041] Furthermore, to achieve the above objectives, this application also proposes a software development apparatus, which includes:

[0042] A visual interface display module is used to display a visual requirements management interface in response to software development requests. The visual requirements management interface includes at least one requirement information acquisition sub-interface.

[0043] The requirement input information receiving module is used to receive the requirement input information entered by the user in the requirement information acquisition sub-interface, and generate requirement output data based on the requirement input information.

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

[0045] The synchronization module for output data to be synchronized is used to synchronize the output data to be synchronized to the visual development interface when the user triggers the synchronization component corresponding to the output data to be synchronized in the output data to obtain the synchronized output data.

[0046] The software development code generation module is used to generate software development code based on the synchronized requirements output data through the visual development interface.

[0047] In addition, to achieve the above objectives, this application also proposes a software development apparatus, the apparatus comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the software development method as described above.

[0048] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and which, when executed by a processor, implements the steps of the software development method described above.

[0049] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the software development method described above.

[0050] This application provides a software development method that, in response to a software development request, displays a visual requirements management interface including a requirements information acquisition sub-interface; receives requirements input information entered by the user in the requirements information acquisition sub-interface and generates requirements output data; redirects to a requirements record display interface, displaying the requirements output data and a synchronization component; when the user triggers the synchronization component for the requirements output data to be synchronized, the requirements output data to be synchronized is synchronized to the visual development interface; and software development code is generated through the visual development interface based on the synchronized requirements output data. This application improves the efficiency of requirements writing by providing a visual requirements tool that interacts with the user, acquires multiple requirements input information from the user through a sub-interface, and generates requirements output data. In response to the user's requirements synchronization request, requirements-related information is synchronized to the visual development interface to automatically generate development code, avoiding manual coding and improving software development efficiency. Attached Figure Description

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

[0052] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0053] Figure 1 This is a flowchart illustrating an embodiment of the software development method of this application.

[0054] Figure 2 This is a schematic diagram of the visual requirements management interface in this application;

[0055] Figure 3 This is a schematic diagram of the requirements record display interface in this application;

[0056] Figure 4 This is a flowchart illustrating Embodiment 2 of the software development method of this application;

[0057] Figure 5 This is a schematic diagram of the basic information sub-interface in this application;

[0058] Figure 6 This is a schematic diagram of the logic processing sub-interface in this application;

[0059] Figure 7 This is a schematic diagram of the flowchart editing sub-interface in this application;

[0060] Figure 8 A schematic diagram illustrating the sub-interfaces designed for the user interface in this application;

[0061] Figure 9 This is a schematic diagram of other sub-interfaces required in this application;

[0062] Figure 10 This is a flowchart illustrating Embodiment 3 of the software development method of this application;

[0063] Figure 11 This is a schematic diagram of the overall preview interface required in this application;

[0064] Figure 12 This is a schematic diagram of the module structure of the software development apparatus according to an embodiment of this application;

[0065] Figure 13 This is a schematic diagram of the device structure of the hardware operating environment involved in the software development method in this application embodiment.

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

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

[0068] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0069] The main solution of this application embodiment is as follows: In response to a software development request, a visual requirements management interface is displayed, the visual requirements management interface including at least one requirements information acquisition sub-interface; requirements input information is received by the user in the requirements information acquisition sub-interface, and requirements output data is generated according to the requirements input information; the user is redirected to the requirements record display interface of the visual requirements management interface, and the requirements output data and the corresponding synchronization component are displayed in the requirements record display interface; when the user triggers the synchronization component corresponding to the requirements output data to be synchronized in the requirements output data, the requirements output data to be synchronized is synchronized to the visual development interface to obtain synchronized requirements output data; software development code is generated through the visual development interface according to the synchronized requirements output data.

[0070] Because of existing technology, in the early stages of software project development, requirements analysts need to manually draw flowcharts, design user interfaces (UI), and write input / output descriptions and requirement logic descriptions using multiple tools. Requirements reviews are conducted offline, and version control is required. Meanwhile, developers need to spend a significant amount of time reading requirements and then writing the source code for the required pages, resulting in low project development efficiency.

[0071] This application provides a solution that, in response to a software development request, displays a visual requirements management interface including a requirements information acquisition sub-interface; receives requirements input information entered by the user in the requirements information acquisition sub-interface, generates requirements output data; redirects to a requirements record display interface, displaying the requirements output data and a synchronization component; when the user triggers the synchronization component for the requirements output data to be synchronized, the requirements output data to be synchronized is synchronized to the visual development interface; and software development code is generated through the visual development interface based on the synchronized requirements output data. This application improves the efficiency of requirements writing by providing a visual requirements tool that interacts with the user, acquires multiple requirements input information from the user through a sub-interface, and generates requirements output data. In response to the user's requirements synchronization request, requirements-related information is synchronized to the visual development interface to automatically generate development code, avoiding manual coding and improving software development efficiency.

[0072] It should be noted that the executing entity of the method in this embodiment can be a computing service device with software development, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone; or it can be a software development device with the same or similar functions. This embodiment and the following embodiments will be described using a software development device as an example.

[0073] Based on this, the embodiments of this application provide a software development method, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the software development method of this application.

[0074] In this embodiment, the software development method includes steps S10 to S50:

[0075] Step S10: In response to a software development request, a visual requirements management interface is displayed, which includes at least one requirement information acquisition sub-interface.

[0076] It should be noted that the "Yuanqi Unified Front-End Development Platform" is a front-end development solution for the financial industry. It aims to improve front-end development efficiency, ensure consistent user experience, and reduce maintenance costs through standardization, componentization, and low-code methods. This application extends the Yuanqi Unified Front-End Development Platform with a visual transaction page requirements tool. During software project development, requirements analysts and developers utilize this tool for requirements writing and code generation.

[0077] Understandably, upon receiving a user's software development request, the requirements tool displays a visual requirements management interface. This interface may include at least one sub-interface for obtaining requirements information, such as a sub-interface for inputting basic information and a sub-interface for inputting processing logic. Each sub-interface can be formatted and displayed in the visual requirements management interface using HTML tags. Each requirement information acquisition sub-interface is used to interact with the user and obtain requirement-related information, such as basic requirement information like the requirement name and functional description, and specific processing logic for each requirement. The visual requirements management interface can be referenced... Figure 2 .

[0078] Step S20: Receive the requirement input information entered by the user in the requirement information acquisition sub-interface, and generate requirement output data based on the requirement input information.

[0079] Understandably, the visual requirements management interface can display a "Create Requirement" component or button. Requirement personnel can click this button to create requirements online, displaying a sub-interface for obtaining requirement information. In this sub-interface, personnel input requirement information, which can include the requirement name, functional description, processing logic, etc. The requirements tool integrates and merges the acquired input information, automatically generating requirement output data, avoiding the need for personnel to manually write requirement documents and improving the efficiency of requirement writing. An example of requirement output data is: "Requirement ID: 100501, Requirement Name: Large-Amount Certificate of Deposit Subscription, Development Status: 2-Under Development, Last Update Date: XXXX Year YY Month ZZ Day, Responsible Person: Administrator 1, ...".

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

[0081] It should be understood that after the user completes the input of the requirements, they are redirected to the requirements record display interface to show the requirements output data. Multiple requirements output data can be displayed in the form of a data list, allowing the user to confirm each data point. Simultaneously, the requirements record display interface also includes a synchronization component to synchronize the requirements output data to the visual development interface, thereby automatically generating software development code. The requirements record display interface can be referenced. Figure 3 As shown.

[0082] Step S40: When the user triggers the synchronization component corresponding to the demand output data to be synchronized in the demand output data, the demand output data to be synchronized is synchronized to the visual development interface to obtain the synchronized demand output data.

[0083] Understandably, requirement output data can be displayed in multiple data entries, each configured with a synchronization component. A "Code Synchronization" button can be placed at the end or beginning of each data entry. For example, with the synchronization component at the end, the requirement output data displayed in the requirement record display interface could be formatted as: "Requirement Number: 100501, Requirement Name: Large-Amount Certificate of Deposit Subscription, Development Status: 2-Under Development, Last Update Date: XXXX Year YY Month ZZ Day, Responsible Person: Administrator 1, Code Synchronization Button". Users confirm each requirement output data entry individually; the data to be synchronized is the data within the requirement output data. After the user confirms the data to be synchronized is correct, the corresponding synchronization component is triggered, synchronizing the data to the visual development interface. For example, after confirming 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 visual development interface. Once the user has confirmed all the required output data and the synchronization is complete, all the data synchronized to the visual development interface is the synchronized required output data.

[0084] Step S50: Generate software development code through the visual development interface based on the synchronized requirements output data.

[0085] It should be understood that the visual development interface calls the data parsing interface in the "Yuanqi Unified Front-end Development Platform" to parse the synchronized required output data and generate source code files in a preset encoding format (e.g., Vue format) to obtain software development code, thereby reducing the amount of code written and development time for developers.

[0086] This embodiment provides a software development method. In response to a software development request, it displays a visual requirements management interface including a requirements information acquisition sub-interface; receives requirements input information entered by the user in the requirements information acquisition sub-interface and generates requirements output data; jumps to a requirements record display interface and displays the requirements output data and synchronization components; when the user triggers the synchronization component for the requirements output data to be synchronized, the requirements output data to be synchronized is synchronized to the visual development interface; and software development code is generated through the visual development interface based on the synchronized requirements output data. This application improves the efficiency of requirements writing by providing a visual requirements tool that interacts with the user, obtains multiple requirements input information from the user through a sub-interface, and generates requirements output data. In response to the user's requirements synchronization request, requirements-related information is synchronized to the visual development interface to automatically generate development code, avoiding manual coding and improving software development efficiency.

[0087] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 4 The requirement information acquisition sub-interface includes a basic information sub-interface, a logic processing sub-interface, and a user interface design sub-interface; the requirement output data includes requirement documents, business process diagrams, and user interface design information; step S20, the software development method further includes steps S201 to S205:

[0088] Step S201: Receive the basic information of the user's requirements input in the basic information sub-interface.

[0089] Understandably, the basic information sub-interface can include input components such as input boxes, dropdown lists, and radio / select buttons. Users input basic requirement information, such as the requirement name, code, and function description, through these components. A sample basic information sub-interface can be found here. Figure 5 As shown.

[0090] Step S202: After the user confirms the input of the basic requirement information, a requirement document is generated based on the basic requirement information, and the user is redirected to the logic processing sub-interface and the logic processing sub-interface is displayed.

[0091] It should be understood that a "Confirm" or "Next" button can be set to check whether the user has completed inputting the basic requirements information. When a button is clicked, it indicates that the user has confirmed the completion of inputting the basic requirements information. The requirements tool then generates a requirements document based on the basic requirements information and redirects the user to the logic processing sub-interface, which is then displayed to the user. The logic processing sub-interface can be found in [reference needed]. Figure 6 As shown.

[0092] Step S203: Receive the logic processing information input by the user in the logic processing sub-interface.

[0093] Understandably, input components such as input boxes and dropdown menus can be set in the logic processing sub-interface, allowing users to input relevant logic processing information from the business system. For example, a business logic description might be: "1. Operation code is hidden from the interface, defaulting to 1-Subscription. 2. After checking the document information, query and display the customer number, customer type, and customer name. (Query interface not found; manual input of customer number, customer type, and customer name is supported.) 3. After selecting the product type, query and display the remaining quota and issuance year. 4. The core service is called upon submission. 5. The transaction success interface displays the fields returned by the core service."

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

[0095] Step S204: After the user confirms the input of the logical processing information, a business process diagram is generated based on the logical processing information and the basic requirement information. The user then jumps to the user interface design sub-interface and displays the user interface design sub-interface.

[0096] It should be understood that after the user confirms the input of the logical processing information, a business process diagram is generated by combining the logical processing information, the flowchart uploaded by the user, and the basic requirement information. The user then navigates to the user interface design sub-interface and displays it to the user.

[0097] In one feasible implementation, the demand information acquisition sub-interface further includes a flowchart editing sub-interface; step S204 may include steps S2041 to S2044:

[0098] Step S2041: Generate a preview flowchart based on the logical processing information and the basic requirement information.

[0099] Understandably, in order to facilitate users' confirmation and modification of the flowcharts generated by the tool, a preview flowchart is first generated based on the logical processing information and basic requirement information for users to preview and confirm.

[0100] Step S2042: Display the preview flowchart and the corresponding flowchart editing component in the logic processing sub-interface.

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

[0102] Step S2043: When the user triggers the flowchart editing component, the user is redirected to the flowchart editing sub-interface, and the preview flowchart is displayed in the flowchart editing sub-interface.

[0103] Understandably, if a user needs to edit a preview flowchart after viewing it, they can click the corresponding flowchart editing component. The page will then redirect to the flowchart editing sub-interface, where the preview flowchart will be displayed to the user in editable mode. The flowchart editing sub-interface can be found here. Figure 7 As shown.

[0104] Step S2044: In response to the user's editing operation on the preview flowchart, update the preview flowchart to obtain the business process flowchart.

[0105] It should be understood that users can edit and preview flowcharts in the flowchart editing sub-interface, such as adding arrows, modifying text, and deleting boxes. The system updates the preview flowchart in real time in response to user editing operations, and obtains the business process flowchart after the user confirms the editing.

[0106] In this embodiment, by displaying a preview flowchart in the logic processing sub-interface, users can confirm whether the automatically generated flowchart needs modification after previewing it. By providing a flowchart editing button, a flowchart editing sub-interface is displayed when the user confirms that the flowchart needs editing, facilitating timely correction and editing of the flowchart and improving the accuracy of the required output data.

[0107] Step S205: Receive page elements input by the user in the user interface design sub-interface, generate user interface design information based on the page elements, and integrate the requirement document, the business process diagram, and the user interface design information to generate requirement output data.

[0108] Understandably, users can also design the UI in the user interface design sub-interface. They can input page elements by uploading files or images, and the requirements tool will generate user interface design information based on these elements. Finally, the requirements document, business process diagram, and user interface design information are integrated. Specifically, the business process diagram and user interface design information can be added as separate items to the requirements document, together with the basic requirements information, to form the requirements document. Then, the text information in the requirements document is extracted to generate requirements output data, which is displayed as a text list in the requirements record display interface.

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

[0110] In one feasible implementation, the user interface design information includes page images, input / output content descriptions, and a page abstract syntax tree; step S205 may include steps S2051 to S2053:

[0111] Step S2051: Receive the table data corresponding to the page elements uploaded by the user in the user interface design sub-interface.

[0112] Step S2052: Generate page images and input / output content descriptions based on the table data.

[0113] Step S2053: Convert the table data into a page abstract syntax tree in a preset programming format.

[0114] It should be noted that the reference Figure 8 This section describes the user interface design sub-interface. This sub-interface can receive Excel files containing page elements uploaded by the user. The Excel file can describe page elements using fields such as: interface area name, interface area type, group name, group type, field name, display format (text box, drop-down list, etc.), data type, and operation type (required, optional, etc.).

[0115] Understandably, the process involves generating UI images and input / output descriptions from an Excel file containing page elements. Then, a method is called to convert the Excel data into a JSON-formatted Abstract Syntax Tree (AST), returning the JSON data. Finally, the "Yuanqi Unified Front-End Development Platform" is used to parse the data, render the UI design front-end page, and display it in the UI preview interface for user viewing.

[0116] In this implementation, the requirements tool can automatically generate UI page images, input and output descriptions of UI page elements, and JSON-formatted page AST abstract syntax tree information after obtaining the Excel data from the page elements filled in the Excel file. This simplifies the UI design of the requirements and improves the efficiency of requirements writing.

[0117] In another feasible implementation, the requirement information acquisition sub-interface may also include other requirement sub-interfaces; the requirement output data may also include requirement common control items and requirement output voucher information; after step S205, steps S206 to S208 may also be included:

[0118] Step S206: Jump to the other requirements sub-interface and display the other requirements sub-interface.

[0119] Step S207: Receive control item information input by the user in the other requirements sub-interface, and generate common requirements control items based on the control item information.

[0120] Step S208: Receive the voucher page information input by the user in the other requirements sub-interface, and generate the requirement output voucher information based on the voucher page information.

[0121] Understandably, to improve the comprehensiveness and completeness of requirement information, other requirement sub-interfaces can be set up, such as control item sub-interfaces and output item sub-interfaces. The control item sub-interface receives dynamically configurable common requirement control items input by the user. The output item sub-interface receives the voucher page Excel file uploaded by the user and generates a voucher UI display based on the voucher information in the Excel file. The voucher UI display can include information such as test title, first and second level headings, and test fields. A voucher preview sub-interface can be set up to display the voucher UI display for user preview. Other requirement sub-interfaces can be referenced. Figure 9 As shown.

[0122] In this implementation, user requirement information is further improved by generating information beyond the UI design, such as common requirement control items and requirement output voucher information.

[0123] Based on the first embodiment of this application, in the third embodiment of this application, the content that is the same as or similar to that in the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 10 The visual requirements management interface also includes a requirements preview interface; after step S20, the software development method further includes steps S21 to S23:

[0124] Step S21: Jump to the overall requirement preview interface, and display the requirement output data, the review component and the release component corresponding to the requirement output data in the overall requirement preview interface.

[0125] Understandably, after confirming that the user has input their requirements, the user is redirected to the overall requirements preview interface. This interface displays the required output data in a list format for preview. Furthermore, corresponding review and publication components can be set up for each piece of required output data. A sample overall requirements preview interface can be found here. Figure 11 As shown.

[0126] Step S22: When the user triggers the review component corresponding to the requirement output data to be reviewed in the requirement output data, the requirement output data to be reviewed is reviewed to obtain the reviewed requirement data.

[0127] Understandably, users can preview and confirm the completeness of the requirement output data in the overall requirement preview interface. After confirmation, the requirement output data needs to be reviewed, meaning that the requirement personnel can select the requirement output data online and add comments, annotations, and replies. The reviewed requirement data is then obtained after the review is completed.

[0128] Step S23: When the user triggers the publishing component corresponding to the reviewed requirement data, the reviewed requirement data is published.

[0129] It should be understood that requirements can be released after the requirements review is approved. When the release component is detected corresponding to the requirements data triggered by the user review, the reviewed requirements data will be released. During release, a version number can be specified, and the current version data is saved. The page Excel file is automatically committed to a code management tool (e.g., Git, SVN), generating a standardized doc format requirements document, which is then automatically committed to SVN for version control. After release, the file can also be exported; released requirements can be exported as a doc format requirements document consistent with the preview page.

[0130] In one feasible implementation, after step S30, steps S31 to S32 may also be included:

[0131] Step S31: In response to the user's change operation on the selected requirement output data to be changed in the requirement record display interface, the requirement output data to be changed is changed according to the change operation to obtain the changed requirement data.

[0132] Step S32: Generate version information and perform requirement version management based on the version information and the changed requirement data.

[0133] It's worth noting that if a user needs to edit or modify a published requirement, a change operation is required. In response to the user's change operation on the output data of the selected requirement in the requirement record display interface, the system modifies the output data accordingly, obtaining the modified requirement data. Simultaneously, the modified requirement data and version information are recorded for requirement version management.

[0134] Understandably, revision history can be viewed after the change is completed. Details of previously published requirements can be viewed online, and the historical version details page can be displayed identically to the preview page.

[0135] In this embodiment, the tool allows requirement personnel to modify requirements online and manage requirement versions based on each modification, facilitating subsequent traceability and rollback operations, thereby improving work efficiency. The tool also enables online requirement writing, review, and publishing, automating the generation of requirement documents.

[0136] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the software development method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0137] This application also provides a software development apparatus, please refer to... Figure 12 The software development apparatus includes:

[0138] The visualization interface display module 10 is used to display a visualization requirement management interface in response to software development requests. The visualization requirement management interface includes at least one requirement information acquisition sub-interface.

[0139] The requirement input information receiving module 20 is used to receive the 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 used to jump to the requirement record display interface of the visual requirement management interface, and to display the requirement output data and the corresponding synchronization component in the requirement record display interface.

[0141] The synchronization module 40 for the output data to be synchronized is used to synchronize the output data to be synchronized to the visual development interface when the user triggers the synchronization component corresponding to the output data to be synchronized in the output data, so as to obtain the synchronized output data.

[0142] The software development code generation module 50 is used to generate software development code based on the synchronized requirements output data through the visual development interface.

[0143] The software development apparatus provided in this application, employing the software development method described in the above embodiments, can solve the technical problem. Compared with the prior art, the beneficial effects of the software development apparatus provided in this application are the same as those of the software development method provided in the above embodiments, and other technical features in the software development apparatus are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0144] This application provides a software development apparatus, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the software development method in Embodiment 1 above.

[0145] The following is for reference. Figure 13 The diagram illustrates a structural schematic of a software development device suitable for implementing the embodiments of this application. The software development device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 13 The software development equipment shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0146] like Figure 13As shown, the software development equipment may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.) that can perform various appropriate actions and processes according to a program stored in a read-only memory 1002 or a program loaded from a storage device 1003 into a random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the software development equipment. The processing unit 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1003 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows the software development equipment to communicate wirelessly or wiredly with other devices to exchange data. Although the figure shows software development equipment with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0147] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application 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 via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0148] The software development equipment provided in this application, employing the software development method described in the above embodiments, can solve the technical problems of software development. Compared with the prior art, the beneficial effects of the software development equipment provided in this application are the same as those of the software development method provided in the above embodiments, and other technical features of the software development equipment are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0149] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0150] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0151] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the software development method in the above embodiments.

[0152] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0153] The aforementioned computer-readable storage medium may be included in the software development equipment; or it may exist independently and not be assembled into the software development equipment.

[0154] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by a software development device, the software development device causes the following actions in response to a software development request: It displays a visual requirements management interface, which includes at least one requirements information acquisition sub-interface; it receives requirements input information entered by a user in the requirements information acquisition sub-interface and generates requirements output data based on the requirements input information; it redirects to a requirements record display interface of the visual requirements management interface and displays the requirements output data and a corresponding synchronization component in the requirements record display interface; when it detects that the user has triggered the synchronization component corresponding to the requirements output data to be synchronized in the requirements output data, it synchronizes the requirements output data to be synchronized to the visual development interface to obtain synchronized requirements output data; and it generates software development code based on the synchronized requirements output data through the visual development interface.

[0155] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0156] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0157] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0158] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described software development method, thereby solving the technical problem. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the software development method provided in the above embodiments, and will not be repeated here.

[0159] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the software development method described above.

[0160] The computer program product provided in this application can solve the technical problem. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as the beneficial effects of the software development method provided in the above embodiments, and will not be repeated here.

[0161] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A software development method, characterized in that, The method includes: In response to a software development request, a visual requirements management interface is displayed. The visual requirements management interface includes at least one requirements information acquisition sub-interface, which includes a basic information sub-interface, a logic processing sub-interface, and a user interface design sub-interface. Receive requirement input information from the user in the requirement information acquisition sub-interface, and generate requirement output data based on the requirement input information. The requirement output data includes requirement documents, business process diagrams and user interface design information. Jump to the requirement record display interface of the visual requirement management interface, and display the requirement output data and the corresponding synchronization component in the requirement record display interface; When the user triggers the synchronization component corresponding to the demand output data to be synchronized in the demand output data, the demand output data to be synchronized is synchronized to the visual development interface to obtain the synchronized demand output data. The software development code is generated by the visual development interface based on the synchronized requirement output data. The visual development interface calls the data parsing interface to parse the synchronized requirement output data and generate source code files in a preset encoding format to obtain the software development code. The step of receiving demand input information input by the user in the demand information acquisition sub-interface and generating demand output data based on the demand input information includes: Receive basic information about your needs from the user in the basic information sub-interface; After the user confirms the input of the basic requirement information, a requirement document is generated based on the basic requirement information, and the user is redirected to the logic processing sub-interface and the logic processing sub-interface is displayed. Receive the logic processing information input by the user in the logic processing sub-interface; After the user confirms the input of the logical processing information, a business process diagram is generated based on the logical processing information and the basic requirement information, and the user interface design sub-interface is redirected and displayed. The system receives page elements input by the user in the user interface design sub-interface, generates user interface design information based on the page elements, and integrates the requirement document, the business process diagram, and the user interface design information to generate requirement output data.

2. The method as described in claim 1, characterized in that, The demand information acquisition sub-interface also includes a flowchart editing sub-interface; The step of generating a business process diagram based on the logical processing information and the basic requirement information after the user confirms the input of the logical processing information includes: A preview flowchart is generated based on the logical processing information and the basic requirement information; The logic processing sub-interface displays the preview flowchart and the corresponding flowchart editing component. When the user triggers the flowchart editing component, the user is redirected to the flowchart editing sub-interface, and the preview flowchart is displayed in the flowchart editing sub-interface. In response to the user's editing operation on the preview flowchart, the preview flowchart is updated to obtain the business process flowchart.

3. The method as described in claim 1, characterized in that, The user interface design information includes page images, input / output content descriptions, and the page abstract syntax tree; The step of receiving page elements input by the user in the user interface design sub-interface and generating user interface design information based on the page elements includes: Receive table data corresponding to page elements uploaded by the user in the user interface design sub-interface; Generate page images and input / output content descriptions based on the table data; The table data is converted into a page abstract syntax tree in a preset programming format.

4. The method as described in claim 1, characterized in that, The requirement information acquisition sub-interface also includes other requirement sub-interfaces; the requirement output data also includes requirement public control items and requirement output voucher information. After the step of receiving page elements input by the user in the user interface design sub-interface and generating user interface design information based on the page elements, the method further includes: Jump to the other requirements sub-interface and display the other requirements sub-interface; Receive control item information input by the user in the other requirements sub-interface, and generate common requirements control items based on the control item information; Receive the voucher page information entered by the user in the other requirements sub-interface, and generate the required output voucher information based on the voucher page information.

5. The method as described in claim 1, characterized in that, The visual requirements management interface also includes an overall requirements preview interface; After the step of receiving the user's requirement input information in the requirement information acquisition sub-interface and generating requirement output data based on the requirement input information, the method further includes: Jump to the overall requirement preview interface, and display the requirement output data, the corresponding review component and release component on the overall requirement preview interface; When the user triggers the review component corresponding to the requirement output data to be reviewed in the requirement output data, the requirement output data to be reviewed is reviewed to obtain the reviewed requirement data. When the user triggers the release component corresponding to the reviewed requirement data, the reviewed requirement data is released.

6. The method as described in claim 5, characterized in that, After the step of navigating to the requirement record display interface of the visual requirement management interface, and displaying the requirement output data and the corresponding synchronization component in the requirement record display interface, the method further includes: In response to the user's change operation on the selected requirement output data to be changed in the requirement record display interface, the requirement output data to be changed is changed according to the change operation to obtain the changed requirement data; Generate version information, and manage requirement versions based on the version information and the changed requirement data.

7. A software development apparatus, characterized in that, The software development device includes: The visualization interface display module is used to respond to software development requests and display a visualization requirement management interface. The visualization requirement management interface includes at least one requirement information acquisition sub-interface, which includes a basic information sub-interface, a logic processing sub-interface, and a user interface design sub-interface. The requirement input information receiving module is used to receive the requirement input information entered by the user in the requirement information acquisition sub-interface, and generate requirement output data based on the requirement input information. The requirement output data includes requirement documents, business process diagrams and user interface design information. The requirement output data display module is used to jump to the requirement record display interface of the visual requirement management interface, and to display the requirement output data and the corresponding synchronization component in the requirement record display interface. The synchronization module for output data to be synchronized is used to synchronize the output data to be synchronized to the visual development interface when the user triggers the synchronization component corresponding to the output data to be synchronized in the output data, so as to obtain the synchronized output data. The software development code generation module is used to generate software development code based on the synchronized requirement output data through the visual development interface. The visual development interface calls the data parsing interface to parse the synchronized requirement output data and generate source code files in a preset encoding format to obtain the software development code. The requirement input information receiving module is further configured to receive basic requirement information input by the user in the basic information sub-interface; after the user confirms the input of the basic requirement information, generate a requirement document based on the basic requirement information, jump to the logic processing sub-interface, and display the logic processing sub-interface; receive logic processing information input by the user in the logic processing sub-interface; after the user confirms the input of the logic processing information, generate a business process diagram based on the logic processing information and the basic requirement information, jump to the user interface design sub-interface, and display the user interface design sub-interface; receive page elements input by the user in the user interface design sub-interface, generate user interface design information based on the page elements, and integrate the requirement document, the business process diagram, and the user interface design information to generate requirement output data.

8. A software development device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the software development method as described in any one of claims 1 to 6.

9. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the software development method as described in any one of claims 1 to 6.

Images