Hierarchy

Common section for discussion of glossary terms. Please create a new topic for each term.
User avatar
Bradford Van Treuren
SJTAG Chair Emeritus
Posts: 152
Joined: Fri Nov 16, 2007 2:06 pm
Location: VT Enterprises Consulting Services, USA

Hierarchy

Post by Bradford Van Treuren »

This post is about the term "Hierarchy" and how that relates to P2654, P1687.1, 1687, and 1149.1-2013. There are also adjective qualifiers used to provide context to what is being referred to as the hierarchy.

From IEEE 1149.1-2013:
Hierarchy: Objects may be contained (used) in other objects in a tree-type arrangement with no loops; that is, no circular references. The containing (outer, higher) object is referred to as the parent, and the contained (inner, lower) object is referred to as the child, and they are said to be in a parent-to-child relationship. In this standard, only user Packages and Test Data Registers have hierarchy. Packages may “use” (refer to) other packages. Test data registers may be composed of segments and fields, where segments may be composed of other segments and fields. Fields may not contain other objects. See also: instance and instantiation.

From IEEE 1678-2014:
Network Hierarchy: A configuration of modules with host-client relationships (i.e., where one module is a host relative to a client module on its right and a client relative to a host module on its left, using the convention that the device interface is on the far left and the instrument interface is on the far right).
Bradford Van Treuren
Distinguished Member of Technical Staff
VT Enterprises Consulting Services