CN111309370A - Version number directed graph sorting audit method and system for multi-project and multi-system environment - Google Patents
Version number directed graph sorting audit method and system for multi-project and multi-system environment Download PDFInfo
- Publication number
- CN111309370A CN111309370A CN201911118026.5A CN201911118026A CN111309370A CN 111309370 A CN111309370 A CN 111309370A CN 201911118026 A CN201911118026 A CN 201911118026A CN 111309370 A CN111309370 A CN 111309370A
- Authority
- CN
- China
- Prior art keywords
- version
- version number
- item
- project
- data
- 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
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 version number directed graph sorting audit method and a system in a multi-project multi-system environment, which can quickly find out wrong version numbers in a large number of system version numbers and prompt the wrong version numbers, thereby reducing the manual burden and improving the release quality. The technical scheme is as follows: the method comprises the steps of collecting all versions of all development projects of a plurality of development departments by means of a unified entry, auditing version numbers by means of a one-way dependency rule and a directed graph algorithm, finding out the version numbers of actual dependency errors under the condition of a single system and a plurality of projects, constructing a project dependency relationship according to the version dependency relationship under the condition of a plurality of systems and a plurality of projects to find out interdependent project errors, and finding out errors of the cyclic dependency of the version numbers (projects) of the plurality of systems according to a directed acyclic principle on the basis of the found correct project dependency information under the condition of a plurality of systems and a plurality of projects.
Description
Technical Field
The invention relates to a system version number auditing technology, in particular to a version number directed graph sequencing auditing method and system in a multi-project multi-system environment.
Background
Generally, an IT technology company has one operation and maintenance department and a plurality of development departments.
The n development departments can initiate m projects (a project refers to a development process that a plurality of persons finish the software functions of some systems once to solve a certain problem or requirement), organize, develop and release a plurality of versions, and the operation and maintenance department is responsible for putting the versions on line. This process is complex, involves a considerable number of people, and is typically managed by project management software for a considerable length of time.
Project management software or version management software such as jira, git, etc. currently exists on the market. Wherein jira is a defect tracking management system, which is a business application software for defect management, task tracking and project management; git is a decentralized version control software.
The project management software, Jira, can record projects and version numbers (the version number refers to an identification number of a system version), and can also show the corresponding relationship between the projects and the version numbers, but has no method for auditing the correctness of the relationship.
git version management software can manage the branching and merging of versions, can judge the correctness of the versions, but lacks the management of the multi-project dependency relationship formed by a plurality of versions, so that a great deal of time is needed to carry out manual audit, the efficiency is low, and errors are easy to occur.
Disclosure of Invention
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
The invention aims to solve the problems and provides a method and a system for checking the ranking of a directed graph of version numbers in a multi-project multi-system environment, which can quickly find wrong version numbers in a large number of system version numbers and prompt the wrong version numbers, thereby reducing the manual burden and improving the release quality.
The technical scheme of the invention is as follows: the invention discloses a version number directed graph sequencing auditing method of a multi-project multi-system environment, which comprises the following steps:
step 1: acquiring data containing project and version number information, preprocessing the data, and removing invalid data to obtain screened data;
step 2: performing dependency audit on the version numbers of the multiple projects of the single system, and finding out the actual version numbers of the dependency errors;
and step 3: performing multi-system multi-project dependency audit, constructing project dependency relations according to version dependency relations, finding out inter-dependent project errors, and then finding out errors of multi-system version number cyclic dependency according to a directed acyclic principle;
and 4, step 4: and displaying the directed graph data and marking error version data.
According to an embodiment of the version number directed graph sorting audit method of the multi-project multi-system environment of the present invention, the step 1 further comprises:
the first step is as follows: collecting item and version number information through a unified entry and storing the item and version number information as a dictionary type, wherein a key of the dictionary type is a version number, and corresponding values comprise a system name, a dependent version number, an item identifier and an item state;
the second step is that: acquiring a system version number which is the same as that of the previous step in the current simulation/production environment through an operation and maintenance interface, setting all version sets in the simulation environment as a virtual item, setting a dependent version number of the virtual item to be null, setting an item identifier as the simulation environment, setting an item state to be online, performing the same treatment on all version sets in the production environment, and if other items conflict with data of the simulation production environment, defaulting that simulation production data is correct, other items are wrong, and data of the simulation production environment is the beginning of version number dependence;
the third step: and removing the data which are collected in the first step and comprise the item and version number information from the online item data of which the version number is less than or equal to the version number in the production environment to obtain the screened data.
According to an embodiment of the version number directed graph sorting audit method of the multi-project multi-system environment of the present invention, the step 2 further comprises:
on the basis of the screened data in the step 1, capturing version numbers according to systems, sequencing the version numbers of each system according to the monotone increasing principle of the version numbers, and acquiring a version number list by each system;
and checking whether the previous version number of each version number is consistent with the dependent version number one by one for each version number list, and if not, marking the version number as an error, wherein the error type is a version dependent error.
According to an embodiment of the version number directed graph sorting audit method of the multi-project multi-system environment of the present invention, step 3 further includes:
on the basis of the screened data in the step 1, capturing a version number according to the items, then judging the version size of each two items in an item list, and distinguishing an item X with a conflict of the version sizes and a normal item Y without the conflict;
judging the version sizes of the items in the X and the items in the Y one by one, putting the items in the X, of which the version size conflicts are not found, into the Y, and marking the rest of the X items after processing as errors, wherein the error types are that the versions of different systems are mutually dependent;
and putting the normal item Y into a directed graph, checking whether a ring exists, marking the item Y as an error if the ring exists, wherein the error type is item cyclic dependence, and sorting the item Y according to a depth-first rule if the ring does not exist.
According to an embodiment of the version number directed graph sorting audit method in the multi-project multi-system environment, between the step 3 and the step 4, the method further includes:
an error is flagged that is less than the production version number and the item status is not on-line/finished, where the error type is on-line but not finished.
The invention also discloses a version number directed graph sequencing auditing system of the multi-project multi-system environment, which comprises:
the acquisition and screening module is used for acquiring data containing project and version number information, then preprocessing the data, and removing invalid data to obtain screened data;
the single-system multi-project version number dependency audit module is used for carrying out dependency audit on the single-system multi-project version numbers and finding out the actual version numbers with dependency errors;
the multi-system multi-project dependence audit module is used for carrying out multi-system multi-project dependence audit, constructing project dependence relations according to version dependence relations, finding out inter-dependent project errors, and then finding out errors of multi-system version number cyclic dependence according to a directed acyclic principle;
and the display module is used for displaying the directed graph data and marking error version data.
According to an embodiment of the version number directed graph sorting audit system of the multi-project multi-system environment, the collection screening module is configured to perform the following processing:
the first step is as follows: collecting item and version number information through a unified entry and storing the item and version number information as a dictionary type, wherein a key of the dictionary type is a version number, and corresponding values comprise a system name, a dependent version number, an item identifier and an item state;
the second step is that: acquiring a system version number which is the same as that of the previous step in the current simulation/production environment through an operation and maintenance interface, setting all version sets in the simulation environment as a virtual item, setting a dependent version number of the virtual item to be null, setting an item identifier as the simulation environment, setting an item state to be online, performing the same treatment on all version sets in the production environment, and if other items conflict with data of the simulation production environment, defaulting that simulation production data is correct, other items are wrong, and data of the simulation production environment is the beginning of version number dependence;
the third step: and removing the data which are collected in the first step and comprise the item and version number information from the online item data of which the version number is less than or equal to the version number in the production environment to obtain the screened data.
According to an embodiment of the version number directed graph sorting audit system of the multi-project multi-system environment, the single-system multi-project version number dependent audit module is configured to perform the following processes:
on the basis of collecting data output by a screening module, capturing version numbers according to systems, sequencing the version numbers of each system according to the principle that the version numbers are monotonically increased, and acquiring a version number list by each system;
and checking whether the previous version number of each version number is consistent with the dependent version number one by one for each version number list, and if not, marking the version number as an error, wherein the error type is a version dependent error.
According to an embodiment of the version number directed graph sorting audit system of the multi-project multi-system environment of the present invention, a multi-system multi-project dependency audit module is configured to perform the following processes:
on the basis of collecting the data output by the screening module, capturing the version number according to the items, and then judging the version size of each two items in the item list to distinguish an item X with a conflict of the version sizes from a normal item Y without the conflict;
judging the version sizes of the items in the X and the items in the Y one by one, putting the items in the X, of which the version size conflicts are not found, into the Y, and marking the rest of the X items after processing as errors, wherein the error types are that the versions of different systems are mutually dependent;
and putting the normal item Y into a directed graph, checking whether a ring exists, marking the item Y as an error if the ring exists, wherein the error type is item cyclic dependence, and sorting the item Y according to a depth-first rule if the ring does not exist.
According to an embodiment of the version number directed graph sorting audit system of the multi-project multi-system environment, the system further comprises:
and the error auditing module is used for marking the item which is smaller than the production version number and has the item status of not being on-line/ended as an error, wherein the error type is on-line but not ended.
Compared with the prior art, the invention has the following beneficial effects: the invention collects all versions of all development projects of n development departments by means of a uniform entrance, audits the version number by a one-way dependency rule and a directed graph algorithm, can find out the version number of actual dependency errors under the condition of single system and multiple projects, constructs the project dependency relationship according to the version dependency relationship under the condition of multiple systems and multiple projects to find out interdependent project errors, and finds out the errors of the cycle dependency of multiple system version numbers (projects) according to the directed acyclic principle on the basis of the found correct project dependency information under the condition of multiple systems and multiple projects.
Drawings
The above features and advantages of the present disclosure will be better understood upon reading the detailed description of embodiments of the disclosure in conjunction with the following drawings. In the drawings, components are not necessarily drawn to scale, and components having similar relative characteristics or features may have the same or similar reference numerals.
FIG. 1 shows a schematic diagram of a single system multi-project audit scenario.
FIG. 2 is a diagram illustrating a project interdependent audit scenario under multi-system multi-project.
FIG. 3 illustrates a schematic diagram of a cyclically dependent audit scenario for multiple systems and items.
FIG. 4 is a flowchart illustrating an embodiment of a version number directed graph ordering audit method in a multi-project multi-system environment.
FIG. 5 illustrates an exemplary diagram of project data in an embodiment of a version number directed graph ordering audit method of a multi-project multi-system environment of the present invention.
Fig. 6A and 6B respectively show an exemplary diagram before and after sorting of single-system multi-project version number dependency audit in the version number directed graph sorting audit method of a multi-project multi-system environment of the present invention.
FIG. 7 is a diagram illustrating an example of a directed graph in multi-system multi-project dependency audit in the version number directed graph ordering audit method of the multi-project multi-system environment of the present invention.
FIG. 8 is a diagram illustrating an embodiment of a version number directed graph ordering audit system of a multi-project multi-system environment of the present invention.
Detailed Description
The invention is described in detail below with reference to the figures and specific embodiments. It is noted that the aspects described below in connection with the figures and the specific embodiments are only exemplary and should not be construed as imposing any limitation on the scope of the present invention.
FIG. 4 is a flowchart illustrating an embodiment of a version number directed graph ordering audit method in a multi-project multi-system environment. Referring to fig. 1, the specific implementation steps of the version number directed graph sorting audit method in the multi-project multi-system environment of the present embodiment are as follows.
Step 1: and acquiring data containing the project and version number information through the unified entry, preprocessing the data, and removing invalid data to obtain screened data.
FIG. 5 illustrates an audit example including a production environment, a simulation environment, an on-line, unfinished project, data to be audited.
The specific implementation of the step 1 comprises the following steps:
first, item and version number information is collected through a unified entry and saved as a dictionary type, such as:
{ bond: the version number of the electronic device,
the value: system name, dependency version number, item identification and item state };
then, a system version number which is the same as that in the previous step in the current simulation/production environment is obtained through an operation and maintenance interface, all version sets in the simulation environment are set as a virtual item, a dependent version number is set to be null, an item identifier is set as the simulation environment, an item state is set to be online, the same processing is carried out on all the version sets in the production environment, if data conflicts between other items and the simulation production environment, default simulation production data are correct, other items are errors, data of the simulation production environment is the start of version number dependence, namely, all the version sets in the production environment are set as another virtual item, a dependent version number is set to be null, an item identifier is set as the production environment, and an item state is set to be online;
and finally, excluding the data including the item and version number information collected in the first step from the item data (invalid data) which are online and have the version number less than or equal to the version number in the production environment to obtain the screened data.
Step 2: and performing dependency audit on the version numbers of the multiple projects of the single system to find out the actual version numbers with the dependency errors.
Take the example shown in fig. 1, where the bold face is the wrong version. The step includes the following processing contents:
firstly, on the basis of the screened data in the step 1, capturing version numbers according to systems, sequencing the version numbers of each system according to the principle that the version numbers are monotonically increased, and acquiring a version number list by each system, wherein the version numbers are arranged from small to large, fig. 6A shows an item example before sequencing, and fig. 6B shows an item example after sequencing;
and then checking whether the previous version number of each version number is consistent with the dependent version number one by one for each version number list, and if not, marking the version number as an error, wherein the error type is a version dependent error.
Wherein the version dependency means: in general, version a is brought online first, and version B is brought online later, so that version B is called to depend on version a, and the version number of version B should be larger than version a. Assuming that the specification requires that the version number should be dependent on one way (monotonically increasing), such as version B, C existing during development while dependent on version a, it is necessary to adjust version C to be dependent on version B in the planned online order of version B, C before release.
And step 3: and (4) carrying out multi-system multi-project dependency audit, constructing project dependency relations according to the version dependency relations, finding out inter-dependent project errors, and then finding out errors of multi-system version number circular dependency according to a directed acyclic principle.
Fig. 2 is an example of project-dependent audit case under multi-system multi-project, and fig. 3 is an example of cyclic-dependent audit case of multi-system multi-project. The specific processing content of the step is as follows:
firstly, on the basis of the screened data in the step 1, capturing a version number according to the items, then judging the version size of each two items in an item list, and distinguishing an item X with a conflict of the version sizes from a normal item Y without the conflict;
and then, carrying out version size judgment on the items in the X and the items in the Y one by one, putting the items in the X, of which the version size conflict is not found, into the Y, and marking the rest of the X items after processing as errors, wherein the error types are that the versions of different systems are mutually dependent.
And finally, putting the normal item Y into a directed graph, checking whether a ring exists or not, marking the item Y as an error if the ring exists, wherein the error type is item cyclic dependence, and sorting the item Y according to a depth-first rule if the ring does not exist. Wherein figure 7 shows an example of a directed graph.
Wherein item dependency refers to that item M depends on N in general if the version of at least one system under item M depends on or is greater than the version under item N, and item M comes on line after item M, and N comes on line first.
And 4, step 4: and displaying the directed graph data and marking error version data.
For example, the directed graph data may be presented in tabular form, with the incorrect version data labeled red.
In addition, on the basis of the above embodiment, the present invention may also add other processing of error audit between step 3 and step 4 of the method of the above embodiment, for example: an error is flagged that is less than the production version number and the item status is not on-line/finished, where the error type is on-line but not finished.
FIG. 8 illustrates the principles of an embodiment of a version number directed graph ordering audit system of the multi-project multi-system environment of the present invention. Referring to fig. 8, the system of the present embodiment includes: the system comprises a collection and screening module, a single-system multi-project version number dependency audit module, a multi-system multi-project dependency audit module and a display module.
The acquisition and screening module is used for acquiring data containing project and version number information through the unified entrance, then preprocessing the data, and removing invalid data to obtain screened data. The acquisition screening module is specifically configured to perform the following processing:
first, item and version number information is collected through a unified entry and saved as a dictionary type, such as:
{ bond: the version number of the electronic device,
the value: system name, dependency version number, item identification and item state };
then, a system version number which is the same as that in the previous step in the current simulation/production environment is obtained through an operation and maintenance interface, all version sets in the simulation environment are set as a virtual item, a dependent version number is set to be null, an item identifier is set as the simulation environment, an item state is set to be online, the same processing is carried out on all the version sets in the production environment, if data conflicts between other items and the simulation production environment, default simulation production data are correct, other items are errors, data of the simulation production environment is the start of version number dependence, namely, all the version sets in the production environment are set as another virtual item, a dependent version number is set to be null, an item identifier is set as the production environment, and an item state is set to be online;
and finally, excluding the data including the item and version number information collected in the first step from the item data (invalid data) which are online and have the version number less than or equal to the version number in the production environment to obtain the screened data.
The single-system multi-project version number dependency audit module is used for carrying out dependency audit on the single-system multi-project version numbers and finding out the actual version numbers of the dependency errors. The single-system multi-project version number dependency auditing module is configured to perform the following specific processing.
Firstly, on the basis of collecting data output by a screening module, capturing version numbers according to systems, sequencing the version numbers of each system according to the principle that the version numbers are monotonically increased, and acquiring a version number list by each system, wherein the version numbers are arranged from small to large, fig. 6A shows an item example before sequencing, and fig. 6B shows an item example after sequencing;
and then checking whether the previous version number of each version number is consistent with the dependent version number one by one for each version number list, and if not, marking the version number as an error, wherein the error type is a version dependent error.
Wherein the version dependency means: in general, version a is brought online first, and version B is brought online later, so that version B is called to depend on version a, and the version number of version B should be larger than version a. Assuming that the specification requires that the version number should be dependent on one way (monotonically increasing), such as version B, C existing during development while dependent on version a, it is necessary to adjust version C to be dependent on version B in the planned online order of version B, C before release.
The multi-system multi-item dependency audit module is used for carrying out multi-system multi-item dependency audit, constructing an item dependency relation according to the version dependency relation, finding out inter-dependent item errors, and then finding out errors of multi-system version number cyclic dependency according to a directed acyclic principle. Wherein the multi-system multi-project dependency audit module is configured to perform the following processes.
Firstly, on the basis of collecting data output by a screening module, capturing version numbers according to items, then judging the version sizes of every two items in an item list, and distinguishing an item X with a conflict of the version sizes from a normal item Y without the conflict;
and then, carrying out version size judgment on the items in the X and the items in the Y one by one, putting the items in the X, of which the version size conflict is not found, into the Y, and marking the rest of the X items after processing as errors, wherein the error types are that the versions of different systems are mutually dependent.
And finally, putting the normal item Y into a directed graph, checking whether a ring exists or not, marking the item Y as an error if the ring exists, wherein the error type is item cyclic dependence, and sorting the item Y according to a depth-first rule if the ring does not exist. Wherein figure 7 shows an example of a directed graph.
Wherein item dependency refers to that item M depends on N in general if the version of at least one system under item M depends on or is greater than the version under item N, and item M comes on line after item M, and N comes on line first.
The display module is used for displaying the directed graph data and marking error version data. For example, the directed graph data may be presented in tabular form, with the incorrect version data labeled red.
Preferably, the system may further comprise an error auditing module, for example, the error auditing module is used for marking an error which is smaller than the production version number and has the project status of not online/ended, wherein the error type is online but not ended.
Additionally, the present invention also discloses a version number directed graph ordering auditing system of a multi-project multi-system environment, comprising a processor and a memory configured to store a series of computer executable instructions and computer accessible data associated with the series of computer executable instructions, wherein the series of computer executable instructions, when executed by the processor, cause the processor to perform the method according to the aforementioned embodiments.
Also disclosed is a non-transitory computer readable storage medium having stored thereon a series of computer executable instructions which, when executed by a computing device, cause the computing device to perform the method as described in the previous embodiments.
While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance with one or more embodiments, occur in different orders and/or concurrently with other acts from that shown and described herein or not shown and described herein, as would be understood by one skilled in the art.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software as a computer program product, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk (disk) and disc (disc), as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks (disks) usually reproduce data magnetically, while discs (discs) reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A version number directed graph sequencing auditing method of a multi-project multi-system environment is characterized by comprising the following steps:
step 1: acquiring data containing project and version number information, preprocessing the data, and removing invalid data to obtain screened data;
step 2: performing dependency audit on the version numbers of the multiple projects of the single system, and finding out the actual version numbers of the dependency errors;
and step 3: performing multi-system multi-project dependency audit, constructing project dependency relations according to version dependency relations, finding out inter-dependent project errors, and then finding out errors of multi-system version number cyclic dependency according to a directed acyclic principle;
and 4, step 4: and displaying the directed graph data and marking error version data.
2. The method as claimed in claim 1, wherein the step 1 further comprises:
the first step is as follows: collecting item and version number information through a unified entry and storing the item and version number information as a dictionary type, wherein a key of the dictionary type is a version number, and corresponding values comprise a system name, a dependent version number, an item identifier and an item state;
the second step is that: acquiring a system version number which is the same as that of the previous step in the current simulation/production environment through an operation and maintenance interface, setting all version sets in the simulation environment as a virtual item, setting a dependent version number of the virtual item to be null, setting an item identifier as the simulation environment, setting an item state to be online, performing the same treatment on all version sets in the production environment, and if other items conflict with data of the simulation production environment, defaulting that simulation production data is correct, other items are wrong, and data of the simulation production environment is the beginning of version number dependence;
the third step: and removing the data which are collected in the first step and comprise the item and version number information from the online item data of which the version number is less than or equal to the version number in the production environment to obtain the screened data.
3. The method as claimed in claim 1, wherein the step 2 further comprises:
on the basis of the screened data in the step 1, capturing version numbers according to systems, sequencing the version numbers of each system according to the monotone increasing principle of the version numbers, and acquiring a version number list by each system;
and checking whether the previous version number of each version number is consistent with the dependent version number one by one for each version number list, and if not, marking the version number as an error, wherein the error type is a version dependent error.
4. The method as claimed in claim 1, wherein the step 3 further comprises:
on the basis of the screened data in the step 1, capturing a version number according to the items, then judging the version size of each two items in an item list, and distinguishing an item X with a conflict of the version sizes and a normal item Y without the conflict;
judging the version sizes of the items in the X and the items in the Y one by one, putting the items in the X, of which the version size conflicts are not found, into the Y, and marking the rest of the X items after processing as errors, wherein the error types are that the versions of different systems are mutually dependent;
and putting the normal item Y into a directed graph, checking whether a ring exists, marking the item Y as an error if the ring exists, wherein the error type is item cyclic dependence, and sorting the item Y according to a depth-first rule if the ring does not exist.
5. The method for checking directed graph ranking of version numbers according to any of the claims 1 to 4, further comprising between step 3 and step 4:
an error is flagged that is less than the production version number and the item status is not on-line/finished, where the error type is on-line but not finished.
6. A version number directed graph sequencing audit system of a multi-project multi-system environment is characterized by comprising:
the acquisition and screening module is used for acquiring data containing project and version number information, then preprocessing the data, and removing invalid data to obtain screened data;
the single-system multi-project version number dependency audit module is used for carrying out dependency audit on the single-system multi-project version numbers and finding out the actual version numbers with dependency errors;
the multi-system multi-project dependence audit module is used for carrying out multi-system multi-project dependence audit, constructing project dependence relations according to version dependence relations, finding out inter-dependent project errors, and then finding out errors of multi-system version number cyclic dependence according to a directed acyclic principle;
and the display module is used for displaying the directed graph data and marking error version data.
7. The version number directed graph ranking audit system of a multi-project multi-system environment of claim 6 wherein the collection screening module is configured to perform the following processing:
the first step is as follows: collecting item and version number information through a unified entry and storing the item and version number information as a dictionary type, wherein a key of the dictionary type is a version number, and corresponding values comprise a system name, a dependent version number, an item identifier and an item state;
the second step is that: acquiring a system version number which is the same as that of the previous step in the current simulation/production environment through an operation and maintenance interface, setting all version sets in the simulation environment as a virtual item, setting a dependent version number of the virtual item to be null, setting an item identifier as the simulation environment, setting an item state to be online, performing the same treatment on all version sets in the production environment, and if other items conflict with data of the simulation production environment, defaulting that simulation production data is correct, other items are wrong, and data of the simulation production environment is the beginning of version number dependence;
the third step: and removing the data which are collected in the first step and comprise the item and version number information from the online item data of which the version number is less than or equal to the version number in the production environment to obtain the screened data.
8. The version number directed graph ordering auditing system of a multi-project multi-system environment according to claim 6 where the single system multi-project version number dependent auditing module is configured to perform the following processing:
on the basis of collecting data output by a screening module, capturing version numbers according to systems, sequencing the version numbers of each system according to the principle that the version numbers are monotonically increased, and acquiring a version number list by each system;
and checking whether the previous version number of each version number is consistent with the dependent version number one by one for each version number list, and if not, marking the version number as an error, wherein the error type is a version dependent error.
9. The version number directed graph ordering auditing system according to claim 6, where a multi-system multi-project dependent auditing module is configured to perform the following processing:
on the basis of collecting the data output by the screening module, capturing the version number according to the items, and then judging the version size of each two items in the item list to distinguish an item X with a conflict of the version sizes from a normal item Y without the conflict;
judging the version sizes of the items in the X and the items in the Y one by one, putting the items in the X, of which the version size conflicts are not found, into the Y, and marking the rest of the X items after processing as errors, wherein the error types are that the versions of different systems are mutually dependent;
and putting the normal item Y into a directed graph, checking whether a ring exists, marking the item Y as an error if the ring exists, wherein the error type is item cyclic dependence, and sorting the item Y according to a depth-first rule if the ring does not exist.
10. The version number directed graph ordering auditing system of a multi-project multi-system environment according to any one of claims 6 to 9, where the system further comprises:
and the error auditing module is used for marking the item which is smaller than the production version number and has the item status of not being on-line/ended as an error, wherein the error type is on-line but not ended.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911118026.5A CN111309370B (en) | 2019-11-15 | 2019-11-15 | Version number directed graph ordering auditing method and system for multi-project multi-system environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911118026.5A CN111309370B (en) | 2019-11-15 | 2019-11-15 | Version number directed graph ordering auditing method and system for multi-project multi-system environment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111309370A true CN111309370A (en) | 2020-06-19 |
| CN111309370B CN111309370B (en) | 2023-08-15 |
Family
ID=71156849
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911118026.5A Active CN111309370B (en) | 2019-11-15 | 2019-11-15 | Version number directed graph ordering auditing method and system for multi-project multi-system environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111309370B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112947896A (en) * | 2021-03-26 | 2021-06-11 | 中国航空无线电电子研究所 | Directed graph-based component dependence analysis method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130227542A1 (en) * | 2012-02-28 | 2013-08-29 | International Business Machines Corporation | Version conflict checking to installable unit |
| CN108334334A (en) * | 2018-03-07 | 2018-07-27 | 政采云有限公司 | A kind of management relies on the method and system of packet version |
| CN108446861A (en) * | 2018-03-28 | 2018-08-24 | 南方电网科学研究院有限责任公司 | Electric power dispatching system multi-source data quality evaluating method based on digraph sequence |
| CN109343841A (en) * | 2018-10-15 | 2019-02-15 | 上海理工大学 | Semantic conflict digestion procedure under real-time collaborative programmed environment |
-
2019
- 2019-11-15 CN CN201911118026.5A patent/CN111309370B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130227542A1 (en) * | 2012-02-28 | 2013-08-29 | International Business Machines Corporation | Version conflict checking to installable unit |
| CN108334334A (en) * | 2018-03-07 | 2018-07-27 | 政采云有限公司 | A kind of management relies on the method and system of packet version |
| CN108446861A (en) * | 2018-03-28 | 2018-08-24 | 南方电网科学研究院有限责任公司 | Electric power dispatching system multi-source data quality evaluating method based on digraph sequence |
| CN109343841A (en) * | 2018-10-15 | 2019-02-15 | 上海理工大学 | Semantic conflict digestion procedure under real-time collaborative programmed environment |
Non-Patent Citations (1)
| Title |
|---|
| 孙清超;郭钢;: "面向多产品协同开发的项目管理研究" * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112947896A (en) * | 2021-03-26 | 2021-06-11 | 中国航空无线电电子研究所 | Directed graph-based component dependence analysis method |
| CN112947896B (en) * | 2021-03-26 | 2023-10-27 | 中国航空无线电电子研究所 | Directed graph-based component dependency analysis method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111309370B (en) | 2023-08-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110175165A (en) | Transaction account checking method, device, computer equipment and storage medium | |
| CN111510468B (en) | Scheduling method and device of computing task, server and computing system | |
| JP2017091329A (en) | Database analysis device and database analysis method | |
| US11086906B2 (en) | System and method for reconciliation of data in multiple systems using permutation matching | |
| JP6419667B2 (en) | Test DB data generation method and apparatus | |
| CN112579621A (en) | Data display method and device, electronic equipment and computer storage medium | |
| CN111309370A (en) | Version number directed graph sorting audit method and system for multi-project and multi-system environment | |
| CN114219596A (en) | Data processing method based on decision tree model and related equipment | |
| CN103092864A (en) | Method and system for generating test data report form | |
| CN111651500A (en) | User identity recognition method, electronic device and storage medium | |
| CN108427675A (en) | Build the method and apparatus of index | |
| CN108804561B (en) | Data synchronization method and device | |
| CN110781235A (en) | Big data based purchase data processing method and device, terminal and storage medium | |
| CN112256978B (en) | Data processing method, device and medium based on data model | |
| CN115543265A (en) | Method and system for shortening new commodity shelf life | |
| CN113610452B (en) | Method, system, equipment and medium for managing key piece materials | |
| CN112559641B (en) | Pull chain table processing method and device, readable storage medium and electronic equipment | |
| CN114356374A (en) | Vehicle data processing method and device and vehicle | |
| CN113780950A (en) | Data processing method, device, server and readable storage medium | |
| CN114511314A (en) | Payment account management method and device, computer equipment and storage medium | |
| CN113138990A (en) | Data blood margin construction and tracing method, device and equipment | |
| CN111723007A (en) | Test case merging method, system, equipment and medium | |
| US11256708B2 (en) | Method of creating process protocols | |
| CN111563092B (en) | Public service data updating method and device | |
| CN109002287B (en) | Management method and device for software in cloud data system |
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 |