CN112860313A - Document and version checking method and device based on requirement items - Google Patents
Document and version checking method and device based on requirement items Download PDFInfo
- Publication number
- CN112860313A CN112860313A CN202110352517.7A CN202110352517A CN112860313A CN 112860313 A CN112860313 A CN 112860313A CN 202110352517 A CN202110352517 A CN 202110352517A CN 112860313 A CN112860313 A CN 112860313A
- Authority
- CN
- China
- Prior art keywords
- submitted
- version
- program list
- program
- requirement
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 230000008859 change Effects 0.000 claims abstract description 44
- 238000004519 manufacturing process Methods 0.000 claims abstract description 37
- 238000012360 testing method Methods 0.000 claims abstract description 30
- 238000007726 management method Methods 0.000 claims abstract description 16
- 238000004590 computer program Methods 0.000 claims description 18
- 238000012790 confirmation Methods 0.000 claims description 8
- 238000012986 modification Methods 0.000 claims description 7
- 230000004048 modification Effects 0.000 claims description 7
- 238000012217 deletion Methods 0.000 claims description 4
- 230000037430 deletion Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000010200 validation analysis Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012954 risk control Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a document and version checking method and device based on a requirement item, and relates to the technical field of financial management, wherein the method comprises the following steps: when the required item is changed, identifying the change category, and determining a program list to be submitted according to the change category; comparing the submitted program list with the program list to be submitted, and automatically identifying the delivery condition of the required item; and automatically confirming the version crossing condition according to the demand items and the resubmission program lists at different production time points. The method can automatically confirm the version issuing condition of the relevant content of the required item during project delivery, identify the risk of the project in advance and control the version quality of the program; and acquiring a program list with cross test time and different production time before the edition setting, and confirming the program version cross condition in advance, so that the program version risk can be controlled more effectively.
Description
Technical Field
The invention relates to the technical field of financial management, in particular to a document and version checking method and device based on a requirement item.
Background
This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
At present, with the division of demand items, the iterative project is more and more popular in risk management and control according to the demand items, but the following problems are encountered in the project risk management and control at present:
1. iterative projects often update itemized documents due to version plan change and test range change, but the existing system cannot prompt addition and deletion of required itemized documents to change information, and project managers need to enter the system to check contents one by one to confirm ranges, so that the situations that project contents are not confirmed timely and project division is not updated timely often occur.
2. At present, after the iterative project version is delivered, partial required items can not be tested due to bottleneck problems, the version delivery condition can only be confirmed by problems, mails and other modes, and the delivery list content can not be confirmed temporarily by a mode of automatically identifying the version delivery condition.
3. At present, the delivery time and the production time of agile iterative project versions are more and more, whether the modified contents are crossed by versions or not is often confirmed to a development center in a formal mail mode, and the condition of the crossed versions cannot be compared in a system automation mode before the versions are installed.
In summary, there is no method for satisfying the requirement item change automatic prompt and the version crossing condition automatic identification in the current system, and how to provide a new scheme, solving the above technical problems is a technical problem to be solved in the field.
Disclosure of Invention
The embodiment of the invention provides a document and version checking method based on a requirement item, which is used for solving the problems that an iterative project cannot automatically prompt the document updating condition due to the change of a test range and cannot automatically confirm the version crossing condition after the project is published, and comprises the following steps:
when the required item is changed, identifying the change category, and determining a program list to be submitted according to the change category;
comparing the submitted program list with the program list to be submitted, and automatically identifying the delivery condition of the required item;
and automatically confirming the version crossing condition according to the demand items and the resubmission program lists at different production time points.
The embodiment of the invention also provides a document and version checking device based on the requirement items, which is used for solving the problems that the updating condition of the document cannot be automatically prompted due to the change of the test range of the iterative project and the version crossing condition cannot be automatically confirmed after the version sending of the project, and comprises the following steps:
the requirement item document management module is used for identifying a change type when a requirement item is changed and determining a program list to be submitted according to the change type;
the version delivery condition identification module is used for comparing the submitted program list with the program list to be submitted and automatically identifying the delivery condition of the required item;
and the version crossing condition confirmation module is used for automatically confirming the version crossing condition according to the demand items and the resubmission program lists at different production time points.
The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the document and version checking method based on the requirement items when executing the computer program.
Embodiments of the present invention further provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the document and version checking method based on requirement entries.
In the embodiment of the invention, compared with the technical scheme that the temporary system in the prior art can meet the requirements of automatic prompt of the change of the requirement items and automatic identification of the version crossing condition, when the requirement items are changed, the change types are identified, and the program list to be submitted is determined according to the change types; comparing the submitted program list with the program list to be submitted, and automatically identifying the delivery condition of the required item; according to the requirement items and the submitted program lists at different production time points, the version crossing condition is automatically confirmed, the document updating condition of the iteration project can be automatically prompted due to the change of the test range, and the version crossing condition of the iteration project can be automatically confirmed after the project is published, so that the project risk can be identified in advance, and the program version quality and the management and control risk can be controlled.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts. In the drawings:
FIG. 1 is a flowchart of a document and version checking method based on requirement items according to an embodiment of the present invention;
FIG. 2 is a flowchart of a document and version checking method based on requirement items according to an embodiment of the present invention (II);
FIG. 3 is a flowchart of a document and version checking method based on requirement items according to an embodiment of the present invention (III);
FIG. 4 is a flowchart of a document and version checking method based on requirement items according to an embodiment of the present Invention (IV);
FIG. 5 is a block diagram of a document and version checking apparatus based on requirement items according to an embodiment of the present invention;
FIG. 6 is a diagram showing an internal structure of the requirement itemized document management module 1 in the embodiment of the present invention;
fig. 7 is a schematic diagram of the internal structure of the version delivery condition identification module 2 in the embodiment of the present invention;
fig. 8 is a schematic diagram of the internal structure of the version crossing condition validation module 3 according to the embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention.
In order to solve the problems that the update condition of a document cannot be automatically prompted due to the change of a test range of an iterative project and the condition of version crossing cannot be automatically confirmed after the project is published, the invention provides a document and version checking method and device based on a requirement item.
FIG. 1 is a flowchart of a document and version checking method based on requirement items according to an embodiment of the present invention, as shown in FIG. 1, the method includes:
step 101: when the required item is changed, identifying the change category, and determining a program list to be submitted according to the change category;
step 102: comparing the submitted program list with the program list to be submitted, and automatically identifying the delivery condition of the required item;
step 103: and automatically confirming the version crossing condition according to the demand items and the resubmission program lists at different production time points.
In this embodiment of the present invention, as shown in fig. 2, when a requirement entry is changed in step 101, identifying a change category, and determining a program list to be submitted according to the change category includes:
step 1011: when the requirement item is changed, identifying whether the change category is a new requirement item, a deletion requirement item or a modification requirement item;
step 1012: and determining the program list to be submitted as a new program list to be submitted, deleting the program list to be submitted or modifying the program list to be submitted according to the change category.
As shown in fig. 2, the method further comprises:
step 1013: and after the change type is identified, calling a mail notification system to automatically notify the related personnel of the project, wherein the notification mail comprises adding a program list to be submitted, deleting the program list to be submitted or modifying the program list to be submitted.
Specifically, the list of submitters includes A, B, C, D, and if the requirement entry is newly added, the list of newly added submitters may include A, B, C, D, E.
The list of submitters includes A, B, C, D, and if the requirement entry is deleted, the list of submitters may include A, B, C.
The submitter list includes A, B, C, D. if the requirement entry is modified, the new submitter list may include A, B, C, E.
In the embodiment of the present invention, as shown in fig. 3, the step 102 of comparing the submitted program list with the program list to be submitted and automatically identifying the delivery condition of the requirement item includes:
step 1021: acquiring the corresponding relation between the requirement item and the program list to be submitted;
step 1022: acquiring a program list of a traditional environment and a program list of a paas environment as submitted program lists;
step 1023: comparing the submitted program list with the program list to be submitted, and identifying the non-delivery program list and the multi-delivery program list.
Specifically, if A, B, C, D, E is included in the committed program list and A, B, C, D is included in the due program list, then E belongs to the undelivered program list;
if A, B, C, D, E is included in the committed program list and A, B, C, D, E, F is included in the due program list, then F belongs to the multiple delivery program list.
As shown in fig. 3, the method further comprises:
step 1024: when the non-delivery program list exists, the output version is not delivered on time; when there is a multi-delivery program manifest (i.e., delivering content other than the program manifest that should be delivered), the output version carries with it the risk.
In the embodiment of the present invention, as shown in fig. 4, step 103 automatically confirms the version crossing condition according to the requirement entries and the resubmission program lists at different production time points, including:
step 1031: identifying whether the version test time of different production time points is crossed or not according to the production time and the test environment, wherein the crossing of the version test time is defined as the condition that the test environment is the same set, the production time is different, and the delivery time of the version with the later production time is earlier than that of the other production time;
step 1032: and acquiring the program lists to be submitted in the versions with the version testing time being crossed, comparing the program lists to be submitted issued at 2 different production time points, and if the program lists to be submitted have the same time points, determining that the program lists to be submitted have the cross.
As shown in fig. 4, the method further includes:
step 1033: and when the program list to be submitted has cross, calling a mail notification system to notify the related personnel of the project.
The embodiment of the invention also provides a document and version checking device based on the requirement items, which is described in the following embodiment. Because the principle of the device for solving the problems is similar to the document and version checking method based on the requirement items, the implementation of the device can refer to the implementation of the document and version checking method based on the requirement items, and repeated parts are not described again.
Fig. 5 is a block diagram of a document and version checking device based on requirement entries according to an embodiment of the present invention, and as shown in fig. 5, the document and version checking device based on requirement entries includes: three modules are as follows: a requirement item document management module 1, a version delivery condition identification module 2 and a version cross condition confirmation module 3, wherein:
the requirement item document management module 1 is used for identifying change types when requirement items are changed and determining a program list to be submitted according to the change types;
the version delivery condition identification module 2 is used for comparing the submitted program list with the program list to be submitted and automatically identifying the delivery condition of the required item;
and the version crossing condition confirming module 3 is used for automatically confirming the version crossing condition according to the demand items and the corresponding submitted program lists at different production time points.
Specifically, the requirement itemized document management module 1: the method mainly realizes that when the required items are changed such as increased, modified and deleted, related personnel of the items are automatically notified, and a program list is prompted to be submitted;
version delivery condition identification module 2: the method mainly realizes that the delivery condition of the required item is automatically identified by comparing the submitted program list with the program list to be submitted;
version cross situation confirmation module 3: the method mainly realizes automatic confirmation of the version crossing condition according to the requirement items at different production time points and the program list to be delivered.
In an embodiment of the present invention, the requirement itemized document management module is specifically configured to:
when the requirement item is changed, identifying whether the change category is a new requirement item, a deletion requirement item or a modification requirement item;
and determining the program list to be submitted as a new program list to be submitted, deleting the program list to be submitted or modifying the program list to be submitted according to the change category.
The requirement itemized document management module is further configured to:
and after the change type is identified, calling a mail notification system to automatically notify the related personnel of the project, wherein the notification mail comprises adding a program list to be submitted, deleting the program list to be submitted or modifying the program list to be submitted.
FIG. 6 is a schematic diagram of the internal structure of the requirement itemized document management module 1, in which:
requirement item change identification means 11: when the requirement item changes, identifying whether the requirement item is newly added, deleted or modified;
program list change unit 12 to be submitted: adding, deleting or modifying a program list to be submitted according to the result of the requirement item change identification unit 11;
the requirement item change reminding unit 13: when the required item or the program list to be submitted is changed, a mail notification system is called to notify related personnel and remind related change details.
In the embodiment of the present invention, the version delivery condition identifying module is specifically configured to:
acquiring the corresponding relation between the requirement item and the program list to be submitted;
acquiring a program list of a traditional environment and a program list of a paas environment as submitted program lists;
comparing the submitted program list with the program list to be submitted, and identifying the non-delivery program list and the multi-delivery program list.
The version delivery condition identifying module is further configured to:
when the non-delivery program list exists, the output version is not delivered on time; when there is a multi-delivery program manifest, the output version carries with it the risk.
Fig. 7 is a schematic diagram of the internal structure of the delivery situation recognition module 2, in which:
the submitter list acquisition unit 21: acquiring a corresponding relation between a requirement item and a program list to be submitted from a development center requirement management platform, and storing the corresponding relation in a database; the corresponding relation between the requirement item and the program list to be submitted can acquire the program list to be submitted, deleted or modified when the requirement item changes, and provide a basis for identifying the undelivered version risk and the crossed versions later;
submitted program list acquisition unit 22: acquiring a program list of a traditional environment from a vaim system and storing the program list in a database, and acquiring a program list of a paas environment from a component package and storing the program list in the database; the vaim system is a system used for deploying programs on a non-paas cloud server; the paas environment refers to a system for deploying programs on a paas cloud server;
identifying an undelivered program list and a multi-delivery program list by comparing the results of the corresponding submitted program list acquisition unit 21 and the submitted program list acquisition unit 22;
the delivery situation recognition unit 23: identifying an undelivered program list and a multi-delivery program list by comparing the results of the corresponding submitted program list acquisition unit 21 and the submitted program list acquisition unit 22;
risk identification unit 24: when the non-delivery program list exists, the output version is not delivered on time; when there is a multi-delivery program manifest, the output version carries with it the risk.
In the embodiment of the present invention, the version crossing condition confirmation module is specifically configured to:
identifying whether the version test time of different production time points is crossed or not according to the production time and the test environment, wherein the crossing of the version test time is defined as the condition that the test environment is the same set, the production time is different, and the delivery time of the version with the later production time is earlier than that of the other production time;
and acquiring the program lists to be submitted in the versions with the version testing time being crossed, comparing the program lists to be submitted issued at 2 different production time points, and if the program lists to be submitted have the same time points, determining that the program lists to be submitted have the cross.
The version crossing condition validation module is further configured to:
and when the program list to be submitted has cross, calling a mail notification system to notify the related personnel of the project.
Fig. 8 is a schematic diagram of the internal structure of the version crossing condition confirmation module 3, in which:
test time cross recognition unit 31: identifying whether versions at different production time are crossed according to the production time and the test environment, wherein the crossed test time is defined as the condition that the test environment is the same set, the production time is different, and the delivery time of the version at the later production time is earlier than that of the other production time;
program list intersection recognizing unit 32: acquiring and comparing program lists to be submitted in versions with crossed test time, and if the program lists to be submitted are the same, determining that the program lists are crossed;
version cross alert unit 33: and when the program lists are crossed, calling a mail system to remind a project principal of making relevant countermeasures.
The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the document and version checking method based on the requirement items when executing the computer program.
Embodiments of the present invention further provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the document and version checking method based on requirement entries.
In the embodiment of the invention, in order to solve the problems that the updating condition of a document cannot be automatically prompted due to the change of a test range of an iterative project and the version crossing condition cannot be automatically confirmed after the project is published, the invention provides a document and version checking method and device based on a requirement item. The method for identifying requirement entry document management, identifying version delivery condition and confirming version cross condition solves the problem of risk control of iterative projects, and has the following advantages:
1. the document and version checking system for the required items can automatically acquire the added and deleted information of the item-based document, and the project responsible person and the project members can receive information such as the added and deleted prompt of the required items, specific modification points, specific modification time and the like through the system in a mail, instant communication system and other modes, so that the project responsible person can conveniently recognize the test requirement in advance, know the project modification points and avoid test omission.
2. By automatically identifying the version delivery condition, the version sending condition of the content related to the required item can be automatically confirmed during delivery of the project, and the risk of the project is identified in advance, so that the purpose of controlling the version quality is achieved, and the application risk of a system running a corresponding program version is reduced.
3. By the method for automatically confirming the version intersection, the program list with intersection in testing time and different commissioning time can be obtained before the edition is installed, the version intersection condition is confirmed in advance, the version risk can be more effectively controlled, and the application risk of a system running the corresponding program version is further reduced.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. A document and version checking method based on requirement items is characterized by comprising the following steps:
when the required item is changed, identifying the change category, and determining a program list to be submitted according to the change category;
comparing the submitted program list with the program list to be submitted, and automatically identifying the delivery condition of the required item;
and automatically confirming the version crossing condition according to the demand items and the resubmission program lists at different production time points.
2. The method for checking documents and versions based on requirement items according to claim 1, wherein when a requirement item is changed, a change category is identified, and a program list to be submitted is determined according to the change category, comprising:
when the requirement item is changed, identifying whether the change category is a new requirement item, a deletion requirement item or a modification requirement item;
and determining the program list to be submitted as a new program list to be submitted, deleting the program list to be submitted or modifying the program list to be submitted according to the change category.
3. The document and version checking method based on requirement entries according to claim 1, further comprising:
and after the change type is identified, calling a mail notification system to automatically notify the related personnel of the project, wherein the notification mail comprises a new program list to be submitted, a deleted program list to be submitted and a modified program list to be submitted.
4. The method for checking documents and versions based on requirement items according to claim 1, wherein comparing the submitted program list with the program list to be submitted, automatically identifying the delivery condition of the requirement items comprises:
acquiring the corresponding relation between the requirement item and the program list to be submitted;
acquiring a program list of a traditional environment and a program list of a paas environment as submitted program lists;
comparing the submitted program list with the program list to be submitted, and identifying the non-delivery program list and the multi-delivery program list.
5. The document and version checking method based on requirement entries according to claim 4, further comprising:
when the non-delivery program list exists, the output version is not delivered on time; when there is a multi-delivery program manifest, the output version carries with it the risk.
6. The method for checking documents and versions based on requirement items according to claim 1, wherein the automatic confirmation of the version crossing condition according to the requirement items and the list of the resubmissors at different production time points comprises:
identifying whether the version test time of different production time points is crossed or not according to the production time and the test environment, wherein the crossing of the version test time is defined as the condition that the test environment is the same set, the production time is different, and the delivery time of the version with the later production time is earlier than that of the other production time;
and acquiring the program lists to be submitted in the versions with the version testing time being crossed, comparing the program lists to be submitted issued at 2 different production time points, and if the program lists to be submitted have the same time points, determining that the program lists to be submitted have the cross.
7. The document and version checking method based on requirement entries according to claim 6, further comprising:
and when the program list to be submitted has cross, calling a mail notification system to notify the related personnel of the project.
8. A document and version checking apparatus based on requirement items, comprising:
the requirement item document management module is used for identifying a change type when a requirement item is changed and determining a program list to be submitted according to the change type;
the version delivery condition identification module is used for comparing the submitted program list with the program list to be submitted and automatically identifying the delivery condition of the required item;
and the version crossing condition confirmation module is used for automatically confirming the version crossing condition according to the demand items and the resubmission program lists at different production time points.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the document and version checking method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method for document and version checking based on requirement entries according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110352517.7A CN112860313B (en) | 2021-03-31 | 2021-03-31 | Method and device for checking documents and versions based on requirement items |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110352517.7A CN112860313B (en) | 2021-03-31 | 2021-03-31 | Method and device for checking documents and versions based on requirement items |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112860313A true CN112860313A (en) | 2021-05-28 |
| CN112860313B CN112860313B (en) | 2024-01-30 |
Family
ID=75992025
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110352517.7A Active CN112860313B (en) | 2021-03-31 | 2021-03-31 | Method and device for checking documents and versions based on requirement items |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112860313B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113485742A (en) * | 2021-07-28 | 2021-10-08 | 中国工商银行股份有限公司 | Host application version registration method and device |
| CN113553259A (en) * | 2021-07-20 | 2021-10-26 | 中国工商银行股份有限公司 | Program list generation method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106327152A (en) * | 2016-08-11 | 2017-01-11 | 宁波亦道信息科技有限公司 | Integrated iteration software development process control system and method |
| CN108089843A (en) * | 2018-01-18 | 2018-05-29 | 福建省农村信用社联合社 | A kind of intelligentized banking establishments grade requirement management systems |
| CN108563512A (en) * | 2018-04-02 | 2018-09-21 | 郑州云海信息技术有限公司 | A kind of system and method for centralized management platform and client synchronization program listing |
| CN108763933A (en) * | 2018-05-23 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of application management method and system based on auto-programming inventory |
-
2021
- 2021-03-31 CN CN202110352517.7A patent/CN112860313B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106327152A (en) * | 2016-08-11 | 2017-01-11 | 宁波亦道信息科技有限公司 | Integrated iteration software development process control system and method |
| CN108089843A (en) * | 2018-01-18 | 2018-05-29 | 福建省农村信用社联合社 | A kind of intelligentized banking establishments grade requirement management systems |
| CN108563512A (en) * | 2018-04-02 | 2018-09-21 | 郑州云海信息技术有限公司 | A kind of system and method for centralized management platform and client synchronization program listing |
| CN108763933A (en) * | 2018-05-23 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of application management method and system based on auto-programming inventory |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113553259A (en) * | 2021-07-20 | 2021-10-26 | 中国工商银行股份有限公司 | Program list generation method and device |
| CN113485742A (en) * | 2021-07-28 | 2021-10-08 | 中国工商银行股份有限公司 | Host application version registration method and device |
| CN113485742B (en) * | 2021-07-28 | 2024-07-02 | 中国工商银行股份有限公司 | Host application version registration method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112860313B (en) | 2024-01-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110321254B (en) | Software version rollback method, device, server and storage medium | |
| US9176728B1 (en) | Global software deployment/remediation management and associated analytics | |
| US8555248B2 (en) | Business object change management using release status codes | |
| CN112860313A (en) | Document and version checking method and device based on requirement items | |
| US11915239B2 (en) | System and method for updating and managing hosted catalogs in a procurement system | |
| CN110889579A (en) | MBOM technical state management and control method based on baseline | |
| CN105528464A (en) | Version management system capable of automatically judging technical condition consistency of associated data | |
| CN111694612A (en) | Configuration checking method, device, computer system and storage medium | |
| CN112561370A (en) | Software version management method and device, computer equipment and storage medium | |
| CN108230129B (en) | Tax function automatic processing method and device | |
| CN103440460A (en) | Application system change validation method and system | |
| CN110865806A (en) | Code processing method, device, server and storage medium | |
| EP3999917B1 (en) | Method and system for generating a digital representation of asset information in a cloud computing environment | |
| CN112363745A (en) | Rule file management method and device, computer equipment and storage medium | |
| CN116795425A (en) | Chip front-end development system and method based on git | |
| CN106855804B (en) | Code change management and control method and device | |
| CN112099806A (en) | CICD-based sql automatic auditing online and executing method | |
| CN113902531A (en) | Automatic generation system, method, electronic device and storage medium for bid document | |
| US9772836B2 (en) | Delivery of correction packages | |
| CN111985868A (en) | Bill of material maintenance method and system for server product production | |
| JP5936496B2 (en) | Job operation management system | |
| CN111222928A (en) | Method and system for monitoring enterprise standard invoicing | |
| CN106445898B (en) | Method and system for processing postal envelope data | |
| US11934800B2 (en) | Generating metadata to facilitate code generation | |
| CN111190819B (en) | State control method for airborne software test project |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |