Difficulty: Easy
Correct Answer: Functional primitives
Explanation:
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:
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:
1) Start with a context diagram and level-1 processes. 2) Iteratively explode complex processes into sub-processes. 3) Stop when a process becomes a single, implementable unit—this is the functional primitive.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:
Transform descriptions are the textual specs, not the process node's name. Data flows are arrows connecting processes and stores/entities. Interfaces are boundaries between systems or modules. External entities are sources/sinks, not processes.Common Pitfalls:Stopping decomposition too early leads to vague processes; going too far creates unnecessary complexity and maintenance overhead.
Final Answer:Functional primitives.
Discussion & Comments