Abstract: The invention relates to a system and method for identifying occurrences of preventive maintenance on computer source code. The method comprises analyzing source code, defining data sets associated with characteristics of the source code, and applying an operation algorithm to the data sets to thereby identify occurrences of preventive maintenance operations that were carried out on the source code. A first instance of a source code and a second instance of the source code are preferably analyzed, wherein the second instance of the source code is a revised version of the first instance of the source code, a first data set associated with the first instance of the source code and a second data set associated with the second instance of the source code are preferably defined, and the operation algorithm is preferably applied to the first data set and the second data set to thereby identify at least one occurrence of a preventive maintenance operation that was carried out on the source code.

Abstract: The present invention provides a method and system for detecting a partial commit of software. A dependency information of the software is extracted from a version history and a bug database. A dimensional matrix containing a set of commit, and relationship information with a set of files with each commit is created from the dependency information. A centrality matrix is computed by performing a first set of matrix transformations on the dimensional matrix. A set of missing files of a partial commit, is identified by performing a second set of matrix transformations on the centrality matrix and a file vector, the file vector including a file dependency information of the partial commit.

Abstract: This technology relates to a method and system for software analytics using business intelligence. The method includes receiving application parameters from a user for an application. The method also includes receiving, data related to the application based on the received application parameters. The method further includes designing an orthogonal dimension model for the application based on the received application parameters; and modeling the received data into the designed orthogonal dimensional model.

Abstract: A method, non-transitory computer readable medium, and apparatus that obtains a version history for a plurality of source code files associated with the computer program. At least one defect probability value is generated for each of the plurality of source code files using at least one metric and the obtained version history. One or more of the plurality of source code files having a higher risk of including one or more defects than one or more other of the plurality of source code files are identified based on the generated defect probability values. Information regarding each of the one or more identified source code files is output.

Abstract: The present invention provides a method and system for detecting a partial commit of software. A dependency information of the software is extracted from a version history and a bug database. A dimensional matrix containing a set of commit, and relationship information with a set of files with each commit is created from the dependency information. A centrality matrix is computed by performing a first set of matrix transformations on the dimensional matrix. A set of missing files of a partial commit, is identified by performing a second set of matrix transformations on the centrality matrix and a file vector, the file vector including a file dependency information of the partial commit.

Abstract: Quality of modularization of source code is tested using different perspectives such as a structural modularity perspective, an architectural modularity perspective, a size perspective, and a similarity of purpose perspective. A history of changes in modularization may be kept such that the degree to which given source code is well-modularized can be determined over time. The changes made to the code by individual programmers may be kept, such that the degree to which their coding enhanced or harmed modularization may be tracked.

Abstract: A system, computer-implemented method, and computer-readable medium for determining the quality of an API includes receiving documentation of the API, determining one or more characteristics of the API based at least in part on the documentation of the API, determining or more measurement values based at least in part on the one or more characteristics of the API, and computing a quality score for the API based at least in part on the one or more measurement values.

Abstract: A method, non-transitory computer readable medium, and apparatus that obtains a version history for a plurality of source code files associated with the computer program. At least one defect probability value is generated for each of the plurality of source code files using at least one metric and the obtained version history. One or more of the plurality of source code files having a higher risk of including one or more defects than one or more other of the plurality of source code files are identified based on the generated defect probability values. Information regarding each of the one or more identified source code files is output.

Abstract: A system and method for improving modularity of a software source code is provided. The system comprises of a user interface for receiving source code; a source code model extractor for parsing and forming a model of the source code; a source code model database for storing the source code model, refactoring operators, and a record of refactoring changes; a modularity improvement analyzer for reading the source code model and modularity problem diagnosis data and generating a set of prescriptions; an optimal improvement suggestion selector for evaluating and selecting prescriptions; and a refactoring engine for receiving selected prescriptions and applying them on the source code.

