Database systems analysis and design
Developments in the database field have tended to emphasise programming technology, with a dearth of accompanying progress in systems analysis and design methods. This paper puts forward an overall view of system design which is intended to act as a constraining framework. It is based upon a pragmatic approach and is presented in a form which could be (and is being) used on large scale implementation projects.
Orderly analysis and design procedures are encouraged. The taking of premature design decisions is discouraged, especially through the recognition of three distinct views of data: conceptual, implementation and storage, and through recognition of distinctions between design of each of these, specification of mappings between them, and design of programs and run sequences. It is envisaged that specific procedures developed elsewhere (see references) could be incorporated into the methodology described here.
KeywordsData Item Record Type Access Path Attribute Subset Schedule Requirement
- 1.ANSI X3 SPARC/DBMS Study Group Interim Report, February 1975.Google Scholar
- 2.CODASYL DDLC Journal of Development 1973. Revised 1975.Google Scholar
- 3.CODASYL COBOL JOD as modified by the DBLTG Database Facility Proposal, March 1975.Google Scholar
- 4.Brown, A.P.G. "Entity Modelling" IFIP TC/2 Conference 1975 (Pub. North Holland Book Co.)Google Scholar
- 5.Robinson, K.A. "Description of stored data, using modified NCC Standards", Private communication, 1974.Google Scholar
- 6.Bramhill, P.S., and Taylor G. "Database Design. From Codd to Codasyl". To be published in "Database Journal", 1976.Google Scholar
- 7.BSC/CODASYL DDLC DBAWG June 1975 Report.Google Scholar