Before writing tables you need to decide what things your system tracks and what you know about each one. Entities are those things, like students or courses, and attributes are their properties. Use this when turning a problem statement into a design, for example spotting that phone_numbers is multivalued or that a dependent has no key of its own. Store raw facts and compute derived ones like age, and expect "what is a weak entity?" in interviews.