| < Day Day Up > |
|
A repository of information about data, such as its meaning, relationships to other data, origin, usage, and format. A data dictionary manages data categories such as aliases, data elements, data records, data structure, data store, data models, data flows, data relationships, processes, functions, dynamics, size, frequency, resource consumption, and other userdefined attributes.
The person responsible for managing data at a logical level, namely data definitions, data policies, and data security.
A collection of logically related data stored together in one or more computerized files; an electronic repository of information accessible via a query language interface.
A software system that controls storing, combining, updating, retrieving, and displaying data records.
A repository of data; a file.
A procedure to verify system requirements that cannot be tested otherwise.
A formal product that must be delivered to (and approved by) the customer.
Includes the Software Development Document, User Manual, Maintenance Manual, and Operations Manual.
The period of time in the Systems Development Life Cycle during which the designs for architecture, software components, interfaces, and data are created, documented, and verified to satisfy system requirements.
The period of time in the Systems Development Life Cycle to convert the deliverables of the Design phase into a complete system.
The period time when a system has been declared surplus and/or obsolete, and the task performed is either eliminated or transferred to other systems.
A formal plan providing the full set of procedures necessary to end the operation or the system in a planned, orderly manner and to ensure that system components and data are properly archived or incorporated into other systems.
Written and/or graphical information describing, defining, specifying, reporting, or certifying activities, requirements, procedures, reviews, or results. See product.
| < Day Day Up > |
|