CN111381861A - Software collaborative production processing method and device - Google Patents
Software collaborative production processing method and device Download PDFInfo
- Publication number
- CN111381861A CN111381861A CN202010255282.5A CN202010255282A CN111381861A CN 111381861 A CN111381861 A CN 111381861A CN 202010255282 A CN202010255282 A CN 202010255282A CN 111381861 A CN111381861 A CN 111381861A
- Authority
- CN
- China
- Prior art keywords
- version
- collaborative
- production
- physical subsystem
- software version
- 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
- 238000004519 manufacturing process Methods 0.000 title claims abstract description 117
- 238000003672 processing method Methods 0.000 title claims abstract description 22
- 238000012360 testing method Methods 0.000 claims abstract description 247
- 238000000034 method Methods 0.000 claims abstract description 29
- 238000001514 detection method Methods 0.000 claims abstract description 27
- 239000000178 monomer Substances 0.000 claims abstract description 11
- 238000012795 verification Methods 0.000 claims abstract description 10
- 238000004806 packaging method and process Methods 0.000 claims abstract description 9
- 238000012550 audit Methods 0.000 claims description 32
- 238000004590 computer program Methods 0.000 claims description 19
- 238000012545 processing Methods 0.000 claims description 18
- 230000010354 integration Effects 0.000 abstract description 23
- 238000010586 diagram Methods 0.000 description 18
- 230000006870 function Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 238000011161 development Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012552 review 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a software collaborative production processing method and a device, wherein the method comprises the following steps: acquiring version package source codes of all physical subsystems of the collaborative commissioning software version; performing compliance detection on the version package source code of each physical subsystem, and packaging to generate a version package of each physical subsystem; performing monomer test on the version packet of each physical subsystem; if the single test result of the version package of each physical subsystem of the collaborative commissioning software version is judged to be passed, carrying out integration test on the collaborative commissioning software version; if the integrated test result of the collaborative commissioning software version is judged to be passed; and prompting to carry out production verification if the user acceptance test result of the collaborative production software version is judged to be passed and the submitted piece of the collaborative production software version is complete. The device is used for executing the method. The software collaborative production processing method and device provided by the embodiment of the invention improve the efficiency of collaborative production.
Description
Technical Field
The invention relates to the technical field of software development, in particular to a software collaborative production processing method and device.
Background
The production on-line is an important link in the software production process, is orderly and controllable in the production on-line process, and has important significance in guaranteeing the on-time production of the software.
For the production of large-scale software, different departments in different areas are required to cooperate with each other, and all the cooperating departments respectively complete the production of partial functions of the software product at the same appointed production point, so that the production of a complete software product is realized. In the prior art, some enterprise software is online and takes an agreed mode to be put into production simultaneously, some enterprises take certain information sharing, but the enterprise-level cooperative production is not integrally controlled, so that the cooperative production efficiency is low, the online process is disordered, the online version switching time is long, the production versions are inconsistent and the like, and great operation risks are caused to the enterprises.
Disclosure of Invention
To solve the problems in the prior art, embodiments of the present invention provide a method and an apparatus for processing a software collaborative commissioning, which can at least partially solve the problems in the prior art.
On one hand, the invention provides a software collaborative production processing method, which comprises the following steps:
acquiring version package source codes of all physical subsystems of the collaborative commissioning software version;
performing compliance detection on the version package source code of each physical subsystem, and packaging to generate a version package of each physical subsystem;
performing monomer test on the version packet of each physical subsystem to obtain a monomer test result of the version packet of each physical subsystem;
if the single test result of the version package of each physical subsystem of the collaborative commissioning software version is judged to be passed, carrying out integrated test on the collaborative commissioning software version to obtain an integrated test result of the collaborative commissioning software version;
if the integrated test result of the collaborative commissioning software version is judged to be passed, obtaining a user acceptance test result of the collaborative commissioning software version;
and prompting to carry out production verification if the user acceptance test result of the collaborative production software version is judged to be passed and the submitted piece of the collaborative production software version is complete.
In another aspect, the present invention provides a software collaborative production processing apparatus, including:
the system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring the version package source codes of all physical subsystems of the collaborative production software version;
the detection unit is used for carrying out compliance detection on the version package source code of each physical subsystem and packaging to generate a version package of each physical subsystem;
the single test unit is used for performing single test on the version packet of each physical subsystem to obtain a single test result of the version packet of each physical subsystem;
the integrated test unit is used for carrying out integrated test on the cooperative production software version after judging that the single test result of the version package of each physical subsystem of the cooperative production software version passes, so as to obtain the integrated test result of the cooperative production software version;
the judging unit is used for acquiring a user acceptance test result of the collaborative production software version after judging that the integrated test result of the collaborative production software version passes;
and the prompting unit is used for prompting to carry out production audit after judging that the user acceptance test result of the collaborative production software version is passed and the submitted piece of the collaborative production software version is complete.
In another aspect, the present invention provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the software co-production processing method according to any of the above embodiments when executing the computer program.
In still another aspect, the present invention provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the software collaborative commissioning processing method according to any one of the above embodiments.
The software collaborative commissioning processing method and device provided by the embodiment of the invention can acquire the version package source codes of all physical subsystems of the collaborative commissioning software version, perform compliance detection on the version package source codes of all the physical subsystems, package the version package of each physical subsystem to generate a single-body test on the version package of each physical subsystem, acquire the single-body test result of the version package of each physical subsystem, perform an integration test on the collaborative commissioning software version after judging that the single-body test result of the version package of each physical subsystem of the collaborative commissioning software version passes, acquire the integration test result of the collaborative commissioning software version, acquire the user acceptance test result of the collaborative commissioning software version when judging that the integration test result of the collaborative commissioning software version passes, and determine that the user acceptance test result of the collaborative commissioning software version passes and the submitted piece of the collaborative commissioning software version is finished After the completion, the production audit is prompted, so that the automation of scanning, detecting and testing of the collaborative production software version is realized, and the collaborative production efficiency is improved.
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 schematic structural diagram of a software collaborative commissioning system according to an embodiment of the present invention.
Fig. 2 is a schematic flow chart of a software collaborative commissioning processing method according to an embodiment of the present invention.
Fig. 3 is a schematic flow chart of a software collaborative commissioning processing method according to another embodiment of the present invention.
Fig. 4 is a schematic flow chart of a software collaborative commissioning processing method according to another embodiment of the present invention.
Fig. 5 is a schematic structural diagram of a software cooperative commissioning processing apparatus according to an embodiment of the present invention.
Fig. 6 is a schematic structural diagram of a software cooperative commissioning processing apparatus according to another embodiment of the present invention.
Fig. 7 is a schematic structural diagram of a software cooperative commissioning processing apparatus according to another embodiment of the present invention.
Fig. 8 is a schematic physical structure diagram of an electronic device according to an 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. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
In order to facilitate understanding of the technical solutions provided in the present application, the following briefly describes related contents of the technical solutions in the present application.
The cooperative production of the software version relates to mutual cooperation of different departments in multiple regions, and if the cooperative production is lack of effective management, the cooperative production is disordered, so that the online efficiency and the production operation are greatly influenced. In order to effectively manage the cooperative production, in the project analysis stage of software development, the requirements are analyzed, the related physical subsystems and production points are identified, and the requirement version of each cooperative party is notified before the production points, namely the cooperative production can not be subjected to requirement range change. After the demand is sealed, the demand range of the cooperative production and the physical subsystem influenced by the demand are automatically identified according to the production points, a series of version plans of the cooperative production are automatically generated according to the physical subsystem and the production points, a baseline plan is created based on the version plans passing examination and approval, the version plans and the baseline plan are uniformly managed, configured and examined and approved, the uniform management of the production of each cooperative party is realized through reasonable flow control, the ordered, controllable and consistent cooperative production is realized, the production risk is effectively reduced, and the production efficiency is improved.
The cooperative production refers to that the production versions of two or more different systems complete the software production together. The production point refers to the production date of the software version. The physical subsystem is a production system distinguished by deployment units. The version plan comprises information such as a physical subsystem, a production point, a version plan name and a collaborative production demand list corresponding to the version. The baseline plan comprises information such as a corresponding version plan, a name of a cooperative department, a physical subsystem, a production point, a storage path of a version package and the like. And (4) version package: a series of codes for bringing software versions online or a collection of files such as executable files, configuration files, etc. A continuous integration pipeline: the process of automatic construction, deployment, testing, release and the like of the application program is realized based on a Jenkins production line.
Fig. 1 is a schematic structural diagram of a software collaborative commissioning system according to an embodiment of the present invention, and as shown in fig. 1, the software collaborative commissioning system according to the embodiment of the present invention includes a server 1 and a plurality of collaborative terminals 2, and the server 1 is in communication connection with the plurality of collaborative terminals 2. Each collaborating party can upload data to the server 1 through the collaborating terminal 2. The server 1 is configured to execute the software collaborative commissioning processing method provided by the embodiment of the present invention. The collaboration terminal includes, but is not limited to, a desktop computer, a notebook computer, and the like.
Fig. 2 is a schematic flow chart of a software collaborative commissioning processing method according to an embodiment of the present invention, and as shown in fig. 2, the software collaborative commissioning processing method according to the embodiment of the present invention includes:
s201, acquiring version package source codes of all physical subsystems of the collaborative production software version;
specifically, each physical subsystem corresponds to one collaborating party, the collaborating party can obtain the version package source code of the physical subsystem after the development of the running program of the physical subsystem is completed, each collaborating party can upload the version package source code of the physical subsystem to a server through a collaborating terminal, and the server can obtain the version package source code of each physical subsystem of the collaborating production software version. Wherein the co-production software version comprises at least one project software version. When the co-production software release includes multiple project software releases, the multiple project software releases may include the same physical subsystems. Each physical subsystem of the co-production software version is preset.
S202, performing compliance detection on the version package source code of each physical subsystem, and packaging to generate a version package of each physical subsystem;
specifically, after obtaining the version package source code of the physical subsystem, the server performs compliance detection on the version package source code of the physical subsystem, and obtains a compliance detection result of the physical subsystem. If the result of the compliance detection of the physical subsystem is qualified, the compliance detection of the physical subsystem is passed, and the server packages the source codes of the version package of the physical subsystem to generate the version package of the physical subsystem. And the server carries out compliance detection on the source code of the version packet of each physical subsystem and packages the source code to generate the version packet of each physical subsystem. The compliance detection may include code scanning, compliance scanning, and the like, and is set according to actual needs, which is not limited in the embodiments of the present invention. The code scanning is used for detecting whether semantic defects, security holes and other problems exist in the source codes of the version packages, and the normative scanning is used for detecting whether grammatical errors exist in the source codes of the version packages.
S203, performing a single test on the version packet of each physical subsystem to obtain a single test result of the version packet of each physical subsystem.
Specifically, after obtaining the version package of the physical subsystem, the server performs a unit test on the version package of the physical subsystem to obtain a unit test result of the version package of the physical subsystem, if the unit test result of the version package of the physical subsystem is qualified, it indicates that the version package of the physical subsystem passes the unit test, and if the unit test result of the version package of the physical subsystem is unqualified, it indicates that the version package of the physical subsystem does not pass the unit test, and a result that the unit test of the version package of the physical subsystem fails may be fed back to a cooperator corresponding to the physical subsystem, so as to modify the version package source code of the physical subsystem. The server performs the individual test on the version packet of each physical subsystem to obtain the individual test result of the version packet of each physical subsystem. The single test may include a unit test, an interface automation test, and the like, and is set according to actual needs, which is not limited in the embodiments of the present invention. The unit test is used for detecting the branch coverage rate and the code line coverage rate of the function of the version packet, and the interface automation test is used for testing the interface related to the version packet, verifying the exchange, transmission, control and management processes of data, mutual logic dependency relationship and the like.
S204, if the single test result of the version package of each physical subsystem of the collaborative commissioning software version is judged to be passed, carrying out integrated test on the collaborative commissioning software version to obtain an integrated test result of the collaborative commissioning software version;
specifically, after obtaining the individual test result of the version packet of each physical subsystem, the server may determine whether the version packet of each physical subsystem passes the individual test according to the individual test result of the version packet of each physical subsystem, and if the individual test result of the version packet of the physical subsystem passes, the version packet of the physical subsystem passes the individual test. After the version packages of the physical subsystems of the collaborative commissioning software version all pass the individual testing, the collaborative commissioning software version may be subjected to an integration test to obtain an integration test result of the collaborative commissioning software version. If the co-production software version only includes one project software version, then there is only one integrated test result. If the cooperative commissioning software version comprises a plurality of project software versions, respectively combining the physical subsystems of each project software version of the cooperative commissioning software version for integrated testing during integrated testing to obtain an integrated test result of each project software version, wherein the integrated test result of the cooperative commissioning software version comprises an integrated test result of the plurality of project software versions.
S205, if the integrated test result of the collaborative commissioning software version is judged to be passed, obtaining a user acceptance test result of the collaborative commissioning software version;
specifically, after obtaining the integration test result of the co-production software version, the server may determine whether the co-production software version passes the integration test according to the integration test result of the co-production software version, and if the integration test result of the co-production software version passes, the co-production software version passes the integration test. The fact that the integrated test result of the collaborative commissioning software version passes means that the integrated test result of each project software version of the collaborative commissioning software version passes, and if the integrated test result of any project software version does not pass, the integrated test result of the collaborative commissioning software version does not pass. After the integrated test result of the collaborative commissioning software version passes, the server may obtain a user acceptance test result of the collaborative commissioning software version. And each project software version of the collaborative commissioning software version needs to be subjected to user acceptance test, and each project software version corresponds to a user acceptance test result. The user acceptance test can be performed by service personnel, a user acceptance test report is issued after the user acceptance test is completed, whether the user acceptance test passes or not can be determined in the user acceptance test report, the service personnel can upload the user acceptance test report to the server, and the server can obtain a user acceptance test result by scanning the user acceptance test report.
And S206, prompting to carry out production audit if the user acceptance test result of the collaborative production software version is judged to be passed and the submitted piece of the collaborative production software version is complete.
Specifically, after obtaining the user acceptance test result of the co-production software version, the server may determine whether the user acceptance test of the co-production software version passes or not based on the user acceptance test result of the co-production software version, if the user acceptance test result of the co-production software version passes, the co-production software version passes the user acceptance test, and if the user acceptance test result of the co-production software version passes, the user acceptance test result of the co-production software version means that the user acceptance test result of each project software version of the co-production software version passes, and the user acceptance test result of any project software version does not pass, so the user acceptance test result of the co-production software version does not pass. The server also judges whether the submitted piece of the collaborative production software version is complete, and if the user acceptance test result of the collaborative production software version is passed and the submitted piece of the collaborative production software version is complete, the server can prompt to carry out production verification. The submitted piece of the software version includes, but is not limited to, a version check report, a safety production maintenance manual, and the like, and is set according to actual needs, and the embodiment of the invention is not limited. The related personnel can upload the submission of the co-production software version to the server, and the server determines whether the submission of the co-production software version is complete by detecting whether the submission of the co-production software version is uploaded. If all the submitted pieces of the collaborative commissioning software version are uploaded, the submitted pieces of the collaborative commissioning software version are complete; if none of the submissions of the co-production software version are missing, the submissions of the co-production software version are incomplete. It can be understood that if the user acceptance test result of the co-production software version is failed or the submitted piece of the co-production software version is incomplete, the user cannot prompt the production audit of the software version.
For example, the server may prompt, through a system message, a short message, a WeChat, or the like, that a relevant person may perform production audit on the collaborative production software version.
The software collaborative commissioning processing method provided by the embodiment of the invention can obtain the version package source codes of all physical subsystems of the collaborative commissioning software version, perform compliance detection on the version package source codes of all the physical subsystems, and package the version packages to generate the version packages of all the physical subsystems, perform single body test on the version packages of all the physical subsystems to obtain the single body test result of the version packages of all the physical subsystems, perform integrated test on the collaborative commissioning software version after judging that the single body test result of the version packages of all the physical subsystems of the collaborative commissioning software version passes, obtain the integrated test result of the collaborative commissioning software version, obtain the user acceptance test result of the collaborative commissioning software version after judging that the integrated test result of the collaborative commissioning software version passes, and obtain the user acceptance test result of the collaborative commissioning software version and complete submission of the collaborative commissioning software version And production audit is prompted, so that the automation of scanning, detecting and testing of the collaborative production software version is realized, and the collaborative production efficiency is improved. In addition, the method can confirm the related information of the collaborative production, and prompt of production audit is timely performed, so that the collaborative production efficiency is further improved.
Fig. 3 is a schematic flow chart of a software collaborative commissioning processing method according to another embodiment of the present invention, and as shown in fig. 3, on the basis of the foregoing embodiments, further before acquiring version package source codes of each collaborating party of a collaborative commissioning software version, the method further includes:
s301, acquiring a production point of the collaborative production software version, each physical subsystem, a collaborative production demand corresponding to each physical subsystem and a collaborative party corresponding to each physical subsystem;
specifically, in a project requirement analysis stage of software development, a software project implementation team may analyze requirements related to a collaborative commissioning software version, and determine a project software version included in the collaborative commissioning software version, physical subsystems related to each project software version, a collaborative commissioning requirement corresponding to each physical subsystem, a collaboration party corresponding to each physical subsystem, and a commissioning point of the collaborative commissioning software version. And the software project implementation team uploads the contents to the server, and the server can acquire the production points of the collaborative production software version, each physical subsystem, the collaborative production requirements corresponding to each physical subsystem and the collaborators corresponding to each physical subsystem. The collaborative commissioning software version may include one project software version or a plurality of project software versions. And the cooperative party corresponding to each physical subsystem is preset, and the cooperative party is an execution team responsible for the development of the version package source code of the physical subsystem.
S302, creating a version plan for each physical subsystem based on the production points, each physical subsystem, the cooperative production demand corresponding to each physical subsystem and the cooperative party.
Specifically, after obtaining the production point of the collaborative production software version, each physical subsystem, the collaborative production demand corresponding to each physical subsystem, and the collaborating party corresponding to each physical subsystem, the server may create a version plan for each physical subsystem based on the production point, each physical subsystem, the collaborative production demand corresponding to each physical subsystem, and the collaborating party, and after the creation is completed, the version plan of each physical subsystem may include the physical subsystem, the production point, the version plan name, and a list of demands to be produced. The creation time of the version plan of the physical subsystem may be preset days before the production point, the preset days may be 12 days, and the creation time is set according to actual needs.
Fig. 4 is a schematic flow chart of a software collaborative commissioning processing method according to another embodiment of the present invention, and as shown in fig. 4, on the basis of the foregoing embodiments, further, the software collaborative commissioning processing method according to the embodiment of the present invention further includes:
s401, obtaining an auditing result of the version plan of each physical subsystem;
specifically, after the creation of the version plan of each physical subsystem is completed, the relevant personnel may audit the version plan of each physical subsystem, and feed back an audit result of the version plan of each physical subsystem to the server. The server may obtain an audit result of the version plan for each physical subsystem. And the auditing result of the version plan of the physical subsystem is a pass result and a non-pass result.
S402, if the verification result of the version plan of the physical subsystem is judged to be passed, establishing a baseline plan for the physical subsystem which passes the verification of the version plan.
Specifically, after obtaining the audit result of the version plan of the physical subsystem, the server may determine whether the version plan of the physical subsystem passes the audit based on the audit result of the version plan of the physical subsystem, if the audit result of the version plan of the physical subsystem passes, the version plan of the physical subsystem passes the audit, the server may create a baseline plan for the physical subsystem that the version plan passes the audit, where the baseline plan may include a corresponding version plan, a physical subsystem, a production point, a code source corresponding to a version package, and version package information. The code source corresponding to the version packet and the version packet information are preset. The creation time of the baseline plan may be a second preset number of days before the production point, and the second preset number of days may be 10 days, and the setting is performed according to actual needs.
On the basis of the foregoing embodiments, further, the software collaborative commissioning processing method provided in the embodiment of the present invention further includes:
and prompting to upload the version package source code if the version package source code of the physical subsystem is not acquired at the first preset time.
Specifically, each cooperative party should complete the version package source code of the physical subsystem before the first preset time and upload the version package source code of the physical subsystem to the server through the cooperative terminal, so as to ensure on-time production of the cooperative production software version. If the server does not acquire the version package source code of the physical subsystem at the first preset time, which indicates that the cooperative party does not upload the version package source code of the physical subsystem, the server may send a prompt message to the cooperative party to prompt the cooperative party to upload the version package source code of the physical subsystem. The first preset time is set according to actual needs, for example, 10 days before a production point of the collaborative production software version, which is not limited in the embodiment of the present invention.
On the basis of the foregoing embodiments, further, the software collaborative commissioning processing method provided in the embodiment of the present invention further includes:
and prompting the user to perform the acceptance test if the user acceptance test result of the collaborative commissioning software version is not obtained at the second preset time.
Specifically, in order to ensure that the collaborative commissioning software version is commissioned on time, the latest time when the collaborative commissioning software version completes the user acceptance test may be set as the second preset time. If the server does not obtain the user acceptance test result of the collaborative commissioning software version at the second preset time, sending a prompt message to relevant personnel to prompt the relevant personnel to perform the user acceptance test on the collaborative commissioning software version. The second preset time is set according to actual needs, and the embodiment of the invention is not limited.
Fig. 5 is a schematic structural diagram of a software collaboration production processing apparatus according to an embodiment of the present invention, and as shown in fig. 5, the software collaboration production processing apparatus according to the embodiment of the present invention includes a first obtaining unit 501, a detecting unit 502, a single testing unit 503, an integrated testing unit 504, a determining unit 505, and a prompting unit 506, where:
the first obtaining unit 501 is configured to obtain version package source codes of each physical subsystem of the collaborative commissioning software version; the detecting unit 502 is configured to perform compliance detection on the version package source code of each physical subsystem, and package the version package source code of each physical subsystem to generate a version package of each physical subsystem; the single testing unit 503 is configured to perform single testing on the version packet of each physical subsystem to obtain a single testing result of the version packet of each physical subsystem; the integration test unit 504 is configured to perform an integration test on the collaborative commissioning software version after determining that the individual test result of the version package of each physical subsystem of the collaborative commissioning software version is passed, so as to obtain an integration test result of the collaborative commissioning software version; the determining unit 505 is configured to obtain a user acceptance test result of the collaborative commissioning software version after determining that the integration test result of the collaborative commissioning software version passes; the prompting unit 506 is configured to prompt to perform production audit after determining that the user acceptance test result of the collaborative production software version is passed and the submitted piece of the collaborative production software version is complete.
Specifically, each physical subsystem corresponds to one collaborating party, the collaborating party can obtain the version package source code of the physical subsystem after completing the development of the running program of the physical subsystem, each collaborating party can upload the version package source code of the physical subsystem to the first obtaining unit 501 through the collaborating terminal, and the first obtaining unit 501 can obtain the version package source code of each physical subsystem of the collaborated production software version. Wherein the co-production software version comprises at least one project software version. When the co-production software release includes multiple project software releases, the multiple project software releases may include the same physical subsystems. Each physical subsystem of the co-production software version is preset.
After obtaining the version package source code of the physical subsystem, the detecting unit 502 performs compliance detection on the version package source code of the physical subsystem to obtain a compliance detection result of the physical subsystem. If the result of the compliance detection of the physical subsystem is qualified, the compliance detection of the physical subsystem is passed, and the server packages the source codes of the version package of the physical subsystem to generate the version package of the physical subsystem. And the server carries out compliance detection on the source code of the version packet of each physical subsystem and packages the source code to generate the version packet of each physical subsystem. The compliance detection may include code scanning, compliance scanning, and the like, and is set according to actual needs, which is not limited in the embodiments of the present invention. The code scanning is used for detecting whether semantic defects, security holes and other problems exist in the source codes of the version packages, and the normative scanning is used for detecting whether grammatical errors exist in the source codes of the version packages.
After obtaining the version package of the physical subsystem, the unit testing unit 503 performs a unit test on the version package of the physical subsystem to obtain a unit test result of the version package of the physical subsystem, if the unit test result of the version package of the physical subsystem is qualified, it indicates that the version package of the physical subsystem passes the unit test, and if the unit test result of the version package of the physical subsystem is unqualified, it indicates that the version package of the physical subsystem does not pass the unit test, and may feed back the result that the unit test of the version package of the physical subsystem fails to the cooperator corresponding to the physical subsystem, so as to modify the version package source code of the physical subsystem. The unit testing unit 503 performs a unit test on the version packet of each physical subsystem to obtain a unit testing result of the version packet of each physical subsystem. The single test may include a unit test, an interface automation test, and the like, and is set according to actual needs, which is not limited in the embodiments of the present invention. The unit test is used for detecting the branch coverage rate and the code line coverage rate of the function of the version packet, and the interface automation test is used for testing the interface related to the version packet, verifying the exchange, transmission, control and management processes of data, mutual logic dependency relationship and the like.
After obtaining the individual test result of the version packet of each physical subsystem, the integrated test unit 504 may determine whether the version packet of each physical subsystem passes the individual test according to the individual test result of the version packet of each physical subsystem, and if the individual test result of the version packet of the physical subsystem passes, the version packet of the physical subsystem passes the individual test. After the version packages of the physical subsystems of the collaborative commissioning software version all pass the individual testing, the collaborative commissioning software version may be subjected to an integration test to obtain an integration test result of the collaborative commissioning software version. If the co-production software version only includes one project software version, then there is only one integrated test result. If the cooperative commissioning software version comprises a plurality of project software versions, respectively combining the physical subsystems of each project software version of the cooperative commissioning software version for integrated testing during integrated testing to obtain an integrated test result of each project software version, wherein the integrated test result of the cooperative commissioning software version comprises an integrated test result of the plurality of project software versions.
After obtaining the integration test result of the co-production software version, the determining unit 505 may determine whether the co-production software version passes the integration test according to the integration test result of the co-production software version, and if the integration test result of the co-production software version passes, the co-production software version passes the integration test. The fact that the integrated test result of the collaborative commissioning software version passes means that the integrated test result of each project software version of the collaborative commissioning software version passes, and if the integrated test result of any project software version does not pass, the integrated test result of the collaborative commissioning software version does not pass. After the integrated test result of the co-production software version passes, the determining unit 505 may obtain a user acceptance test result of the co-production software version. And each project software version of the collaborative commissioning software version needs to be subjected to user acceptance test, and each project software version corresponds to a user acceptance test result. The user acceptance test can be performed by service personnel, a user acceptance test report is issued after the user acceptance test is completed, whether the user acceptance test passes or not can be determined in the user acceptance test report, the service personnel can upload the user acceptance test report to the server, and the judgment unit 505 can obtain a user acceptance test result by scanning the user acceptance test report.
After obtaining the user acceptance test result of the co-production software version, the prompting unit 506 may determine whether the user acceptance test of the co-production software version passes or not based on the user acceptance test result of the co-production software version, if the user acceptance test result of the co-production software version passes, the co-production software version passes the user acceptance test, and if the user acceptance test result of the co-production software version passes, the user acceptance test result of the co-production software version means that the user acceptance test result of each project software version of the co-production software version passes, and the user acceptance test result of any project software version does not pass, and the user acceptance test result of the co-production software version does not pass. The prompting unit 506 may further determine whether the submitted piece of the co-production software version is complete, and if the user acceptance test result of the co-production software version is passed and the submitted piece of the co-production software version is complete, the prompting unit 506 may prompt to perform production audit. The submitted piece of the software version includes, but is not limited to, a version check report, a safety production maintenance manual, and the like, and is set according to actual needs, and the embodiment of the invention is not limited. The relevant personnel may upload the submission of the co-production software version to the prompting unit 506, and the prompting unit 506 determines whether the submission of the co-production software version is complete by detecting whether the submission of the co-production software version has been uploaded. If all the submitted pieces of the collaborative commissioning software version are uploaded, the submitted pieces of the collaborative commissioning software version are complete; if none of the submissions of the co-production software version are missing, the submissions of the co-production software version are incomplete. It can be understood that if the user acceptance test result of the co-production software version is failed or the submitted piece of the co-production software version is incomplete, the user cannot prompt the production audit of the software version.
The software collaborative commissioning processing device provided by the embodiment of the invention can acquire the version package source codes of each physical subsystem of the collaborative commissioning software version, perform compliance detection on the version package source codes of each physical subsystem, and package the version packages to generate the version packages of each physical subsystem, perform single test on the version packages of each physical subsystem to acquire the single test result of the version packages of each physical subsystem, perform integrated test on the collaborative commissioning software version after judging that the single test result of the version packages of each physical subsystem of the collaborative commissioning software version passes, acquire the integrated test result of the collaborative commissioning software version, acquire the user acceptance test result of the collaborative commissioning software version after judging that the integrated test result of the collaborative commissioning software version passes, and acquire the user acceptance test result of the collaborative commissioning software version and complete submission of the collaborative commissioning software version And production audit is prompted, so that the automation of scanning, detecting and testing of the collaborative production software version is realized, and the collaborative production efficiency is improved. In addition, the method can confirm the related information of the collaborative production, and prompt of production audit is timely performed, so that the collaborative production efficiency is further improved.
Fig. 6 is a schematic structural diagram of a software collaborative commissioning processing apparatus according to another embodiment of the present invention, as shown in fig. 6, on the basis of the foregoing embodiments, further, the software collaborative commissioning processing apparatus according to the embodiment of the present invention further includes a second obtaining unit 507 and a first creating unit 508, where:
the second obtaining unit 507 is configured to obtain a production point of the collaborative production software version, each physical subsystem, a collaborative production demand corresponding to each physical subsystem, and a collaborative party corresponding to each physical subsystem; the first creating unit 508 is configured to create a version plan for each physical subsystem based on the production point, each physical subsystem, the collaborative production demand corresponding to each physical subsystem, and the collaborator.
Specifically, in a project requirement analysis stage of software development, a software project implementation team may analyze requirements related to a collaborative commissioning software version, and determine a project software version included in the collaborative commissioning software version, physical subsystems related to each project software version, a collaborative commissioning requirement corresponding to each physical subsystem, a collaboration party corresponding to each physical subsystem, and a commissioning point of the collaborative commissioning software version. The software project implementation team uploads the above contents to the second obtaining unit 507, and the second obtaining unit 507 can obtain the production points of the collaborative production software version, each physical subsystem, the collaborative production requirements corresponding to each physical subsystem, and the collaborators corresponding to each physical subsystem. The collaborative commissioning software version may include one project software version or a plurality of project software versions. And the cooperative party corresponding to each physical subsystem is preset, and the cooperative party is an execution team responsible for the development of the version package source code of the physical subsystem.
After obtaining the production point of the collaborative production software version, each physical subsystem, the collaborative production demand corresponding to each physical subsystem, and the collaborator corresponding to each physical subsystem, the first creating unit 508 may create a version plan for each physical subsystem based on the production point, each physical subsystem, the collaborative production demand corresponding to each physical subsystem, and the collaborator, and after the creation is completed, the version plan of each physical subsystem may include the physical subsystem, the production point, the version plan name, and the list of the demand to be produced. The creation time of the version plan of the physical subsystem may be a first preset number of days before the production point, where the first preset number of days may be 12 days, and the first preset number of days is set according to actual needs, which is not limited in the embodiment of the present invention.
Fig. 7 is a schematic structural diagram of a software collaborative commissioning processing apparatus according to another embodiment of the present invention, as shown in fig. 7, on the basis of the foregoing embodiments, further, the software collaborative commissioning processing apparatus according to the embodiment of the present invention further includes a third obtaining unit 509 and a second creating unit 510, where:
the third obtaining unit 509 is configured to obtain an audit result of the version plan of each physical subsystem; the second creating unit 510 is configured to create a baseline plan for each physical subsystem after determining that the result of the review of the version plan of the physical subsystem is passed.
Specifically, after the creation of the version plan of each physical subsystem is completed, the relevant personnel may audit the version plan of each physical subsystem, and feed back an audit result of the version plan of each physical subsystem to the third obtaining unit 509. The third obtaining unit 509 may obtain an audit result of the version plan of each physical subsystem. And the auditing result of the version plan of the physical subsystem is a pass result and a non-pass result.
After obtaining the audit result of the version plan of the physical subsystem, the second creating unit 510 may determine, based on the audit result of the version plan of the physical subsystem, whether the version plan of the physical subsystem passes the audit, if the audit result of the version plan of the physical subsystem passes the audit, and the server may create a baseline plan for the physical subsystem that the version plan passes the audit, where the baseline plan may include a corresponding version plan, a physical subsystem, a production point, a code source corresponding to a version package, and version package information. The code source corresponding to the version packet and the version packet information are preset. The creation time of the baseline plan may be a second preset number of days before the production point, and the second preset number of days may be 10 days, and the setting is performed according to actual needs.
The embodiment of the apparatus provided in the embodiment of the present invention may be specifically configured to execute the processing flows of the above method embodiments, and the functions of the apparatus are not described herein again, and refer to the detailed description of the above method embodiments.
Fig. 8 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention, and as shown in fig. 8, the electronic device may include: a processor (processor)801, a communication Interface (Communications Interface)802, a memory (memory)803 and a communication bus 804, wherein the processor 801, the communication Interface 802 and the memory 803 complete communication with each other through the communication bus 804. The processor 801 may call logic instructions in the memory 803 to perform the following method: acquiring version package source codes of all physical subsystems of the collaborative commissioning software version; performing compliance detection on the version package source code of each physical subsystem, and packaging to generate a version package of each physical subsystem; performing monomer test on the version packet of each physical subsystem to obtain a monomer test result of the version packet of each physical subsystem; if the single test result of the version package of each physical subsystem of the collaborative commissioning software version is judged to be passed, carrying out integrated test on the collaborative commissioning software version to obtain an integrated test result of the collaborative commissioning software version; if the integrated test result of the collaborative commissioning software version is judged to be passed, obtaining a user acceptance test result of the collaborative commissioning software version; and prompting to carry out production verification if the user acceptance test result of the collaborative production software version is judged to be passed and the submitted piece of the collaborative production software version is complete.
In addition, the logic instructions in the memory 803 may be implemented in the form of software functional units and stored in a computer readable storage medium when the logic instructions are sold or used as independent products. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The present embodiment discloses a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, enable the computer to perform the method provided by the above-mentioned method embodiments, for example, comprising: acquiring version package source codes of all physical subsystems of the collaborative commissioning software version; performing compliance detection on the version package source code of each physical subsystem, and packaging to generate a version package of each physical subsystem; performing monomer test on the version packet of each physical subsystem to obtain a monomer test result of the version packet of each physical subsystem; if the single test result of the version package of each physical subsystem of the collaborative commissioning software version is judged to be passed, carrying out integrated test on the collaborative commissioning software version to obtain an integrated test result of the collaborative commissioning software version; if the integrated test result of the collaborative commissioning software version is judged to be passed, obtaining a user acceptance test result of the collaborative commissioning software version; and prompting to carry out production verification if the user acceptance test result of the collaborative production software version is judged to be passed and the submitted piece of the collaborative production software version is complete.
The present embodiment provides a computer-readable storage medium, which stores a computer program, where the computer program causes the computer to execute the method provided by the above method embodiments, for example, the method includes: acquiring version package source codes of all physical subsystems of the collaborative commissioning software version; performing compliance detection on the version package source code of each physical subsystem, and packaging to generate a version package of each physical subsystem; performing monomer test on the version packet of each physical subsystem to obtain a monomer test result of the version packet of each physical subsystem; if the single test result of the version package of each physical subsystem of the collaborative commissioning software version is judged to be passed, carrying out integrated test on the collaborative commissioning software version to obtain an integrated test result of the collaborative commissioning software version; if the integrated test result of the collaborative commissioning software version is judged to be passed, obtaining a user acceptance test result of the collaborative commissioning software version; and prompting to carry out production verification if the user acceptance test result of the collaborative production software version is judged to be passed and the submitted piece of the collaborative production software version is complete.
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.
In the description herein, reference to the description of the terms "one embodiment," "a particular embodiment," "some embodiments," "for example," "an example," "a particular example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
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 software collaborative production processing method is characterized by comprising the following steps:
acquiring version package source codes of all physical subsystems of the collaborative commissioning software version;
performing compliance detection on the version package source code of each physical subsystem, and packaging to generate a version package of each physical subsystem;
performing monomer test on the version packet of each physical subsystem to obtain a monomer test result of the version packet of each physical subsystem;
if the single test result of the version package of each physical subsystem of the collaborative commissioning software version is judged to be passed, carrying out integrated test on the collaborative commissioning software version to obtain an integrated test result of the collaborative commissioning software version;
if the integrated test result of the collaborative commissioning software version is judged to be passed, obtaining a user acceptance test result of the collaborative commissioning software version;
and prompting to carry out production verification if the user acceptance test result of the collaborative production software version is judged to be passed and the submitted piece of the collaborative production software version is complete.
2. The method of claim 1, prior to obtaining the version package source code for each physical subsystem of the co-production software version, further comprising:
acquiring a production point of the collaborative production software version, each physical subsystem, a collaborative production demand corresponding to each physical subsystem and a collaborative party corresponding to each physical subsystem;
and creating a version plan for each physical subsystem based on the production points, each physical subsystem, the cooperative production demand corresponding to each physical subsystem and the cooperative party.
3. The method of claim 2, further comprising:
obtaining an auditing result of the version plan of each physical subsystem;
and if the verification result of the version plan of the physical subsystem is judged to be passed, establishing a baseline plan for each physical subsystem.
4. The method of claim 1, further comprising:
and prompting to upload the version package source code if the version package source code of the physical subsystem is not acquired at the first preset time.
5. The method of any of claims 1 to 4, further comprising:
and prompting the user to perform the acceptance test if the user acceptance test result of the collaborative commissioning software version is not obtained at the second preset time.
6. A software collaborative production processing device is characterized by comprising:
the system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring the version package source codes of all physical subsystems of the collaborative production software version;
the detection unit is used for carrying out compliance detection on the version package source code of each physical subsystem and packaging to generate a version package of each physical subsystem;
the single test unit is used for performing single test on the version packet of each physical subsystem to obtain a single test result of the version packet of each physical subsystem;
the integrated test unit is used for carrying out integrated test on the cooperative production software version after judging that the single test result of the version package of each physical subsystem of the cooperative production software version passes, so as to obtain the integrated test result of the cooperative production software version;
the judging unit is used for acquiring a user acceptance test result of the collaborative production software version after judging that the integrated test result of the collaborative production software version passes;
and the prompting unit is used for prompting to carry out production audit after judging that the user acceptance test result of the collaborative production software version is passed and the submitted piece of the collaborative production software version is complete.
7. The apparatus of claim 6, further comprising:
a second obtaining unit, configured to obtain a production point of the collaborative production software version, each physical subsystem, a collaborative production demand corresponding to each physical subsystem, and a collaborative party corresponding to each physical subsystem;
and the first creating unit is used for creating a version plan for each physical subsystem based on the production points, each physical subsystem, the cooperative production demand corresponding to each physical subsystem and the cooperative party.
8. The apparatus of claim 7, further comprising:
the third acquisition unit is used for acquiring the auditing result of the version plan of each physical subsystem;
and the second creating unit is used for creating a baseline plan for each physical subsystem after judging that the auditing result of the version plan of the physical subsystem is passed.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method according to any of claims 1 to 5 are implemented when the computer program is executed by the processor.
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 of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010255282.5A CN111381861A (en) | 2020-04-02 | 2020-04-02 | Software collaborative production processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010255282.5A CN111381861A (en) | 2020-04-02 | 2020-04-02 | Software collaborative production processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111381861A true CN111381861A (en) | 2020-07-07 |
Family
ID=71217414
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010255282.5A Pending CN111381861A (en) | 2020-04-02 | 2020-04-02 | Software collaborative production processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111381861A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112540997A (en) * | 2020-12-17 | 2021-03-23 | 中国农业银行股份有限公司 | Data resource management method, device, equipment and medium |
| CN113407230A (en) * | 2021-06-04 | 2021-09-17 | 中船重工奥蓝托无锡软件技术有限公司 | Intelligent main model management system based on data driving |
| CN113778507A (en) * | 2021-07-26 | 2021-12-10 | 北京芬香科技有限公司 | Supporting pipe type online method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106325883A (en) * | 2016-08-31 | 2017-01-11 | 中国建设银行股份有限公司 | Development method and system for industry business area information system |
| CN107239292A (en) * | 2017-06-28 | 2017-10-10 | 郑州云海信息技术有限公司 | It is a kind of to automate the method and apparatus for building software version |
| CN109284225A (en) * | 2018-08-22 | 2019-01-29 | 深圳点猫科技有限公司 | A kind of quality determining method and electronic equipment of multi-person synergy exploitation programming code |
| CN109683899A (en) * | 2017-10-18 | 2019-04-26 | 中移(苏州)软件技术有限公司 | A kind of software integrating method and device |
-
2020
- 2020-04-02 CN CN202010255282.5A patent/CN111381861A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106325883A (en) * | 2016-08-31 | 2017-01-11 | 中国建设银行股份有限公司 | Development method and system for industry business area information system |
| CN107239292A (en) * | 2017-06-28 | 2017-10-10 | 郑州云海信息技术有限公司 | It is a kind of to automate the method and apparatus for building software version |
| CN109683899A (en) * | 2017-10-18 | 2019-04-26 | 中移(苏州)软件技术有限公司 | A kind of software integrating method and device |
| CN109284225A (en) * | 2018-08-22 | 2019-01-29 | 深圳点猫科技有限公司 | A kind of quality determining method and electronic equipment of multi-person synergy exploitation programming code |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112540997A (en) * | 2020-12-17 | 2021-03-23 | 中国农业银行股份有限公司 | Data resource management method, device, equipment and medium |
| CN113407230A (en) * | 2021-06-04 | 2021-09-17 | 中船重工奥蓝托无锡软件技术有限公司 | Intelligent main model management system based on data driving |
| CN113407230B (en) * | 2021-06-04 | 2023-09-29 | 中船奥蓝托无锡软件技术有限公司 | Intelligent main model management system based on data driving |
| CN113778507A (en) * | 2021-07-26 | 2021-12-10 | 北京芬香科技有限公司 | Supporting pipe type online method and system |
| CN113778507B (en) * | 2021-07-26 | 2024-02-20 | 北京芬香科技有限公司 | Method and system for supporting pipe type online |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111381861A (en) | Software collaborative production processing method and device | |
| CN110543326B (en) | DevOps intelligent operation and maintenance method based on block chain | |
| CN109472442B (en) | Automatic processing system and method for work order | |
| US20180165184A1 (en) | Production-like testing and complex business to business auditing system | |
| CN110532021B (en) | Processing method of configuration file of distributed control system, client and service device | |
| CN110888626A (en) | Software integration project matrix type process management system | |
| Larsson et al. | Revisiting the challenges in aligning RE and V&V: Experiences from the public sector | |
| CN112035240A (en) | Task management method, device and system | |
| CN105468507A (en) | Branch fulfillment detection method and apparatus | |
| CN110908708B (en) | Code release method, device and system | |
| US10990925B2 (en) | Document event brokering and audit system | |
| US11107146B2 (en) | Document routing system | |
| CN108156045A (en) | A kind of software definition grouping conveying network SPTN tests system and method | |
| CN105933396A (en) | Method and system for realizing long flow by cooperating system interfaces of different channels | |
| CN111897725B (en) | Automatic test method, medium, equipment and system for middle platform service | |
| CN111523808B (en) | Model centralized management method, system, equipment and storage medium | |
| CN112114954A (en) | Job scheduling configuration method and device of software system | |
| CN105446729B (en) | The automatic transmission realizing method of code update and system based on SAP platform | |
| CN112099805A (en) | Method and device for issuing application, electronic equipment and storage medium | |
| Colazo | Structural changes associated with the temporal dispersion of teams: Evidence from open source software projects | |
| CN106972942B (en) | Alarm processing method and system | |
| CN112561370B (en) | Method and device for managing software release, computer equipment and storage medium | |
| CN112381253B (en) | Nuclear power station penetration inspection task management method, system, electronic equipment and storage medium | |
| CN106547679B (en) | Script management method and script management platform | |
| CN114791828A (en) | Microcode version information processing flow control method and device |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220927 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Applicant after: CHINA CONSTRUCTION BANK Corp. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200707 |
|
| RJ01 | Rejection of invention patent application after publication |