KR101390220B1 - Method for recommending appropriate developers for software bug fixing and apparatus thereof - Google Patents
Method for recommending appropriate developers for software bug fixing and apparatus thereof Download PDFInfo
- Publication number
- KR101390220B1 KR101390220B1 KR1020120125615A KR20120125615A KR101390220B1 KR 101390220 B1 KR101390220 B1 KR 101390220B1 KR 1020120125615 A KR1020120125615 A KR 1020120125615A KR 20120125615 A KR20120125615 A KR 20120125615A KR 101390220 B1 KR101390220 B1 KR 101390220B1
- Authority
- KR
- South Korea
- Prior art keywords
- debugging
- developer
- bug
- bug report
- class
- Prior art date
Links
- 230000000875 corresponding Effects 0.000 claims abstract description 25
- 206010057190 Respiratory tract infection Diseases 0.000 claims 2
- 238000000034 method Methods 0.000 description 4
- 238000010276 construction Methods 0.000 description 3
- 238000003064 k means clustering Methods 0.000 description 2
- 239000000203 mixture Substances 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000007619 statistical method Methods 0.000 description 2
- 241000687904 Soa Species 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006011 modification reaction Methods 0.000 description 1
- 230000003287 optical Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3608—Software analysis for verifying properties of programs using formal methods, e.g. model checking, abstract interpretation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/366—Software debugging using diagnostics
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/01—Social networking
Abstract
Description
The present invention relates to a developer recommendation technique for software bug correction, and more particularly, to a method and apparatus for correcting a bug using a social network of developers based on the possibility of software bug correction when a bug report occurs.
The present invention is derived from the research conducted as part of the Basic Research Project-General Researcher Support Project-Basic Research Support Project (Type I) of the Ministry of Education, Science and Technology and the Korea Research Foundation. [Task Management Number: 20120007149, Project Name: AOP SOA-based Framework of Reliable Agent Applications]
In information processing devices called so-called built-in devices such as information appliances and mobile phones, the software scale is increasing. By adding functions for network correspondence and increasing user demand, it is required to realize many new functions in a short time by using software. With such an increase in the size of the software, it is required to secure the quality of the software, and a countermeasure against a bug caused by this is also required.
In addition, embedded systems, such as switching systems, home appliances, and mobile terminals, provide a variety of processors and software modules. You must go through the debugging process to detect and heal the bug through the test of.
When a number of developers develop a conventional embedded system, information about a bug detected through a test on an embedded chip inside the embedded system is output in a debug message form. If a bug is detected without generating an optional debug message according to the developer's requirements, such as selective extraction of a debug message or a module for which the debug message is to be checked, the debug message is set to be output uniformly. Assigned directly to the developer to fix the bug.
As such, an example of the related art for selecting a developer that can increase efficiency for bug correction is illustrated in Korean Patent Laid-Open Publication No. 10-2006-0066912 entitled "Method for outputting a debug message when debugging a mobile communication terminal". When a number of developers debug each module of the mobile communication terminal, a debugging message including bug information detected as a result of the debugging is selectively outputted by each developer, module, and port. By doing so, it was derived with the purpose of checking the debug message output according to the developer's requirements.
However, even with the above prior art, when a bug report generated in software is not assigned to an appropriate developer, a problem arises in that the software development cost is increased by increasing the time and cost of bug correction.
The present invention is derived to solve the above problems of the prior art, the purpose of utilizing a combination of developers' experience and past correction costs to utilize the social network of developers based on the possibility of software bug correction and to rank the developer candidates to be.
Specifically, the invention converts the bug report into a vector representation when a new bug report is submitted to the database. Subsequently, the SVM (Support Vector Machine) is applied to search for a class including similar bug reports, and the settling time and the developer's characteristics are extracted from the reports belonging to the class. The extracted features are used to build a social network of developers and select debugging developers. In addition, it aims to provide a method and apparatus for collecting debugging-related characteristic information of debugging developers included in social networks, and using the same to set priorities for debugging developers.
In order to achieve the above object, the debugging developer recommendation method and apparatus according to an embodiment of the present invention includes a bug report receiving unit, class search unit, social network construction unit, debugging developer recommendation unit.
The bug report receiving unit receives a bug report generated when a bug occurs in a software program.
The class searching unit searches for a class including at least one or more similar bug reports corresponding to the bug report received in the bug report receiving unit among the classes previously stored in the database.
In this case, the bug report may be converted into a vector representation, and a class including a similar bug report corresponding to the bug report converted into the vector representation may be searched using a support vector machine (SVM).
The social network building unit builds a social network about the connection relationship between the class bug reports using the class bug reports retrieved by the class searching unit.
Finally, the debugging developer recommendation section recommends debugging developers who respond to bug reports based on the social networks built in the social network building section.
In this case, it may be recommended in consideration of the number of bug report correction times and the bug report correction time stored in advance for each of the debugging developers included in the social network.
The present invention utilizes the developer's social network based on the possibility of software bug correction, and combines the developer's experience and past correction costs to rank the developer candidates to develop an appropriate developer recommendation technique for software bug correction, thereby improving the software development cost. There is an advantage to saving.
In addition, developers who develop large software can recommend appropriate developers to correct software bugs according to the developer's characteristics to reduce the debugging time of the software and improve the quality of software development.
1 is a flowchart illustrating a debugging developer recommendation corresponding to a bug report according to an exemplary embodiment of the present invention.
2 is a flowchart illustrating a search for a class including a similar bug report according to an exemplary embodiment of the present invention.
3 is a flowchart illustrating a recommendation of a debugging developer according to an exemplary embodiment of the present invention.
4 illustrates a conceptual configuration of a debugging developer recommendation apparatus corresponding to a bug report according to an embodiment of the present invention.
5 illustrates a conceptual configuration of a class search unit according to an embodiment of the present invention.
6 illustrates a conceptual configuration of a debugging developer recommendation unit according to an embodiment of the present invention.
7 illustrates a conceptual configuration of an algorithm for searching for a class including a similar bug report using an SVM according to an embodiment of the present invention.
8 illustrates a conceptual configuration of a social network according to an embodiment of the present invention.
Other objects and features of the present invention will become apparent from the following description of embodiments with reference to the accompanying drawings.
Preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.
However, the present invention is not limited to or limited by the embodiments. Like reference symbols in the drawings denote like elements.
1 is a flowchart illustrating a debugging developer recommendation corresponding to a bug report according to an exemplary embodiment of the present invention.
When a bug occurs from the software program, the generated bug report is received (S110). Subsequently, the class including the most similar pseudo bug report corresponding to the received bug report among the classes previously stored in the database is searched (S120). At this time, the class pre-stored in the database may include information related to the bug report and information related to the debugging developer in advance. In addition, the most similar bug report may refer to a bug report with the highest similarity, and may include at least one or more similar bug reports with high similarity.
Subsequently, a social network for connection relations between class bug reports is constructed using class bug reports included in the retrieved class (S130). At this time, the social network sets each of the developers included in the class bug reports as a node, and the node corresponding to the developers in consideration of the total number of requests for debugging in each of the configured nodes and the frequency of requesting debugging in each of the remaining nodes. Acquiring a connection relationship between the two, and using the connection relationship between the acquired nodes can build a social network.
After that, the debugging developer corresponding to the bug report is recommended based on the established social network (S140). In this case, step S140 may recommend the debugging developer in consideration of the number of bug report correction times and the bug report correction time stored in advance for each of the debugging developers included in the social network.
2 is a flowchart illustrating a search for a class including a similar bug report according to an exemplary embodiment of the present invention.
The method of searching for a class including a similar bug report converts a bug report generated from a software program into a vector representation (S121). At this time, the bug report can be processed into a natural language and converted into a vector representation.
Subsequently, the class including the most similar pseudo bug report corresponding to the bug report converted into the vector representation is searched using the support vector machine (SVM) (S122).
In this case, a method of measuring similarity between the bug report converted to the vector representation and the similar bug reports corresponding thereto may be expressed by Equation 1.
[Equation 1]
here
Also,
&Quot; (2) "
here
The similarity of the title and description of the bug report is then measured to find the class that contains the bug report. In this case, a method of measuring the similarity between the bug report and the similar bug report may be expressed by Equation 3.
&Quot; (3) "
here
3 is a flowchart illustrating a recommendation of a debugging developer according to an exemplary embodiment of the present invention.
Extracting at least one debugging developer who can debug a bug report from the debugging developers in the social network built by using the class bug reports in the class including the similar bug report (S141).
Subsequently, the priority of the extracted debugging developer is set using the previously stored debugging related property information for the extracted at least one debugging developer (S142). In this case, priorities may be set in consideration of preset weights for each of the extracted debugging developers, and the weights may be included in debugging related property information, but are not limited thereto and may be stored as separate information from debugging related property information. It may be. In addition, by comparing the weight of each of the debugging developers with a preset reference value, the debugging developer having a weight less than or equal to the reference value may be excluded from the priority.
Here, the weight is given to each of the many debugging developers by the experts who have a lot of experience in debugging the bug report in the relevant field, for example, a score from 1 to 5 is relatively given. For example, a debugging developer having a score less than or equal to two points by comparing two points may be excluded from the priority.
Of course, the weights assigned to each of the debugging developers may be preset and stored, and the stored weights may be continuously updated based on statistical analysis or expert opinion.
Further, as a method of setting the priorities of the debugging developers in step S142, the components of the debugging-related characteristic information for each of the debugging developers, for example, the number of similar bug report corrections, the debugging time, the source code type, the debugging cost, etc. Each of the components may be given a preset weight for each component, and the priority may be set based on a calculated value by assigning a weight to each component. Of course, the method of setting the priority is not limited to the above-described techniques, and may include any method applicable to the present invention.
After that, the debugging developer corresponding to the bug report is recommended in consideration of the set priority (S143).
4 illustrates a conceptual configuration of a debugging developer recommendation apparatus corresponding to a bug report according to an embodiment of the present invention.
The debugging developer recommendation device 400 may be represented by a bug report receiver 410, a class search unit 420, a social network construction unit 430, and a debugging developer recommendation unit 440.
The bug report receiving unit 410 receives a bug report on a bug generated from a software program.
The class retrieval unit 420 retrieves a class including the most similar pseudo bug report corresponding to the bug report received by the bug report receiving unit 410 among the classes previously stored in the database.
The social network builder 430 builds a social network for the connection relationship between the class bug reports by using the class bug reports included in the class retrieved by the class search unit 420. At this time, the social network sets each of the developers included in the class bug reports as a node, and the node corresponding to the developers in consideration of the total number of requests for debugging in each of the configured nodes and the frequency of requesting debugging in each of the remaining nodes. Acquiring a connection relationship between them, and building the social network using the obtained connection relationship between the nodes.
The debugging developer recommendation unit 440 recommends a debugging developer corresponding to the bug report received by the bug report receiving unit 410 based on the social network established by the social network building unit 430. In this case, the debugging developer recommendation unit 440 may select the debugging developer in consideration of at least one or more of the similar bug report correction number, debugging time, source code type, and debugging cost stored in advance for each of the debugging developers who build the social network. I can recommend it.
5 illustrates a conceptual configuration of a class search unit according to an embodiment of the present invention.
The class search unit 420 may be represented by the vector representation converter 421 and the SVM using unit 422.
The vector representation converter 421 converts the bug report received by the bug report receiver 410 into a vector representation.
The SVM user unit searches for a class including the most similar pseudo bug report corresponding to the bug report converted into the vector representation by the vector representation converter 421 using a support vector machine (SVM).
6 illustrates a conceptual configuration of a debugging developer recommendation unit according to an embodiment of the present invention.
The debugging developer recommendation unit 440 may be represented by a debuggable developer extractor 441 and a priority setting unit 442.
The debuggable developer extractor 441 extracts at least one debugging developer who can debug a bug report from among the debugging developers of the social network built by the social network builder 430.
The priority setting unit 442 sets the priority of the extracted debugging developer by using previously stored debugging related property information for at least one debugging developer extracted from the debuggable developer extracting unit 441 and considers the set priority. Recommends debugging developers to respond to bug reports. In this case, the priority setting unit 442 may set the priority in consideration of preset weights for each of the debugging developers extracted by the debuggable developer extracting unit 441. In addition, a debugging developer whose weight is equal to or less than a preset value may be excluded from the priority.
Here, the weights used to set the priority can be regarded as a relatively high score given to each of many debugging developers by experts who have a lot of experience in debugging bug reports in the field, and these weights are set / stored in advance. It may be used, and may be updated continuously based on statistical analysis or expert opinion.
Further, the priority setting unit 442 is a component of each of the components of the debugging-related characteristic information for each of the debugging developers, for example, the number of similar bug report correction, debugging time, source code type, debugging cost, etc. The priority may be set based on a value calculated by assigning a predetermined weight to each component and by assigning a weight to each component.
7 illustrates a conceptual configuration of an algorithm for searching for a class including a similar bug report using an SVM according to an embodiment of the present invention.
The algorithm model shown in FIG. 7 is a k-means clustering algorithm, and {B1, B2, ...., BN} represents a set of similar bug reports clustered by the k-means clustering algorithm. New bug report
New bug report when maximum value (MAXSBBR) is obtained by similarity measure
Where the maximum value (MAXSBBR) is the new bug report
SVMPredict, which represents the SVM distinct model, provides the probability that a new bug report can be included in each similar report set.
Get all SVMPredict values for each similar report set, and check or calculate the maximum value of SVMPredict. At this time, the maximum value of the SVMPredict is a predetermined threshold value
8 illustrates a conceptual configuration of a social network according to an embodiment of the present invention.
If a class exists that contains similar bug reports similar to a bug report, configure it as a social network. Social networks can be used to analyze complex sets of relationships between members of social systems. Such a social network can be usefully used to explore the relationship of debugging developers in a class that includes a similar bug report in accordance with one embodiment of the present invention.
As shown in FIG. 8, the social network shows each developer's relationship by setting each of the developers extracted from the class bug reports as nodes dev1, dev2, dev3, dev4, dev5.
For example, when node dev4 of the social network receives a bug report, node dev4 may request debugging from the developers of node dev1 to fix the bug.
The rate at which a developer who receives a bug report requests debugging for each developer may be represented by Equation 4.
&Quot; (4) "
f i -n / (SUM (f i ) +1)
In this case, f i -n represents the number (frequency) of the bug report debugging developer i and the developer n who annotated the bug report. SUM (f i ) represents the total number of times all commenters appeared with developer i. For example, the frequency of requesting debugging from the dev4 node to the dev1 node becomes f 4 -1 , and the total number of requesting debugging from the dev4 node to other nodes, that is, the dev1, dev2, dev3, and dev5 nodes becomes SUM (f 4 ).
Debugging developer recommendation method according to an embodiment of the present invention is implemented in the form of program instructions that can be executed by various computer means may be recorded on a computer readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the medium may be those specially designed and constructed for the present invention or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.
In the present invention as described above has been described by the specific embodiments, such as specific components and limited embodiments and drawings, but this is provided to help a more general understanding of the present invention, the present invention is not limited to the above embodiments. For those skilled in the art, various modifications and variations are possible from these descriptions.
Accordingly, the spirit of the present invention should not be construed as being limited to the embodiments described, and all of the equivalents or equivalents of the claims, as well as the following claims, belong to the scope of the present invention .
400: Debugging Developer Recommendation
410: bug report receiver
420: class search unit
430: social network construction unit
440: Debugging Developer Recommendation
Claims (15)
Retrieving a class among the classes previously stored in a database, the class including the most similar pseudo bug report corresponding to the received bug report;
Establishing a social network for a connection relationship between the class bug reports using class bug reports included in the retrieved class; And
Recommending a debugging developer corresponding to the bug report based on the established social network;
Lt; / RTI >
Recommend the debugging developer,
Debugging developer recommendation method for recommending the debugging developer in consideration of the number of bug report correction number and the bug report correction time stored in advance for each of the debugging developers included in the social network.
Searching for a class containing the similar bug report,
Converting the bug report into a vector representation; And
Retrieving a class containing the most similar pseudo bug report corresponding to the bug report converted to the vector representation using a support vector machine (SVM);
Debugging developer recommendation method that includes.
The social network sets each of the developers included in the class bug reports as a node, and responds to the developers in consideration of the total number of requests for debugging in each of the configured nodes and the frequency of requesting debugging for each of the remaining nodes. Obtaining a connection relationship between the nodes, and building the social network using the obtained connection relationship between the nodes.
Recommend the debugging developer,
Extracting at least one debugging developer capable of debugging the bug report among debugging developers included in the social network;
Setting a priority of the extracted debugging developer using the previously stored debugging related property information of the extracted at least one debugging developer; And
Recommending a debugging developer corresponding to the bug report in consideration of the set priority.
Debugging developer recommendation method that includes.
The setting of the priority is
Debugging developer recommendation method for setting the priority in consideration of the weight set in advance for each of the extracted developer.
The setting of the priority is
Debugging developer recommendation method for excluding a debugging developer having a weight equal to or less than a predetermined reference value from a priority.
A class search unit for searching for a class including a most similar pseudo bug report corresponding to the received bug report among classes previously stored in a database;
A social network constructing unit for constructing a social network for connection relations between the class bug reports using class bug reports included in the retrieved class; And
A debugging developer recommending unit for recommending a debugging developer corresponding to the bug report based on the established social network;
Lt; / RTI >
The debugging developer recommendation section,
And a debugging developer recommending device for recommending the debugging developer in consideration of the number of bug report correction times and the bug report correction time stored in advance for each of the debugging developers included in the social network.
The class search unit,
A vector representation converter for converting the bug report into a vector representation; And
An SVM using unit for searching for a class including the most similar pseudo bug report corresponding to the bug report converted to the vector representation using a support vector machine (SVM);
Debugging developer recommendation device that includes.
The social network sets each of the developers included in the class bug reports as a node, and responds to the developers in consideration of the total number of requests for debugging in each of the configured nodes and the frequency of requesting debugging for each of the remaining nodes. Obtaining a connection relationship between the nodes, and the debugging developer recommending device for building the social network using the obtained connection relationship between the nodes.
The debugging developer recommendation section,
A debuggable developer extracting unit for extracting at least one debugging developer who can debug the bug report among debugging developers included in the social network; And
Set a priority of the extracted debugging developer by using the previously stored debugging related property information for the extracted one or more debugging developers, and recommend a debugging developer corresponding to the bug report in consideration of the set priority. A priority setting unit;
Debugging developer recommendation device that includes.
Wherein the priority setting unit comprises:
Debugging developer recommendation device for setting the priority in consideration of the weight set in advance for each of the extracted developer.
Wherein the priority setting unit comprises:
Debugging developer recommending device for excluding a debugging developer having a weight equal to or less than a predetermined reference value from a priority.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR1020120125615A KR101390220B1 (en) | 2012-11-07 | 2012-11-07 | Method for recommending appropriate developers for software bug fixing and apparatus thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR1020120125615A KR101390220B1 (en) | 2012-11-07 | 2012-11-07 | Method for recommending appropriate developers for software bug fixing and apparatus thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| KR101390220B1 true KR101390220B1 (en) | 2014-04-30 |
Family
ID=50658937
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| KR1020120125615A KR101390220B1 (en) | 2012-11-07 | 2012-11-07 | Method for recommending appropriate developers for software bug fixing and apparatus thereof |
Country Status (1)
| Country | Link |
|---|---|
| KR (1) | KR101390220B1 (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20160088737A (en) * | 2015-01-16 | 2016-07-26 | 서울시립대학교 산학협력단 | System and Method for Bug Fixing Developers Recommendation and Bug Severity Prediction based on Topic Model and Multi-Feature |
| KR20160088730A (en) * | 2015-01-16 | 2016-07-26 | 서울시립대학교 산학협력단 | System and Method for Recommending Bug Fixing Developers based on Multi-Developer Network |
| CN107480141A (en) * | 2017-08-29 | 2017-12-15 | 南京大学 | It is a kind of that allocating method is aided in based on the software defect of text and developer's liveness |
| KR101928389B1 (en) | 2017-05-11 | 2018-12-12 | 서울시립대학교 산학협력단 | Bug severity prediction system and method by analyzing emotion words |
| KR20190074697A (en) * | 2017-12-20 | 2019-06-28 | 주식회사 함샤우트 | System and method of intermediating developing project |
| KR102273219B1 (en) * | 2020-03-06 | 2021-07-06 | 주식회사 코딩로봇연구소 | System and method for recommending occupational group for software developer |
| US11307966B2 (en) | 2020-04-06 | 2022-04-19 | Red Hat, Inc. | Shared software debugging service |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR980004049A (en) * | 1996-06-27 | 1998-03-30 | 배순훈 | How to correct microcom bug |
| JP2004086583A (en) * | 2002-08-27 | 2004-03-18 | Masanori Minami | Expert recommendation system and its device |
| KR20050054150A (en) * | 2003-12-04 | 2005-06-10 | 한국전자통신연구원 | Real-time debugging method |
-
2012
- 2012-11-07 KR KR1020120125615A patent/KR101390220B1/en active IP Right Grant
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR980004049A (en) * | 1996-06-27 | 1998-03-30 | 배순훈 | How to correct microcom bug |
| JP2004086583A (en) * | 2002-08-27 | 2004-03-18 | Masanori Minami | Expert recommendation system and its device |
| KR20050054150A (en) * | 2003-12-04 | 2005-06-10 | 한국전자통신연구원 | Real-time debugging method |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20160088737A (en) * | 2015-01-16 | 2016-07-26 | 서울시립대학교 산학협력단 | System and Method for Bug Fixing Developers Recommendation and Bug Severity Prediction based on Topic Model and Multi-Feature |
| KR20160088730A (en) * | 2015-01-16 | 2016-07-26 | 서울시립대학교 산학협력단 | System and Method for Recommending Bug Fixing Developers based on Multi-Developer Network |
| KR101691083B1 (en) * | 2015-01-16 | 2016-12-29 | 서울시립대학교 산학협력단 | System and Method for Bug Fixing Developers Recommendation and Bug Severity Prediction based on Topic Model and Multi-Feature |
| KR101697992B1 (en) * | 2015-01-16 | 2017-01-19 | 서울시립대학교 산학협력단 | System and Method for Recommending Bug Fixing Developers based on Multi-Developer Network |
| KR101928389B1 (en) | 2017-05-11 | 2018-12-12 | 서울시립대학교 산학협력단 | Bug severity prediction system and method by analyzing emotion words |
| CN107480141A (en) * | 2017-08-29 | 2017-12-15 | 南京大学 | It is a kind of that allocating method is aided in based on the software defect of text and developer's liveness |
| CN107480141B (en) * | 2017-08-29 | 2020-09-18 | 南京大学 | Software defect auxiliary allocation method based on text and developer liveness |
| KR20190074697A (en) * | 2017-12-20 | 2019-06-28 | 주식회사 함샤우트 | System and method of intermediating developing project |
| KR102013321B1 (en) * | 2017-12-20 | 2019-08-22 | 주식회사 잇플루언서 | System and method of intermediating developing project |
| KR102273219B1 (en) * | 2020-03-06 | 2021-07-06 | 주식회사 코딩로봇연구소 | System and method for recommending occupational group for software developer |
| US11307966B2 (en) | 2020-04-06 | 2022-04-19 | Red Hat, Inc. | Shared software debugging service |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101390220B1 (en) | Method for recommending appropriate developers for software bug fixing and apparatus thereof | |
| US10657264B2 (en) | Techniques for correlating vulnerabilities across an evolving codebase | |
| US10430255B2 (en) | Application program interface mashup generation | |
| US10997134B2 (en) | Automatic entity resolution with rules detection and generation system | |
| US20130332466A1 (en) | Linking Data Elements Based on Similarity Data Values and Semantic Annotations | |
| CN109960810B (en) | Entity alignment method and device | |
| CN112889042A (en) | Identification and application of hyper-parameters in machine learning | |
| CN107145446B (en) | Application program APP test method, device and medium | |
| US10346294B2 (en) | Comparing software projects having been analyzed using different criteria | |
| US20160196200A1 (en) | Test selection method and test selection apparatus | |
| US10346758B2 (en) | System analysis device and system analysis method | |
| EP2810184A1 (en) | Filtering redundant consumer transaction rules | |
| US10296527B2 (en) | Determining an object referenced within informal online communications | |
| JP5903376B2 (en) | Information recommendation device, information recommendation method, and information recommendation program | |
| CN110532304B (en) | Data processing method and device, computer readable storage medium and electronic device | |
| JP6060039B2 (en) | Specific point name determination device, specific point name determination method, and specific point name determination program | |
| CN109582906B (en) | Method, device, equipment and storage medium for determining data reliability | |
| JP2017123521A (en) | Failure cause specification device and program | |
| JP2017004500A (en) | Analysis assistance method, analysis assistance program, and analysis assistance device | |
| US10127128B2 (en) | Performance engineering platform using probes and searchable tags | |
| CN104580109A (en) | Method and device for generating click verification code | |
| CN106651408B (en) | Data analysis method and device | |
| US11115338B2 (en) | Intelligent conversion of internet domain names to vector embeddings | |
| TWI604322B (en) | Solution searching system and method for operating a solution searching system | |
| CN114298417A (en) | Anti-fraud risk assessment method, anti-fraud risk training method, anti-fraud risk assessment device, anti-fraud risk training device and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| A201 | Request for examination | ||
| E902 | Notification of reason for refusal | ||
| E701 | Decision to grant or registration of patent right | ||
| GRNT | Written decision to grant | ||
| FPAY | Annual fee payment |
Payment date: 20170316 Year of fee payment: 4 |
|
| FPAY | Annual fee payment |
Payment date: 20180323 Year of fee payment: 5 |
|
| FPAY | Annual fee payment |
Payment date: 20190329 Year of fee payment: 6 |