Azure DevOps Server: Difference between revisions

Revision as of 09:50, 11 July 2007

Revision as of 10:42, 12 July 2007

Line 3:

==Architecture==

[[Image:TFS.svg|thumb|225px|right|Team Foundation Server 3-tier architecture]]

Team Foundation Server works in a three-tier architecture: the ''client tier'', the ''application tier'' and the ''data tier''. The ''client tier'' is used for creating and managing projects and accessing the items that are stored and managed for a project. TFS does not include any UI for this tier, rather it exposes [[web service]]s which client applications can use to integrate TFS functionality with themselves. These web services are used by applications like [[Visual Studio Team System]] to use TFS as data storage back end or dedicated TFS management applications like the included ''Team Foundation Client''. The web services are in the ''application layer''. The ''application layer'' also includes a web portal and a document repository facilitated by [[Windows SharePoint Services]]. The web portal, called the ''Team Project Portal'', acts as the central point of communication for projects managed by TFS. The document repository is used for both project items and the revisions tracked, as well as for aggreagtedaggregated data and generated reports. The ''data layer'', essentially a [[Microsoft SQL Server|SQL Server 2005 Standard Edition]] installation, provides the persistent data storage services for the document repository. The ''data tier'' and ''application tier'' can exist on different physical or virtual servers as well, provided they are running [[Windows Server 2003]] or better. The ''data tier'' is not exposed to the ''client tier'', only the ''application tier'' is.

Most activity in Team Foundation Server revolves around a "work item". Work items are a single unit of work which needs to be completed. In many respects they are similar to a "bug" item in [[bug tracking system]]s such as [[Bugzilla]], in that a work item has fields to define Area, Iteration, Assignee, Reported By, a history, file attachments, and any number of other attributes. Work items themselves can be of several different types, such as a ''Bug'', a ''Task'', a ''Quality of Service Assessment'', a ''Scenario'', and so forth. The framework chosen for any given project in a Team Foundation Server defines what types of work items are available and what attributes each type of work item contains. These items are internally stored in [[XML]] format, and their schema can be customized to add other attributes to different items, or create new items on a per-project basis. Each work item has an associated control policies which control who is allowed to access and/or change the items. It also includes notification and logging capabilities to log all the creation, access or change events (controlled by policies) and optionally notify certain users when certain events occur.