Browse Prior Art Database

Mechanism for System Internal Communication Control During Development, Maintenance and Execution

IP.com Disclosure Number: IPCOM000085349D
Original Publication Date: 1976-Mar-01
Included in the Prior Art Database: 2005-Mar-02
Document File: 3 page(s) / 39K

Publishing Venue

IBM

Related People

Belady, LA: AUTHOR [+2]

Abstract

In a programming system comprising the code and the data objects on and with which the code operates in execution, the data objects may be referenced or have their value or content changed from many different places in the code. While, during execution, one is concerned with the location and value of the objects, during the initial programming process and the subsequent code maintenance and enhancement process the attributes of prime importance are the name or identity, the structure and the meaning or semantics of each object. Whenever any one of these three attributes is changed, it is necessary to check and possibly modify every occurrence of that data object in the entire code to compensate or allow for the change that has been made in the object.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

Mechanism for System Internal Communication Control During Development, Maintenance and Execution

In a programming system comprising the code and the data objects on and with which the code operates in execution, the data objects may be referenced or have their value or content changed from many different places in the code. While, during execution, one is concerned with the location and value of the objects, during the initial programming process and the subsequent code maintenance and enhancement process the attributes of prime importance are the name or identity, the structure and the meaning or semantics of each object. Whenever any one of these three attributes is changed, it is necessary to check and possibly modify every occurrence of that data object in the entire code to compensate or allow for the change that has been made in the object.

The purpose of the described mechanism is to add a level of dynamic checking that, at execution time and during either testing or production runs, detects any occurrences of Any object that was modified, or modified and tested, at the time of the last change to that object. The subject mechanism provides that free communication between different elements or objects, such as program modules and data arrays, be restricted by being channeled through an internal access method or map. This is essentially a table in which there is associated with each element a collection of information, for example, when the code was last modified and/or other development related data.

All elements or modules of a programming system, whether under development or ready for execution, are resident in the files, i.e., outside some (virtual) address space. Elements are exposed to each other or some unauthorized user only if they are loaded into a virtual address space, for development or execution. Clearly, a monitoring/protection mechanism is needed with a speed commensurate to that of the CPU.

Loading is performed by a special pa...