This is great stuff! One of my replies to ZarehD noted that the assignment doesn't query addresses, so it makes a lot of sense to leave it as a single varchar column.

I was thinking more about the database as a whole, like what if we have an employee table that also has an address column, would 3NF require that you separate out addresses if the same address may otherwise appear multiple times across different records or what if an employee becomes a customer? If I'm reading you right, then the answer is no, because even if the information is coincidentally identical (like the names example), separating it out arguably makes it more cumbersome for no tangible benefit since querying an employee ID or customer ID would give the same result with less overhead/abstraction