Business Rules Analysis Flashcards

What does 'rule granularity' refer to in business rules management?

Answer: The level of detail at which a rule is specified — whether it is high-level policy or detailed operational rule

Rule granularity describes whether a rule is expressed at a high policy level ('All customers must be treated fairly') or at a detailed operational level ('Customers must receive a response within 24 business hours') — different levels serve different purposes.

In a business rules catalog, which information is typically included for each documented rule?

Answer: Rule ID, rule statement, source/authority, owner, status, and effective date

A complete business rules catalog entry includes: unique identifier, the rule statement, its source or authority, the owning business unit, current status, and effective dates for applicability.

What is the difference between a 'constraint' rule and an 'enabling condition' rule?

Answer: Constraint rules restrict behavior; enabling condition rules specify what must be true for an action to be permitted or triggered

Constraint rules restrict or prohibit specific behaviors ('You cannot...' or 'You must not...'), while enabling condition rules specify the conditions that must be met for a particular action to be allowed or triggered.

Why should business rules be maintained separately from process documentation?

Answer: Because business rules change more frequently and independently than process flows, and mixing them makes maintenance harder

Business rules change independently of process flows (due to regulatory changes, policy updates) and mixing them makes it harder to maintain both accurately — separate documentation enables independent lifecycle management.

Which of the following BEST illustrates a 'computation rule' in business analysis?

Answer: Annual bonus = base salary × (performance rating / 5) × bonus percentage

A computation rule defines how a value is calculated — specifying the formula or algorithm used to derive a result, such as a bonus amount calculated from salary and performance factors.

In requirements documentation, what is the BEST way to express a business rule?

Answer: As a precise, atomic, testable statement using clear conditional language

Business rules should be expressed as precise, atomic (single concept per rule), testable statements — this enables unambiguous implementation and clear acceptance testing.