Abstract: Systems, methods, and computer-readable media for determining the quality of an API by one or more computing devices includes: receiving documentation of the API; determining, based on the documentation, values that include at least one of names of the methods, parameters of the methods, and functions of the methods; determining one or more measurement value including at least one of a complexity of the API, a consistency of the parameters of the API, a level of confusion of the API, a logical method groupings of the API, a thread safety of the API, an exception notification of the API, and a documentation quality of the API; and specifying at least one quality metric for the API based on the measurement values.

Abstract: Topics in source code can be identified using Latent Dirichlet Allocation (LDA) by receiving source code, identifying domain specific keywords from the source code, generating a keyword matrix, processing the keyword matrix and the source code using LDA, and outputting a list of topics. The list of topics is output as collections of domain specific keywords. Probabilities of domain specific keywords belonging to their respective topics can also be output. The keyword matrix comprises weighted sums of occurrences of domain specific keywords in the source code.

Abstract: The invention relates to a system and method for identifying occurrences of preventive maintenance on computer source code. The method comprises analyzing source code, defining data sets associated with characteristics of the source code, and applying an operation algorithm to the data sets to thereby identify occurrences of preventive maintenance operations that were carried out on the source code. A first instance of a source code and a second instance of the source code are preferably analyzed, wherein the second instance of the source code is a revised version of the first instance of the source code, a first data set associated with the first instance of the source code and a second data set associated with the second instance of the source code are preferably defined, and the operation algorithm is preferably applied to the first data set and the second data set to thereby identify at least one occurrence of a preventive maintenance operation that was carried out on the source code.

Abstract: Multiple architects may concurrently create and modify a model of computer software, each on their own client at a different location. Each change that is made to a model is forwarded to a server for analysis. The server may determine whether the change creates a conflict. If no conflict is detected, the change may be approved, saved, and propagated by the server to all of the other clients that are working on the same model. If a conflict is detected, on the other hand, the change may not be approved by the server. The server may instead provide notice of the conflict.

Abstract: Quality of modularization of source code is tested using different perspectives such as a structural modularity perspective, an architectural modularity perspective, a size perspective, and a similarity of purpose perspective. A history of changes in modularization may be kept such that the degree to which given source code is well-modularized can be determined over time. The changes made to the code by individual programmers may be kept, such that the degree to which their coding enhanced or harmed modularization may be tracked.

Abstract: The present invention describes a process, system and computer program product for assessing the modularity of an object-oriented program. The process includes calculation of metrics associated with various properties of the object-oriented program. Analysis is performed on the basis of the calculated metrics.

Abstract: A system and method for improving modularity of a software source code is provided. The system comprises of a user interface for receiving source code; a source code model extractor for parsing and forming a model of the source code; a source code model database for storing the source code model, refactoring operators, and a record of refactoring changes; a modularity improvement analyzer for reading the source code model and modularity problem diagnosis data and generating a set of prescriptions; an optimal improvement suggestion selector for evaluating and selecting prescriptions; and a refactoring engine for receiving selected prescriptions and applying them on the source code.

Abstract: Topics in source code can be identified using Latent Dirichlet Allocation (LDA) by receiving source code, identifying domain specific keywords from the source code, generating a keyword matrix, processing the keyword matrix and the source code using LDA, and outputting a list of topics. The list of topics is output as collections of domain specific keywords. Probabilities of domain specific keywords belonging to their respective topics can also be output. The keyword matrix comprises weighted sums of occurrences of domain specific keywords in the source code.

Abstract: Quality of modularization of source code is tested using different perspectives such as a structural modularity perspective, an architectural modularity perspective, a size perspective, and a similarity of purpose perspective. A history of changes in modularization may be kept such that the degree to which given source code is well-modularized can be determined over time. The changes made to the code by individual programmers may be kept, such that the degree to which their coding enhanced or harmed modularization may be tracked.

Abstract: Quality of modularization of source code is tested using different perspectives such as a structural modularity perspective, an architectural modularity perspective, a size perspective, and a similarity of purpose perspective. A history of changes in modularization may be kept such that the degree to which given source code is well-modularized can be determined over time. The changes made to the code by individual programmers may be kept, such that the degree to which their coding enhanced or harmed modularization may be tracked.