Mike,

In my opinion if you don't have a tool like Rose, and the time and training invested in using it, the UML, and a compatible methodology, then you're just not in the ballgame when it comes to analyzing and designing medium to larger sized applications involving more than one developer.

Visual Modeler is unsuitable because it does not support scenario and state diagrams. It also crashes like the stuffed pig that it is.

Also, forget about any benefits you may presume come from round trip engineering. It just doesn't happen unless you are creating something real trivial. It's over touted and essentially limiting and useless.

Rose is useful for apps of all sizes, yes.

The UML is now a universal standatd, so learn it. Yesterday. I can't fathom understanding a contemporary OO book or article without it.

Note that in Rose you aren't creating a "framework for code". You're modeling. Like if you use AutoCad you're not creating a "framework for a house", you are drafting.

If you're involved with more than one other developer and a bunch of stakeholders then I strongly recommend Requisite Pro from Rational -- it's the best and most useful product they make.

IMO