This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Not really I guess. A component diagram is a structural diagram. Although with the number of use cases the complexity increases, so with more use cases your structure will also be more complex, which will most likely result in a bigger number of component diagrams.