Abstract: A method of ranking a plurality of parts of a software code is disclosed for identification of one or more candidate parts of the software code for alteration. The software code is associated with a change history register indicative of previous alterations of the parts of the software code. The method includes (for each of the plurality of parts of the software code) determining a plurality of constituent metrics of the part of the software code by parsing the change history register and the software code determining an alteration recency metric for the part of the software code based on the time indications of the change history register, and scaling one or more of the constituent metrics based on the alteration recency metric.

Abstract: A method is disclosed of evaluating an organizational partition of developers into groups, wherein the evaluation is in relation to alterations of a software code. The software code is associated with a change history register indicative of previous alterations of the parts of the software code, each previous alteration being associated with a developer identity. The method includes parsing the change history register to acquire an association metric indicative of a number of associations between a developer identity and one of the previous alterations. The method also includes determining intra-group collaboration metrics and inter-group collaboration metrics for each group based on the association metrics. The intra-group collaboration metric is indicative of a sum over one or more parts of the software code.

Abstract: A method for identifying critical parts in software code comprised in a number of software code files. The method comprises fetching at least two revisions of the software code, wherein the at least two revisions includes a first revision and a second revision, and the second revision being a latter revision. The method further comprises comparing the second revision to the first revision in order to identify at least a first and a second segment of software code in the second revision that have been changed, fetching at least a first and second timestamp correlated with the change of the at least first and second segment of software code respectively, and determining a time difference between the change of the at least first and second segment of software code based on the at least first and second timestamp. If the time difference is within a predetermined range, the method includes assigning a temporal coupling between the at least first and second segment of software code.

Abstract: A method is disclosed of evaluating an organizational partition of developers into groups, wherein the evaluation is in relation to alterations of a software code. The software code is associated with a change history register indicative of previous alterations of the parts of the software code, each previous alteration being associated with a developer identity. The method includes parsing the change history register to acquire an association metric indicative of a number of associations between a developer identity and one of the previous alterations. The method also includes determining intra-group collaboration metrics and inter-group collaboration metrics for each group based on the association metrics. The intra-group collaboration metric is indicative of a sum over one or more parts of the software code.

Abstract: A method of ranking a plurality of parts of a software code is disclosed for identification of one or more candidate parts of the software code for alteration. The software code is associated with a change history register indicative of previous alterations of the parts of the software code. The method includes (for each of the plurality of parts of the software code) determining a plurality of constituent metrics of the part of the software code by parsing the change history register and the software code determining an alteration recency metric for the part of the software code based on the time indications of the change history register, and scaling one or more of the constituent metrics based on the alteration recency metric.

Abstract: The inventive concept relates to a method for identifying critical parts in software code comprised in a number of software code files. The method comprises fetching at least two revisions of the software code, wherein the at least two revisions comprises a first revision and a second revision, the second revision being a latter revision.