Introduction
This
document provides comprehensive process model of MSF CMMI and what can be
customized. Each
process template in Team Foundation Server provides a different set of default
work items, work item queries, product templates, reports, security groups, and
guidance. In addition, each process has a distinct and different philosophy of
software development practice that dictates how the process template works
within Team Foundation Server.
MSF for CMMI Process Improvement
provides rich connections to the CMMI process to help organizations quickly
implement mature software development practices. This site contains updates to
the process guidance, bug fixes, and supporting material for this process.
Process Template can be downloaded
from following link.
Reference:
Process Guidance can be downloaded
from following link.
Team members use work items to track work to
be done. Depending on the installed methodology, such as MSF for CMMI Process
Improvement or MSF for Agile Software Development, a selection of types of work
items, such as bug, requirement, risk, and task, will be available to the
members of your team.
Dashboard
can be used to define the process of your company. From the dashboard link could be
provided to documents library where all documents templates are managed.
Build
types in Team Foundation Build are set to designate a specific build computer.
The build computer must be setup appropriately in order to be used as a build
computer. This section covers the build computers installation and
prerequisites.
Reference:
http://msdn.microsoft.com/en-us/library/ms181711(VS.80).aspx
Team Foundation source control can be
customized by administrators to meet the specific needs of a team. Code Check
in Check out can be managed via TFS.
Team Foundation source control provides
standard source-code version control functionality, which can scale to handle
thousands of developers. Beyond the typical source control functionality, Team
Foundation is also an enterprise class software configuration management product
that provides integrated version control, issue tracking, and process
management for development teams.
Team Foundation source control
includes the following features:
Besides being integrated into the
Visual Studio environment with other Team Foundation technologies, such as
creating a build and work item tracking, the source control also includes a
stand-alone graphical user interface and a command line interface.
Reference:
http://msdn.microsoft.com/en-us/library/ms243831(VS.80).aspx
http://msdn.microsoft.com/en-us/library/ms181237(VS.80).aspx
Team System Web Access is a customizable Web interface that can access Team Foundation Server project data.
· Create, view, query for, and track work items.
· Manage a project's document libraries.
· View version-controlled files and related version information.
· Manage the software build process by running builds and reviewing build results.
· Generate reports to track status and trend information over time for a team project.
· Customize browser themes and user settings.
Document
Library will be created in share point site once MSF template based project is
created.
Team Foundation security is based on users
and group.
Team
Foundation Administrator Can install and maintain a Team Foundation Server, in
addition to administer permissions and security for other roles. Members of
this group are the only ones who can create new projects on an Team Foundation
Server. Can also customize process guidance. This is the most privileged group,
and should be restricted to as few users as possible.
Team
Project Administrator Also known as a project manager or a project lead, this
role can maintain a team project work item database and project portal. Can
administer permissions and security for the team project. This is the second
most privileged group, and should be restricted to as few users as possible.
Team
Project Contributor
Can access, read, and write work items, view the team project Web site, and
view process guidance for a team project. This is the group that most users
will belong to. The following table summarizes the permissions that are
required for each example role.
|
Role
Must Be a Member of: |
Team
Foundation Server Administrator Role |
Team
Project Administrator Role |
Team
Project Contributor Role |
|
Application-tier and data
tier-computer groups |
Windows Administrators |
n/a |
n/a |
|
Team Foundation Server default
groups |
Team Foundation Administrators |
Project Administrators |
Contributors |
|
Windows SharePoint Services groups |
Site Administrator |
Project site-level Administrator |
Project site-level Contributors |
|
Reporting Services groups |
Content Manager, Site Administrator |
Project site-level Content Manager |
Project site-level Browser |
Customization of MSF
Process guidance is the content that
documents your specific software development process.
Make your
changes and customize the process guidance by editing the source XML files.
Use the
MSFWinBuild tool to pre-render all the XML source content into HTML files. The
HTML files open with static content and yield faster performance.
As you make
changes, you can view the changes in a browser to verify that they are correct.
If you created
or deleted files during customization, update the manifest in wsstasks.xml to
make sure that the correct process guidance files are installed when a new team
project is created.
Note
MSFWinBuild automatically updates
wsstasks.xml to list the HTML files created by MSFWinBuild.
| You must Sign In to use this message board. | ||||||
|
||||||
|
||||||
|
||||||