Hi! > Regarding the last sentence: interesting. What other criteria mightthere > be? (For example, an iTunes-style "SmartList" that fetches allclasses > with, say, a particular stereotype?)
As Bob mentioned, you could put together classes on a diagram that are connected by associations, generalizations, depedencies and such. With ArgoUML I find it easy to manually do this thanks to the property panel and the "add to diagram" feature for edges in the explorer pane. But some more automation is possible (e.g. "add all associated elements"). > Let's say we import the project as an ArgoUML model, and the > generateddiagrams are useless. As you say, the imported sources provide > "thebasis 'vocabulary'". Didn't that just save use from creating > hundredsof classes manually? Even if every diagram was hand-crafted in > orderto be useful, that import rather nicely automates the most > tediouspart. Exactly! That's why I'm mostly import with generation of diagrams disabled, and then I start working on the diagram free model. > Yeah. There are tons of ways to use ArgoUML. That's one reason I'm > sointerested in the project. :) Some ideas here: 1. generate a class diagram with a package overview (can be fully automated, easy layout algo) 2. generate a component diagram for all the jar files, even dig deeper by analysing dependencies 3. use classes and even method bodies for easily contructing sequence diagrams (I started this but got stucked) 4. generate a collaboration diagram from a sequence diagram 5. create dependencies between use cases and packages/classifiers/diagrams and create diagrams for that use case using these dependencies ... (The new dev wiki could be a nice place to exchange ideas) Thomas -- GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion! http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
