Content deleted Content added
→Reporting: more |
→Reporting: shared services |
||
Line 18:
TFS uses its logging framework for automated data collection as well. The logging infrastructure monitors and logs information regarding access and use of the work items and source code, which can then be used by the analysis services to find trends. TFS includes a warehouse adapter in the data tier, which caches data from the underlying normalized database in a form suitable for analytics - in fact tables and dimension tables. [[SQL Server Analysis Services]] are then used to analyze this data, and reports created. Reports can span multiple work items including bug trends, code churning, build trends amongst others. Other analysis applications can also use the data directly pulled off the web services.
===Shared services===
TFS provides a handful of services that can be used for integration with other applications like [[IDE]]s and [[Project Management System]]s. The ''linking service'' allows loosely coupled relationships to be created between items, for example a ''bug'' item and the source code revision(s) it applies to. The ''security services'' allows creation of security groups from users, to which access rights are then assigned. The ''classification service'' allows definition of policies to automatically classify items based on a multitude of criteria and the ''eventing service'' allows any component to raise an event and a notification action assigned to the event. The notification can be either using [[web feed|feed]] [[syndication]] or e-mail, or invoking other web service.
==Team build==
| |||