Browse Prior Art Database

Configuration Management Using an Entity-Relationship Data Model

IP.com Disclosure Number: IPCOM000035723D
Original Publication Date: 1989-Aug-01
Included in the Prior Art Database: 2005-Jan-28
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Cardin, R: AUTHOR [+3]

Abstract

The article describes a data model that is used by the Configuration Development Facility (CDF). The CDF data model defines a data structure for, in this case, the definition of hardware device information.

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

Page 1 of 1

Configuration Management Using an Entity-Relationship Data Model

The article describes a data model that is used by the Configuration Development Facility (CDF). The CDF data model defines a data structure for, in this case, the definition of hardware device information.

In CDF, data is structured on the basis of the well-known entity-relationship (E/R) concept. The concept utilizes named entities. Entities can be physical and real or conceptual and abstract. Entities are classified according to type and described by means of attributes and attribute values. In this case, the entity types represent various classes of hardware devices, e.g., terminals, card readers, printers and processors. Entities can be related to one another and the relationship itself can be described by attributes. In this case, a relationship is established between hardware devices, i.e., device connectivity. The device-to-device relationship permits the specification of the following: 1. the two hardware devices involved in the

connection,

2. the two physical interfaces involved in the

connection,

3. the cables involved in the connection, and

4. the flow of control between the devices.

As a result of this E/R data structure, no multiple connection records for the purpose of defining multiple logical paths to a hardware device are required.

Another relationship is established between device address information (not device numbers) and specific (device) interfaces. In this case, only the part of the address that the in...