dev \ efor blog

dev \ efor architecture for enterprise edition

Posted February 12th, 2009 by Ersan

Hello,

Since we are getting close to release beta version of enterprise edition.. I’d like to give some information about the dev \ efor enterprise architecture…

The generic architecture of dev \ efor looks like this

Here goes the details…

Developers open their team projects… With dev \ efor enterprise client, they will let TFS server know, which workitems they are working on by clicking the assigned workitems to them, which looks like this

The activity datas for developers are stored in their local computer (which will make it available to use dev \ efor in offline mode ) and these raw activity datas will be available at the TFS server when developers check-in their files to the server…

The activity datas are sent to the dev \ efor web service which will be installed to an IIS server. The web service gather the raw activity data and stores it to dev\efor database which is installed to the same server with TFS databases.

If a check-in triggers a team build ( if you apply continous integration practice for instance) , the associated team projects code metric values are measured and also stored in TFS Database. As a thumb of rule, the code metric values are only measured and stored when you have a successful team build.

Then, the dev \ efor service gather these datas from devefor database and put them as custom facts and dimensions to TFS Warehouse which will make it available to use these values with out-of-box TFS Warehouse cubes and generate custom reports stored in warehouse ( such as number of bug per KLOC etc. )

We are planning to provide some reports out-of-box when you install dev \ efor such as trend of code metrics and effort metrics per workitem.

Cheers !

Ersan.