摘要:
A set of tools and other mechanisms automatically enforce software development change policies by providing a way to map physical source control system codelines to projects and by providing a way to maintain current project and codeline state information. The set of tools and other mechanisms also provide ways to define change management rules and policies, as well as, ways to evaluate and allow or deny each proposed change against the defined change policy.
摘要:
Techniques are provided for capturing the ID of a work item, and the corresponding effort level information, as a part of the actual check-in process of the artifacts into the underlying change management system. This effort information can then be propagated to an external system for subsequent reporting and analysis. In one embodiment, tasks (or similar items such as issues or bugs) are entered into a common task or issue tracking system. As part of this process each task is assigned a unique identifier. A “call-out” is added to the source control management system which captures the effort level and task ID associated with the proposed change. The data entered is validated to ensure that the task ID is valid and that the effort entered is within a valid range. If the data entered is valid, the change to the underlying artifact is allowed to proceed and the effort and task information is stored for later analysis. If the data is not valid, the proposed change is rejected and an appropriate error message is returned to the user.
摘要:
A set of tools and other mechanisms automatically enforce software development change policies by providing a way to map physical source control system codelines to projects and by providing a way to maintain current project and codeline state information. The set of tools and other mechanisms also provide ways to define change management rules and policies, as well as, ways to evaluate and allow or deny each proposed change against the defined change policy.
摘要:
Techniques are provided for analyzing data called “pivot points” which allows users to instantly generate a report based on all available dimensions for any cell in a tabular report or any data point in a graphical report. In one embodiment, the techniques involve placing a unique UI element or menu next to or on each data point, and clicking on this UI element brings up an automatically filtered list of the valid reports available for just this sub-set of the data. Once the user selects which view they want, a report is automatically generated based on those dimensions with just this subset of data.
摘要:
Techniques are provided for analyzing data called “pivot points” which allows users to instantly generate a report based on all available dimensions for any cell in a tabular report or any data point in a graphical report. In one embodiment, the techniques involve placing a unique UI element or menu next to or on each data point, and clicking on this UI element brings up an automatically filtered list of the valid reports available for just this sub-set of the data. Once the user selects which view they want, a report is automatically generated based on those dimensions with just this subset of data.
摘要:
Techniques are provided for tracking and analyzing defect density by source file or module. Defect density is the number of distinct defects which required changes to be made (to fix the defect) to a particular file or module in a given period of time. This metric is very useful for identifying the most critical areas of weakness of the system and hence the areas where additional investment/action may be taken. For example, this metric can be used to prioritize the area in which unit tests should be written, for which additional automated system tests should be written or which a project should be undertaken to re-write the error prone file or module to improve its quality and maintainability.
摘要:
Techniques are provided for capturing the ID of a work item, and the corresponding effort level information, as a part of the actual check-in process of the artifacts into the underlying change management system. This effort information can then be propagated to an external system for subsequent reporting and analysis. In one embodiment, tasks (or similar items such as issues or bugs) are entered into a common task or issue tracking system. As part of this process each task is assigned a unique identifier. A “call-out” is added to the source control management system which captures the effort level and task ID associated with the proposed change. The data entered is validated to ensure that the task ID is valid and that the effort entered is within a valid range. If the data entered is valid, the change to the underlying artifact is allowed to proceed and the effort and task information is stored for later analysis. If the data is not valid, the proposed change is rejected and an appropriate error message is returned to the user.
摘要:
Techniques are provided for tracking and analyzing defect density by source file or module. Defect density is the number of distinct defects which required changes to be made (to fix the defect) to a particular file or module in a given period of time. This metric is very useful for identifying the most critical areas of weakness of the system and hence the areas where additional investment/action may be taken. For example, this metric can be used to prioritize the area in which unit tests should be written, for which additional automated system tests should be written or which a project should be undertaken to re-write the error prone file or module to improve its quality and maintainability.
摘要:
The embodiments herein provide a system and a method for integrating a data from a source to a destination. The method comprises generating a global-id, setting an event-id corresponding to an entity id in the global id, polling a data from a source, sorting changes of a source system based on a time of update and an entity id, creating and comparing an old as of state value and a new as of state value for each field for each update in the entity in the source and destination to detect a conflict on an entity, sending a time of update in the entity and a revision id of a change to the destination, comparing the global id with an event id for each entity at the destination to detect a presence of an entity in the destination and processing an entity at the destination based an event id.
摘要:
A multi-threaded binary translation system performs atomic operations by a thread, such operations include processing a load linked instruction and a store conditional instruction. The store conditional instruction updates data stored in a shared memory address only when at least three conditions are satisfied. The conditions are: a copy of a load linked shared memory address of the load linked instruction is the same as the store conditional shared memory address, a reservation flag indicates that the thread has a valid reservation, and the copy of data stored by the load linked instruction is the same as data stored in the store conditional shared memory address.