In the SA graphical language of SADT precisely the same box-and-arrow graphic syntax and semantics (as a package) is used for completely dual Activity Modeling and Data Modeling (and perhaps, similarly also for States versus Transitions of modeled systems).
|
Activity Modeling (per box) |
|
|---|---|
|
Box name verb; Arrow label noun |
Box name noun; Arrow label verb |
|
Control required; May omit all Input |
Input required; May omit all Control |
 |
 |
The omission permission ("May omit...") properly is a feature of the pragmatics (the interaction between meaningful signs and their users) of the SA language. Except for that choice, A and D also have the same DT pragmatics -- especially in their sharing of SA's Reader/Author Cycle which makes the use of natural-language names and labels practical.
Hence in SADT, both data and activities (modeling real-world things and happenings, respectively) can be well-structured and always are intimately related together.
The natural way to relate any modular subject matter to an SADT model (and especially to self-relate, together, the A- or D-Model parts of a Complete SA Model) is to use:
For either Data or Activity subject matter, each unit of modular meaning is classified into its own unique box of meaning in the well-structured SADT model. By definition --
The end-box's node number then is assigned to the item, as a tag, in the original modular structure.
If the effective atomic level, even of multiple models, is colored with the rainbow colors, then the SA model's structure can be contour-mapped onto the Tied subject document.
When this is done for self-mapping the A and D parts of a complete SA model (of models...) all external boundary arrows (which specify the boundary conditions for all the Top Boxes) will have been mappped into the dual-model boxes, so
Every arrow-label's meaning will have been mapped to the dual model, and the A and D dual atomic-level boxes therefore have tightly-prescribed meanings that are requirements to be met by features of any putative instance of what has been modeled. The degree of penetration toward the two atomic levels is a quantitative measure of the "fit" of the model to the classified subject.
Because IDEF0 only models activities by boxes, and the "data or
objects" of the new IDEF0 standard are only modeled by arrows (never
having a chance at the SA Box role) -- there is no way to more
precisely map IDEF1X entities to IDEF0 modeling. [IDEF1X is an
entity/relation type of database design methodology that only shares
the IDEF name.]
Although all SA arrows are drawn with solid lines, these deeper views graphicallly show their semantics.
A possibility is that which may (but need not) BE.
When it IS -- that is called the realization of the possibility. See the above illustration for ordinary interface sticks and Call sticks.
O-to-I and O-to-C (and O-to-M, too), are the interfaces between the box parts of a diagram whole. They may join and fork (collectively called branching) and are realized by non-forking sticks between blobs (as shown). Thus SA has "sticky blob semantics".
If all are primitive sticks, the entire vine (from roots to tips) would have the same meaning if any segment is labeled. If different parts of several such vines are bundled together, however, they are insulated from each other by an insulating sheath, and may branch arbitrarily. But after such bundling, any new label will be a constraint on the sticks of possibility that pass through its segment. Any branch of any vine that conflicts with the new label is killed off, as a ruled-out possibility. Those that survive are what make up the actual ICOM meanings at all the boxes through which they pass (each one seeking its terminating atoms). Throughout all this,
To animate or simulate the meaning, the sticky blobs of possibility can be tagged as realized, to correspond to Colored Petri Nets, etc.
Notice that the tunneled Input shown here on the uppermost box should have a O-side tunnel, like the leftmost box, because it shows how the same standard tunnel syntax/semantics can show the explicit distribution of Support for ordinary Child-Diagram tunneled boundary arrows, which always have been a fixture of SA, but have needed more complete syntax.
