Rose diagrams and their usefullness
Spotted this on Ted Leung's blog
The second presentation was on Model-Driven Development using Rational XDE. This just didn't do much for me, because I'm not a fan of RUP or ROSE, etc. I've used some tools to produce RUP diagrams from code, but I've never found tools like this to be helpful in the forward direction. Mostly they make it easier to deal with the structure of classes and objects, but specifying control flow via sequence diagrams is less efficient than banging out the code. Unfortunately for Rational, the speaker agreed -- he said he frequently writes code that he usese to generate the sequence diagrams. The presentation was short, and not that much of a product pitch.
Kind of funny that the speaker did that, actually...
Comments
Re: Rose diagrams and their usefullness
[Rich Demers] May 21, 2003 15:57:11.675
Comment on Rose diagrams and their usefullness by Rich Demers
I shudder every time I think of my last exposure to ROSE/RUP. The "architects" had done a half-baked UML model in Rose and gotten the "dev team" to sign off. This was considered a great improvement over the complete lack of design/direction previously in place. The dev team proceded to code from the model, and forbade the architects from doing any further design work. Disaster! Half-baked is half-baked and you never get a finished cake that way. It's OK to start developing with a partial design, but work on the design has to continue - with revisions as necessary. But then, this was a RUP project, a waterfall in the extreem.