Application development method and device
By dividing the application development process into requirements analysis, code development and code testing stages, and using tool chains to associate each subprocess, the full process online management and automation are achieved, and the process incoherence and intricate data records in the existing technology are solved. The problem has improved the quality of project delivery and R&D efficiency.
Patent Information
- Application Number
- CN202310645466.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-01
- Publication Date
- 2024-12-03
AI Technical Summary
The existing application development process lacks online management of the entire process, resulting in incoherent processes, intricate data records, incomplete tool chains, and inability to realize automated and refined management of the R&D process, affecting the quality of project delivery and R&D efficiency.
By dividing the application development process into three stages: requirements analysis, code development and code testing, different fields are used for process management, and each subprocess is associated with the tool chain to realize online management and automation of the entire process, and record input parameters and outputs are recorded. Results to ensure that the data is authentic and trustworthy.
It has improved the quality of project delivery, realized multi-dimensional data analysis, improved R&D efficiency and process improvement, and formed a highly automated software development workflow to support refined quality management.
Smart Images

Figure CN119065637A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a method and device for application development. Background Art
[0002] Application development must comply with certain processes and technical development specifications. Each member of the application development team must follow a unified standard deployment to design, develop, test, and communicate in order to improve development efficiency and project development quality. However, the current application development process has not formed an online and digital development process. The development and testing tools are discrete tools that are disconnected from the process and development and testing process, that is, the tool flow is disconnected from the information flow, and the pipeline of the development process has not been formed, ignoring the importance of the testing process.
[0003] At the same time, the current R&D process management is coarse-grained, only including the general records of the stages, the process records are not detailed enough, and there is a lack of a complete tool chain to support the R&D workflow. When statistical analysis of the development process is required later, it can only be done by manually filling in the information into the system. The inaccurate and erroneous information filled in by the manual operation deviates from the actual situation, resulting in unreliable process data. Summary of the invention
[0004] In view of this, the embodiment of the present invention provides a method and device for application development, which can realize online management of the entire process of application development, solve process problems, and improve the quality of project delivery through process system constraints; meet the entire process management from the demand analysis stage to the code testing stage, and can be widely used in application software development and testing process management, and can also improve R&D efficiency. In addition, during the application development process, process data such as input parameters and output results are recorded, so that the data for subsequent data statistical analysis is authentic and reliable. Through the data analysis of the entire process, multi-dimensional (project, personnel, team, application, code) data energy efficiency analysis is met. Through energy efficiency data analysis, the R&D efficiency and process improvement are reversely promoted, and a virtuous cycle is continuously formed.
[0005] To achieve the above-mentioned purpose, according to one aspect of an embodiment of the present invention, a method for application development is provided, comprising: in response to an application development requirement analysis instruction, creating a requirement analysis task and generating a requirement number, parsing the requirement analysis task to generate a requirement analysis sub-process corresponding to the requirement number, and performing requirement analysis according to the requirement analysis sub-process; in response to a code development instruction, establishing an association relationship between an application identifier of the application and the requirement number, and generating a code development sub-process corresponding to the application identifier based on a result of the requirement analysis, performing code development according to the code development sub-process to obtain application code; in response to a code testing instruction, creating a code testing task, and establishing an association relationship between a test task identifier and the application identifier, generating a code testing sub-process corresponding to the test task identifier based on the code testing task, and testing the application code according to the code testing sub-process to complete application development.
[0006] Optionally, the requirement analysis sub-process includes: requirement creation, requirement review and requirement acceptance; performing requirement analysis according to the requirement analysis sub-process includes: responding to a requirement creation instruction, obtaining requirement information according to the requirement analysis task, and generating an application development flowchart according to the requirement information; responding to a requirement review instruction, reviewing the application development flowchart to generate a requirement review result; and when the requirement review result is passed, responding to a requirement acceptance instruction, generating an acceptance form according to the requirement acceptance information.
[0007] Optionally, after generating the application development flowchart according to the demand information, the method further includes: displaying the application development flowchart in a graphical manner.
[0008] Optionally, the code development sub-process includes: system design review, code submission, unit test coverage statistics, security compliance detection, dependency conflict detection, code static scanning, code review and code integration; code development is performed according to the code development sub-process, including: in response to a system design review instruction, reviewing the system design file of the application to generate a system design review result; in response to a code submission instruction, if the system design review result is a passed review, generating code submission information and application code change information based on the submitted development code and the application identifier; in response to a unit test coverage statistics instruction, obtaining a code coverage report file and application code based on the application identifier, and obtaining unit test coverage statistics information in combination with the code coverage report file and the application code; in response to a security compliance In response to a detection instruction, vulnerability detection and privacy compliance scanning are performed based on the application code branch to be detected and the application code, and a security compliance detection result is generated; in response to a dependency conflict detection instruction, component dependency conflict detection is performed based on the application code branch to be detected and the application code, and a dependency conflict detection result is generated; in response to a code static scanning instruction, a predetermined code specification scan is performed based on a code quality management platform based on the application code branch to be detected and the application code, and a code static scanning result is generated; in response to a code review instruction, a code review is performed based on the application code branch to be reviewed and the application code, and a code review result is generated; in case the code review result is a passed review, in response to a code integration instruction, the submitted development code is merged into the application code branch to be detected for code integration.
[0009] Optionally, the code testing sub-process includes: creating test tasks, sending test reports, compiling and building, code scanning, smoke testing, test acceptance / rejection, creating test plans, test case review, UI automation testing, interface automation testing, functional test coverage / monitoring, sending test reports, sending online notifications, and sending online verification reports; testing the application code according to the code testing sub-process includes: responding to a create test task instruction, creating a test task according to test requirement information, and generating test task information; responding to a send test report instruction, assembling the test requirement information and the test task information, and sending the assembled test report to relevant personnel ; In response to the compile and build instruction, the identification of the application to be tested is obtained according to the test task information, and the test environment deployment is completed according to the test requirement information and the identification of the application to be tested, and the progress of the compile and build is displayed; in response to the code scanning instruction, the code coverage report file and the application code are obtained according to the test requirement information and the identification of the application to be tested, and the unit test coverage statistics are obtained by combining the code coverage report file and the application code; in response to the smoke test instruction, according to the test requirement information, the identification of the application to be tested and the test case, a smoke test is performed on the application to be tested, and a smoke test result is generated; in response to the test acceptance / rejection instruction, according to the smoke test The test result generates test acceptance information or test rejection information; in the case of test acceptance, in response to the instruction to create a test plan, a test plan is generated according to the test task information and the identification of the application to be tested, and the execution results of the functional test cases and the automated test cases are counted; in response to the test case review instruction, a test case review is performed according to the execution results of the functional test cases and the automated test cases to be reviewed, and the test case review results are generated; in response to the UI automated test instruction, a UI automated test is performed according to the test task information, the identification of the application to be tested and the UI automated test case, and the execution results of the UI automated test case are counted; in response to the interface automated test instruction , perform interface automation testing according to the test task information, the application identifier to be tested and the interface automation test case, and count the execution results of the interface automation test case; in response to the functional test coverage / monitoring instruction, obtain the application deployment server information according to the application identifier to be tested, perform coverage testing on the application to be tested deployed on the application deployment server according to the functional test case and the automation test case, and generate coverage test results; in response to the instruction to send a test report, assemble and generate a test report according to the test requirement information, the application identifier to be tested, the functional test case and the coverage test results of the automation test case according to the test report template, and send it to relevant personnel;In response to the instruction to send an online notification, according to the test requirement information, the identification of the application to be tested, and the inspection results before the application goes online, the online notification is assembled and generated according to the online notification template, and sent to relevant personnel; in response to the instruction to send an online verification report, according to the test requirement information, the identification of the application to be tested, and the inspection results after the application acceptance, the online verification report is assembled and generated according to the online verification report template, and sent to relevant personnel. ;
[0010] Optionally, the method further includes: in the process of application development, associating and storing the input parameters and output results included in each sub-process with each node of the sub-process; and displaying the relevant information of each node by operating each node.
[0011] Optionally, the method also includes: at the nodes of demand acceptance, test creation, test report sending, test report sending, online notification sending and online verification report sending, notification information is generated according to the output results of the nodes and sent to relevant personnel.
[0012] According to another aspect of an embodiment of the present invention, there is provided an application development device, comprising: a requirement analysis module, for responding to an application development requirement analysis instruction, creating a requirement analysis task and generating a requirement number, parsing the requirement analysis task to generate a requirement analysis sub-process corresponding to the requirement number, and performing requirement analysis according to the requirement analysis sub-process; a code development module, for responding to a code development instruction, establishing an association relationship between an application identifier of the application and the requirement number, and generating a code development sub-process corresponding to the application identifier based on a result of the requirement analysis, and performing code development according to the code development sub-process to obtain application code; a code testing module, for responding to a code testing instruction, creating a code testing task, establishing an association relationship between a test task identifier and the application identifier, generating a code testing sub-process corresponding to the test task identifier based on the code testing task, and testing the application code according to the code testing sub-process to complete application development.
[0013] According to another aspect of an embodiment of the present invention, there is provided an electronic device, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the application development method provided by an embodiment of the present invention.
[0014] According to another aspect of the embodiments of the present invention, a computer-readable medium is provided, on which a computer program is stored. When the program is executed by a processor, the method for developing an application provided by the embodiments of the present invention is implemented.
[0015] An embodiment of the above invention has the following advantages or beneficial effects: by responding to the application development requirement analysis instruction, creating a requirement analysis task and generating a requirement number, parsing the requirement analysis task to generate a requirement analysis sub-process corresponding to the requirement number, and performing requirement analysis according to the requirement analysis sub-process; in response to the code development instruction, establishing an association relationship between the application identification and the requirement number of the application, and generating a code development sub-process corresponding to the application identification according to the result of the requirement analysis, performing code development according to the code development sub-process to obtain application code; in response to the code testing instruction, creating a code testing task, and establishing an association relationship between the test task identification and the application identification, and generating code corresponding to the test task identification according to the code testing task The test sub-process tests the application code according to the code test sub-process to complete the technical solution of application development. By dividing the entire application development process into the requirements analysis stage, the code development stage and the code testing stage, and using different fields as key information for process management in each stage, and through these fields to associate the sub-processes corresponding to the requirements analysis stage, the code development stage and the code testing stage to generate a software development workflow, the online management of the entire process of application software development is realized, the process problem is solved, and the quality of project delivery is improved through process system constraints; it meets the entire process management from the requirements analysis stage to the code testing stage, which can be widely used in the application software development and testing process management, and can also improve the R&D efficiency. In addition, in the process of application software development, the process data such as input parameters and output results are recorded, so that the data in the subsequent data statistical analysis is authentic and reliable. Through the data analysis of the entire process, the multi-dimensional (project, personnel, team, application, code) data energy efficiency analysis is met. Through the energy efficiency data analysis, the R&D efficiency and process improvement are reversely promoted, and a virtuous cycle is continuously formed.
[0016] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.
[0018] Figure 1 is a schematic diagram of main steps of a method for developing an application according to an embodiment of the present invention;
[0019] Figure 2 It is a schematic diagram of each node of the application development workflow of an embodiment of the present invention;
[0020] Figure 3 is a schematic diagram of output results of creating a demand node according to an embodiment of the present invention;
[0021] Figure 4is a schematic diagram of main modules of a device for application development according to an embodiment of the present invention;
[0022] Figure 5 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;
[0023] Figure 6 It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION
[0024] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.
[0025] The acquisition, storage, use, and processing of data in the technical solution of the present invention are in compliance with the relevant provisions of national laws and regulations.
[0026] The existing application software development process does not have a complete online development process, and most of the relevant data in the development process is manually filled in for recording. This will bring the following disadvantages:
[0027] 1. The process was not fully online, and some key process data was missing during the R&D process, making it impossible to conduct quantitative analysis of the R&D process;
[0028] 2. The R&D and testing tools designed are discrete and do not form a tool chain, which makes it impossible to integrate the R&D process data;
[0029] 3. Lack of R&D workflow and automation tool integration concept, ignoring the importance of the R&D process;
[0030] 4. The existing R&D process has not been realized online and digital, which is not conducive to the control and quantification of the R&D process;
[0031] 5. The software development and testing control process cannot achieve process automation and refined management.
[0032] The purpose of the present invention is to design a tool chain corresponding to the workflow based on the workflow of application development, form a highly automated software process pipeline, and make its workflow online, automated, and digital. This can bring the following effects:
[0033] 1) Due to the online operation, all developer operations are performed through corresponding tools, so the data of these operations are automatically recorded by the system, instead of R&D and test personnel manually filling the information back into the system after performing the operation; for example, who did what and when, and the detailed data of the results are saved and stored in the database, and the performance process data is statistically analyzed for process and process improvement, assisting managers in performing refined management actions;
[0034] 2) Highly integrated automation can greatly solve process problems and improve the quality of project delivery through process system constraints. At the same time, through data analysis of the entire process, it can meet the multi-dimensional (project, personnel, team, application) data energy efficiency analysis. Through energy efficiency data analysis, it can reversely push to improve R&D efficiency and process improvement, and continuously form a virtuous cycle.
[0035] 3) Guide and assist software developers and software testers to efficiently complete application software development work, speed up software iteration, and improve application software development and delivery efficiency;
[0036] 4) Realize "digitalization of quality control process" and "visualization of performance", providing a one-stop platform support for the team to implement refined quality management.
[0037] Figure 1 Schematic diagram of the main steps of the method for application development according to an embodiment of the present invention. Figure 1 As shown, the application development method of the embodiment of the present invention mainly includes the following steps S101 to S103.
[0038] Step S101: in response to an application development requirement analysis instruction, create a requirement analysis task and generate a requirement number, parse the requirement analysis task to generate a requirement analysis sub-process corresponding to the requirement number, and perform requirement analysis according to the requirement analysis sub-process;
[0039] Step S102: in response to the code development instruction, establishing an association relationship between the application identifier of the application and the requirement number, generating a code development sub-process corresponding to the application identifier according to the result of the requirement analysis, and performing code development according to the code development sub-process to obtain application code;
[0040] Step S103: In response to the code testing instruction, a code testing task is created, and an association relationship between the test task identifier and the application identifier is established, a code testing sub-process corresponding to the test task identifier is generated according to the code testing task, and the application code is tested according to the code testing sub-process to complete application development.
[0041] According to the above-mentioned steps S101 to S103, the entire application software development process is divided into a requirement analysis stage, a code development stage and a code testing stage, and different fields are used as key information for process management in each stage. These fields are used to associate the sub-processes corresponding to the requirement analysis stage, the code development stage and the code testing stage to generate an application software development workflow, thereby realizing online management of the entire software development process, solving process problems, and improving the quality of project delivery through process system constraints; meeting the entire process management from the requirement analysis stage to the code testing stage, it can be widely used in software development and testing process management, and can also improve R&D efficiency.
[0042] According to one embodiment of the present invention, the requirement analysis sub-process includes: requirement creation, requirement review and requirement acceptance; performing requirement analysis according to the requirement analysis sub-process includes: responding to a requirement creation instruction, obtaining requirement information according to the requirement analysis task, and generating an application development flowchart according to the requirement information; responding to a requirement review instruction, reviewing the application development flowchart to generate a requirement review result; and, if the requirement review result is passed, responding to a requirement acceptance instruction, generating an acceptance form according to the requirement acceptance information.
[0043] According to another embodiment of the present invention, after generating the application development flowchart according to the demand information, the method further includes: displaying the application development flowchart in a graphical manner.
[0044] According to another embodiment of the present invention, the code development sub-process includes: system design review, code submission, unit test coverage statistics, security compliance detection, dependency conflict detection, code static scanning, code review and code integration; code development is performed according to the code development sub-process, including: in response to a system design review instruction, reviewing the system design file of the application to generate a system design review result; in response to a code submission instruction, generating code submission information and application code change information according to the submitted development code and the application identifier when the system design review result is a passed review; in response to a unit test coverage statistics instruction, obtaining a code coverage report file and application code according to the application identifier, and obtaining unit test coverage statistics in combination with the code coverage report file and the application code; in response to In response to the security compliance detection instruction, vulnerability detection and privacy compliance scanning are performed according to the application code branch to be detected and the application code, and a security compliance detection result is generated; in response to the dependency conflict detection instruction, component dependency conflict detection is performed according to the application code branch to be detected and the application code, and a dependency conflict detection result is generated; in response to the code static scanning instruction, based on the application code branch to be detected and the application code, a predetermined code specification scan is performed based on the code quality management platform, and a code static scanning result is generated; in response to the code review instruction, a code review is performed according to the application code branch to be reviewed and the application code, and a code review result is generated; in response to the code integration instruction, when the code review result is a passed review, the submitted development code is merged into the application code branch to be detected for code integration.
[0045] According to another embodiment of the present invention, the code testing sub-process includes: creating test tasks, sending test reports, compiling and building, code scanning, smoke testing, test acceptance / rejection, creating test plans, test case review, automated testing, interface automated testing, functional test coverage / monitoring, sending test reports, sending online notifications, and sending online verification reports; testing the application code according to the code testing sub-process includes: responding to a create test task instruction, creating a test task according to test requirement information, and generating test task information; responding to a send test report instruction, assembling the test requirement information and the test task information, and sending the assembled test report to relevant personnel; in response to the compilation and construction instruction, the identification of the application to be tested is obtained according to the test task information, and the test environment deployment is completed according to the test requirement information and the identification of the application to be tested, and the progress of the compilation and construction is displayed; in response to the code scanning instruction, the code coverage report file and the application code are obtained according to the test requirement information and the identification of the application to be tested, and the unit test coverage statistics are obtained by combining the code coverage report file and the application code; in response to the smoke test instruction, according to the test requirement information, the identification of the application to be tested and the test case, a smoke test is performed on the application to be tested, and a smoke test result is generated; in response to the test acceptance / rejection instruction, according to the The smoke test result generates test acceptance information or test rejection information; in the case of test acceptance, in response to the create test plan instruction, a test plan is generated according to the test task information and the application identifier to be tested, and the execution results of the functional test cases and the automated test cases are counted; in response to the test case review instruction, a test case review is performed according to the execution results of the functional test cases and the automated test cases to be reviewed, and the test case review results are generated; in response to the UI automation test instruction, a UI automation test is performed according to the test task information, the application identifier to be tested and the UI automation test case, and the execution results of the UI automation test case are counted; in response to the interface automation test instruction Instructions, perform interface automation testing according to the test task information, the application identifier to be tested and the interface automation test case, and count the execution results of the interface automation test case; in response to the functional test coverage / monitoring instruction, obtain the application deployment server information according to the application identifier to be tested, perform coverage testing on the application to be tested deployed on the application deployment server according to the functional test case and the automation test case, and generate coverage test results; in response to the instruction to send a test report, assemble and generate a test report according to the test requirement information, the application identifier to be tested, the functional test case and the coverage test results of the automation test case according to the test report template, and send it to relevant personnel;In response to the instruction to send an online notification, according to the test requirement information, the identification of the application to be tested, and the inspection results before the application goes online, the online notification is assembled and generated according to the online notification template, and sent to relevant personnel; in response to the instruction to send an online verification report, according to the test requirement information, the identification of the application to be tested, and the inspection results after the application acceptance, the online verification report is assembled and generated according to the online verification report template, and sent to relevant personnel. ;
[0046] According to another embodiment of the present invention, the application development method of the embodiment of the present invention can also associate and store the input parameters and output results included in each sub-process with each node of the sub-process during the application development process; and display the relevant information of each node by operating the each node.
[0047] According to another embodiment of the present invention, the application development method of the embodiment of the present invention, at the nodes of demand acceptance, test creation, test report sending, test report sending, online notification sending and online verification report sending, also generates notification information based on the output results of the nodes and sends it to relevant personnel.
[0048] Figure 2 It is a schematic diagram of each node of the application development workflow of an embodiment of the present invention. In one embodiment of the present invention, in the process of application development, the execution process of the demand analysis phase, the code development phase, and the code testing phase is refined respectively, and more than 20 process nodes are designed. With a highly automated pipeline design concept, each capability node is connected in series according to the R&D process to form an operable workflow, wherein each process node capability can be supported by an independent process tool. The entire workflow connects each sub-process in series with the requirement number, application identifier (for example, application name or application number), and test task identifier to form an operable pipeline. In the demand analysis phase, a requirement number is generated when a requirement is created, and the requirement number is used as key information for process management. When the code development phase is entered after the requirement is accepted, the application code that needs to be changed is associated with the requirement number, and the application identifier corresponding to the code warehouse is used as key information for process management. When the code testing phase is entered after the test is created, the test task is associated with the application code, and the test task identifier ID is used as key information for process management. In this way, the data of the entire development process can be associated with each other, and have relevance, which is the key point for digitalization.
[0049] like Figure 2As shown in , the main nodes in the demand analysis phase are: demand creation, demand review and demand acceptance; the main nodes in the code development phase are: system design review, code submission, unit test coverage statistics, security compliance detection, dependency conflict detection, code static scanning, code review and code integration; the main nodes in the code testing phase are: creating test tasks, sending test reports, compiling and building, code scanning, smoke testing, test acceptance / rejection, creating test plans, test case review, UI (User Interface, user interface) automated testing, interface automated testing, functional test coverage / monitoring, sending test reports, sending online notifications, sending online verification reports, etc. The following is a detailed introduction to the operations or functional implementations performed by each node.
[0050] Requirements analysis phase:
[0051] 1) Demand creation: In response to a demand creation instruction, demand information is obtained according to a demand analysis task, and an application development flowchart is generated based on the demand information.
[0052] Node capability description: After the product manager accepts the business requirements, he / she enters the requirement information into the system through the requirement creation capability provided by the software development workflow; input parameters: requirement name, requirement details, requirement submitter, expected date, etc.; output results: generate a requirement number, and automatically generate the sub-processes in the code development phase and the sub-processes in the code testing phase for the requirement number, and display them in a graphical way. Figure 3 FIG. 1 is a schematic diagram of the output result of a demand creation node according to an embodiment of the present invention. Figure 3 As shown, the graphical sub-process of the code development phase and the sub-process of the code testing phase output by the requirement creation node are shown.
[0053] 2) Requirements review: In response to the requirements review instruction, the application development flowchart is reviewed to generate requirements review results.
[0054] Node capability description: After creating a requirement, the product manager clicks the "Requirement Review" node on the software development workflow, and a form for initiating the requirement review pops up. After clicking Submit, an invitation to a requirement review meeting is automatically issued, enabling online management of the requirement review process and document deliverables. Input parameters: review participants, uploaded review requirement documents, meeting time and location, meeting agenda, and other information. If it is a second review, a review initiation function is provided. Output results: automatic invitation to a review meeting, output of review conclusions, and online management and follow-up of meeting to-do items.
[0055] 3) Demand acceptance: When the demand review result is passed, in response to the demand acceptance instruction, an acceptance form is generated according to the demand acceptance information.
[0056] Node capability description: The prerequisite is that the demand review is passed. The developer clicks the "Demand Acceptance" node on the software development workflow, an acceptance form pops up, and then submits the form information; input parameters: personnel involved in the demand, expected start time, expected end time, split of demand development tasks (personnel, start / end time, task name, task hours) and other information; output result: submit the form information, and automatically notify the relevant parties of the acceptance information by email or instant messaging tools.
[0057] Code development phase:
[0058] 1) System design review: In response to the system design review instruction, the system design document of the application is reviewed to generate a system design review result.
[0059] Node capability description: When the developer clicks the "System Design Review" node on the software development workflow, the system design review form pops up. After clicking Submit, a system design review meeting invitation is automatically issued to achieve online management of the system design review process and document delivery; Input parameters: Participants in the review, upload review design documents, meeting time and location, meeting agenda and other information. If it is a second review, a review initiation function is provided; Output results: Automatically issue meeting invitations, output review conclusions, and manage and follow up meeting to-do items online.
[0060] 2) Code submission: When the system design review result is passed, in response to a code submission instruction, code submission information and application code change information are generated according to the submitted development code and the application identifier.
[0061] Node capability description: Developers involved in this requirement select and associate the system applications that need to be changed for the implementation of this requirement (system application information comes from metadata maintenance, refer to the description content). After the requirement is associated with the application, the commit information of the associated code library is automatically obtained and saved in the library. Clicking the "Code Submission" node can display who submitted all associated applications, when they were submitted, and the detailed content of the submitted code. Among them, system application information includes, for example: application name, code library address, product line, branch information, deployment content source path, etc.; Input parameters: Associate the application that needs to be changed for this requirement, and the developer writes the code locally and submits it to the corresponding code library; Output result: Automatically obtain the commit information and change information of the associated code library.
[0062] 3) Unit test coverage statistics: In response to the unit test coverage statistics instruction, the code coverage report file and the application code are obtained according to the application identifier, and the unit test coverage statistics information is obtained by combining the code coverage report file and the application code.
[0063] Node capability description: The project must have unit test (unit test is unit test, which refers to checking and verifying the smallest testable unit in the software) code and the Jacoco dependency must be configured in the project before it can be used (using JaCoCo to count the coverage of Java project unit test code). The developer or tester clicks the "Unit Test Coverage Statistics" node on the software development workflow, and a confirmation prompt box pops up. After confirmation, the unit test coverage statistics are automatically performed. This node is not required and can be manually skipped in the process; input parameters: the path and name of the Jacoco coverage report file (.exec) associated with the requirement, the path of the class file after the project is compiled, the directory of the project source code file, and the exclusion of files that do not need to be counted; output results: parse the unit test coverage statistics report, save the information in the database, and display it in charts.
[0064] 4) Security compliance testing: In response to the security compliance testing instruction, vulnerability detection and privacy compliance scanning are performed based on the application code branch to be tested and the application code, and a security compliance testing result is generated.
[0065] Node capability description: Developers and testers click the "Security Compliance Detection" node on the software development workflow to automatically perform source code security audits (code vulnerabilities, referenced components, etc.) and privacy compliance scans on the associated application code base; Input parameters: The code base address of the application associated with the requirement and the branch to be detected, which defaults to the master branch; Output results: Parse the detection report, save the information in the database and display it in charts, including information such as the number of detected vulnerabilities and vulnerability details.
[0066] 5) Dependency conflict detection: In response to the dependency conflict detection instruction, component dependency conflict detection is performed according to the application code branch to be detected and the application code, and a dependency conflict detection result is generated.
[0067] Node capability description: Developers and testers click the "Dependency Conflict Detection" node on the software development workflow to automatically perform component dependency conflict detection on the code base of the associated application and quickly locate the conflict location; Input parameters: The code base address of the application associated with the requirement and the branch to be detected, which is the master branch by default; Output results: Parse the detection report, save the information in the database and display it in charts, including component conflict details and other information.
[0068] 6) Code static scanning: In response to the code static scanning instruction, a code quality management platform is used to perform a predetermined code specification scan based on the application code branch to be detected and the application code, and a code static scanning result is generated.
[0069] Node capability description: Developers and testers click the "Code Static Scan" node on the software development workflow to automatically scan the code base of the associated application for Sonar (Sonar (SonarQube) is an open source platform for managing the quality of source code) and the established code specifications. The user generates a configuration properties file for the sonar operation by inputting parameters in the sonar atom. Use sonar-scanner to perform the scanning task. After the execution is completed, you can view detailed data in the "Run Report" of the software development workflow; Input parameters: The code base address of the application associated with the requirement, the branch to be detected, the default is the master branch; Output results: Parse the detection report, save the information in the database and display it in a chart.
[0070] 7) Code review: In response to the code review instruction, a code review is performed based on the application code branch to be reviewed and the application code, and a code review result is generated.
[0071] Node capability description: When the developer clicks the "Code Review" node on the software development workflow, a code review form pops up. After clicking Submit, a system design review meeting invitation is automatically issued, and the review participants confirm the review conclusion. Input parameters: Review participants select the code library address of the application associated with the requirement, the branch information to be reviewed, the meeting time and location, the meeting agenda, and other information. If it is a second review, a review initiation function is provided. Output results: Automatically issue a meeting invitation, output the review conclusion, manage and follow up the meeting to-do items online, and record all review process information.
[0072] 8) Code integration: When the code review result is passed, in response to a code integration instruction, the submitted development code is merged into the application code branch to be tested to perform code integration.
[0073] Node capability description: On the premise that the code review is passed, the developer clicks the "Code Integration" node on the software development workflow, and a window pops up, where the development branch code of the system application associated with the requirement can be merged into the test branch for submission for testing; input parameters: the code library address of the application associated with the requirement, and the branch to be tested; output results: the development branch code is merged into the test branch, and information such as who, when, and the changed code line is recorded for traceability.
[0074] Code testing phase:
[0075] 1) Create a test task: In response to a create test task instruction, create a test task according to test requirement information and generate test task information.
[0076] Node capability description: After code integration is completed, the developer clicks the "Create Test" node on the software development workflow, and a form window pops up (automatically bringing the requirement information and application-related information associated with the requirement); input parameters: testers participating in the requirement test task, expected test completion time and other information; output results: generate a test task, and notify the corresponding tester via email and / or instant messaging tools, with test task information attached.
[0077] 2) Sending a test report: In response to a sending a test report instruction, the test requirement information and the test task information are assembled, and the assembled test report is sent to relevant personnel.
[0078] Node capability description: After submitting the test task, the developer clicks the "Send Test Report" node on the software development workflow, and a confirmation prompt box pops up. After confirmation, the node automatically collects demand information, test tasks and other information, and automatically assembles the information and sends it by email; input parameters: inherit the demand information and test task information of the software development workflow; output results: automatically send test report emails and instant messaging messages to relevant personnel.
[0079] 3) Compile and build (download code, compile and package, deploy): In response to the compile and build instruction, obtain the identification of the application to be tested according to the test task information, complete the test environment deployment according to the test requirement information and the identification of the application to be tested, and display the progress of the compile and build.
[0080] Node capability description: After receiving the test report, the tester clicks the "Compile and Build" node on the software development workflow, and a list of applications associated with the requirement pops up. Clicking Build will automatically complete the deployment of the test environment. Input parameters: Inherit the requirement information of the software development workflow and the test application information of the test task. Output results: Automatically complete the deployment of the test environment and display the progress of the compilation and build.
[0081] 4) Code scanning (consistent with the "unit test coverage statistics" function in the code development process): In response to the code scanning instruction, the code coverage report file and the application code are obtained according to the test requirement information and the identification of the application to be tested, and the unit test coverage statistics are obtained by combining the code coverage report file and the application code.
[0082] Node capability description: The tester clicks the "Code Scan" node on the software development workflow to perform unit test coverage statistics for the merged test branch. A confirmation prompt box pops up. After confirmation, unit test coverage statistics are automatically performed on the application code associated with the requirement. This node is not required and can be manually skipped in the process; input parameters: inherit the requirement information of the software development workflow and the application information of the test task; output results: parse the unit test coverage statistics report, save the information in the database and display it in charts.
[0083] 5) Smoke test: In response to the smoke test instruction, a smoke test is performed on the application to be tested according to the test requirement information, the identification of the application to be tested and the test case, and a smoke test result is generated.
[0084] Node capability description: The tester clicks the "Smoke Test" node on the software development workflow to automatically execute the test task and the corresponding use case execution progress, UI automation case, and interface automation case in the test plan, and summarize the test results for display (used to determine whether it is testable and provide a basis for judgment for test access); Input parameters: Inherit the manual test case, UI automation case, and interface automation case information associated with the test plan; Output results: Automatically trigger the UI and interface automation cases, query the execution results of the manual test cases, and display the result data.
[0085] 6) Test acceptance / rejection: In response to a test acceptance / rejection instruction, test acceptance information or test rejection information is generated according to the smoke test result.
[0086] Node capability description: After the smoke test is completed, the tester determines whether to accept the test task based on the result data of the smoke test (used to determine whether it is testable and provide a basis for test admission). The tester clicks the "Test Acceptance / Rejection" node, and a form pops up. The acceptance operation formally enters the code testing phase, and the rejection operation enters the code creation testing phase; input parameters: inherit the test task ID of the software development workflow; output results: the test task status changes to testing, and records relevant information such as the acceptance time and acceptor.
[0087] 7) Create a test plan: When the test is accepted, in response to the instruction to create a test plan, a test plan is generated according to the test task information and the identification of the application to be tested, and the execution results of the functional test cases and the automated test cases are counted.
[0088] Node capability description: When the tester receives a test task, click the "Create Test Plan" node and a form will pop up. In this form, you can associate functional test cases from the case library and associate UI and interface automated test cases from the automated test platform; Input parameters: Inherit the test task ID and application information of the software development workflow; Output results: Generate a test plan and count the execution results of functional test cases and automated test cases.
[0089] 8) Test case review: In response to the test case review instruction, the test case review is performed according to the execution results of the functional test cases and automated test cases to be reviewed, and the test case review results are generated.
[0090] Node capability description: The tester clicks the "Test Case Review" node on the software development workflow, and the test review form pops up. After clicking Submit, an invitation to a system design review meeting is automatically issued, and the review participants confirm the review conclusions. Input parameters: The review participants select the test plan to associate functional test cases and automated test cases, meeting time and location, meeting agenda and other information. If it is a second review, the review initiation function is provided. Output results: Automatically issue meeting invitations, output review conclusions, manage and follow up on meeting to-do items online, and record all review process information.
[0091] 9) UI automation test: In response to the UI automation test instruction, the UI automation test is performed according to the test task information, the identification of the application to be tested and the UI automation test case, and the execution results of the UI automation test case are counted.
[0092] Node capability description: When the tester clicks the "UI Automation Test" node, he can trigger the UI automation use case associated with the test plan (specify the use case designed in the UI automation test platform, which must be associated with the application when it is created); Input parameters: inherit the test task application information of the software development workflow, and pass the application information to the UI automation trigger execution interface (after receiving the application information, the interface will automatically execute the UI automation use case of the associated application); Output results: return the execution results of the automation use case associated with the test application, and parse the results and store them in the database.
[0093] 10) Interface automation test: In response to the interface automation test instruction, the interface automation test is performed according to the test task information, the identification of the application to be tested and the interface automation test case, and the execution results of the interface automation test case are counted.
[0094] Node capability description: When the tester clicks the "Interface Automation Test" node, the interface automation use case associated with the test plan can be triggered (specify the use case designed in the interface automation test platform, which must be associated with the application when it is created); Input parameters: inherit the test task application information of the software development workflow, and pass the application information to the interface for interface automation trigger execution (after receiving the application information, the interface will automatically execute the UI automation use case of the associated application); Output results: return the execution results of the automation use case associated with the test application, and parse the results and store them in the database.
[0095] 11) Functional test coverage / monitoring: In response to the functional test coverage / monitoring instruction, the application deployment server information is obtained according to the identification of the application to be tested, and the coverage test is performed on the application to be tested deployed on the application deployment server according to the functional test cases and automated test cases, and the coverage test results are generated.
[0096] Node capability description: When the tester clicks the "Functional Test Coverage / Monitoring" node, the 'Start' and 'Stop' dialog boxes pop up. When the operation starts, JaCoCo statistics for functional test code coverage collection is started. When the operation stops, JaCoCo functional test code coverage collection is stopped and statistics are started. The main purpose of this node operation is to view the relevant indicators of code coverage statistics after functional testing; input parameters: inherit the test task application information of the software development workflow, and obtain the deployment server IP of the application; output results: output the covered code instructions when the functional test and UI and interface automation cases are executed, which is used to judge whether the test coverage is complete.
[0097] 12) Sending a test report: In response to a test report sending instruction, a test report is generated according to a test report template based on the test requirement information, the identification of the application to be tested, the coverage test results of the functional test cases and the automated test cases, and sent to relevant personnel.
[0098] Node capability description: After the tester completes the test and the operation test passes, the process flows to sending the test report. Click the "Send Test Report" node and the test report form pops up; input parameters: automatically inherit the software development workflow's requirement information, test application information, test case information, code vulnerability bug information, etc.; output results: automatically assemble information according to the test report template and automatically send it in the form of an email.
[0099] 13) Sending an online notification: In response to the instruction to send an online notification, an online notification is generated according to the online notification template based on the test requirement information, the identification of the application to be tested, and the inspection result before the application goes online, and sent to relevant personnel.
[0100] Node capability description: After the tester sends the test report, the developer clicks the "Send Online Notice" node, and a form for sending the online notice pops up. The developer needs to confirm the confirmation items before going online in this form; Input parameters: Automatically inherit the software development workflow's requirement information, test application information, and confirmation items before going online; Output results: Automatically assemble information according to the online notice template and automatically send it in the form of an email.
[0101] 14) Sending online verification report: In response to the instruction to send online verification report, an online verification report is generated according to the test requirement information, the identification of the application to be tested, and the inspection results after application acceptance, according to the online verification report template, and sent to relevant personnel.
[0102] Node capability description: After the developer sends the online notice, the online operation is carried out. After the online operation is completed, the developer organizes the testers and product managers to conduct online acceptance. Click the "Send Online Verification Report" node, and the online acceptance form pops up. The developer, tester, and product manager need to confirm the confirmation items after acceptance in this form respectively; Input parameters: Automatically inherit the demand information, test application information, confirmation items after acceptance, etc. of the software development workflow; Output results: Automatically assemble information according to the online verification report template and automatically send it in the form of email.
[0103] Figure 4 Schematic diagram of the main modules of the device for application development according to an embodiment of the present invention. Figure 4 As shown, the application development device 400 of the embodiment of the present invention mainly includes a demand analysis module 401, a code development module 402 and a code testing module 403.
[0104] The requirement analysis module 401 is used to create a requirement analysis task and generate a requirement number in response to an application development requirement analysis instruction, parse the requirement analysis task to generate a requirement analysis sub-process corresponding to the requirement number, and perform requirement analysis according to the requirement analysis sub-process;
[0105] A code development module 402, configured to establish an association relationship between the application identifier of the application and the requirement number in response to a code development instruction, and generate a code development sub-process corresponding to the application identifier according to a result of the requirement analysis, and perform code development according to the code development sub-process to obtain application code;
[0106] The code testing module 403 is used to create a code testing task in response to a code testing instruction, and to establish an association between the test task identifier and the application identifier, to generate a code testing sub-process corresponding to the test task identifier according to the code testing task, and to test the application code according to the code testing sub-process to complete application development.
[0107] According to one embodiment of the present invention, the requirement analysis sub-process includes: requirement creation, requirement review and requirement acceptance; the requirement analysis module 401 can also be used to: respond to a requirement creation instruction, obtain requirement information according to the requirement analysis task, and generate an application development flowchart according to the requirement information; respond to a requirement review instruction, review the application development flowchart to generate a requirement review result; if the requirement review result is passed, respond to a requirement acceptance instruction, generate an acceptance form according to the requirement acceptance information.
[0108] According to another embodiment of the present invention, the demand analysis module 401 may also be used to: after generating the application development flowchart according to the demand information, display the application development flowchart in a graphical manner.
[0109] According to another embodiment of the present invention, the code development sub-process includes: system design review, code submission, unit test coverage statistics, security compliance detection, dependency conflict detection, code static scanning, code review and code integration; the code development module 402 can also be used for: in response to a system design review instruction, reviewing the system design file of the application to generate a system design review result; in response to a code submission instruction, generating code submission information and application code change information according to the submitted development code and the application identifier when the system design review result is a passed review; in response to a unit test coverage statistics instruction, obtaining a code coverage report file and application code according to the application identifier, and obtaining unit test coverage statistics information in combination with the code coverage report file and the application code; in response to a security In response to the compliance detection instruction, vulnerability detection and privacy compliance scanning are performed based on the application code branch to be detected and the application code, and a security compliance detection result is generated; in response to the dependency conflict detection instruction, component dependency conflict detection is performed based on the application code branch to be detected and the application code, and a dependency conflict detection result is generated; in response to the code static scanning instruction, a predetermined code specification scan is performed based on the code quality management platform based on the application code branch to be detected and the application code, and a code static scanning result is generated; in response to the code review instruction, a code review is performed based on the application code branch to be reviewed and the application code, and a code review result is generated; in case the code review result is a passed review, in response to the code integration instruction, the submitted development code is merged into the application code branch to be detected for code integration.
[0110] According to another embodiment of the present invention, the code testing sub-process includes: creating test tasks, sending test reports, compiling and building, code scanning, smoke testing, test acceptance / rejection, creating test plans, test case review, UI automation testing, interface automation testing, functional test coverage / monitoring, sending test reports, sending online notifications, and sending online verification reports; the code testing module 403 can also be used to: respond to a create test task instruction, create a test task according to test requirement information, and generate test task information; respond to a send test report instruction, assemble the test requirement information and the test task information, and send the assembled test report to relevant personnel; respond to a compile and build instruction, according to the test task In response to the code scanning instruction, the code coverage report file and the application code are obtained according to the test requirement information and the application identification to be tested, and the unit test coverage statistics are obtained in combination with the code coverage report file and the application code; in response to the smoke test instruction, a smoke test is performed on the application to be tested according to the test requirement information, the application identification to be tested and the test case, and a smoke test result is generated; in response to the test acceptance / rejection instruction, test acceptance information or test rejection information is generated according to the smoke test result; in the case of test acceptance, in response to the creation of the test In response to the test plan instruction, a test plan is generated according to the test task information and the identification of the application to be tested, and the execution results of the functional test cases and the automated test cases are counted; in response to the test case review instruction, a test case review is performed according to the execution results of the functional test cases and the automated test cases to be reviewed, and the test case review results are generated; in response to the UI automated test instruction, a UI automated test is performed according to the test task information, the identification of the application to be tested and the UI automated test case, and the execution results of the UI automated test case are counted; in response to the interface automated test instruction, an interface automated test is performed according to the test task information, the identification of the application to be tested and the interface automated test case, and the execution results of the interface automated test case are counted ; in response to the functional test coverage / monitoring instruction, obtain the application deployment server information according to the identification of the application to be tested, perform coverage test on the application to be tested deployed on the application deployment server according to the functional test cases and the automated test cases, and generate coverage test results; in response to the instruction to send a test report, assemble and generate a test report according to the test requirement information, the identification of the application to be tested, the functional test cases and the coverage test results of the automated test cases according to the test report template, and send it to relevant personnel; in response to the instruction to send an online notification, assemble and generate an online notification according to the online notification template according to the test requirement information, the identification of the application to be tested, and the inspection results before the application goes online, and send it to relevant personnel;In response to the instruction to send an online verification report, an online verification report is generated according to the test requirement information, the identification of the application to be tested, and the inspection result after the application acceptance, according to the online verification report template, and sent to relevant personnel. ;
[0111] According to another embodiment of the present invention, the application development device 400 also includes a data storage module (not shown in the figure), which is used to: during the application development process, associate and store the input parameters and output results included in each sub-process with each node of the sub-process; and display the relevant information of each node by operating the each node.
[0112] According to another embodiment of the present invention, the application development device 400 also includes a notification module (not shown in the figure), which is used to: at the nodes of demand acceptance, test creation, test report sending, test report sending, online notification sending and online verification report sending, and also generate notification information based on the output results of the node and send it to relevant personnel.
[0113] According to the technical solution of the embodiment of the present invention, by responding to the application development requirement analysis instruction, creating a requirement analysis task and generating a requirement number, parsing the requirement analysis task to generate a requirement analysis sub-process corresponding to the requirement number, and performing requirement analysis according to the requirement analysis sub-process; in response to the code development instruction, establishing an association relationship between the application identifier and the requirement number of the application, and generating a code development sub-process corresponding to the application identifier according to the result of the requirement analysis, performing code development according to the code development sub-process to obtain the application code; in response to the code testing instruction, creating a code testing task, and establishing an association relationship between the test task identifier and the application identifier, generating a code test task corresponding to the test task identifier according to the code testing task Sub-processes, according to the code testing sub-process, test the application code to complete the technical solution of application development. By dividing the entire application development process into the requirements analysis stage, the development stage and the code testing stage, and using different fields as key information for process management in each stage, and through these fields to associate the sub-processes corresponding to the requirements analysis stage, the development stage and the code testing stage to generate software development workflows, the online management of the entire process of application software development is realized, the process problem is solved, and the quality of project delivery is improved through process system constraints; the entire process management from the requirements analysis stage to the code testing stage is met, which can be widely used in the management of application software development and testing processes, and can also improve R&D efficiency. In addition, in the process of application software development, process data such as input parameters and output results are recorded, so that the data in the subsequent data statistical analysis is authentic and reliable. Through the data analysis of the entire process, multi-dimensional (project, personnel, team, application, code) data energy efficiency analysis is met. Through energy efficiency data analysis, the improvement of R&D efficiency and process improvement are reversely promoted, and a virtuous cycle is continuously formed.
[0114] Figure 5 An exemplary system architecture 500 is shown to which the method or apparatus for application development according to the embodiment of the present invention can be applied.
[0115] like Figure 5 As shown, system architecture 500 may include terminal devices 501, 502, 503, a network 504 and a server 505. Network 504 is used to provide a medium for communication links between terminal devices 501, 502, 503 and server 505. Network 504 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.
[0116] Users can use terminal devices 501, 502, 503 to interact with server 505 through network 504 to receive or send messages, etc. Terminal devices 501, 502, 503 can be installed with various communication client applications, such as software development applications, software management applications, code management applications, etc. (only examples).
[0117] The terminal devices 501 , 502 , and 503 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.
[0118] The server 505 may be a server that provides various services, such as a background management server that provides support for websites browsed by users using terminal devices 501, 502, and 503 (for example only). The background management server may respond to the application development request and other data received, create a demand analysis task and generate a demand number, parse the demand analysis task to generate a demand analysis sub-process corresponding to the demand number, and perform demand analysis according to the demand analysis sub-process; respond to the code development instruction, establish an association relationship between the application identifier of the application and the demand number, generate a code development sub-process corresponding to the application identifier according to the result of the demand analysis, and perform code development according to the code development sub-process to obtain application code; respond to the code test instruction, create a code test task, establish an association relationship between the test task identifier and the application identifier, generate a code test sub-process corresponding to the test task identifier according to the code test task, test the application code according to the code test sub-process to complete application development and other processing, and feed back the processing result (such as application development result record - for example only) to the terminal device.
[0119] It should be noted that the application development method provided in the embodiment of the present invention is generally executed by the server 505 , and accordingly, the application development device is generally set in the server 505 .
[0120] It should be understood that Figure 5 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.
[0121] Reference below Figure 6 , which shows a schematic diagram of the structure of a computer system 600 of a terminal device or a server suitable for implementing an embodiment of the present invention. Figure 6 The terminal device or server shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.
[0122] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the system 600 are also stored. The CPU 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.
[0123] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage section 608 as needed.
[0124] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the central processing unit (CPU) 601, the above-mentioned functions defined in the system of the present invention are executed.
[0125] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more 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 invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.
[0126] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0127] The units or modules involved in the embodiments of the present invention may be implemented by software or hardware. The units or modules described may also be provided in a processor, for example, may be described as: a processor including a requirement analysis module, a code development module and a code testing module. Among them, the names of these units or modules do not constitute a limitation on the units or modules themselves in certain cases. For example, the code testing module may also be described as "a module for responding to a code testing instruction, creating a code testing task, and establishing an association between the test task identifier and the application identifier, generating a code testing sub-process corresponding to the test task identifier according to the code testing task, and testing the application code according to the code testing sub-process to complete application development".
[0128] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently and not be assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device includes: in response to the application development requirement analysis instruction, creating a requirement analysis task and generating a requirement number, parsing the requirement analysis task to generate a requirement analysis sub-process corresponding to the requirement number, and performing requirement analysis according to the requirement analysis sub-process; in response to the code development instruction, establishing an association relationship between the application identification of the application and the requirement number, and generating a code development sub-process corresponding to the application identification according to the result of the requirement analysis, and performing code development according to the code development sub-process to obtain application code; in response to the code test instruction, creating a code test task, and establishing an association relationship between the test task identification and the application identification, generating a code test sub-process corresponding to the test task identification according to the code test task, and testing the application code according to the code test sub-process to complete application development.
[0129] According to the technical solution of the embodiment of the present invention, by responding to the application development requirement analysis instruction, creating a requirement analysis task and generating a requirement number, parsing the requirement analysis task to generate a requirement analysis sub-process corresponding to the requirement number, and performing requirement analysis according to the requirement analysis sub-process; in response to the code development instruction, establishing an association relationship between the application identifier and the requirement number of the application, and generating a code development sub-process corresponding to the application identifier according to the result of the requirement analysis, performing code development according to the code development sub-process to obtain the application code; in response to the code testing instruction, creating a code testing task, and establishing an association relationship between the test task identifier and the application identifier, generating a code test task corresponding to the test task identifier according to the code testing task Sub-processes, according to the code testing sub-process, test the application code to complete the technical solution of application development. By dividing the entire application development process into the requirements analysis stage, the development stage and the code testing stage, and using different fields as key information for process management in each stage, and through these fields to associate the sub-processes corresponding to the requirements analysis stage, the development stage and the code testing stage to generate software development workflows, the online management of the entire process of application software development is realized, the process problem is solved, and the quality of project delivery is improved through process system constraints; the entire process management from the requirements analysis stage to the code testing stage is met, which can be widely used in the management of application software development and testing processes, and can also improve R&D efficiency. In addition, in the process of application software development, the process data such as input parameters and output results are recorded, so that the data in the subsequent data statistical analysis is authentic and reliable. Through the data analysis of the entire process, the multi-dimensional (project, personnel, team, application, code) data energy efficiency analysis is met. Through the energy efficiency data analysis, the R&D efficiency and process improvement are reversely promoted, and a virtuous cycle is continuously formed.
[0130] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.
Claims
1. A method for application development, characterized in that: include: In response to an application development requirement analysis instruction, create a requirement analysis task and generate a requirement number, parse the requirement analysis task to generate a requirement analysis sub-process corresponding to the requirement number, and perform requirement analysis according to the requirement analysis sub-process; In response to the code development instruction, an association relationship between the application identifier of the application and the requirement number is established, and a code development sub-process corresponding to the application identifier is generated according to the result of the requirement analysis, and code development is performed according to the code development sub-process to obtain application code; In response to a code testing instruction, a code testing task is created, and an association relationship between the test task identifier and the application identifier is established. A code testing sub-process corresponding to the test task identifier is generated according to the code testing task, and the application code is tested according to the code testing sub-process to complete application development.
2. The method according to claim 1, characterized in that The demand analysis sub-process includes: demand creation, demand review and demand acceptance; Perform demand analysis according to the demand analysis sub-process, including: In response to the requirement creation instruction, acquiring requirement information according to the requirement analysis task, and generating an application development flow chart according to the requirement information; In response to the requirement review instruction, reviewing the application development flowchart to generate a requirement review result; When the demand review result is passed, in response to the demand acceptance instruction, an acceptance form is generated according to the demand acceptance information.
3. The method according to claim 2, characterized in that After generating the application development flow chart according to the demand information, the method further includes: The application development flowchart is presented in a graphical manner.
4. The method according to claim 1, characterized in that: The code development sub-process includes: system design review, code submission, unit test coverage statistics, security compliance detection, dependency conflict detection, code static scanning, code review and code integration; Code development is performed according to the code development sub-process, including: In response to the system design review instruction, reviewing the system design document of the application to generate a system design review result; If the system design review result is passed, in response to a code submission instruction, generate code submission information and application code change information according to the submitted development code and the application identifier; In response to the unit test coverage statistics instruction, a code coverage report file and an application code are obtained according to the application identifier, and unit test coverage statistics information is obtained by combining the code coverage report file and the application code; In response to the security compliance detection instruction, performing vulnerability detection and privacy compliance scanning according to the application code branch to be detected and the application code, and generating a security compliance detection result; In response to the dependency conflict detection instruction, performing component dependency conflict detection according to the application code branch to be detected and the application code, and generating a dependency conflict detection result; In response to the code static scanning instruction, based on the application code branch to be detected and the application code, a predetermined code specification scan is performed based on the code quality management platform, and a code static scanning result is generated; In response to the code review instruction, perform a code review according to the application code branch to be reviewed and the application code, and generate a code review result; When the code review result is that the review is passed, in response to a code integration instruction, the submitted development code is merged into the application code branch to be tested to perform code integration.
5. The method according to claim 1, characterized in that: The code testing sub-process includes: creating test tasks, sending test reports, compiling and building, code scanning, smoke testing, test acceptance / rejection, creating test plans, test case review, UI automated testing, interface automated testing, functional test coverage / monitoring, sending test reports, sending online notifications, and sending online verification reports; Testing the application code according to the code testing sub-process includes: In response to the instruction to create a test task, create a test task according to the test requirement information, and generate test task information; In response to the instruction to send a test report, assembling the test requirement information and the test task information, and sending the assembled test report to relevant personnel; In response to the compiling and building instruction, the identification of the application to be tested is obtained according to the test task information, and the test environment deployment is completed according to the test requirement information and the identification of the application to be tested, and the progress of the compiling and building is displayed; In response to the code scanning instruction, a code coverage report file and an application code are obtained according to the test requirement information and the identification of the application to be tested, and unit test coverage statistics are obtained by combining the code coverage report file and the application code; In response to the smoke test instruction, performing a smoke test on the application to be tested according to the test requirement information, the identification of the application to be tested and the test case, and generating a smoke test result; In response to a test acceptance / rejection instruction, generating test acceptance information or test rejection information according to the smoke test result; In the case of test acceptance, in response to the instruction to create a test plan, a test plan is generated according to the test task information and the identification of the application to be tested, and execution results of functional test cases and automated test cases are counted; In response to the test case review instruction, perform a test case review according to the execution results of the functional test cases and automated test cases to be reviewed, and generate a test case review result; In response to the UI automation test instruction, perform UI automation test according to the test task information, the identification of the application to be tested and the UI automation test case, and count the execution results of the UI automation test case; In response to the interface automation test instruction, perform interface automation test according to the test task information, the application identifier to be tested and the interface automation test case, and count the execution results of the interface automation test case; In response to the functional test coverage / monitoring instruction, the application deployment server information is obtained according to the identification of the application to be tested, the coverage test is performed on the application to be tested deployed on the application deployment server according to the functional test case and the automated test case, and a coverage test result is generated; In response to the instruction to send a test report, a test report is generated according to the test requirement information, the identification of the application to be tested, the coverage test results of the functional test cases and the automated test cases, and is assembled according to a test report template and sent to relevant personnel; In response to the instruction to send an online notification, according to the test requirement information, the identification of the application to be tested, and the inspection result before the application is launched, an online notification is generated according to the online notification template, and sent to relevant personnel; In response to the instruction to send an online verification report, an online verification report is generated and assembled according to an online verification report template based on the test requirement information, the identification of the application to be tested, and the inspection results after application acceptance, and sent to relevant personnel.
6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: In the process of application development, the input parameters and output results included in each sub-process are associated and stored with each node of the sub-process; And, relevant information of each node is displayed by operating each node.
7. The method according to claim 6, characterized in that The method further comprises: At the nodes of demand acceptance, test creation, test report sending, test report sending, online notification sending and online verification report sending, notification information is generated based on the output results of the node and sent to relevant personnel.
8. A device for application development, characterized in that: include: A requirement analysis module, for responding to an application development requirement analysis instruction, creating a requirement analysis task and generating a requirement number, parsing the requirement analysis task to generate a requirement analysis sub-process corresponding to the requirement number, and performing requirement analysis according to the requirement analysis sub-process; A code development module, configured to establish an association relationship between the application identifier of the application and the requirement number in response to a code development instruction, generate a code development sub-process corresponding to the application identifier according to a result of the requirement analysis, and perform code development according to the code development sub-process to obtain application code; A code testing module is used to respond to a code testing instruction, create a code testing task, and establish an association relationship between the test task identifier and the application identifier, generate a code testing sub-process corresponding to the test task identifier according to the code testing task, and test the application code according to the code testing sub-process to complete application development.
9. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 7.
10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.
Citation Information
Cited By
Development method and development device of process robot and computer program product
CN119718295A
Railway application software research and development process management method
CN120045164A
A railway application software development process management method
CN120045164B
