ACM Home Page
Please provide us with feedback. Feedback
A method for describing information required by the database design process
Full text PdfPdf (1.22 MB)
Source International Conference on Management of Data archive
Proceedings of the 1976 ACM SIGMOD international conference on Management of data table of contents
Washington, D.C.
SESSION: Session III - logical design table of contents
Pages: 53 - 64  
Year of Publication: 1976
Author
Beverly K. Kahn  The University of Michigan, Ann Arbor, Michigan
Sponsor
SIGMOD: ACM Special Interest Group on Management of Data
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 42,   Citation Count: 16
Additional Information:

abstract   references   cited by   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  

ABSTRACT

Current research in the area of database design has been directed towards the development of structured or automated database design techniques. The first phase of the database design process, information requirements specification and analysis, is unfortunately ignored. The lack of concern for whether or not the input to the design techniques can be collected in the real world and for wheather or not the input is an adequate and complete representation can only result in an inadequate and possible useless database design.Most database models and design techniques utilize only process-oriented information. Other techniques utilize non process-oriented information whose foundation may not be clearly identifiable. The use of only process-oriented information may result in a narrowly defined unimaginative database design which may be unresponsive to the changing needs of the organization. To overcome the shortcomings of this traditional approach, it is necessary to complement it with an additional approach.This can be accomplished in three steps. First, the description and use of the information required for the database design process must be clearly stated. Second, two independent perspectives for viewing the required information must be considered: the information structure perspective and the usage perspective. The information perspective depicts the natural characteristics of data, inherent groupings and relationships. This perspective is not bound to existing or future applications; hence it is a more general and flexible view of information than one which is process oriented. The usage perspective describes how data items are utilized by the system in order to accomplish its processing requirements. Third, a vehicle for aiding the specification itegration of these two independent perspectives must be considered.


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
AURDAL 1975 Aurdal, Eivind, "A Mulit-Level Procedure for Design of File," CASCADE Working Paper No. 39, University of Trondheim, Norway, 1975.
2
 
3
BASTARACHE 1975 Bastarache, Michel J., "Problem Statement Analyzer Users Guide," ISDOS Working Paper No. 90, The University of Michigan, Ann Arbor, Michigan, May 1975.
 
4
BELFORD 1975 Belford, Genieva G., "Dynamic Data Clustering and Partitioning," Research in Network Data Management and Resource Sharing, Preliminary Research Study Report, University of Illinois, Champaign -Urbana, May 1975.
 
5
CODD 1971a Codd, Edward F., "Further Normalization of the Data Base Relational Model", IBM Research Report RJ909, San Jose, CA, August 1971.
 
6
CODD 1971b Codd, Edward F., "Normalized Data Base Structure: A Brief Tutorial", Proceedings of the 1971 ACM SIGFIDET Workshop on Data Description, Access, and Control, Ann Arbor, MI, May 1974, pp. 1-17.
 
7
 
8
DISSEN 1975 Dissen, et al., "Problem Statement Analyzer Command Descriptions," ISDOS Working Paper No. 91, The University of Michigan, June 1975.
 
9
HERSHEY 1975 Hershey et al., "Problem Statement Language Version 3.0 Language Reference Manual," ISDOS Working Paper No. 68, The University of Michigan, May 1975.
 
10
 
11
HOFFER and SEVERANCE 1975 Hoffer, J. A. and Severance, D. G., "The Use of Cluster Analysis in Physical Data Base Design," Proceedings of the International Conference on Very Large Data Bases, Framingham, MA, September 1975, pp. 69-86.
 
12
HUBBARD and RAVER 1975 Hubbard, G. and Raver, N., "Automating Logical File Design," Proceedings of the International Conference on Very Large Data Bases, Framingham, MA, September 1975, pp. 227-254.
 
13
IBM 1975 IBM, Data Base Design Aid General Information Manual, GH 20-1626-0. IBM, Data Base Design Aid - Designers Guide, GH 20-1627-0.
 
14
KAHN 1975 Kahn, Beverly, K., "A Review of Systems Analysis and Data Base Design Techniques," ISDOS Working Paper No. 129, The University of Michigan, November 1975.
 
15
KAHN 1976 Kahn et al., "Data Requirements Description and Analysis Reports," ISDOS Working Paper No. 136, The University of Michigan, 1976.
 
16
KROHN 1973 Krohn, M. J., "Use of the Computer as a Systems Documentation and Design Aid," Approaches to Systems Design, ed. by Boot, 1973, pp. 105-111.
 
17
MARTIN 1976 Martin, James, "Third Normal Form," Computer Data-Base Organization, Prentice-Hall, Englewood, NJ, 1975, pp. 169-178.
 
18
MATHERS 1974 Mathers, James O., "The Data Independent Access Model, A Review and Discussion," COINS Technical Report 74A-1, February 1974.
 
19
 
20
MITOMA and IRANI 1975 Mitoma, M. F., and Irani, K. B., "Automatic Data Base Schema Design and Optimization," Proceedings of the International Conference on Very Large Data Bases, Framingham, MA, September 1975.
 
21
RAMPE 1975 Rampe, Gayla, "An Approach to Data Base Design," unpublished paper, AT&T Lone Lines, White Plains, NY, 1975.
22
 
23
SENKO 1974 Senko, M. E., "Data Description Language in the Context of a Multilevel Structured Description: DIAM II with FLORAL," IBM Research Report #6769, 1974.
 
24
SEVERANCE and EISNER 1975 Severance, D. G., and Eisner, M. J., "Mathematical Technique for Efficient Record Segmentation in Large Shared Data Bases," unpublished paper, Cornell University, 1975.
 
25
SHEPPARD 1974 Sheppard, Donna L., "Data Base: A Business Approach to System Design," unpublished paper, Cincom Systems Inc., August 1974.
 
26
SPARC/DBMS 1975 ANSI/X3/SPARC Study Group on Data Base Management Systems, Interim Report, American Standards Committee Project 226, Document No. 7514TS01, CBSMA, Washington, DC, 1975.
 
27
STEVENS 1974 Stevens et al., "Structured Design," IBM Systems J. 2(1974), pp. 115-139.
 
28
STRUNZ 1973 Strunz, H., "Systems for Systems Development (A Review of the Current State of the Art)," Approaches to System Design, ed.by Boot, 1973, pp. 53-62.
 
29
TEICHROEW 1971 Teichroew, D. and Sayani, H., "Automation of System Building," DATAMATION, August 15, 1971, pp. 25-30.
 
30
TEICHROEW 1974 Teichroew et al., "An Introduction to PSL/PSA," ISDOS Working Paper No. 86, The University of Michigan, March 1974.
 
31
TEICHROEW 1975 Teichroew, D. and Bastarache, M., PSL User's Manual," ISDOS Working Paper No. 98, The University of Michigan, March 1975.
 
32
Teichroew, D., and Bastarache, M., "PSA Reports," ISDOS Working Paper No. 99, The University of Michigan, July 1975.

CITED BY  16