The first real step will be to think about what kind of data we need to store and then design a database schema to efficiently store that data. To keep things simple (but realistic), let's set our specification as follows:
Translated into a relational database schema, that means we'll have a
people table that will assign a unique identifier to each
Then we'll have an
addresses table that will allow each person to have multiple addresses, each consisting of a unique ID (so it's easy to reference later), a
location ("Office", ...