This glossary defines key terms that are used in the Visual Studio Application Lifecycle Management (ALM) Help.
The total time spent inside this function or module, including time in functions or modules called from this function.
Number of transitions between user (ring 3) and kernel mode (ring 0) in function and items it calls.
The topology of the deployment environment including protocols, security levels, and services. This architecture provides a logical mapping to the deployment environment, such as the datacenter.
The process of tagging the source code in order to measure the amount of time spent in each area.
instrument a binary
To insert diagnostic probes into your binary to collect performance data.
A profiling technique that involves inserting diagnostic probes into the program being profiled. See also: sampling
An increase in the time it takes code to run when you instrument a binary. The increase is caused by additional code, known as a probe, that is inserted to monitor application performance.
A feature for debugging a managed application at specific points in time. It captures and records what the application does while it is running. When an error occurs, you can view the state of the application at any time from the start to the point of the error.
Any event that happens during a run of your application that can be recorded by IntelliTrace or Lab Management.
The information that is collected by IntelliTrace. The file name extension is .iTrace.
The process of getting the product to a known state and incrementally building upon it. Also, an interim milestone of the developing phase, leading to the scope complete milestone.
isolated development environment
A private copy of the database that is created from the database project and typically filled with data by using a data generation plan. You can use an isolated development environment to safely implement and test changes to the database schema without interfering with other development processes. After you complete your tests, you can then share your changes with rest of the team when you check your version of the schema into version control.
A period of time, often about a month, in which software is developed and verified to result in a shippable increment of the product or project.
The budget used for planning the development activity for an iteration, based on rough order of magnitude estimates. The iteration budget is obtained from the velocity report and is measured in ideal person days.
The length of the fixed period of time that comprises an iteration. The iteration length usually stays constant over the entire project.
The list of scenarios, quality of service requirements, and tasks for the upcoming iteration.
The set of tests that are run after the build verification tests. These tests verify the functionality called for in the iteration plan.
The development of a solution by building, testing, and deploying a core set of basic features first, then adding features in successive versions.