Method of collaborative software development

• US 9,799,007 B2
• Filed: 08/18/2014
• Issued: 10/24/2017
• Est. Priority Date: 08/18/2014
• Status: Active Grant

• Current Assignee: Drexel University
• Original Assignee: Drexel University
• Inventors: Blincoe, Kelly Coyle, Valetto, Giuseppe
• Primary Examiner(s): Pham, Tuan A
• Application Number:
  US14/462,387
• Publication Number:
  US 20160048805A1
• Time in Patent Office: 1,163 Days
• Field of Search: None
• CPC Class Codes: G06Q 10/101 Collaborative creation, e.g. joint development of products or services

Abstract

A method of collaboratively developing software includes recording a plurality of developers'"'"' tasks relating to a collection of software development files via software executing on a computer. The method further includes calculating a proximity score between a plurality of tasks based on the overlap of the developers'"'"' activities via software executing on a computer. The method further includes selecting and capturing a group of task properties that along with the proximity score can be used to select a group of task pairings that require coordination. The method further includes notifying the developers assigned to the task pairings selected that they may need to coordinate their development efforts.

Claims

1. A method of collaboratively developing software, comprising:

(a) recording a plurality of developers'"'"' tasks as the tasks occur via software executing on a computer, wherein the tasks comprise viewing and editing files;

(b) determining an actual score between two tasks via software executing on a computer, wherein the actual score is determined by a weight comprising;

a high amount of weight comprising 1 when a common file is edited in both tasks, a low amount of weight comprising 0.59 when the common file is viewed in both tasks, and a middle amount of weight comprising 0.79 when the common file is viewed in one task and edited in the other task;

(c) calculating a score between the two tasks via software executing on a computer by dividing the actual score by a maximum potential score to produce a ratio, wherein the maximum potential score is a union of files between the two tasks that have been edited and/or viewed; and

(d) determining the developers of the two tasks need to coordinate if the score exceeds a threshold score.

2. The method of claim 1, further comprising:

(e) collecting information about code file software architecture, operating system, hardware, and/or other attributes associated with the involved software system prior to step (a); and

(f) selecting the two tasks based on the information collected in step (e).

3. The method of claim 1, further comprising:

(e) querying the plurality of developers or system experts on which entities require collaborating and the degree to that collaboration;

(f) selecting the two tasks based on the information collected in step (e).

4. The method of claim 1, wherein the threshold in step (d) is a score equal to or greater than the mean+2 standard deviations.