Victoria .NET UG VSTS Topics Anyone?

Comments

# Kent Sharkey said on August 5, 2005 08:55 PM:

I'd like to see something like, "A day in the life of VSTS users." Show a class as it goes from design, through coding (with Source Control), then testing.

Alternately, something on MSF/Agile, as I haven't found much there yet.

Or, whatever I can get from you for a new article ;)

# Jason Kemp said on August 5, 2005 09:43 PM:

Deployment questions:
I've tried to install VSTS Beta 2 but the TFS install dies 'cause I don't have SharePoint. What are all the MS products required to get the thing installed?

Suppose I already have spent a lot of time, money and effort building a custom formal process around my tools for version control, document repository, bug database, unit testing, profiling tools, etc. Why should I switch to Team System?

And what is it REALLY going to cost my company of, say, 50 people? How much hardware? Software Licenses? And maintenance of all the above.

Is it easy to keep my <insert tool here> and use the rest of the TS (think NUnit, CVS, Bugzilla)?

Is it worth getting the whole system if the architect, developer, and unit tester is the same person?

Technical questions:
I can't for the life of me find how to turn on coverage. Where do I do that?

How easy is it to write custom add-ins to force VSTS into the process my company uses?

I wouldn't mind seeing an end-to-end demo of the developer tools: take a design, write the code, test the code, perf the code.

That's all I can think off the top of my head :)

I'm looking forward to your talk. If you're preparing this early, it should be great. I usually prepare the night before :) BTW, can you a link to the victoria user group home page on the left there.

# Paolo Marcucci said on August 7, 2005 11:02 AM:

It would be interesting to see how the whole VSTS methodology could be scaled from teams of 5 to 50 to 500 devs.

# Nolan Zak said on August 7, 2005 06:34 PM:

Kate Gregory had a really good question today: http://www.gregcons.com/kateblog/PermaLink.aspx?guid=fbc94b50-1cb8-4965-aa09-b40c9727d073

# Jean-Daniel Cusin said on August 9, 2005 03:23 PM:

One of the Team System articles lists the following requirements of a well integrated, automated software development life cycle and development environment. It would be great to see you demonstrate the essential features of Team System to corroborate with this list, perhaps using a small development going through its life cycle process as an example.

-Capture, analyze, and manage requirements; identifying trace relationships between requirements, architectural design and implementation constructs, enabling validation that requirements have been implemented, and supporting impact analysis when requirements change.

-Define software architecture in a way that supports security, performance and reliability analysis, and other forms of evaluation; and in a way that enables predictable assembly of systems from components, and efficient and reversible step-by-step transformations from requirements and deployment,

-Define how the executable components of a system are packaged, identifying the types of resources in the deployment environment required by each component, and binding the components to specific instances of those resource types,

-Define test cases, test data sets, test harnesses, and other artifacts, making it easier to evaluate the quality of software developed using models, and to manage and display the test results

-Identify traceability relationships between models and other artifacts, making it easier to support business impact analysis when systems go down, configure systems to satisfy requirements, and enforce constraints during system configuration,

-Define configurations of source artifacts used to build executables, making it easier to version those configurations, and to associate defect reports and feature change requests with specific versions.

# Jonathan Zack said on August 25, 2005 12:39 PM:

There seems to be much confusion out there regarding how Team System will be used by non-developer types. For example, how will deployment of the Team Explorer (aka Team Foundation Client in the beta) work for employees without the full Visual Studio 2005 IDE on their desktops? Also, how will licensing work for employees just using the Team Explorer? Staying under 5 licenses (http://msdn.microsoft.com/howtobuy/vs2005/editions/team/#pricing) will be tough even for small companies if licenses apply to those using just Team Explorer.

I don't think we have to spend too much time on this topic but it is definitely something that should be clarified.

Thanks!

# Jason Kemp said on August 30, 2005 01:07 AM:

I've been toying with MSBuild lately. What kind of MSBuild support does VSTS have? Can I use the features from the IDE in my daily build script? If so, which ones and how is it done?

# Jared Warren said on August 30, 2005 11:55 AM:

Focus on workflow more than technical details: if the workflow is good enough we'll learn to live with whatever the details are. If you're going to demo tests, we'd find it much more valuable to see it from a test-driven perspective than test-after. How seemfully do other revision control systems plug in? How are templates and code-completion plugins developed?