Experience-how the project is divided into modules (MVC)

In general, there are only two cases:
If we have a project that looks like this:
Look for one, like a group of us:

• Sub-module according to MVC

  • Root directory Controller

    • Buy
    • Door
    • Business
    • It's mine
    • More

  • Model

    • Buy
    • Door
    • Business
    • It's mine
    • More
  • View
    
    • Buy
    • Door
    • Business
    • It's mine
    • More

• Divide MVC by module

  • Buy
    
    • Controller
    • Model
    • View

  • Door

    • Controller
    • Model
    • View

  • Business

    • Controller
    • Model
    • View

  • It's mine

    • Controller
    • Model
    • View

  • More

    • Controller
    • Model
    • View

We are now to compare, of course, two models have a company in use, we can not say to the company, see such a division, it is very surprised, ordinary heart treatment.

• If the first division of the way, such as: Our business view needs to tell the controller (proxy, etc.), or the controller needs to transmit value and so on. Then have to go to such a large pile inside to find the corresponding controller, is not feel a little bit inconvenient.
• Then the second relatively, it solves the problem, so according to my personal advice, I choose the second kind, of course, we also do not too tangled, follow the company.

Experience-how the project is divided into modules (MVC)