CN115660595A - Software development document automatic checking method based on RPA management platform - Google Patents
Software development document automatic checking method based on RPA management platform Download PDFInfo
- Publication number
- CN115660595A CN115660595A CN202211361289.0A CN202211361289A CN115660595A CN 115660595 A CN115660595 A CN 115660595A CN 202211361289 A CN202211361289 A CN 202211361289A CN 115660595 A CN115660595 A CN 115660595A
- Authority
- CN
- China
- Prior art keywords
- version
- checking
- mailbox
- conformity
- basic information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention relates to a software development document automatic checking method based on an RPA management platform, which comprises the following steps: 1) Inquiring the version, acquiring basic information, checking whether requirements associated with the version and the PAT change order accord with a check rule, summarizing the basic information and the non-conformity reason into a non-conformity item tracking table, and sending the non-conformity item tracking table to a mailbox; 2) Scanning a mailbox and downloading a non-conforming item tracking table, acquiring a version required to be checked by each system, logging in and skipping an SVN path corresponding to each system, according to a comparison rule, judging whether a file under the corresponding path conforms to a check rule, recording the reason of the non-conforming item to the non-conforming item tracking table, and sending a table to the mailbox; 3) Scanning the mailbox, downloading the non-conforming item tracking list, reading the inspection result, generating an inspection result file list, and sending the non-conforming item tracking list and the inspection result file list to a service person for checking through the mail. Compared with the prior art, the method has the advantages of no need of butting a database, convenience in viewing results, high efficiency and the like.
Description
Technical Field
The invention relates to the field of software development project quality management, in particular to an automatic software development document checking method based on an RPA management platform.
Background
According to the regulations of the quality management of the software development project of the credit card center, all project managers of the credit card center need to fill in the version information of the software development project on a software development version platform and upload relevant compliance documents, and the compliance documents need to follow the requirements of a uniform editing format.
A quality assurance team performs quality inspection on version information and compliance documents of a software development project on a software development version platform specially through a manual means. In the examination process, the quality assurance team refers to the examination items and the examination standards in the quality examination sheet, examines the version information of each project on the software development version platform and each document deliverable, and records the non-conforming item tracking table of the project if the non-conforming item is detected.
At present, quality audit processes are all manual operations, mainly manually auditing version information of a software development project on a software development version platform and documents related to the project, such as WORD, EXCEL, PDF and the like according to fixed rules, but with the increasing number of the projects, the manual inspection and tracking workload is large, the consumed time is long, incomplete, the inspection result has certain hysteresis, and the accuracy of manual inspection is not high.
Robot Process RPA (Robotic Process Automation), referred to as a Process robot for short. The automation of the process can be realized through a mode of simulating manual operation. Chinese patent CN114782015A discloses an inspection method and system for project document quality examination based on RPA, the inspection method comprising: identifying a project manager, submitting documents to a management system according to project management requirements and requirements of different stages, and generating an audit task; saving the document to a public database, the public database being accessible by both the robot and the management system; the robot monitors the task queue and obtains the project information of the audit task; and calling a document to be checked according to the project information, and checking according to rules to obtain a checking result.
However, the method needs to be connected with a database in a butt joint mode, is complex, only checks whether the project document is wrong or not, and has a relatively simple check result.
Therefore, how to implement a software project quality inspection method which is simple in method, comprehensive in inspection result and capable of improving inspection efficiency and accuracy becomes a technical problem to be solved.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provide a project audit scene checking method based on an RPA management platform.
The purpose of the invention can be realized by the following technical scheme:
the software development document automatic checking method based on the RPA management platform comprises the following steps:
1) The method comprises the steps that a process robot logs in a version management page of a software development version platform under the PAT environment, inquires all versions in specified time, obtains all basic information in a version number, checks whether all requirements associated with the versions and a PAT change order accord with a check rule, and sends basic information and a non-conformity reason assembly non-conformity item tracking table to a mailbox of the UAT environment if the basic information and the non-conformity reason assembly do not accord with the check rule; if yes, only filling the basic information into the non-conforming item tracking table and sending the basic information to the mailbox of the UAT environment;
2) The process robot scans the mailbox in the UAT environment and downloads the non-conforming item tracking table, acquires the version required to be checked of each system, logs in the SVN, skips the SVN path corresponding to each system, confirms whether the file under the path corresponding to the version required to be checked conforms to the check rule according to the comparison rule, records the reason of the non-conforming item to the non-conforming item tracking table, and sends the table to the mailbox in the PAT environment;
3) The process robot scans the mailbox in the PAT environment, downloads the non-conforming item tracking table, reads all the inspection results of the table, generates an inspection result file table, and sends the non-conforming item tracking table and the inspection result file table to business personnel for checking and confirmation through mails.
Further, all versions of the specified time are all versions within 30 days before the current time.
Further, all the basic information comprises software names, version numbers, estimated production time, associated requirement sheet numbers and item classifications.
Further, all the basic information is acquired through a crawler technology.
Further, the checking of all requirements associated with the version includes whether a requirement exists, whether the requirement is uploaded, and whether the requirement is confirmed.
Further, the PAT change list associated with the checked version comprises the existence of a change number, security document check and performance document check.
Further, the comparison rule includes whether the project level table exists, whether the project schedule exists, whether the single number of the project level table is consistent with that of the production summary table, and whether each requirement specification corresponds to a system design specification.
Further, the generating of the inspection result file table specifically includes: counting the total number of the inspection items and the total number of the non-conformity items of each phase, calculating the non-conformity rate of each phase, generating a data histogram according to the data, filling the data and the data histogram of each phase into a counting table page of an inspection result file table, and writing the data of all the non-conformity items into an inspection detail table sheet page.
Another aspect of the present invention provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and wherein the processor implements any of the methods described above when executing the program.
The invention also provides a computer-readable storage medium, on which a computer program is stored, characterized in that the program, when executed by a processor, implements the method of any of the above.
Compared with the prior art, the invention has the following beneficial effects:
1. according to the invention, data are directly gathered at the local client, a database does not need to be butted, the method is simple and easy to use, and a data histogram form is generated, so that service personnel can conveniently and visually watch the inspection result; the invention not only checks whether the document is wrong, but also acquires and checks the basic information of the website, and compares whether the document information and the website information are wrong, so that the checking is more comprehensive and specific; the website information is acquired through a crawler technology, and the method is quicker.
2. According to the invention, the RPA process robot is used for inspecting the project, so that a large amount of manpower is saved, the inspection efficiency is improved, and the inspection cost is reduced.
3. Compared with manual detection, the flow robot detection has comprehensiveness, accuracy and timeliness. The comprehensiveness: manual inspection inspects one or two hundred major files at a maximum a day, and robots can complete thousands of document inspections in a matter of hours. The accuracy is as follows: the manual inspection of the document easily causes inaccurate inspection results, and the robot can accurately inspect the results. And (3) timeliness: the manual completion of the document inspection at one time takes a lot of time (in terms of days) and the inspection results cannot be summarized quickly, so that the document defects cannot be rectified in time, and the process robot can complete the document inspection within a few hours and summarize the result files so as to rectify the document defects in time.
Drawings
FIG. 1 is a schematic overall flow diagram of the present invention;
FIG. 2 is a schematic flow chart of the present invention.
Detailed Description
The invention is described in detail below with reference to the figures and specific embodiments. The present embodiment is implemented on the premise of the technical solution of the present invention, and a detailed implementation manner and a specific operation process are given, but the scope of the present invention is not limited to the following embodiments.
Examples
As shown in fig. 1 and 2, the method for automatically checking software development documents based on an RPA management platform comprises the following steps:
1) The process robot logs in a version management page of a software development version platform in a PAT environment (formal production environment), inquires all versions in 30 days before the current time, acquires all basic information (software names, version numbers, estimated production time, associated requirement sheet numbers, item classification and the like) in the version numbers, checks whether all requirements associated with the versions meet check rules (whether the requirements exist, whether rules need to be uploaded, whether the rules need to be confirmed and the like), checks whether PAT change sheets associated with the versions meet the check rules (whether change numbers exist, safety document check, performance document check and the like), assembles the basic information and the reasons which do not meet a non-conforming item tracking table, and sends the non-conforming item tracking table to a mailbox in the UAT environment.
2) The process robot scans the mailbox in the UAT environment (test environment) and downloads the non-conforming item tracking table, acquires the version required to be checked of each system, logs in the SVN, jumps to the SVN path corresponding to each system, confirms whether the file under the path corresponding to the version required to be checked accords with the check rule according to the comparison rule (whether the project grade table, the project schedule table and the like exist, whether the single number of the project grade table is consistent with the single number of the production summary table, whether each requirement specification correspondingly exists the system design specification and the like), records the reason of the non-conforming item to the non-conforming item tracking table, and sends the table to the mailbox in the PAT environment.
3) The process robot scans a mailbox in a PAT environment (formal production environment), downloads a non-conforming item tracking table, reads all inspection results of a table, counts the total number of inspection items of each phase and the total number of non-conforming items, calculates the non-conforming rate of each phase, generates a data histogram according to data, fills the data and the data histogram of each phase into a statistical table page of an inspection result file table, writes the data of all the non-conforming items to an inspection detail table sheet page, and finally sends the non-conforming item tracking table and the inspection result file table to a service worker for checking and confirmation through mails.
The inspection method inspects the items through the RPA flow robot, thereby saving a large amount of manpower, improving the inspection efficiency and reducing the inspection cost; and a database does not need to be docked, and the data is directly summarized at the local client, so that the method is simple and easy to use. The method also facilitates business personnel to visually watch the inspection result by generating a data histogram; the method not only checks whether the document is wrong, but also acquires and checks the basic information of the website, and compares whether the document information and the website information are wrong, so that the checking is more comprehensive and specific; and the website information is acquired through a crawler technology, so that the method is more rapid.
Compared with manual inspection, the inspection method has comprehensiveness, accuracy and timeliness. The concrete expression is as follows:
the comprehensiveness: manual inspection inspects one or two hundred major files at a maximum a day, and robots can complete thousands of document inspections in a matter of hours.
The accuracy is as follows: the manual document inspection easily causes inaccurate inspection results, and the robot can accurately inspect the results.
And (3) timeliness: the manual completion of the document inspection at one time takes a lot of time (in days) and the inspection results cannot be summarized quickly, so that the document defects cannot be rectified in time, and the process robot can complete the document inspection within several hours and summarize the result files so as to rectify the document defects in time.
The foregoing detailed description of the preferred embodiments of the invention has been presented. It should be understood that numerous modifications and variations could be devised by those skilled in the art in light of the present teachings without departing from the inventive concepts. Therefore, the technical solutions that can be obtained by a person skilled in the art through logical analysis, reasoning or limited experiments based on the prior art according to the concepts of the present invention should be within the scope of protection determined by the claims.
Claims (10)
1. A software development document automatic checking method based on RPA management platform is characterized in that the checking method comprises:
1) The method comprises the steps that a process robot logs in a version management page of a software development version platform under the PAT environment, inquires all versions in specified time, obtains all basic information in a version number, checks whether all requirements associated with the versions and a PAT change order accord with a check rule, and sends basic information and a non-conformity reason convergence item non-conformity tracking table to a mailbox in the UAT environment if the basic information and the non-conformity reason convergence item do not accord with the check rule; if yes, only filling the basic information into the non-conforming item tracking table and sending the basic information to the mailbox of the UAT environment;
2) The process robot scans the mailbox in the UAT environment and downloads the non-conforming item tracking table, acquires the version required to be checked by each system, logs in the SVN (version control system), skips the SVN path corresponding to each system, confirms whether the file under the path corresponding to the version required to be checked conforms to the check rule according to the comparison rule, records the reason of the non-conforming item to the non-conforming item tracking table, and sends the table to the mailbox in the PAT environment;
3) The process robot scans the mailbox in the PAT environment, downloads the non-conforming item tracking table, reads all the inspection results of the table, generates an inspection result file table, and sends the non-conforming item tracking table and the inspection result file table to business personnel for checking and confirmation through mails.
2. The method according to claim 1, wherein the all versions at the specified time are all versions within 30 days before the current time.
3. The method according to claim 1, wherein the basic information includes software name, version number, estimated production time, associated order number and item classification.
4. The RPA management platform-based method for automatically checking software development documents according to claim 3, wherein all the basic information is obtained by a crawler technology.
5. The method according to claim 1, wherein all requirements associated with the checked version include whether a requirement exists, whether a requirement is uploaded, and whether a requirement is confirmed.
6. The RPA management platform-based method of automatically checking software development documentation according to claim 1, wherein the PAT change tickets checking for version association include the presence of a change number, security documentation checking, and performance documentation checking.
7. The method according to claim 1, wherein the rules include whether a project level table exists, whether a project schedule table exists, whether a single number of the project level table is consistent with a single number of a production summary table, and whether each requirement specification is associated with a system design specification.
8. The method for automatically checking software development documents based on an RPA management platform according to claim 1, wherein the generating of the check result file table specifically comprises: counting the total number of the inspection items and the total number of the non-conformity items of each phase, calculating the non-conformity rate of each phase, generating a data histogram according to the data, filling the data and the data histogram of each phase into a counting table page of an inspection result file table, and writing the data of all the non-conformity items into an inspection detail table sheet page.
9. An electronic device comprising a memory and a processor, the memory having stored thereon a computer program, wherein the processor, when executing the program, implements the method of any of claims 1-8.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211361289.0A CN115660595A (en) | 2022-11-02 | 2022-11-02 | Software development document automatic checking method based on RPA management platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211361289.0A CN115660595A (en) | 2022-11-02 | 2022-11-02 | Software development document automatic checking method based on RPA management platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115660595A true CN115660595A (en) | 2023-01-31 |
Family
ID=84995011
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211361289.0A Pending CN115660595A (en) | 2022-11-02 | 2022-11-02 | Software development document automatic checking method based on RPA management platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115660595A (en) |
-
2022
- 2022-11-02 CN CN202211361289.0A patent/CN115660595A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103678109A (en) | Dump document analysis method, device and system | |
| CN115187125A (en) | Laboratory data management method, device, equipment and medium | |
| CN115809653A (en) | Intelligent contract auditing method and system | |
| CN111709464B (en) | System and screening method based on data dictionary configuration and seal image recognition technology | |
| CN117522612A (en) | Communication expense reimbursement method, equipment and medium based on RPA | |
| CN115660595A (en) | Software development document automatic checking method based on RPA management platform | |
| CN116629770A (en) | Supplier data auditing method and system based on graphical identification technology | |
| CN110991150A (en) | Data format conversion method and device and account reporting system | |
| CN116150199A (en) | Data checking method and system based on RPA robot | |
| CN111640030B (en) | Processing device, equipment and storage medium for insurance claim failure data | |
| KR102416998B1 (en) | Appatus for automatically collecting and classification tax related documents and method thereof | |
| Salmen | Employing RPA and AI to automize order entry process with ındividual and small-sized structures: a SME business case study | |
| US20100104143A1 (en) | Method and System for Processing Operator Log Documents | |
| CN106445898B (en) | Method and system for processing postal envelope data | |
| CN110543424B (en) | Test method and device for electronic tax platform | |
| CN113327023A (en) | Traversal test method and device, electronic equipment and computer readable storage medium | |
| CN112766892A (en) | Method and device for combining fund ratio of RPA and AI and electronic equipment | |
| CN113051165A (en) | Method, device, monitoring server and medium for processing test order | |
| CN112307106A (en) | Data preprocessing method and device | |
| CN108256805B (en) | Method and device for realizing electronic pair order of oil import business | |
| CN115983956B (en) | Bid file detection method and system | |
| US20220391922A1 (en) | Automated docketing checker | |
| CN113919646A (en) | Invoice automatic prefabricating and posting method and device, storage medium and electronic equipment | |
| CN114372776A (en) | Invoice authenticity query process automation method and system | |
| CN117670377A (en) | Web-side invoice identification and verification based method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |