Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
A source sampling rate is associated with first or second groups of sampling rates. A playback rate is determined by: (a) selecting the source sampling rate if the source sampling rate is supported by a playback environment; (b) otherwise if there is a highest first rate from the first or second groups of playback sampling rates which is supported by the playback environment and is lower than the source sampling rate, selecting the first rate; (c) otherwise if there is a slowest second rate from the group that the source sampling rate is associated with that is supported by the playback environment and is higher than the source sampling rate, selecting the second rate; (d) otherwise selecting the slowest sampling rate supported by the playback environment from the group that the source sampling rate is not associated with as the playback rate.
Abstract:
In one embodiment, a client device may send one or more sub-session requests to one or more corresponding session controllers through a computer network to obtain one or more corresponding sub-session tokens that indicate in which sub-sessions of an online collaborative computing session the client device is permitted to participate. The client device may then receive particular sub-session tokens (e.g., based on certain permissions), which may then be sent to a collaboration server to establish one or more permitted sub-sessions of the online collaborative computing session with the client device as indicated by the received sub-session tokens.