How Visual Studio 2010 Ultimate edition helps in team productivity?
In this article , I have demonstrated how Visual Studio 2010 Ultimate edition helps in team productivity? I have also included two major features of visual studio 2010 ultimate edition i.e. architecture explorer and sequence diagrams. I hope this article will help you.
Introduction:
Project must have the starting point which can be given by Visual Studio 2010 Ultimate edition.
Most projects have their own code bases which can be used for further enhancement of projects.
Visual Studio 2010 Ultimate edition gives you new architecture tools which decrease the cost of maintainance.
It improves the project development because it gives the flow of information.
Involvement of UML part:
Visual Studio 2010 has feature of Sequence diagrams:
Developer needs to understand the sequence of calls to the method so that they make relevant changes accordingly.
The sequence diagramallows developers to right click a method to generate a full sequence diagram which shows all different classes that the methods are interacting with.
Other advantage:
The new architecture tool also helps to minimize the lack of system documentation in the first place.
Visual Studio 2010 Ultimate edition and TFS together provide the design experience that can be tied with the documentation.
User can get exact idea from design to documentation.
Visual Studio 2010 has UML 2.1 compliant modeling too.
Use case diagrams:
User , process and their activities together gives visualization of the system.
Visual Studio 2010 gives ability to link with one or more work items.
Visual Studio 2010 gives the clear picture to new developers about the system they are working on.
It reduces the time required to find the impact on the system if any change will make in the system.
Visual Studio 2010 has feature of architecture explorer
Architecture explorer which is a solution for most of the problem in traditional approach.
It determines what the application looks like from any of the levels.
Level can be method level , class level, namespace level, assembly level or any solution level.
It also gives dependency view which will help you to determine which items are connected with each other and which one is changing by you.
Developer can view the relationships and can analyze the modification impact which reduces the risk of the change.
This way developer can focus more time on project development and less time on fixing the existing issues if any.
Findnig this post solves a problem for me. Thanks!