Assume that the development team has come up with the following high level user stories:

$\backslash$table$[[$Story ID$,$Story description$],[$US$1,$As a User$*,$ I want to search for and view property listings by zip code$],[$US$2,\backslash$table$[[$As a User$*,$ I want to send a message to the owner$/$agent of a property$],[$that I am interested in$]]],[$US$3,\backslash$table$[[$As a Premium User, I want to perform an advanced search for properties$],[$matching my preferred area$/$price$/$home type, etc.$]]],[$US$4,$As a Premium User, I want to list a property that I own, for rent$],[$US$5,$As a Premium User, I want to list a property that I own, for sale$],[$US$6,\backslash$table$[[$As a Real$-$Estate Agent, I want to list a property for sale, on behalf of my$],[$client$]]]]$

The role name "User" is used in stories that apply to both Free and Premium Users.

Activity tasks:

Perform high level conceptual design:

From the given high level user stories, extract a few main entities that are relevant to the database aspect of the application $($i$.$e$.,$ entities that need to be persisted in some form$).$ Hint: look at the nouns in the application vision and user stories to help you identify entities.

Identify main relationships between these entities that are relevant to the database aspect of the application $($i$.$e$.,$ relationships that need to be represented in some form within the database$).$ Express these relationships in simple English phrases$/$sentences $($e$.$g$.,$ "Employee works for a Department", "Department has a Manager"$).$ Hint: look at the verbs and connectors in your user stories to help you identify relationships.

FORMAT:

Entities:

Entity $1$

Entity $2$

Relationships:

Entity $1$ relationship phrase $>$ Entity $2$

Remember: This is only a high level conceptual design. It is unlikely that you will think of every single entity and relationship at this time.