How does a DBMS that follows the relational model handle entities, attributes of entities, and ...

Entities and attributes are fairly simple. Each entity has its own table. The attributes of an entity become the columns in the table. In a relational model database a one-to-many relationship is represented by using common columns in two or more tables. More formally, a relation is essentially a two-dimensional table. Each column in a table should have a unique name, and entries within each column should all match this column name. Also, each row (also called a record or a tuple in some programs) should be unique. After all, if two rows in a table contain identical data, the second row doesn't provide any information that you don't already have. In addition, for maximum flexibility in manipulating data, the order in which columns and rows appear in a table should be immaterial. Finally, a table's design should be as simple as possible; you should restrict each position in a table to a single entry by not allowing multiple entries (called a repeating group) in an individual location in the table.