Rational vs MS Team System

How is Rational going to react with the arrival of MS VSTS. Here are some thoughts:
- java? Obviously, if you have a client with java project or mixed java-.net projects, it seems clear that those cies would remain with RAtional suite.
- rational tools are stable and available now. VSTS will come out in 1.0 version in 2005. Probably not until 2006 that bugs will be ironed out. From now until then, it will be a long and bumpy road. any project that starts until then should consider rational tools, unless you are willing to experiment. In which case, ensure you have Microsoft support (ie. the client must be big and the project meaningful to VSTS team)
- let's face it, MS VSTS 1.0 is not going to be great for projects with large teams. I expect performance issues, probably conflicts, painful use in distributed delivery projects, etc. VSTS will probably be great for small teams (<10-20 people total I would think) in the same location. Then again, such small teams cannot afford Rational suite so there is VSTS market target...
- IBM is planning a complete revamp of their rational products in Q404, with much better performance for tools like XDE, which will become integrated into eclipse and written from scratch to use EMF. Round trip engineering will be easier and much faster.
- finally, VSTS is a first cut that focusses on the most burning SW development issues. It deals mainly with communicating tasks to various team members but leaves the soft eng aspects of the work behind. For example, the diagramming tools are very basic and do not yet support code generation a-la-MDA. This is where developer productivity will increase the most by allowing them to focus on design rather than code (plumbing). Rational is already targetting those applications and there are numerous open source tools available on the market.

Posted in |

2 comments:

  1. Farid Mheir Says:

    eweek has some comments from Grady Booch of Rational, basically going in the same directrion that I was going to in this blog.
    http://www.eweek.com/article2/0,1759,1598889,00.asp

  2. Sam Guckenheimer Says:

    I’m surprised by your blog. This week at Tech Ed, Microsoft is announcing Visual Studio Team System almost a year before its release, and we have been briefing partners and customers for nine months before. I realize that we have our work cut out for us to educate people on our offering but with so much lead time we should have ample opportunity. In this context, your conjectures seem out of place I’d like to comment on each of your points.

    - java? – we demonstrated first-class integrations with tools from Borland and Compuware. You can fully expect that the extensibility of Team System will be used by our partners to provide a first-class Java development environment too.
    - rational tools are stable and available now – certainly, they are available now. Microsoft has a year to stabilize Team System and fully understands the quality expectations of its customers. We will welcome your comparison of stability when we ship.
    - let's face it, MS VSTS 1.0 is not going to be great for projects with large teams -- Much of VSTS is the productization of tools Microsoft uses internally, in teams of thousands of software engineers. You question that VSTS will have adequate performance – we’ll gladly accept that challenge and we’ll relish the comparison in Total Cost of Ownersihp.
    - IBM is planning a complete revamp of their rational products in Q404 – Since IBM has made no announcements here, we can only guess. If your assertion is true, then it sounds like IBM/Rational customers will also face a V1 product and your challenges may be well placed there too.
    - finally, VSTS is a first cut that focusses on the most burning SW development issues. -- We agree with that.
    For example, the diagramming tools are very basic and do not yet support code generation a-la-MDA. – Actually, the SOA designers and class designer generate code with complete fidelity (no lossy roundtrips, no GUIDs in your face, and no need to maintain models separate from your source).
    Farid, I applaud your enthusiasm for the good things about Rational. If you use the same lens to view Visual Studio Team System, I’m sure your enthusiasm will spread there too.
    Sam Guckenheimer
    Group Product Planner
    Visual Studio Team System