მოგეხსენებათ Visual Studio Team System არის ძალიან მოსახერხებელი თულების ერთობლიობა რომლიც აადვილებს პროექტებზე მუშაობას. მისი სხვადასხვა დანამატები შესაძლებლობას იძლევა გუნდურად მოხდეს მოცემულ პროექტზე მუშოაბა. დაწვრილებითი ინფორმაცია შეგიძლიათ ნახოთ ვიკიპედიაზე
ამონარიდი:
In the modern world of development, developers no longer work alone or in groups of three
or four people in a set of side-by-side cubicles. Today’s developers typically work in larger
teams scattered across the globe. Developers have become a global commodity. Many companies
in the United States perform some type of outsourcing in which they hire developers who
work in India, China, Canada, Russia, or other parts of the United States. This presents a
unique challenge to software project teams.
Development teams may include project managers, developers, architects, testers, support
staff, and others. How do the team members communicate? What information should be
shared, and whom should it be shared with? Should some people have access to some code
but not other code? These questions apply not only to developers located in different parts of
the world, but also to teams that work in the same building or the same city.
დავამატებდი იმას რომ მოსახერხებელია პროექტების მენეჯმენტი (ინტეგრაცია მაიკროსოფტ პროჯექტთან და ექსელთან, ხდება თასქების გაწერა, ბაგების აღწერა, იუნით ტესტირება, ტესტირება იუზერების გარკვეულ რაოდენობაზე და ა.შ ასევე თითოეული პროექტისთვის იქმნება პორტალი რომელიც წარმოადგენილია შეარფონთის ვებსერვისების სახით.
ამონარიდი წიგნიდან თუ რაა უპრატესობები :
What Are the Benefits of Using Visual Studio
Team System?
Who would benefit from using VSTS for their projects? In short, the answer is everyone.
Specifically, it benefits project managers, architects, developers, testers, infrastructure architects,
users, and stakeholders. Here’s how:
• Project managers can get up-to-date information on which items on the project
schedule are being worked and when they are completed through familiar tools like
Microsoft Project and Excel.
• System architects can design an application as it applies to the network infrastructure
and communicate that to the deployment and development team.
• Infrastructure support gets a solid understanding of the deployment needs of the
application.
• Technical architects can design classes, relationships, and hierarchies that automatically
generate skeleton code.
• Developers can look at the class diagrams to understand what is occurring. Any changes
they make to the code will be reflected in the diagrams—no reverse-engineering of the
model is necessary. Code can be effectively unit tested.
• Testers can use integrated testing tools, which allow for more thorough testing. Tests
can also be run automatically via automated build tools.
• Application stakeholders can view reports on the progress of the application through
Microsoft SharePoint Services.
As you can see, many individuals can benefit from the use of VSTS. These benefits translate
directly in a higher return on investment because everything becomes easier and faster
for everyone.
Aside from individuals who benefit from using VSTS, organizations and departments will
also find tremendous advantages in using this tool. The first and most obvious benefit is that it
promotes communication between team members, which is crucial to the success of a project.
It allows for problems to be caught early and solved quickly before they become serious
issues that affect the schedule. These problems can range from developers not completing
work on time to bugs in the code.
VSTS also allows for the analysis of work across multiple projects. It becomes simple for
organizations to track their project history and use that information to predict future project
schedules. Projects can be reported on by category, developer, deliverable, milestone, and so
on. You literally have the power of an online analytical processing (OLAP) database at your
fingertips, filled with all of your project information down to the code level and bug-tracking
level. To achieve this type of reporting, you’ve needed to use several different, costly systems.
With VSTS, it is all rolled into one integrated system.
All of these benefits come down to one thing: a higher return on investment with one
tool than you would get with combinations of tools. When you use one tool for each area of
development—such as Borland JBuilder for development, CVS for source control, Rational
ClearQuest for issue tracking, Cognos ReportNet for reporting, Ant for building, and JUnit for
testing—it becomes exceedingly difficult to keep things simple. On the other hand, you have
the following benefits with VSTS:
• VSTS allows all developers to use one tool with which they are familiar. It does not
require a developer to learn how to use six different tools to perform the task.
• VSTS integrates all of the needed functionality, including a project management tool
and reporting tool, directly into one interface—something that no other integrated
development environment (IDE) can do in its out-of-the-box version.
But let’s say that you have an in-house testing tool that you would rather use than the tool
that comes with VSTS. Because VSTS is an extensible environment, integrating other tools into
it requires a minimal amount of work (depending on what you want to integrate). Many tool
vendors have been working with Microsoft to create integration points with their tools so that
you can swap them with ones that come with VSTS. You are not locked into a wholly Microsoft
solution.
All of these points lead to only one conclusion: there is no downside to using VSTS.
ჰოდა ახლა რა მაინტერესებს, ვინც იყენებთ როგორ შეფასაებდით
და ხომარიცით ჩემთან დოკუმენტები რატომ არ არის team explorer-ში (წითელი ხაზი აქვს გდასმული)
მადლობთ ყურადღებისთვის
This post has been edited by Lekso-Dav on 22 Apr 2010, 19:52