Current SP88 work models Batch Objects in the diagrammatic notation pr
omoted by Rumbaugh et al. This notation represents independent object
elements and their possible relationships generally, with a different
emphasis than object programming languages like C + +, whose objects a
re built out of component objects. The notation models arbitrary objec
t structures, but it blurs the essential (aggregation) hierarchy of th
e Application Model and its component subObjects, with the inheritance
hierarchy and other relationships. Like many first notations its comp
lications need to be pared down to a rememberable set of three or four
icons. This paper will use an equivalent, tutorial variant, for Proce
ss Control Batch modeling and pairing down the concepts. The applicati
on is modeled as a single whole with logical, Self-Similar, parts, div
ided either in terms of the logical parts of the corresponding process
, or in terms of the associated distinct control functions. This frame
work emphasizes single applications, aggregated from parts. Inheritanc
e of similar process or equipment subObjects are expressed by similar
names or icons. This paper will outline the parts of a general Batch m
odel and relate this model to the author's earlier language papers. (C
) 1997 Published by Elsevier Science B.V.