Rational Rose vs. Together J

Discussions

General J2EE: Rational Rose vs. Together J

  1. Rational Rose vs. Together J (2 messages)

    Can anyone recommend using one tool over the other for modeling a J2EE application, and why you think so.
  2. Having used both in fairly large projects, I can say I prefer Togethersoft's Control Center over Rational Rose.
    Togethersoft integrates modelling, coding, CVS control, design patterns, etc into a pretty slick interface. The only down-side to Togethersoft is that it's quite a resource hog; you better have a decent machine to run it on.

    I beleive you can download an evaluation copy of Control Center from Togethersofts site.

    Glenn

  3. 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!

    Creates:
    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

    Cons:
    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