Code development using continued machine learnings

• US 10,481,879 B2
• Filed: 03/30/2018
• Issued: 11/19/2019
• Est. Priority Date: 02/07/2018
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Stevens, Joshua Bates, Tilford, John S., Castilla, Guillermo Serrato, Narayanan, Srivatsn, Calvert, Simon, Wilson-Thomas, Mark Alistair, Chen, Deborah, Allamanis, Miltiadis, Brockschmidt, Marc Manuel Johannes, Shanmugam, Kesavan
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US15/942,279
• Publication Number:
  US 20190243617A1
• Time in Patent Office: 599 Days
• Field of Search: 717101-107, 717120-122
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 8/33 Intelligent editors
• CPC Class Codes: G06F 8/35 model driven
• CPC Class Codes: G06F 8/42 Syntactic analysis
• CPC Class Codes: G06F 8/75 Structural analysis for program understanding
• CPC Class Codes: G06N 20/00 Machine learning
• CPC Class Codes: G06N 5/022 Knowledge engineering; Knowledge acquisition

Abstract

Improving how a codebase, which may include source code, related databases, test files, code history, and/or changes, is drafted, edited, debugged, or otherwise developed. Machine learning is performed on a model codebase to establish a machine learning model. When a change to a codebase occurs, the machine learning model may be applied to evaluate that change. A change context providing context for this change is accessed. An analyzer then analyzes the change using the machine learning model and at least a part of the change context to generate an analysis result. Some information about the result is rendered. After rendering that information, a determination regarding how a user responded to the information is performed, and a subsequent analysis is then modified based on the user'"'"'s response.

Claims

1. A computer system comprising:

one or more processors; and

one or more computer-readable hardware storage devices having stored thereon computer-executable instructions that, when executed by the one or more processors, cause the computer system to;

within an architecture that includes one or more analyzer components, receive a notification indicating that a codebase has undergone a change from a collaborative code review request service, the notification including a scope of the change;

access a change context that provides context for the change;

perform, by one of the one or more analyzer components, analysis of the change using at least a portion of the change context,

the one analyzer component selected based on the scope of the change;

detect receipt of a result of the analysis;

receive, by an orchestrator service, the result of the analysis from the one analyzer

component, the collaborative code review request service periodically polling the orchestrator service to inquire about the result of the analysis;

cause at least some information of the result to be rendered to a user;

determine how the user responded to the rendered information; and

automatically modify a subsequent analysis performed by at least the one analyzer component based on how the user responded to the rendered information.

2. The computer system of claim 1, wherein the codebase'"'"'s change occurs as a part of a collaborative code review request.

3. The computer system of claim 1, wherein accessing the change context includes:

identifying a context of the codebase; and

based on a determined a scope of the change, extracting the change context from the codebase'"'"'s context, wherein the change context is extracted from the codebase'"'"'s context as a result of the change context being identified as corresponding to the change.

4. The computer system of claim 1, wherein the one analyzer component identifies and accesses the change context.

5. The computer system of claim 1, wherein each of the one or more analyzer components performs a different type of analysis.

6. The computer system of claim 1, wherein a probability indication is also rendered with the at least some information, the probability indication indicating a level of confidence associated with the result.

7. The computer system of claim 1, wherein determining how the user responded to the rendered information includes determining that the user subsequently edited the codebase based on the at least some information that was rendered.

8. The computer system of claim 1, wherein determining how the user responded to the rendered information includes determining that the user did not subsequently edit the codebase based on the at least some information that was rendered.

9. The computer system of claim 1, wherein determining how the user responded to the rendered information includes receiving a notice indicating that the user marked the at least some information either as positive information or as negative information and using at least that notice to make the determination.

10. The computer system of claim 1, wherein modifying the subsequent analysis performed by the one analyzer component includes causing the one analyzer component to learn from the result.

11. A method for improving user development of source code, the method being implemented by a computer system that includes one or more processors, the method comprising:

within an architecture that includes one or more analyzer components, receiving a notification indicating that a codebase has undergone a change from a collaborative code review request service, the notification including a scope of the change;

accessing a change context that provides context for the change;

performing, by one of the one or more analyzer components,

analysis of the change using at least a portion of the change context, the one analyzer component selected based on the scope of the change;

detecting receipt of a result of the analysis;

receiving, by an orchestrator service, the result of the analysis from the one analyzer component, the collaborative code review request service periodically polling

the orchestrator service to inquire about the result of the analysis;

causing at least some information of the result to be rendered to a user;

determining how the user responded to the rendered information; and

automatically modifying a subsequent analysis performed by at least the one analyzer component based on how the user responded to the rendered information.

12. The method of claim 11, wherein the one or more analyzer components are selected for use during a registration of the codebase.

13. The method of claim 11, wherein the computer system additionally provides access control for the codebase such that an authentication is performed prior to accessing the codebase.

14. The method of claim 11, wherein at least a part of the change context is extracted from a context associated with the codebase, and wherein the context is generated by:

identifying program files that include at least a part of the codebase; and

building a context graph based on the program files.

15. The method of claim 11, wherein each of the one or more analyzer components is an instance that provides isolation between the analysis performed for the codebase and other analyses performed for different source code by other instances.

16. The method of claim 11, wherein the change context includes one or more context portions associated with the change.

17. One or more hardware storage devices having stored thereon computer-executable instructions that are structured to be executable by one or more processors of a computer system to thereby cause the computer system to:

within an architecture that includes one or more analyzer components, receive a notification indicating that a codebase has undergone a change from a collaborative code review request service, the notification including a scope of the change;

access a change context that provides context for the change;

perform, by one of the one or more analyzer components, analysis of the change using at least a portion of the change context,

the one analyzer component selected based on the scope of the change;

detect receipt of a result of the analysis;

receive, by an orchestrator service, the result of the analysis from the one analyzer

component, the collaborative code review request service periodically polling the orchestrator service to inquire about the result of the analysis;

cause at least some information of the result to be rendered to a user;

determine how the user responded to the rendered information; and

automatically modify a subsequent analysis performed by at least the one analyzer component based on how the user responded to the rendered information.