Patent application number | Description | Published |
20080201629 | METHOD AND SYSTEM FOR DETECTING SYNCHRONIZATION ERRORS IN PROGRAMS - A method and system for error detection in programs with collective synchronization and/or procedures are provided. In one aspect, the method and system may use interprocedural analysis for matching synchronizations in a program in order to detect synchronization errors, and, if no such errors exist, may determine the synchronization phases of the program. The method and system in one aspect may use a combination of path expressions and interprocedural program slicing to match the synchronization statements that may execute along each program path. If the synchronization matching succeeds, the method and system in one aspect may determine the sets of synchronization statements that synchronize together. A matching failure may indicate the presence of a synchronization error and the method and system in one aspect may construct a counter example to illustrate the error. | 08-21-2008 |
20080288957 | METHOD AND SYSTEM FOR OPTIMIZING COMMUNICATION IN MPI PROGRAMS FOR AN EXECUTION ENVIRONMENT - A system and method for mapping application tasks to processors in a computing environment that takes into account the hardware communication topology of a machine and an application communication pattern. The hardware communication topology (HCT) is defined according to hardware parameters affecting communication between two tasks, such as connectivity, bandwidth and latency; and, the application communication pattern (ACP) is defined to mean the number and size of bytes that are communicated between the different pairs of communicating tasks. By collecting information on the messages exchanged by the tasks that communicate, the communication pattern of the application may be determined. By combing the HCT and ACP a cost model for a given mapping can be determined. Any algorithm computing a mapping can use the HCT, ACP, and the cost model, thus the combination of an HCT, ACP, and cost model allow an automatically optimized mapping of tasks to processing elements to be achieved | 11-20-2008 |
20090300166 | MECHANISM FOR ADAPTIVE PROFILING FOR PERFORMANCE ANALYSIS - Adaptive profiling for performance analysis of a computer system controls one or more agents to monitor a plurality of events occurring in a target computer system based on an adaptive logic. Collected data may be filtered and analyzed to determine one or more contributor events that attribute to performance of the target computer system. One or more patterns are observed or detected in said collected data, behavior of said one or more agents are adjusted based on said detected one or more patterns. The adaptive logic may be further reconfigured based on said detected one or more patterns. | 12-03-2009 |
Patent application number | Description | Published |
20130325763 | PREDICTING LIKELIHOOD OF ON-TIME PRODUCT DELIVERY, DIAGNOSING ISSUES THAT THREATEN DELIVERY, AND EXPLORATION OF LIKELY OUTCOME OF DIFFERENT SOLUTIONS - A task effort estimator may determine a probability distribution of an estimated effort needed to complete unfinished tasks in a project based on one or more of a set of completed tasks belonging to a project and attributes associated with the completed tasks belonging to the project, a set of completed tasks not belonging to the project and attributes associated with the completed tasks not belonging to the project, or the combination of both. A project completion predictor may determine a probability distribution of completion time for the project based on the probability distribution of an estimated effort needed to complete the unfinished tasks in the project, and one or more resource and scheduling constraints associated with the project. | 12-05-2013 |
20140222485 | EXPLORING THE IMPACT OF CHANGING PROJECT PARAMETERS ON THE LIKELY DELIVERY DATE OF A PROJECT - A user may be allowed to specify a change in one or more parameter data associated with the project, the one or more parameter data used previously to compute a probability distribution of completion time of the project. The probability distribution of completion time of the project may be recomputed based on the change. The recomputed probability distribution of the completion time of the project may be presented. An option to save the recomputed probability distribution may be provided. An option may be provided to specify another change in one or more parameter data associated with the project and repeat the recomputing and the presenting procedures based on another change in one or more parameter data associated with the project. | 08-07-2014 |
20140222497 | DETECTING PATTERNS THAT INCREASE THE RISK OF LATE DELIVERY OF A SOFTWARE PROJECT - Historic and current development data associated with the project may be gathered. A catalog of patterns, each pattern associated with a data measure and an analysis routine capable of detecting the pattern according to the data measure in a given data set may be obtained. A pattern describes a particular indication in the historical and development data, which arises one or more of, at a discrete point in time or over a period of time. The analysis routine may be applied to the historic and current development data. A notification may be issued responsive to identifying the pattern in the historic and current development data. The applying and the issuing may be performed for each pattern in the catalog of patterns. | 08-07-2014 |
20140236654 | INCORPORATING USER INSIGHTS INTO PREDICTING, DIAGNOSING AND REMEDIATING PROBLEMS THAT THREATEN ON-TIME DELIVERY OF SOFTWARE AND SYSTEMS - Incorporating user insights in predicting, diagnosing and remediating problems that threaten on-time delivery of a project may comprise gathering information. The information may be conveyed to one or more users. A user may be allowed to input a new value associated with the project, the new value assessed based on the information and representing an expert assessment of the information. The user may be allowed to also indicate a period of time the user considers the information to be applicable. The new value and the period of time may be incorporated into data used in a prediction algorithm that predicts probability distribution of completion time of the project as the project is progressing. | 08-21-2014 |
20140236660 | GUI SUPPORT FOR DIAGNOSING AND REMEDIATING PROBLEMS THAT THREATEN ON-TIME DELIVERY OF SOFTWARE AND SYSTEMS - A graphical interface module may provide a set of graphical presentations comprising at least: a Likelihood of Delivery chart showing a probability distribution of predicted delivery dates; a Delivery Date Risk Trend chart showing how the completion time for the project predicted according to the Likelihood of Delivery chart has changed over time; and a Burndown chart that shows at least work-items of planned work for the project. Each of the Likelihood of Delivery chart, the Delivery Date Risk Trend chart, and the Burndown chart has a timeline axis. | 08-21-2014 |
20140258966 | CONTINUOUS UPDATING OF TECHNICAL DEBT STATUS - A system and method to automatically and continuously update the urgency rating of a backlog item associated with a technical debt item in a software development project are described. The technical debt represents potential additional work or rework associated with current code. The method includes a user defining a plurality of components that comprise the software development project. The method also includes a processor associating the technical debt with one or more components of the plurality of components, and the processor updating the urgency of the backlog item associated with the technical debt according to a function based on a development event associated with at least one of the one or more components. | 09-11-2014 |
20140258967 | CONTINUOUS UPDATING OF TECHNICAL DEBT STATUS - A system and method to automatically and continuously update the urgency rating of a backlog item associated with a technical debt item in a software development project are described. The technical debt represents potential additional work or rework associated with current code. The method includes a user defining a plurality of components that comprise the software development project. The method also includes a processor associating the technical debt with one or more components of the plurality of components, and the processor updating the urgency of the backlog item associated with the technical debt according to a function based on a development event associated with at least one of the one or more components. | 09-11-2014 |