Most of the analysis process focuses on the EDFD representation.
By restricting the requirement for manifestation in an EDFD to these relationship types, we would remove the rule's conjectural status.
Every functional attribute of an entity would have to appear as a function in the EDFD that decomposes that entity.
In such cases we can represent the state-transition logic in an EDFD by assigning a different function to handle the data in each range.
The design generator maps entities in an EDFD to ordinary objects in an object diagram.
EDFDs are just like conventional DFDs except that the nodes fall into two categories: entities and functions.
Lower level EDFDs decompose each active entity either into subentities or into functions performed by the entity (or into some combination of the two).
An object-oriented specification consists of a hierarchy of EDFDs and a set of entity relationship diagrams.
The first of these requirements provides us with a straightforward semantics for EDFDs. The second requirement is our insurance that the specification will be objected-oriented.
Besides checking for new functions, we need to examine the EDFDs and reassess the placement of functions already present.
The analyst must be open to reorganizing the EDFDs in this step.
It does not make use of the expressive power of the EDFDs themselves.