Browse Prior Art Database

Relationships in a Data Base for Program Design

IP.com Disclosure Number: IPCOM000039301D
Original Publication Date: 1987-May-01
Included in the Prior Art Database: 2005-Feb-01
Document File: 1 page(s) / 11K

Publishing Venue

IBM

Related People

Miller, DH: AUTHOR

Abstract

The preceding article describes a system based on an entity-attribute relationship data base. It assists developers in designing, building, testing and maintaining an integrated set of computer applications and comprises facilities to manipulate and interrogate information in the data base. Developers interrogate the data base to evaluate the impact of adding, changing, or removing design elements. The developers define entities such as fields, records, files, menus, modules, etc., which, together with their attributes, are related to each other in meaningful structures.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Relationships in a Data Base for Program Design

The preceding article describes a system based on an entity-attribute relationship data base. It assists developers in designing, building, testing and maintaining an integrated set of computer applications and comprises facilities to manipulate and interrogate information in the data base. Developers interrogate the data base to evaluate the impact of adding, changing, or removing design elements. The developers define entities such as fields, records, files, menus, modules, etc., which, together with their attributes, are related to each other in meaningful structures. To store both normal as well as inverse relationships in the data base, the files are organized as follows: Physical File Logical File 1 Logical File 2

Parent Name Key 1 Key 2

Child Name Key 3 Key 1

Sequence Number Key 2 Key 3 The records in the Physical File are stored in arrival sequence. The records in Logical File 1 are sequenced by child name within the sequence number and within the parent name. The records in Logical File 2 are the inverse and are sequenced by the Sequence Number within the Parent's Name and within the Child's Name. Both of the logical files cover the same physical file. Access is via the appropriate logical file.

1