Abstract: A computer-implemented method for code classification includes parsing source code stored on a code carrier to obtain a plurality of code structure characteristics of the source code, and evaluating the code structure characteristics on at least three code structure levels. In some embodiments, the at least three code structure levels include one or more of: a global level, a module level, an intermodule level, a function level, an inter-function level, and an implementation level. The evaluation on each code structure level includes, for each of one or more level-specific conditions, determining whether the code structure characteristics violate the level-specific condition, and representing the violation by a weighted value. The method also includes combining the weighted values for at least some of the violated level-specific conditions over the at least three code structure levels to generate one or more code quality indicator for the source code.

Abstract: A computer-implemented method is disclosed for determining a cycle time in a software project. The method includes obtaining a task data item by accessing project management data, wherein the project management data is indicative of migration of software project tasks through different project phases including an in-progress phase. The task data item includes a task identifier indicating a task corresponding to the task data item, and a task time stamp indicating when the task migrated to the in-progress phase. The method also includes obtaining a version control data item by accessing version control data, wherein the version control data is indicative of software commits of the software project. Corresponding apparatus and computer program product are also disclosed.

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.