The Goal of The EDA Is to Have a Methodological Project The goal of the EDA is to have a methodological process to help you learn about a new data set. Rea

The Goal of The EDA Is to Have a Methodological Project The goal of the EDA is to have a methodological process to help you learn about a new data set. Read the instructions first, work on a detailed EDA with R studio. Instruction of the Project
You are interviewing for a job at Zillow. Jennifer Lee, the recruiter, has provided you a data set
on 2014-15 home sales in King County that she would like you to analyze, find several insights
on the market, and write up your findings. This is effectively a test of your basic analysis and
communication skills. Jennifer says you can work on this with one of the other job applicants
because they want to see your ability to work in teams. She understands that you do not know
much about the housing market so may need to bounce ideas off of each other. The specifics of
the task are outlined below. Jennifer will be sharing your findings with the Zillow hiring
manager, so it is critical that your writing and graphs in the memo are clear to people without a
technical background and concise for someone that has limited time.
The data set “kc_home_sales.csv” contains the following variables:
1. date: date of the sale
2. price: sale price of the home
3. bedrooms: number of bedrooms in the home
4. bathrooms: number of bathrooms in the home
5. sqft_living: house size in square feet, not including garage
6. sqft_lot: lot size in total square feet
7. floors: numer of levels in the house, x.5 means there is a split-level
8. waterfront: lot is located on the water
9. view: home has a view, higher number means better view
10. grade: quality of initial home build and finishing’s, higher is better
11. condition: the overall maintenance of the home, regardless of initial build quality or grade
12. yr_built: year the home was built
13. yr_renovated: most recent year the home was renovated, 0 if not renovated
14. zip_code: the zip code of the home’s neighborhood
15. lat: latitude location of the home
16. long: longitude location of the home
Each observation is for the sale of a specific home
Your Task:
• Complete a base and detailed EDA in an R Notebook as your Technical Appendix.
(Please take a look at the Example-Technical Apeendix.rmd first, follow each step to
complete the new Technical Appendix).
• Use a variety of tidyverse data verbs to select, filter, group, mutate, and summarize
variables—be adventurous!
• Create exploratory and presentation visualizations.
• Knit the Technical Appendix with a table of contents to show all code and output. Make
sure your code is well documented and include data comments/questions regarding your
findings. Remember code documentation is in the code chunk and data comments are
after the output (but leave a blank line between output and data comment so they begin on
a new line). You may want to label sections by EDA step and/or the question you are
exploring to organize the TA. Save visuals so you can load them in your memo.
• Determine your two preferred market insights for the King County housing market and
create presentation quality visuals to support each finding. Though you may create many
graphs in your EDA, you will only want to use a several of your visuals to illustrate your
findings. It is important the visuals are easy to understand so make sure it is not
complicated or cluttered, with clear titles and axis labels. I expect you to have at least
two nicely formatted visuals; quality is more important than quantity.
• Write up a two-page, four-paragraph summary of the project:
a. An introduction: why is the analysis important, a brief description of the data, and
a brief description of your findings. Think of this as an executive summary.
b. A paragraph and presentation quality visual(s) for each of the two findings. If
you have more than two findings then you have to decide which you think are the
most important. You can mention other findings in a sentence or two in the
conclusion/summary.
c. A conclusion/summary.
• Knit these as a Word memo with text and visuals (no code) from RMarkdown
(Take a look at the word memo example files I provided, fill out the proper
heading). Write the memo for a lay audience—no code, no technical visuals
(boxplots and correlation graphs are technical so do not use them), and no jargon.
The memo with visuals should be 2 pages or less.
Submit the technical appendix and Word Memo

Purchase answer to see full
attachment