In data flow diagramming, what are the processes at the most detailed (lowest) level of decomposition called?

Introduction / Context:
Data flow diagrams (DFDs) model how data moves through a system and how processes transform it. Analysts decompose complex processes into simpler ones across multiple levels. The smallest indivisible process that does one clear task is termed a functional primitive.

Given Data / Assumptions:

• Higher-level processes have been decomposed several times.
• Each lowest-level process can be specified by a mini-spec or structured logic.
• No further meaningful decomposition is needed for design and build.

Concept / Approach:
A functional primitive performs a single, well-defined transformation. For each, analysts prepare a process specification (using pseudocode, decision tables, or structured English) describing inputs, outputs, and rules. Decomposition stops when each primitive is implementable and testable independently.

Step-by-Step Solution:

Verification / Alternative check:
If further breaking a process adds no clarity or only repeats trivial steps, you have reached the primitive level. Document its logic and connect flows to stores and external entities.

Why Other Options Are Wrong:

Common Pitfalls:
Stopping decomposition too early leads to vague processes; going too far creates unnecessary complexity and maintenance overhead.

Final Answer:
Functional primitives.