If I tell you, I have to…

You may also like...

6 Responses

  1. RJ says:

    Tweakers.net disaggrees :

    Soma Somasegar, vice-president of Microsofts Developer Divisision told today that the next CTP of VS.NEt 2005 will become available this april 🙂

    http://www.tweakers.net/nieuws/36132 (sorry dutch)

    But after reading the source and your interpretation i guess tweakers.net is wrong after all 🙂

  2. Versant’s O/R mapper is in beta for quite some time. It’s one of the most overrated and expensive pieces of software I’ve ever seen. But then again, some people just want to pay way too much for software 😉

  3. Chrissy says:

    Dennis! You are here? I am too. Let’s meet. email me. [email protected] 🙂

  4. @Frans : Hehehehe, I can’t believe them either! Some are even willing to pay to see a product presentation of some large company. I have heard… 😉

    But seriously, never heard of the product. My guess however is, that whenever the product is released, there will be a pretty amount of marketing, also sponsored by Microsoft. Then everyone will believe that’s the product to have, because of the MS "support" and every other OR/M will be judged based on Versant’s tool! 🙂

    Kinda sucks, doesn’t it?! 😉

  5. Erwyn van der Meer says:

    You’ve probably read it elsewhere by now, but in fact Indigo and Avalon WinFX CTP is scheduled to be released before Beta 2 of Visual Studio 2005 and the .NET Framework 2.0. As such the WinFX CTP will be based on a different build of the .NET Framework 2.0. And it also means it will ship with an older build of VS 2005 that is tuned especially for Indigo and Avalon.

    If I interpret the post http://blogs.msdn.com/brada/archive/2005/02/09/369802.aspx by Brad Abrams correctly, the WinFX CTP will be released within the next few weeks.

  6. James says:

    Requirement Management tools will increase requirements definition phase by:

    providing more administrative functions for BA’s

    overcomplicating the simple analyst activities (Adam & eve stages of scratching around drawing models)

    creates more documents

    decreases productivity with unnecessary system burdens

    employing a very user unfriendly interface for end users

    irritating to use, very idiosyncratic

    Other points:

    Respected industry professionals steer clear of these tools (such as Craig Larman)

    Software development is not predictive manufacturing but new product development, therefore re-use at best is negligible

    Low tech tools such as paper and pens are faster, easy to use and can be performed anywhere

    BA’s typically talk, workshop and write up requirements, therefore MS Word is perfect for this

    Customers buy working software, not glossy specs or models

    Facilitates documentation development, not software development!

    Software development is about great people working close, not great tools working for "me".

    In the wash up it won’t improve software end products for customers. People and OO training do!


    beaurocratic steps just to set up and maintain documents

    has many unnecessary "add ins" such as advanced traceability and version control.

    most source code it generates is unusable


    Doesn’t control scope, just creates more hurdles to document and maintain scope

    Are over-priced drawing tools with sub standard workflow

    Is incredibly expensive per staff head

    Conflicts with many departments use of a document repository

Click on a tab to select how you'd like to leave your comment

Leave a Reply

Your email address will not be published. Required fields are marked *