Visual Studio Team Foundation Server
For the Information Needs of a Programmer/Analyst
The variety of hats that a programmer/analyst can wear within an organization is as large as the data consumption of the 21st Century is ravenous. The information needs that accompany these roles are just as large. Visual Studio Team Foundation Server is the answer. With a myriad of capabilities, a staggering level of customizability, and a powerful backend to handle most of the heavy lifting, TFS is the solution to the data access problems of the modern IS Department.
For the Information Needs of a Programmer/Analyst Job Description A
“My personal experience with TFS vs. (Subversion) et al is that initial setup for TFS is cake and provides excellent integration out of the box. My Svn/ VisualSVN/CC.NET/ NAnt implementation took me days to get installed and integrated (first timer!). Once up and running, they both work well, but (i) prefer TFS.” – Post from StackOverflow.com
Visual Studio 1
Team Foundation Server
Visual Studio Team Foundation Server
Initial Setup for TFS is Cake
1. Planning, developing, testing, and documenting new systems or modifications to existing systems The primary job that a programmer will have is systems development. They can be tasked with new systems development, to create a system where there hasn’t previously been one, or they can be tasked with modifying an existing system. The goal of legacy systems modification could be to add new functionality, improve old or broken functionality, or just modernize systems that were written with older technologies that can no longer perform their responsibilities efficiently, weren’t as scalable as currently necessary, or (especially in the case of web applications) are simply no longer supported. Either way, these tasks can be generated by requests from company personnel and/or clients, or the programmer/analyst may be responsible for suggesting and designing innovative modifications to applications employed within the organization. This puts the developers in direct contact with the clients, the end users, and any other stakeholders in the project. The more interaction the development teams have with their clients, the more likely the system will conform to their needs. The information access that programmers need for development, whether new or legacy, is as broad a spectrum as the job description. For legacy systems, the development teams need access to the source code, all previous documentation, including project descriptions, systems context diagrams, database model diagrams like ERDs, and anything else used to create the logic behind the system. They will also need access to any databases that the current system uses, any new ones that will need to be implemented to create the desired functionality, and any other databases within the organization (or the client’s organization) that need to be accessed by system. In addition, the developers need to be able to make contributions in one location, accessible by the rest of the team. While this may seem like a no-brainer, the complexities of the logistics of team collaboration (especially when team members are not geo-located), especially where source control is involved, can become staggering. Version tracking for all documents and code is an absolute must. One version control failure for a development team in full swing can set said team back days, weeks, or even months by the time it is discovered, especially if version tracking is poor. 2 Team Foundation Server handles these needs beautifully. For collaboration and...
Please join StudyMode to read the full document