U.S. Department of Transportation
Federal Highway Administration
1200 New Jersey Avenue, SE
Washington, DC 20590

Skip to content
Facebook iconYouTube iconTwitter iconFlickr iconLinkedInInstagram

California Division

Home / About / Field Offices / California Division / Systems Engineering Guidebook for ITS

Home What's New Systems Engineering Guidebook Views Search Glossay Resources Feedback Site Map
Process View

Glossary: D


A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z



Recorded information, regardless of medium or characteristics, of any nature, including administrative, managerial, financial, and technical.
Data product
Information that is inherently generated as the result of work tasks cited in a Statement of Work [SOW] or in a source document invoked in the contract. Such information is produced as a separate entity [for example, drawing, specification, manual, report, records, and parts list].
A collection of related data stored in one or more computerized files in a manner that can be accessed by users or computer programs via a database management system.
Database management system
An integrated set of computer programs that provide the capabilities needed to establish, modify, make available, and maintain the integrity of a database.
Data Exchange
Database Management System
Detail Design Review
The process of successively breaking down the system into components that can be built or procured. Functional and physical decomposition are the key activities that are used. Functional decomposition is breaking a function down into its smallest parts. For example, the function ramp metering decomposes into a number of sub-functions, e.g. detection, meter rate control, main line metering, ramp queuing, time of day, and communications. Physical decomposition defines the physical elements needed to carry out the function. For example, the ramp metering physical decomposition includes loops or video detection, WWV time [world wide standard clock for accurate time], fiber or twisted pair for communications, 2070 or 170 controllers, and host computer.
Those characteristics of a system or components that are selected by the developer in response to the requirements.
Detailed Design Document
The product baseline used to develop the hardware and software components of the system.
An organization that develops products ["develops" may include new development, modification, reuse, reengineering, maintenance, or any other activity that results in products] for itself or another organization.
Development model
A specific portion of the life cycle model that relates to the definition, decomposition, development, and implementation of a system or a part of a system.
Development strategy
The way the development and deployment of the overall system will be carried out. For example, an evolutionary development strategy means that the system will be developed and deployed in multiple segments over time. These pieces are complete functional units that will perform independently from other functional pieces. Incremental development is the development of pieces that are done concurrently or nearly concurrently by the same or different development teams.
Department of Transportation


Return to top
Page last modified on September 21, 2016
Federal Highway Administration | 1200 New Jersey Avenue, SE | Washington, DC 20590 | 202-366-4000