Course contentsShow
← Computer Science
Lesson 1622 of 2,87237. Database Design and NormalizationFree lesson

Functional Dependency Notation and Terminology

Learning the formal notation X → Y and key terms like determinant, dependent, and trivial vs non-trivial dependencies.

Functional Dependency Notation and Terminology

What you'll learn: You'll master the formal notation for expressing functional dependencies and understand the precise terminology database designers use.

Core Notation: X → Y

In database design, we write functional dependencies using the arrow notation X → Y, read as "X functionally determines Y" or "Y depends on X."

  • X is called the determinant (the attribute or set of attributes on the left)
  • Y is called the dependent (the attribute or set of attributes on the right)

Think of it like a math function: given the same input X, you always get the same output Y.

Example

Consider StudentID → StudentName, Major. Here:

  • StudentID is the determinant
  • StudentName and Major are the dependents
  • This means: if you know a StudentID, you can uniquely determine that student's name and major

Trivial vs Non-Trivial Dependencies

Trivial dependencies are always true but useless for design. They occur when Y is a subset of X:

  • StudentID, Major → StudentID (trivial—StudentID appears on both sides)
  • These tell us nothing interesting

Non-trivial dependencies provide real design information:

  • StudentID → Major (non-trivial—Major is not part of StudentID)
  • These reveal actual relationships in your data and guide normalization

Why This Matters

You need this notation to communicate constraints precisely. Saying "StudentID determines Major" in conversation is vague; writing StudentID → Major is exact and lets you apply normalization algorithms systematically.

Key Takeaway: Use X → Y notation where X is the determinant and Y is the dependent; focus on non-trivial dependencies (where Y isn't part of X) for meaningful database design insights.