File:Physical Data Model Options.jpg
|
This diagram image could be re-created using vector graphics as an SVG file. This has several advantages; see Commons:Media for cleanup for more information. If an SVG form of this image is available, please upload it and afterwards replace this template with
{{vector version available|new image name}}.It is recommended to name the SVG file “Physical Data Model Options.svg”—then the template Vector version available (or Vva) does not need the new image name parameter. |
Summary
| Description |
English: Physical Data Model —Options.
The Physical Data Model (PDM) describes how the information represented in the Logical Data Model is actually implemented, how the information-exchange requirements are implemented, and how the data entities and their relationships are maintained. There should be a mapping from a given Logical Data Model to the Physical Data Model if both models are used. The form of the Physical Data Model can vary greatly, as shown in Figure 31. For some purposes, an additional entity-relationship style diagram will suffice. The Data Definition Language (DDL) may also be used. References to message format standards (which identify message types and options to be used) may suffice for message-oriented implementations. Descriptions of file formats may be used when file passing is the mode used to exchange information. Interoperating systems may use a variety of techniques to exchange data, and thus have several distinct partitions in their Physical Data Model with each partition using a different form. The figure illustrates some options for expressing the Physical Data Model and an other table (in the original document) provides a listing of the types of information to be captured. |
| Date | |
| Source | Treasury Enterprise Architecture Framework. Version 1, July 2000 |
| Author | Department of the Treasury Chief Information Officer Council |
Licensing
|
This work is in the public domain in the United States because it is a work prepared by an officer or employee of the United States Federal Government as part of that person’s official duties under the terms of Title 17, Chapter 1, Section 105 of the US Code.
Note: This only applies to original works of the Federal Government and not to the work of any individual U.S. state, territory, commonwealth, county, municipality, or any other subdivision. This template also does not apply to postage stamp designs published by the United States Postal Service since 1978. (See § 313.6(C)(1) of Compendium of U.S. Copyright Office Practices). It also does not apply to certain US coins; see The US Mint Terms of Use.
|
 |
| This file has been identified as being free of known restrictions under copyright law, including all related and neighboring rights. | ||
File history
Click on a date/time to view the file as it appeared at that time.
| Date/Time | Thumbnail | Dimensions | User | Comment | |
|---|---|---|---|---|---|
| current | 01:17, 20 December 2008 | | 828 × 484 (73 KB) | Mdd | == Summary == {{Information |Description={{en|Physical Data Model —Options.}} |Source= [http://www.eaframeworks.com/TEAF/teaf.doc Treasury Enterprise Architecture Framework]. Version 1, July 2000 |Date=July 2000 |Author= Department of the Treasury Chief |
File usage
The following page uses this file:
Global file usage
The following other wikis use this file:
- Usage on no.wikipedia.org
- Usage on uk.wikipedia.org
