In relational database theory, Armstrong’s Axioms are a set of three basic rules that describe the logical behavior of functional dependencies. These rules are sound and complete, meaning all valid functional dependencies can be derived from them.

Armstrong’s Axioms are used to:

  • Derive new functional dependencies from a given set.

  • Compute attribute closure.

  • Prove whether a functional dependency logically follows from a given set.

Three Basic Axioms

1. Reflexivity Rule

If YXY \subseteq X, then XYX \to Y.

  • Meaning: Any set of attributes functionally determines its own subsets.

  • Such dependencies are trivial.

Example:
If X={A,B}X = \{A, B\} and Y={A}Y = \{A\}, then {A,B}{A}\{A, B\} \to \{A\} holds.

2. Augmentation Rule

If XYX \to Y, then XZYZXZ \to YZ for any attribute set ZZ.

  • Meaning: Adding the same attributes to both sides of a functional dependency does not change its validity.

Example:
If ABA \to B, then {A,C}{B,C}\{A, C\} \to \{B, C\}.

3. Transitivity Rule

If XYX \to Y and YZY \to Z, then XZX \to Z.

  • Meaning: Dependencies can be chained together.

Example:
If ABA \to B and BCB \to C, then ACA \to C follows.

Derived Rules

Using the three axioms, several useful derived rules can be obtained:

  • Union Rule:
    If XYX \to Y and XZX \to Z, then XYZX \to YZ.

  • Decomposition Rule:
    If XYZX \to YZ, then XYX \to Y and XZX \to Z.

  • Pseudotransitivity Rule:
    If XYX \to Y and YZWYZ \to W, then XZWXZ \to W.

These rules form the basis for algorithms that compute attribute closure and verify valid functional dependencies.

How Armstrong’s Axioms Help in Design

  • They allow systematic derivation of all implied functional dependencies from a given set.

  • They support normalization by helping to analyze dependencies.

  • They provide a formal foundation for closure computation and key discovery.

Summary

Armstrong’s Axioms in DBMS are three basic rules—reflexivity, augmentation, and transitivity—that govern functional dependencies. From these, all valid functional dependencies can be derived. They are essential for understanding attribute closure, dependency reasoning, and normalization in relational database design.