|
ABSTRACT
Data independence is a relatively new concept in database management technology. In essence, the objective of data independence is the insulation of application programs from the underlying database management system. The remarkably widespread appreciation for the notion is in part a result of the vigorous discussion generated by the reports of the Data Base Task Group of CODASYL and the Joint GUIDE-SHARE Data Base Requirements Group. While the pros and cons have been discussed at some length, very little has been written or spoken on the implications of data independence on the architecture of database management systems. It is the purpose of this paper to identify and elaborate on some of the problems associated with the design of a data-independent system.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
C.J. Date and P. Hopewell, File Definition and Logical Data Independence, proceedings of the 1971 ACM-SIGFIDET Workshop, November 11-12, 1971.
|
 |
2
|
|
| |
3
|
E.F. Codd, A Data Base Sublanguage Founded on the Relational Calculus, Proceedings of the 1971 ACM-SIGFIDET Workshop, November 11-12, 1971.
|
| |
4
|
CODASYL Data Base Task Group Report, April, 1971.
|
| |
5
|
GUIDE-SHARE Data Base Requirements Group Report, November, 1970.
|
| |
6
|
R.W. Engles, An Analysis of the April 1971 Data Base Task Group Report, Proceedings of the 1971 ACM-SIGFIDET Workshop, November 11-12, 1971.
|
| |
7
|
P. Lavallee, S. Ohayon, and R. Sauvain, Non—Procedural Access to DMS Databases, Proceedings 19th International XDS Users' Group Meeting, December 7-8, 1972.
|
|