Visualization and Modelling Tools
-
Hi All, I've been out of the application development cycle for quite a while, but now need to touch up again (and quickly). So I was wondering which Visualization and Modelling Tools you would recommend to review, something like StarUML or RationalRose etc. Also which modelling "language" is mainstream these days, still UML, anything else perhaps ? Thanks OD
-
Hi All, I've been out of the application development cycle for quite a while, but now need to touch up again (and quickly). So I was wondering which Visualization and Modelling Tools you would recommend to review, something like StarUML or RationalRose etc. Also which modelling "language" is mainstream these days, still UML, anything else perhaps ? Thanks OD
-
Not much has changed has it. UML is still as standard and as next to useless, as it ever was and Rational Rose is still over priced and still flakier than VB6 on a good day. Modelling is still hard and few have the resources to do it at all let alone properly. I'd call it an opportunity for a major rethink and a developer driven push to update or replace UML with something practical and the tools to match. Time to stop being pushed into an inadequate way of thinking about software design by the limited range of agreement between a bunch of bickering professors. I'd like the kind of tools building architects have where they can wander around a building before they've built it and check out the view from the 5th floor balcony. Where they can try out different lighting designs and see what effect they'll have, calculate how much material they'll need automagically and see whether standard stairwells will fit or not. We wrote those tools so why can't we do as well for ourselves?;) Feel free to Soapbox this thread as you see fit.
Nothing is exactly what it seems but everything with seems can be unpicked.
-
Not much has changed has it. UML is still as standard and as next to useless, as it ever was and Rational Rose is still over priced and still flakier than VB6 on a good day. Modelling is still hard and few have the resources to do it at all let alone properly. I'd call it an opportunity for a major rethink and a developer driven push to update or replace UML with something practical and the tools to match. Time to stop being pushed into an inadequate way of thinking about software design by the limited range of agreement between a bunch of bickering professors. I'd like the kind of tools building architects have where they can wander around a building before they've built it and check out the view from the 5th floor balcony. Where they can try out different lighting designs and see what effect they'll have, calculate how much material they'll need automagically and see whether standard stairwells will fit or not. We wrote those tools so why can't we do as well for ourselves?;) Feel free to Soapbox this thread as you see fit.
Nothing is exactly what it seems but everything with seems can be unpicked.
Matthew, are there at least some commonly accepted Best Practices for documenting projects ? I have already decided that we will use Doxygen to document/comment the source code, but what do we use to depict the actual design/architecture/data flow/etc of our project ? Regards