Decision tables in systems analysis: What best describes a decision table and its purpose in specifying system logic?

Difficulty: Easy

Correct Answer: documents rules that select one or more actions based on one or more conditions

Explanation:


Introduction / Context:
Decision tables are a classic analysis tool used to express complex business rules in a compact, testable format. They complement data-flow diagrams and process narratives by focusing solely on conditional logic and the actions that follow.


Given Data / Assumptions:

  • We need a definition that emphasizes conditions and actions.
  • Decision tables are tabular, not graphical like flowcharts.
  • They are used to reduce ambiguity in requirements and testing.


Concept / Approach:
A decision table enumerates possible combinations of condition states (for example, true/false, ranges, categories) and maps each combination to the corresponding action set. This format prevents missed cases, supports coverage analysis, and translates cleanly into test cases or code branches.


Step-by-Step Solution:
Identify the essence of decision logic: condition evaluation → action selection.Recognize that decision tables list every relevant condition across columns or rows.Actions are specified per condition combination, ensuring completeness and consistency.Select the option describing “rules that select actions based on conditions.”


Verification / Alternative check:
Analysts often derive test matrices directly from decision tables; if each condition combination maps to a unique action set, execution and testing are straightforward.


Why Other Options Are Wrong:

  • Represents the information flow: That is a data-flow diagram’s role.
  • Accurate picture of the system: Too vague; many tools provide “pictures.”
  • Shows decision paths visually: More like flowcharts or decision trees; decision tables are tabular.
  • None of the above: Incorrect because option describing rules and actions is correct.


Common Pitfalls:
Forgetting to include “don’t care” states; mixing data movement with rule logic; not normalizing overlapping rules which can cause conflicts.


Final Answer:
documents rules that select one or more actions based on one or more conditions

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion