title: EF Code First, Model First or Db First? for a many changing medium-large app
body: <p>We are going to develop a medium-large customized web app for a private company using MVC 4 and EF 5.</p>
  
  <p>Early analysis and previous experiences on that business field show that it will have more than 150 tables/entities and because our customer isn't a software engineer and we know that our data model will change many times through the progress of the project.</p>
  
  <p>Now, my Q is which approach is better for us according of the following:</p>
  
  <p>1) Causes less effort on updating data model and data store because of many changes that will occur.</p>
  
  <p>2) Takes less time to create the data store and helps progress the project faster.</p>
  
  <p><strong>Note</strong>: This app will work with big sets of data (10k, 100k objects for some entities). However, it will have few (and maybe sometimes no) concurrent requests and online users.</p>
  
  <p>Thanks in advance</p>