CN112950138B - Collaborative development state management method, device and server - Google Patents
Collaborative development state management method, device and server Download PDFInfo
- Publication number
- CN112950138B CN112950138B CN202010953951.6A CN202010953951A CN112950138B CN 112950138 B CN112950138 B CN 112950138B CN 202010953951 A CN202010953951 A CN 202010953951A CN 112950138 B CN112950138 B CN 112950138B
- Authority
- CN
- China
- Prior art keywords
- user
- information
- development
- characteristic
- data information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000011161 development Methods 0.000 title claims abstract description 136
- 238000007726 management method Methods 0.000 title abstract description 14
- 238000012545 processing Methods 0.000 claims abstract description 57
- 238000004891 communication Methods 0.000 claims abstract description 30
- 238000012360 testing method Methods 0.000 claims description 59
- 238000000034 method Methods 0.000 claims description 49
- 238000004590 computer program Methods 0.000 claims description 21
- 238000010276 construction Methods 0.000 claims description 9
- 238000012986 modification Methods 0.000 claims description 5
- 230000004048 modification Effects 0.000 claims description 5
- 230000008439 repair process Effects 0.000 claims description 4
- 230000008569 process Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000007667 floating Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000002195 synergetic effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/101—Collaborative creation, e.g. joint development of products or services
Landscapes
- Business, Economics & Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Stored Programmes (AREA)
Abstract
The application is in the field of software development, and provides a collaborative development state management method, device and server, which comprise the following steps: acquiring development data information sent by a first user; determining a second user cooperatively processing the development data information according to the development data information provided by the first user; and updating the processing items corresponding to the development data information to a page registered by the second user, and sending the state information of the processing item update to the communication terminal corresponding to the second user. The second user can acquire the updated state information timely, and the data to be processed can be acquired conveniently through the login page of the second user, so that the collaborative development efficiency can be effectively improved.
Description
Technical Field
The application belongs to the field of software development, and particularly relates to a state management method, device and server for collaborative development.
Background
In a software development or software upgrade process, cooperation work of a plurality of developers and testers is generally required. Moreover, the work of the testers often has a sequential connection, for example, after the developer develops the code, the testers need to test. After the tester finishes the test, the test result needs to be fed back to the developer, and the developer adjusts the test result.
In the current process of work engagement and cooperation, after the previous work item is completed, the current state information is usually notified to the next cooperator by using instant communication tools of both parties or an offline communication mode. In the development process, the update of the state information is possibly omitted because the update process of the state information is troublesome, which is unfavorable for improving the collaborative development efficiency.
Disclosure of Invention
In view of this, the embodiments of the present application provide a method, an apparatus, and a server for collaborative development of state management, so as to solve the problems in the prior art.
A first aspect of an embodiment of the present application provides a method for managing states of collaborative development, where the method includes:
acquiring development data information sent by a first user;
determining a second user cooperatively processing the development data information according to the development data information provided by the first user;
and updating the processing items corresponding to the development data information to a page registered by the second user, and sending the state information of the processing item update to the communication terminal corresponding to the second user.
With reference to the first aspect, in a first possible implementation manner of the first aspect, before acquiring the development data information that is provided by the first user, the method further includes:
receiving a characteristic development request sent by a third user, wherein the characteristic development request comprises a project name associated with the request, a first user for developing the characteristic and demand information;
creating a characteristic branch in a database warehouse corresponding to the project name, and generating a characteristic development task corresponding to the characteristic development request;
and updating the state information and the demand information of the characteristic branch development to a page which is logged in by the first user, and sending the state information of the characteristic branch development to a communication terminal corresponding to the first user.
With reference to the first aspect, in a second possible implementation manner of the first aspect, after sending status information of the transaction update to a communication terminal corresponding to the second user, the method further includes:
receiving a characteristic merging request of a second user, and merging the development data information with a corresponding database warehouse;
testing and constructing the combined data;
and performing characteristic test according to the data after the test construction processing.
With reference to the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, after performing a characteristic test according to the data after the test construction process, the method further includes:
if the development data information subjected to the test construction processing passes the characteristic test, setting a characteristic branch corresponding to the development data information to be in a protected state of prohibiting modification;
if the development data information after the test construction processing does not pass the characteristic test, fault information is fed back to a page logged in by the first user, and state information of test feedback is sent to a communication terminal corresponding to the first user.
With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, if the development data information passes a characteristic test, the method further includes:
combining a plurality of data development information;
and carrying out pre-release test on the combined data, and updating the state information of the page logged in by the first user according to the pre-release test result.
With reference to the first aspect, the first possible implementation manner of the first aspect, the second possible implementation manner of the first aspect, the third possible implementation manner of the first aspect, or the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the development data information is characteristic data corresponding to an iterative development version or characteristic data corresponding to a thermal repair development.
With reference to the first aspect, in a sixth possible implementation manner of the first aspect, determining, according to development data information provided by the first user, a second user that cooperatively processes the development data information includes:
determining a second user appointed by cooperatively processing the development data information according to the set tester in the development data information;
or determining a second user for processing the development data information according to the characteristic information corresponding to the development data information.
A second aspect of embodiments of the present application provides a cooperatively developed state management apparatus, the apparatus including:
the information acquisition unit is used for acquiring development data information sent by a first user;
the second user determining unit is used for determining a second user cooperatively processing the development data information according to the development data information submitted by the first user;
and the state updating unit is used for updating the processing items corresponding to the development data information to the page registered by the second user and sending the state information updated by the processing items to the communication terminal corresponding to the second user.
A third aspect of the embodiments of the present application provides a server comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method according to any one of the first aspects when the computer program is executed.
A fourth aspect of the embodiments of the present application provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the steps of the method according to any one of the first aspects.
Compared with the prior art, the embodiment of the application has the beneficial effects that: after the server acquires the development data information of the first user, a second user cooperatively processing the development data information is determined according to the development data information of the first user, the state information of the processing items is updated through the login page of the second user, and the state information updated through the processing items is displayed on the corresponding communication terminal, so that the second user can acquire the updated state information timely, and the data to be processed can also be acquired conveniently through the login page of the second user, thereby effectively improving the efficiency of the collaborative development.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required for the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic implementation flow diagram of a collaborative state management method according to an embodiment of the present application;
FIG. 2 is a schematic flow chart of an implementation of generating a feature branch development according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a cooperatively developed state management device according to an embodiment of the present application;
fig. 4 is a schematic diagram of a server provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to illustrate the technical solutions described in the present application, the following description is made by specific examples.
Fig. 1 is a schematic implementation flow diagram of a collaborative development state management method according to an embodiment of the present application, which is described in detail below:
s101, acquiring development data information which is sent by a first user.
The first user, the second user and the third user mentioned later refer to different types of users. For example, the first user, the second user, or the third user may be a code developer, a code tester, a project manager, or the like. Different types of users can log in a platform or a server for collaborative development in interfaces such as a webpage through account signals, and state information of project tasks corresponding to the users is checked in the webpage.
Wherein project manager can create new feature requirements for project or software in the logged page according to customer requirements, or software update requirements. The code developer can carry the local code to a server or platform after the code data writing is completed locally according to the created characteristic requirements. After receiving the test notification, the code tester can perform characteristic test, pre-release test and the like on the code data proposed by the code developer, and determine whether to release or return modification according to the test result.
The development data information may be different according to the type of the first user and the current stage.
For example, when the first user is a project manager, the development data information may be development request information for a characteristic of a project or software. When the first user is a code developer, the development data information may be code data corresponding to software characteristics written by the developer. When the first user is a code tester, the development data information may be test result information of the code, for example, may include a code failure problem, and the like.
The development data information may be characteristic data corresponding to the iterative development version, or may also be characteristic data corresponding to the thermal repair development.
S102, determining a second user cooperatively processing the development data information according to the development data information provided by the first user.
When the server receives the development data information sent by the first user, a second user needing to trigger the collaborative process can be determined according to the development data information sent by the first user.
For example, when development data information sent by the first user is received as code data, the second user is a code tester for testing the code data. When the development data information provided by the first user is a test result, the second user can be a code developer. When the development data information provided by the first user is the characteristic development request information of the software or the project, the second user may be a code developer or the like.
In a possible implementation, the second user specified by the first user may also be included when developing the data information presented by the first user. The second user is determined according to the designation information included in the development data information.
Alternatively, in a possible implementation, each user has a specific user type, such as a user type of code developer, project manager, or code tester. The second user may comprise a plurality of users. For example, when a project or a characteristic requirement of software is created, it may be determined that the second user is a user of all code developer types.
Or in a possible implementation manner, the user type required to cooperate with the development data information can be obtained first, and the working state information of the searched user can be obtained after searching all users belonging to the user type according to the determined user type. The working state information of the user comprises historical working record information of the user, workload information of the user and the like. The history information of the user includes the user's characteristic processing experience, processing efficiency, and the like. And selecting a better user as a second user according to the working state information of the user and combining the weight corresponding to the workload information and the working record information of the user.
And S103, updating the processing items corresponding to the development data information to a page registered by the second user, and sending the state information of the processing item update to the communication terminal corresponding to the second user.
When determining to process the second user corresponding to the development data information provided by the first user, the item of processing the development data information provided by the first user may be displayed in the page on which the second user logs in. For example, a feature request list submitted by a project or software manager, or a code test list submitted by a code developer, or a list of code test feedback submitted by a code tester may be displayed in a page registered by the second user. When the second user is in the login state, the list information can be updated in the login page, and an update information reminder, such as a floating window for generating update information, can be generated.
In the page logged in by the second user, specific content of the development data information can be checked in a clicking or downloading mode according to the updated list information, so that maintenance and management of the development data information by the first user and the second user are facilitated.
The processing item is updated in the page registered by the second user, and the status information of the processing item update may be sent to the communication terminal corresponding to the second user.
The communication terminal corresponding to the second user may be a communication terminal logged in by the instant communication tool of the second user, and the status information updated by the processing item is sent to the instant communication tool of the second user.
Or the communication terminal installed with the mobile communication number of the second user sends a voice or short message reminder to the mobile communication number of the second user, such as to the mobile phone number of the second user.
Therefore, in the embodiment of the application, after the first user submits the development data information, the second user needing to cooperate can update the processing items on the logged-in page, and the communication terminal corresponding to the second user receives the status information updated by the processing items, so that the second user can more reliably acquire the processing item update information, and the processing efficiency of the collaborative development is improved.
In a possible implementation manner, when the second user does not process the item at all times, reminding information of the item processing can be sent to the second user according to the emergency degree of the item. Alternatively, when the item is unprocessed for a predetermined period of time and the second user includes a plurality of users, the attribute of the item to be processed may be modified to any one of the plurality of users to be a specified single user, and status information specifying the processing of the item may be transmitted to the specified user. Thereby facilitating more efficient synergistic processing of the event.
In a possible implementation manner of the present application, when acquiring development data information that is sent by the first user as code development data, a task creation flow as shown in fig. 2 may be further included before the development data information is acquired, where the task creation flow includes:
s201, a characteristic development request sent by a third user is received, wherein the characteristic development request comprises a project name associated with the request, a first user who develops the characteristic and requirement information.
The third user may be the same as the first user or may be different from the first user. For example, the third user may be a code developer when the third user is the same as the first user. Or, the third user may be a project manager, and receive a feature development request from the project manager to obtain a project name to be developed, a first user who develops the feature, and requirement information.
The project name is used for determining software or projects to which the characteristics to be developed belong. The demand information may be characteristic information of a thermal repair or a daily iteration of the software.
S202, creating a characteristic branch in a database warehouse corresponding to the project name, and generating a characteristic development task corresponding to the characteristic development request.
After receiving the property development request, a property branch is created in the corresponding database warehouse according to the project name, so that code data written by the first user can be received and stored in the property branch conveniently.
And S203, updating the state information and the demand information of the characteristic branch development to a page on which the first user logs in, and sending the state information of the characteristic branch development to a communication terminal corresponding to the first user.
According to the generated characteristic development task, the characteristic development task can be updated to a page which is logged in by the first user, and state information of characteristic branch development is sent to a communication terminal corresponding to the first user, so that the first user can timely know characteristic branch information which needs collaborative development.
In this embodiment of the present application, after the second user performs the merging process according to the logged page or the state information of the corresponding communication terminal, the second user may receive the code data of the characteristic branch sent by the second user, merge the code data of the characteristic branch with the data in the database warehouse, and then automatically trigger, or perform the characteristic test on the data code after the merging process by means of the triggering of the second user.
After the test is completed, the test result may be sent to the second user, and the second user may determine whether to return the first user to modify the code data according to the test result. If the development data information after the test construction processing passes the characteristic test, the characteristic branch corresponding to the development data information can be set to be in a protected state of prohibiting modification, the tested characteristic branch is prevented from being modified, and the reliability of the characteristic branch operation is improved.
If the development data information after the test construction processing does not pass the characteristic test, fault information can be fed back to a page logged in by the first user, and state information of test feedback can be sent to a communication terminal corresponding to the first user. Therefore, the first user can timely know the test result of the code data with the characteristic branches, and the code data is adjusted according to the feedback result.
In a possible implementation manner of the application, if the development data information passes the characteristic test, the method can further comprise a pre-release test process for the development data information.
Specifically, two or more data development information may be combined, and the combined data may be pre-distributed and debugged. After the test is completed, the state information of the page logged in by the first user is updated according to the test result of the pre-release test. For example, after passing the pre-release test, the test may be displayed on the page on which the first user is logged in, or the released status information may be displayed. Or, when the pre-release test is passed, the reminding information of the state update can be sent to the communication terminal corresponding to the first user.
It will be appreciated that the users of the property test and the pre-release test may also be different users.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not limit the implementation process of the embodiment of the present application in any way.
Fig. 3 is a schematic diagram of a cooperatively developed state management device according to an embodiment of the present application, where the device includes:
an information obtaining unit 301, configured to obtain development data information sent by a first user;
a second user determining unit 302, configured to determine a second user cooperatively processing development data information according to the development data information submitted by the first user;
and the state updating unit 303 is configured to update the processing item corresponding to the development data information to a page registered by the second user, and send the state information of the processing item update to the communication terminal corresponding to the second user.
The state management apparatus for collaborative development shown in fig. 3 corresponds to the state management method for collaborative development shown in fig. 1.
Fig. 4 is a schematic diagram of a server according to an embodiment of the present application. As shown in fig. 4, the server 4 of this embodiment includes: a processor 40, a memory 41 and a computer program 42 stored in the memory 41 and executable on the processor 40, such as a co-developed state management program. The processor 40, when executing the computer program 42, implements the steps of the various co-developed state management method embodiments described above. Alternatively, the processor 40, when executing the computer program 42, performs the functions of the modules/units of the apparatus embodiments described above.
Illustratively, the computer program 42 may be partitioned into one or more modules/units that are stored in the memory 41 and executed by the processor 40 to complete the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing a specific function describing the execution of the computer program 42 in the server 4.
The server 4 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, etc. The server may include, but is not limited to, a processor 40, a memory 41. It will be appreciated by those skilled in the art that fig. 4 is merely an example of the server 4 and is not meant to be limiting as the server 4 may include more or fewer components than shown, or may combine certain components, or different components, e.g., the server may further include input and output devices, network access devices, buses, etc.
The processor 40 may be a central processing unit (Central Processing Unit, CPU), other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 41 may be an internal storage unit of the server 4, such as a hard disk or a memory of the server 4. The memory 41 may be an external storage device of the server 4, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the server 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the server 4. The memory 41 is used for storing the computer program as well as other programs and data required by the server. The memory 41 may also be used for temporarily storing data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. 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 application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other manners. For example, the apparatus/terminal device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each method embodiment described above. . Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium may include content that is subject to appropriate increases and decreases as required by jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is not included as electrical carrier signals and telecommunication signals.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.
Claims (10)
1. A method of state management for collaborative development, the method comprising:
the method comprises the steps that a server obtains development data information sent by a first user;
the server determines a second user cooperatively processing the development data information according to the development data information submitted by the first user, and specifically comprises the following steps: acquiring a user type which needs to cooperate with the development data information, searching all users belonging to the user type according to the determined user type, acquiring the working state information of the searched users, wherein the working state information of the users comprises historical working record information of the users and working load information of the users, the historical working record information of the users comprises characteristic processing experience and processing efficiency of the users, and selecting a second user according to the working state information of the users and combining the working load information of the users and weights corresponding to the working record information;
and the server updates the processing items corresponding to the development data information to a page registered by the second user, and sends the state information of the processing item update to the communication terminal corresponding to the second user.
2. The method of claim 1, wherein prior to obtaining the development data information submitted by the first user, the method further comprises:
receiving a characteristic development request sent by a third user, wherein the characteristic development request comprises a project name associated with the request, a first user for developing the characteristic and demand information;
creating a characteristic branch in a database warehouse corresponding to the project name, and generating a characteristic development task corresponding to the characteristic development request;
and updating the state information and the demand information of the characteristic branch development to a page which is logged in by the first user, and sending the state information of the characteristic branch development to a communication terminal corresponding to the first user.
3. The method according to claim 1, wherein after transmitting the status information of the transaction update to the communication terminal corresponding to the second user, the method further comprises:
receiving a characteristic merging request of a second user, and merging the development data information with a corresponding database warehouse;
testing and constructing the combined data;
and performing characteristic test according to the data after the test construction processing.
4. A method according to claim 3, wherein after the performance testing from the test build processed data, the method further comprises:
if the development data information subjected to the test construction processing passes the characteristic test, setting a characteristic branch corresponding to the development data information to be in a protected state of prohibiting modification;
if the development data information after the test construction processing does not pass the characteristic test, fault information is fed back to a page logged in by the first user, and state information of test feedback is sent to a communication terminal corresponding to the first user.
5. The method of claim 4, wherein if the development data information passes a characteristic test, the method further comprises:
combining a plurality of data development information;
and carrying out pre-release test on the combined data, and updating the state information of the page logged in by the first user according to the pre-release test result.
6. The method according to any one of claims 1 to 5, wherein the development data information is characteristic data corresponding to an iterative development version or characteristic data corresponding to a thermal repair development.
7. The method of claim 1, wherein determining a second user who co-processes the development data information based on the development data information provided by the first user comprises:
determining a second user appointed by cooperatively processing the development data information according to the set tester in the development data information;
or determining a second user for processing the development data information according to the characteristic information corresponding to the development data information.
8. A co-developed state management apparatus, the apparatus comprising:
the information acquisition unit is used for acquiring development data information sent by a first user by the server;
the second user determining unit is used for determining a second user cooperatively processing the development data information according to the development data information sent by the first user by the server, and specifically comprises the following steps: acquiring a user type which needs to cooperate with the development data information, searching all users belonging to the user type according to the determined user type, acquiring the working state information of the searched users, wherein the working state information of the users comprises historical working record information of the users and working load information of the users, the historical working record information of the users comprises characteristic processing experience and processing efficiency of the users, and selecting a second user according to the working state information of the users and combining the working load information of the users and weights corresponding to the working record information;
and the state updating unit is used for updating the processing items corresponding to the development data information to the page registered by the second user by the server and sending the state information of the processing item update to the communication terminal corresponding to the second user.
9. A server comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 7 when the computer program is executed.
10. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010953951.6A CN112950138B (en) | 2020-09-11 | 2020-09-11 | Collaborative development state management method, device and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010953951.6A CN112950138B (en) | 2020-09-11 | 2020-09-11 | Collaborative development state management method, device and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112950138A CN112950138A (en) | 2021-06-11 |
| CN112950138B true CN112950138B (en) | 2024-03-12 |
Family
ID=76234571
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010953951.6A Active CN112950138B (en) | 2020-09-11 | 2020-09-11 | Collaborative development state management method, device and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112950138B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102456177A (en) * | 2010-10-27 | 2012-05-16 | 镇江华扬信息科技有限公司 | Software project management system |
| US9483259B1 (en) * | 2012-05-07 | 2016-11-01 | Google Inc. | System and method for providing real-time execution of source code in a collaborative online software development environment |
| CN106355318A (en) * | 2016-08-29 | 2017-01-25 | 深圳市中润四方信息技术有限公司 | Information release processing method and system |
| CN107679818A (en) * | 2017-05-10 | 2018-02-09 | 平安科技（深圳）有限公司 | Software project management method, terminal and computer-readable recording medium |
| CN108492005A (en) * | 2018-02-26 | 2018-09-04 | 平安普惠企业管理有限公司 | Project data processing method, device, computer equipment and storage medium |
| CN108537503A (en) * | 2018-03-26 | 2018-09-14 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | software development management system |
| CN108876201A (en) * | 2018-07-24 | 2018-11-23 | 武汉空心科技有限公司 | Development approach, platform and the system quickly delivered |
| CN109683859A (en) * | 2018-12-04 | 2019-04-26 | 郑州云海信息技术有限公司 | A kind of computer software development management platform, equipment and readable storage medium storing program for executing |
| CN110471859A (en) * | 2019-09-12 | 2019-11-19 | 泰康保险集团股份有限公司 | Service test method, device, medium and electronic equipment |
| CN111190824A (en) * | 2019-12-28 | 2020-05-22 | 中国平安人寿保险股份有限公司 | Monitoring method, monitoring device, terminal equipment and storage medium |
| CN111352747A (en) * | 2020-02-20 | 2020-06-30 | 深圳壹账通智能科技有限公司 | Cooperative operation method and device |
| CN111598428A (en) * | 2020-05-12 | 2020-08-28 | 远光软件股份有限公司 | Method and device for managing process nodes, storage medium and server |
-
2020
- 2020-09-11 CN CN202010953951.6A patent/CN112950138B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102456177A (en) * | 2010-10-27 | 2012-05-16 | 镇江华扬信息科技有限公司 | Software project management system |
| US9483259B1 (en) * | 2012-05-07 | 2016-11-01 | Google Inc. | System and method for providing real-time execution of source code in a collaborative online software development environment |
| CN106355318A (en) * | 2016-08-29 | 2017-01-25 | 深圳市中润四方信息技术有限公司 | Information release processing method and system |
| CN107679818A (en) * | 2017-05-10 | 2018-02-09 | 平安科技（深圳）有限公司 | Software project management method, terminal and computer-readable recording medium |
| CN108492005A (en) * | 2018-02-26 | 2018-09-04 | 平安普惠企业管理有限公司 | Project data processing method, device, computer equipment and storage medium |
| CN108537503A (en) * | 2018-03-26 | 2018-09-14 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | software development management system |
| CN108876201A (en) * | 2018-07-24 | 2018-11-23 | 武汉空心科技有限公司 | Development approach, platform and the system quickly delivered |
| CN109683859A (en) * | 2018-12-04 | 2019-04-26 | 郑州云海信息技术有限公司 | A kind of computer software development management platform, equipment and readable storage medium storing program for executing |
| CN110471859A (en) * | 2019-09-12 | 2019-11-19 | 泰康保险集团股份有限公司 | Service test method, device, medium and electronic equipment |
| CN111190824A (en) * | 2019-12-28 | 2020-05-22 | 中国平安人寿保险股份有限公司 | Monitoring method, monitoring device, terminal equipment and storage medium |
| CN111352747A (en) * | 2020-02-20 | 2020-06-30 | 深圳壹账通智能科技有限公司 | Cooperative operation method and device |
| CN111598428A (en) * | 2020-05-12 | 2020-08-28 | 远光软件股份有限公司 | Method and device for managing process nodes, storage medium and server |
Non-Patent Citations (2)
| Title |
|---|
| Zerrouk, M等.Managing model conflicts in collaborative modeling using Constraint Programming.2018 IEEE 5TH INTERNATIONAL CONGRESS ON INFORMATION SCIENCE AND TECHNOLOGY (IEEE CIST'18).2018,第117-123页. * |
| 基于系统重构的内控管理平台设计与开发;陈龙;万方中国学位论文数据库;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112950138A (en) | 2021-06-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210240604A1 (en) | Api driven continuous testing systems for testing disparate software | |
| CN115812298A (en) | Block chain management of supply failure | |
| CN114185900B (en) | Service data processing method, device, computer equipment and storage medium | |
| CN110865806B (en) | Code processing method, device, server and storage medium | |
| CN103440460A (en) | Application system change validation method and system | |
| CN111459629A (en) | Azkaban-based project operation method and device and terminal equipment | |
| US11347533B2 (en) | Enhanced virtual machine image management system | |
| CN112445860B (en) | Method and device for processing distributed transaction | |
| CN112950138B (en) | Collaborative development state management method, device and server | |
| CN109814911A (en) | Method, apparatus, computer equipment and storage medium for Manage Scripts program | |
| CN115587041A (en) | Mobile application delivery task processing method and device, electronic equipment and storage medium | |
| CN113918525A (en) | Data exchange scheduling method, system, electronic device, medium, and program product | |
| EP3206173A1 (en) | Systems and methods for generating blueprints for enterprises | |
| CN113011858A (en) | Audit project configuration and execution method and device | |
| CN113935847A (en) | Online process risk processing method, device, server and medium | |
| US20200097870A1 (en) | Work task commitment manager | |
| CN111475291A (en) | Data processing method, system, server and medium | |
| CN110650063A (en) | Centralized bank third-party software simulation system and method | |
| CN112799797A (en) | Task management method and device | |
| CN115496470A (en) | Full-link configuration data processing method and device and electronic equipment | |
| CN117520299A (en) | Data processing method, device, equipment and medium during migration of financial system | |
| CN117520196A (en) | Verification method, device and system for flow configuration file based on flow engine | |
| CN115658623A (en) | Batch data import method and device, storage medium and computer equipment | |
| CN115460077A (en) | Configuration information updating method and device, storage medium and electronic device | |
| CN114266547A (en) | Method, device, equipment, medium and program product for identifying business processing strategy |
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 |