title: Application Architecture in practice - Uncle Bob
body: <p>According Uncle Bob /<a href="http://www.youtube.com/watch?feature=player_detailpage&amp;v=WpkDN78P884#t=1672s" rel="nofollow">source</a>/, every user story should have separated "integrator/controller". Its sounds good because classes will be small and do the only one thing. </p>
  
  <p>But in the real world I didnt see architecture organized in that way. Always if there was eg AccountController it contained all methods related with Account. In Uncle Bob "way" this should be designed just like this:</p>
  
  <pre><code>+Controllers
  ---+Account
  ------+DepositMoneyIntoAccount
  ------+WithdrawalMoneyFromAccount
  ------+TransferMoneyToAccount
  </code></pre>
  
  <p>or maybe Im misunderstanding of Uncle Bob? But if not, have someone of you see architecture organized in this look? Its practical in real world?</p>
  
  <p>Regards</p>