Add a comment

 

Re: The delivery mechanism is an annoying detail

Good to see some Rational Rose vets in here ;) I spent about 5 years from 2001 with Rose on a large project which was half-EJB (we used session beans and connectors but not entity beans because their performance was terrible!). We used most of Rose's features from analysis downwards, and below a certain level generated the tedious aspects such as glue code. There was also a fairly formal hand-off between architecture, design and coding, and I was in all the roles at one point or other. What I learned from this process was that far from helping with managing scale and complexity (small projects typically having multi-purpose architecture/developer roles by nature), in a large project your model and division of responsibilities can become a burden. It got to the stage where our wiki which covered the architecture, design principles, idioms etc was far more useful than the model itself, simply because it was digestible and more easily applied. Having an architecture and good design / coding idioms was essential, but beyond that, rather than trying to scale up to lots of low-level developers with a couple of designers and trying to manage that with detailed modelling, you were better with just a small number of highly experienced developers who could cut across all levels, and who didn't really need a (full) model at all. I haven't used formal UML diagrams or model->code generation since 2006, and I don't miss them. :)

Re: The delivery mechanism is an annoying detail


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).