Autonomous vehicle simulation system
US-2024001921-A1 · Jan 4, 2024 · US
US9658939B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9658939-B2 |
| Application number | US-201213597689-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 29, 2012 |
| Priority date | Aug 29, 2012 |
| Publication date | May 23, 2017 |
| Grant date | May 23, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A technique to determine defect density in a portion or subset of code. Changes to code may be tracked. Defects in the code that are addressed by the changes may also be tracked. A defect density in a portion or subset of the code having a characteristic can be determined by identifying changes modifying the portion or subset of the code and that address a defect.
Opening claim text (preview).
What is claimed is: 1. A computing system, comprising: a code tracker to track changes to a code base, wherein the changes are authored by a first author; a defect tracker to track defects in the code base and to maintain a correlation between the changes and the defects addressed by the changes; and a defect density module to determine a number of defects in a portion of the code base authored by a second author by determining how many defects are addressed by changes occurring in the portion of the code base. 2. The computing system of claim 1 , comprising a user interface to specify the second author. 3. The computing system of claim 2 , wherein the user interface is configured to specify a time period, the portion of the code base being limited to code authored by the second author during the time period. 4. The computing system of claim 1 , wherein the defect density module is configured to identify the portion of the code base by requesting from the code tracker code in the code base authored by the second author. 5. The computing system of claim 4 , wherein the code tracker is configured to provide to the defect density module code whether the code is original code added to the code base or changes to the original code. 6. The computing system of claim 1 , wherein the portion of the code base comprises non-consecutive lines of code. 7. The computing system of claim 1 , wherein the defect density indicates a number of defects per unit of program code for the second author. 8. A method, comprising: tracking changes to a code base using a source code management application, wherein the changes are authored by a first author; maintaining a correlation between defects in the code base and changes addressing the defects; and determining a defect density in a subset of the code base authored by a second author by identifying how many defects are addressed by changes that modify the subset of the code base. 9. The method of claim 8 , further comprising: determining a second defect density in a second subset of the code base by identifying how many defects are addressed by changes that modify the second subset of the code base; and displaying a graph comparing the defect density and the second defect density. 10. The method of claim 9 , wherein the second subset of the code base constitutes code authored by a third author and that implements a development requirement. 11. The method of claim 10 , wherein the defect density indicates a proficiency of the third author with the development requirement. 12. The method of claim 10 , wherein the development requirement is at least one of a feature, property, and functionality that the code base is supposed to have. 13. The method of claim 8 , further comprising receiving specification of the second author via a user interface. 14. The method of claim 13 , wherein the second author is one of multiple developers that authored code in the code base. 15. The method of claim 8 , further comprising identifying a trend in the defects based at least in part on the defect density. 16. A non-transitory computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to: track changes to source code having multiple authors, wherein the changes are authored by a first author; track defects addressed by the changes; and determine a defect density in a portion of the source code authored by a second author by identifying changes that modify the portion of the source code authored by the second author and that address a defect. 17. The computer-readable medium of claim 16 , the storage medium storing instructions that, when executed by a processor, cause the processor to maintain a correlation between change sets that address a defect and defects addressed by the change sets. 18. The computer-readable medium of claim 16 , wherein the portion of the source code authored by the second author includes a line of code authored by another author when it was added to the source code but was authored by the second author in a subsequent change.
Debugging of software · CPC title
Version control (security arrangements therefor G06F21/57); Configuration management · CPC title
Reliability or availability analysis · CPC title
Performance of employee with respect to a job function · CPC title
Software metrics · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.