D (Visual Studio ALM Glossary)

This glossary defines key terms that are used in the Visual Studio Application Lifecycle Management (ALM) Help.

• data collection logger
  Software that logs profiling data to a performance data file.

• Data Definition Language (DDL)
  Statements in SQL that define, instead of manipulate, data (for example, CREATE TABLE, CREATE INDEX, GRANT, and REVOKE).

• data generation plan
  A file that contains information about a particular database schema and how Data Generator will generate data for it.

• Data Manipulation Language (DML)
  Statements in SQL that manipulate, instead of define, data (for example, INSERT, UPDATE, DELETE, and SELECT).

• database development life cycle
  A structured process that is imposed upon the development of the database portion of an application. It is essentially a subset of the software development life cycle that is specific to one or more databases in an application.

• database object
  A database component (for example, a table, index, trigger, view, key, constraint, default, rule, user-defined data type, or stored procedure in a database). Can also refer to a database.

• database project
  An offline representation of a database. Each database project contains the scripts that are required to deploy a new database or to update an existing database to a database server. A database project does not contain the data that resides in that database. Database projects are saved as .dbproj files.

• database refactoring
  The process by which you can modify the names of database objects in such a way that all instances of those names within the database project are modified at the same time. For example, if you rename a column in a database table by using refactoring, you also update all stored procedures, views, indexes, functions, unit tests, and so on that reference the column.

• database unit test
  A unit test that validates whether a certain aspect of your database is working as you expect.

• debugger event
  A diagnostic event in IntelliTrace that occurs within the Visual Studio Debugger when it is running your application.

• debugging with IntelliTrace
  When you debug by using IntelliTrace, you can navigate to various points in time where events of interest have been recorded.

• declarative tests
  Ordinary Web tests that are generated by using the Web Test Recorder that is launched when a new Web test is created.

• dependent module
  A module that contains dependencies from other modules.

• deployed environment
  A group of virtual machines located on a team project host group and controlled by Microsoft Test Manager. A deployed environment can be running or stopped.

• development task
  An assigned unit of development work usually created to build part of a scenario or quality of service requirement. The development task describes the objective of the developer in the context of an iteration.

• diagnostic data adapter
  An assembly that has functionality to enable a user to either collect diagnostic data to understand what is occurring on a system when a test is running, or perform actions on the system while a test is running. For example, a diagnostic data adapter could perform actions to reduce the amount of memory available, or impact network performance.

• differentiating factor
  The part of a scenario that determines its uniqueness from other scenarios. The goal of a differentiating factor is to prevent multiple scenarios from being created that describe the same flow through the system.

• directive
  An instruction in a text template that directs the engine and the host on how to process the template.

• disable rule
  Choose this option if you do not want to do the analysis for a particular rule, versus suppressing a particular instance of message.

• disciplines
  Particular specializations that categorize activities and guidance within a process according to a common theme; these may relate to one or to many roles. Key disciplines span across the project lifecycle.

• distribution group
  A collection of users, computers, contacts, and other groups that is used only for e-mail distribution.

• document template
  The individual .doc, .dot, .xls, .xlt files, and so forth that we provide with a process to give users a starting point. Some are samples that are edited. Others are templates that must be saved to a new file (from .dot to .doc); these must be in sync with, but separate from, process guidance, both of which roll into the process templates.

• domain class
  A diagram element that represents a class in a domain-specific language.

• domain model
  The graphical and in-memory representation (store) of a domain-specific language. You create a domain model by using the Domain-Specific Language Designer Wizard, and you customize a domain model by using the Domain-Specific Language Designer.

• domain model element
  A diagramming element that defines a domain-specific language. Domain model elements include domain classes, domain relationships, connectors, and shapes.

• domain relationship
  A diagram element that represents an embedding or reference relationship in a domain-specific language.

• domain-specific language
  A custom language that targets a problem domain and defines the problem at a high level of abstraction.

• DREAD
  A ranking of the risk that is associated with a vulnerability or a security requirement. DREAD stands for Damage potential, Reproducibility, Exploitability, Affected users, Discoverability.

• duplicate link
  A Team Foundation link between two work items that represent the same work item. In practice, this occurs when two people report the same bug.