Data processing that occurs one record at a time.
The process of analyzing two related data records and, if differences exist between them, finding the cause and bringing the two records into agreement.
The discipline, process, or organization responsible for the systematic organization and managed storage of information sources through the end of their life cycles.
Storing historical documentation or electronic records for a set period of time, usually mandated by law or other type of compliance requirement. The programs and processes and policies to enact appropriate Record Retention.
see Record Management
Recursive Referential Integrity
see also Referential Integrity (RI). One special type of "RI" involves just a single table, tied back to itself. A set of columns is set up as the foreign key, referencing the primary key column(s), but of another record. In this manner, a hierarchy can be created within the table. For example, in a table that stores Products, one product can be a subtype of another product.
Data that is used to categorize other data (e.g., code tables or lookup tables) or for relating data in a database to information beyond the boundaries of the enterprise. Reference Data can be considered the simplest type of Master Data. See also Master Data.
The concept of enforced relationships between tables based on the definition of a primary key and foreign key. The existence of a value in one dataset is dependent on the existance of the same value in another linked dataset. Referential Integrity implements rules in a relational-database schemes that are used to preserve the relationships between tables when you add or delete records. For example, a state may not be deleted from a table containing states if any address records include that state.
Retesting of previously tested code following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.
A collection of data items organized as a set of formally described tables from which data can be accessed or reassembled in many different ways without the need to reorganize the database tables.
Relational Database Management System (RDBMS )
Database technology that was designed to support high volume transaction processing (OLTP) and is typically the foundation for a data warehouse. See also Database Management System.
An association between occurrences of one or more entities. A 1-to-1 relationship means that the first entity has one -- and only one -- other entity. (For example, a person is supposed to have only one Social Security Number. This is an example of a relationship that would be 1-to-1 in a perfect world, but actually isn't.) A 1-to-many relationship means that one entity is related to many others. For example, the name "John" is held by many people. A many-to-many relationship means just what it says. For example, there are many products for sale in the grocery store, and many people who shop there. Many-to-many relationships have to be resolved to be useful. For instance, one person will buy many products during a single transaction. One vendor will provide many products to the store during a different type of transaction.
Formal notification and distribution of an approved version of software.
The Process responsible for Planning, scheduling and controlling the movement of Releases to Test and Live Environments. The primary objective of Release Management is to ensure that the integrity of the Live Environment is protected and that the correct Components are released. Release Management works closely with Configuration Management and Change Management. (ITIL definition)
A characteristic of data. It means that the data are meaningful to theperformance of the process or application for which they are collected.
A characteristic of data. It means the ability of a system, process, or parameter to do what is expected or specified under set conditions and designated time interval without failure.
The copying of data from one data store or site to another. Typically, replication takes place to improve service response times and availability. Replication is frequently employed as part of a backup and recovery strategy.
see Data Replication
The process of printing or displaying information contained in a database. Reporting strategies must be considered in the design of databases, Data Warehouses, and other types of data collections.
In a data context, a repository is a collection of information. Metadata repositories, for example, collect metadata about IT systems, applications, or other subjects.
Request for Change (RFC)
In an IT Service Management (ITSM) context, a document containing a call for an adjustment of a system. It is a trigger in the change management process.
A formal statement of what is needed. This might be a condition or capability needed by a user to solve a problem or achieve an objective, or a condition or capability that must be met or possessed by a product or product component to satisfy a contract, standard or specification.
The management of all requirements received by or generated by the project, including both technical and non-technical requirements. This involves coordination, prioritization, and sometimes technologies.
The evidence of an association between a requirement and its source requirement, its implementation, and its verification.
To withdraw an application, IT Service etc. from use in the live environment.
Return on Investment (ROI)
A measurement of the expected benefit of an investment. Calculated by dividing the average increase in financial benefit (taken over an agreed number of years) by the investment.
An evaluation of a Change, Problem, Process, Project etc. Reviews are typically carried out at predefined points in the Lifecycle, and especially after Closure. The purpose of a Review is to ensure that all Deliverables have been provided, and toentify opportunities for improvement. (Baseline ITIL definition)
acronym for Request for Information
Radio frequencyentification tags are transponders, devices that upon receiving a radio signal transmit one of their own.
acronym for Request for Proposal
The possibility of suffering harm or loss, or those circumstances or events that have the potential to have a negative impact.
The evaluation, classification, and prioritization of risks.
A part of Risk Management, where assets areentified, threats to those assets are analyzied, and a determination is made about how vulnerable each asset is to those threats.
An organized, thorough approach toentify concerns, circumstances, or events that may prevent the project from progressing as planned.
In a broad sense, to assess, minimize, and prevent negative consequences posed by a potential threat. The term "Risk Management" has significantly different meanings that can affect Data Governance programs. At an enterprise level, "risk" refers to many types of risk (operational, financial, compliance, etc.); managing risk is a key responsibility of Corporate Boards and Executive Teams. Within financial institutions (or in the context of a GRC program), Risk Management may be a boundary-spanning department that focuses on risk to investments, loans, or mortgages. At a project level, "Risk Management" is an effort that should be undertaken as part of Project Management, focusing on risks to the successful completion of the project. From a Compliance/Auditing/ Controls perspective, "Risk Assessments" and "Risk Management" are high-effort activities included in the COSO, and COBIT frameworks and required by Sarbanes-Oxley and other compliance efforts. Data Governance programs may be asked to support any of these Risk Management efforts, and may need input from these efforts to resolve data-related issues.
Actions developed for selected risks to reduce the likelihood of a risk affecting a project or the impact of the risk, should it occur.
Data that is stored in an inappropriate field in a database. For example, storing a comment in an address field.
Rogue Data Usage
Accessing or using information in an manner that is not authorized or proper.
an acronym for Return on Investment or Risk of Incarceration.
A description of a entity (person, team, department, etc.) with a definable set of responsibilities.
see Drill Up
Roll Up Query
A query that summarize data at a level higher than the previous level of detail.
Synonym for deployment. Most often used to refer to complex or phased deployments.
Rough Order of Magnitude estimate.
In a database, a single data record.
Copyright 2004-2008 The Data Governance Institute, LLC. All Rights Reserved The site is brought to you in partnership with the Business Intelligence Network