Method for identifying critical parts in software code

1. A method for identifying critical parts in software code comprised in a number of software code files, said method comprising:

fetching at least two revisions of said software code, wherein said at least two revisions comprises a first revision and a second revision, said second revision being a latter revision;

comparing said second revision to said first revision in order to identify at least a first and a second segment of software code in said second revision that have been changed;

fetching at least a first and second timestamp correlated with said change of said at least first and second segment of software code respectively;

determining a time difference between said change of said at least first and second segment of software code based on said at least first and second timestamp;

if said time difference is within a predetermined range, assigning a temporal coupling between said at least first and second segment of software code;

if said temporal coupling has been assigned, identifying said first and/or second segment of software code as critical parts;

suggesting how to re-arrange said software code such that said critical parts appear closer to each other; and

re-arranging said software code according to said suggestion, wherein the re-arranging comprises one or more of:

moving one of the critical parts closer to another one of the critical parts,

combining a first software code file comprising one of the critical parts with a second software code file comprising another one of the critical part, or

splitting a software code file comprising the critical parts and arranging the critical parts in one of the split software code files.

2. The method according to claim 1 , wherein the software code is comprised in at least two software code files.

3. The method according to claim 1 , further comprising the step of providing a suggestion on how to split one or several of said number of software code files and/or combine at least two software code files such that said critical parts appear closer to each other.

4. The method according to claim 3 , further comprising the step of splitting and/or combining said one or several of said number of software code files according to said suggestion.

5. The method according to claim 1 , further comprising the step of identifying a number of developers involved in said change of said at least first and second segment of software code, and wherein the step of assigning a temporal coupling between said at least first and second segment of software code further comprises a prerequisite that the same developer has been involved in said change of said at least first and second segment of software code.

6. The method according to claim 1 , further comprising the step of identifying a number of ticket identifiers referenced in said change of said at least first and second segment of software code, and wherein the step of assigning a temporal coupling between said at least first and second segment of software code further comprises the prerequisite that said change of said at least first and second segment of software code have been made with reference to the same ticket identifier.

7. The method according to claim 1 , further comprising:

identifying a number of developers that have been involved in developing said number of critical parts; and

providing names of said number of developers.

8. A computer having a processor executing computer program code to perform the steps of claim 1 .

9. The computer according to claim 8 , wherein the computer program code is embodied on a non-transitory, computer readable medium.

10. A computer program product comprising a non-transitory computer readable medium, having thereon computer program code loadable into a data processing unit and configured to cause execution of the method according to claim 1 when run by the data processing unit.