Deliverables: Identifying the Parent of a Deliverable

November 11th, 2004 (kb#45)

If a Deliverable is an input or an output to a Node, it should have a parent Deliverable if the Node has a parent Activity on a higher-level map.

When this child/parent relationship is initially established, the child Deliverable stores a record of its parent. This record contains the name (as represented by a Deliverable's displayed text) and shape reference ID of the parent Deliverable. Later, when verifying the identity of a Deliverable's parent, the following rules when comparing the parent record and potential parents are applied in this order:

  1. Seek to match by name.
  2. If there are several higher-level Deliverables that match by name, then the shape reference ID is used to distinguish between them.
  3. If there are several higher-level Deliverables that match by name, but there is no match on shape reference ID, then the first Deliverable that matches by name is chosen.
  4. If there is no match on name, then the shape reference ID alone is used.

This mechanism allows parent/child relationships to be maintained even when parent Deliverables are renamed, but also to retain the conventional method of matching by name used by Process Navigator when making associations between elements.

Comments