Source Code Control (SCC)
SCC is the major contributor to Software Configuration Management. SCC in TFSincludes normal version control, Branching, Merging, Shelving and Unshelving etc.TFS maintains the source control in SQL Server 2005. By default it allows multiplecheck-out. We can place locks in such a way that either the locked files cannot bechecked out or if they are checked out they cannot be checked in. TFS also supportscheck-in policies which make it mandatory on the team members to execute certainactions when they are checking in some source code.SCC also works as a point of convergence between the team project and thetechnological solution. Team project allows for architecture, collaboration,monitoring and control of the project. It is very peripherally concerned with thetechnology. The technological solution does not involve itself with projectmanagement or versioning etc. Every unit of source code to be generated is taggedwith a work item. Work item store the management data about the technologicalentities. Storage and management of work items is done through SCC.
For every team project TFS creates a SharePoint portal site. This site containssections for Process guidance, Reports and documents. It provides appropriatepermissions to contributors, readers and guests. Through the process guidance wecan learn about the process template that is selected for the project. Various reportsprovide the health and progress of the project. Clients can have a look at the reportseven across the Internet for status monitoring.
Work Item Tracking
Work items are tagged collection of data representing some abstract entities liketask, bug, Quality of Service Requirement etc. We need to monitor status of each of these entities. At the same time each work item and entity pair will belong to a userat any given moment. The user will work upon the entity like task or bug and theneither set the status of the work item to close or re-assign it to some other user forfurther work on the entity. TFS keeps track of status of each work item and the userwho owns that work item at that time.
Each developer compiles the application in his / her workspace on the local machine.After compilation the code is checked in the source code control. The checked in codehas to be built to ensure its interoperability with code created at other time, maybe,by some other developers. This build process should be carried out periodically toensure integrity of all the checked in code. TFS allows creation of build at pre-