We are wondering the best way to formally model our projects at the design phase before we start coding. UML doesn't seem to represent Spring apps very well, as the classes are glued together by Spring rather than by their direct relationships to each other. (I just reverse-engineered the UML for my last Spring project using myEclipse, and I mainly see a load of discrete interface/class implementation pairs.)
I did find this an issue also while I was coding that project, as a way to visually conceptualise the way the project hung together felt lacking.
What I really want is a convention to pictorially represent the Spring relationships together with the class relationships in my project (and then of course ideally a tool to forward and reverse engineer!)
Is there such a thing and I'm just missing it?


Reply With Quote
