Relational Data Model & Math Relations

CS403 Database Management Systems Lecture 14 marks the critical transition from conceptual database design to logical database design, introducing the theoretical foundations and structural properties of the Relational Data Model (RDM). While conceptual design employs semantic, graphical constructs such as Entity-Relationship diagrams that remain independent of specific database management systems, logical database design translates conceptual schemas into concrete, descriptive data models tailored for implementation. Historically introduced by IBM researcher Dr. Edgar F. (E.F.) Codd in 1970, the relational model revolutionized enterprise computing, supplanting older hierarchical and network models to establish the foundation of modern commercial database systems, including Oracle, IBM DB2, Microsoft SQL Server, and MySQL. The enduring prominence of the relational data model rests upon two foundational pillars: conceptual simplicity and mathematical rigor. Architecturally, RDM achieves simplicity by representing all data entities, relationships, and user views through a single uniform structure: the two-dimensional relation, or table. Rows within a table represent tuples or individual entity instances, while columns represent attributes. Grounded in formal set theory, a mathematical relation is rigorously defined as a subset of the Cartesian product of one or more attribute domains. Given attribute domains consisting of all permissible atomic values, their Cartesian product generates all possible ordered tuples; a database relation instance represents a valid real-world subset of those tuples conforming to a relation schema. The lecture details the six fundamental structural properties governing relational tables: first, every cell at the intersection of a row and column must contain an atomic, single value, satisfying First Normal Form; second, each column must possess a distinct attribute name; third, values appearing in any column must originate from the identical attribute domain; fourth, the horizontal ordering of columns is immaterial; fifth, the vertical ordering of rows or tuples is immaterial; and sixth, every row must be distinct, prohibiting duplicate tuples. This guide prepares Virtual University students for CS403 midterm examinations, solved past papers by Moaaz and Waqar Siddhu, and practice MCQs.