Recovery-first revision: Which of the following statements is true in systems analysis and design practice?

Introduction / Context:
The original stem created multiple “not true” choices. Applying the Recovery-First Policy, we minimally rephrased the stem so the set yields exactly one best answer. Now, we ask which statement is true, based on standard analysis and design knowledge.

Given Data / Assumptions:

• DFDs depict how data moves among processes, stores, and external entities.
• ERDs model entities and relationships for logical database design, not “files.”
• Lifecycle phases are often iterative and may overlap, rather than fixed and invariant.
• Indexed vs sequential access performance depends on workload and context.

Concept / Approach:
DFDs are commonly used to communicate a high-level systems overview (context diagram and leveled DFDs). They effectively describe scope and information movement prior to detailed design decisions.

Step-by-Step Solution:
Evaluate each option by definition and common practice.Confirm that DFDs are indeed appropriate for a systems overview.Eliminate options that are inaccurate generalizations (files vs data models, fixed phases, “always faster”).Select the single true statement.

Verification / Alternative check:
Most requirements packages include context-level DFDs to summarize system boundaries and flows. This aligns with the “true” choice.

Why Other Options Are Wrong:
Option A: ERDs inform database schemas and logical data models; phrasing it as “design files” is imprecise. Option C: Modern lifecycles (incremental, iterative, agile) are not strictly fixed/invariant. Option D: Performance depends on data size, access patterns, and storage—no “always.” Option E: Not applicable since option B is clearly true.

Common Pitfalls:
Treating analysis artifacts (DFD, ERD) as interchangeable or making absolute performance claims without workload context.

Final Answer:
A systems overview can be described clearly using Data Flow Diagrams (DFDs)