The Architectural Logic of Database Systems

1. Front Matter

   Pages i-xiv

   PDF

2. Foundations of Databases

   • E. J. Yannakoudakis

   Pages 1-16

3. The Logic of the Database Environment

   • E. J. Yannakoudakis

   Pages 17-30

4. Data Structures and Data Models

   • E. J. Yannakoudakis

   Pages 31-62

5. The Architecture of Database Software

   • E. J. Yannakoudakis

   Pages 63-108

6. Communicating with Databases in Natural Language

   • E. J. Yannakoudakis

   Pages 109-134

7. Database Design Methodology

   • E. J. Yannakoudakis

   Pages 135-161

8. Canonical Synthesis for Database Design

   • E. J. Yannakoudakis

   Pages 162-192

9. Relational Architecture

   • E. J. Yannakoudakis

   Pages 193-213

10. A Network Database Language

    • E. J. Yannakoudakis

    Pages 214-237

11. Dictionary of Database Terminology

    • E. J. Yannakoudakis

    Pages 238-280

12. Appendix. Example Reports from Canonical Synthesis

    • E. J. Yannakoudakis

    Pages 281-309

13. Acronyms

    • E. J. Yannakoudakis

    Pages 311-312

14. Back Matter

    Pages 313-318

    PDF

If we look back to pre-database systems and the data units which were in use, we will establish a hierarchy starting with the concept of 'field' used to build 'records' which were in turn used to build higher data units such as 'files'. The file was considered to be the ultimate data unit of information processing and data binding 'monolith'. Moreover, pre­ database systems were designed with one or more programming languages in mind and this in effect restricted independent develop­ ment and modelling of the applications and associated storage structures. Database systems came along not to turn the above three units into outmoded concepts, but rather to extend them further by establishing a higher logical unit for data description and thereby offer high level data manipulation functions. It also becomes possible for computer professionals and other users to view all information processing needs of an organisation through an integrated, disciplined and methodical approach. So, database systems employ the concepts field, record and file without necessarily making them transparent to the user who is in effect offered a high level language to define data units and relation­ ships, and another language to manipulate these. A major objective of database systems is to allow logical manipulations to be carried out independent of storage manipulations and vice versa.

• Logic
• algorithms
• computer
• database
• database design
• database system
• design
• field
• form
• functions
• information
• modeling
• modelling
• programming
• programming language

• Postgraduate School of Computer Sciences, University of Bradford, Bradford, West Yorkshire, UK

  E. J. Yannakoudakis

Policies and ethics