I (Visual Studio Team System Glossary)
This glossary defines key terms that are used in the Microsoft Visual Studio 2005 Team System Help.
- inclusive time
The total time spent inside this function or module, including time in functions or modules called from this function.
- inclusive transitions
Number of transitions between user (ring 3) and kernel mode (ring 0) in function and items it calls.
- infrastructure architecture
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
- instrumentation overhead
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.
- internal release
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.
(1) A fixed period of calendar time, generally between 1 and 6 weeks, for scheduling tasks and planning activities. Typically, iterations are consecutively numbered and follow one another sequentially. (2) A node on the Common Structure Service hierarchy that represents a schedule abstraction.
- iteration budget
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.
- iteration length
The length of the fixed period of time that comprises an iteration. The iteration length usually stays constant over the entire project.
- iteration plan
The list of scenarios, quality of service requirements, and tasks for the upcoming iteration.
- iteration tests
The set of tests that are run after the build verification tests. These tests verify the functionality called for in the iteration plan.
- iterative development
The development of a solution by building, testing, and deploying a core set of basic features first, then adding features in successive versions.