title: Can a component consists of different classes from different layers?
body: <p>I am currently drawing a component diagram. The architecture follows what a typical MVC3 application - controllers, services and model (using a repository pattern). </p>
  
  <p>Can a component, says User Management, be comprised off classes from different layer? For example, the User Management component consists of its controller, service and model. </p>
  
  <p>However I present the User Management component as such, how do I show that the service is also a 'component'? That is, it can be swapped out from another service that implements the same interface?</p>
  
  <p>Does it defeat the purpose of a component design if a class by itself is a component?</p>