Doddy Christiana Saputra

The Component Diagram can show various classes, interfaces, pages, executables etc. packaged into deployable units called components. Components expose interfaces which are either the provider interface or the paired consumer interface. Component can have internal other multiple components which represent any deployable unit like web site, class library, page etc. and the container component can delegate the interface implementation to these internal components. In the following example the ITester interface of the Development component is consuming the ITester interface of the Testing component. Testing component has Tests and Unit Tests as further internal components. Tests component implements the ITester interface so the Testing component delegates tasks of ITester interface to Tests component. Similarly Unit Tests component implements IUnitTest interface so the Tests component further delegates the tasks of IUnitTest to Unit Tests component.


This diagram is a process artifact where we define the technology which will be used to implement the solution, components and their packaging, database schemas, UI models etc. Although in Beta 1 of Team System 2010 for Architects does not provide explicit tools for architects, it does provide a diagram named Component Diagram.

Cool Guys isn’t … see u later

This entry was posted on Tuesday, October 20th, 2009 at 1:20 am and is filed under VSTS / TFS, Framework & Architecture, Brainstorming, Customization, Design Pattern. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.