Hey, does anyone know of a tool that I can use to convert existing java docs into some sort of UML diagrams?
Within my company there is a large (ridiculously large) amount of code which has no UML attached to it.
Is there any tools that can transform code/java docs or Large Database in UML? (I need to document the DB aswell)
Cheers,
T.
> > Cheers Aleen I'll have a look into this now and
> > CeciNEstPasUnProgrammeur thanks once again for a
> > ground breaking answer........ *cough*cough*
>
> yDoc was the second featured link on Google.
But it's a lot of effort, isn't it? *rolleyes*
> Yes, but I was asking for an opinion on which tools
> are good..... sorry if I neglected to use the words
> "personal recommendation".
In that case you also neglected to state your specific requirements, as some tools might more appropriate for your environment than others.
Also, in that case, Aleen's reply was just as unhelpful, as nothing was said about it being "good".
Tom, requests for tools normally don't go down well unless you show that you have already done some ground work in finding them.
So posting something like: I've searched for web for them, and found yDoc and ArgoUML (1). Does anyone have any xp with them, and can recomend one or the other, or a different tool to do the job?
Otherwise if just looks like you are too lazy to search the web. You might find that unfair, but most posters here are too lazy, or inexprenced to search the web themselfs. This is naturally rather irratating when the answer is the first or second hit in Google.
1) Which can build from source, not JavaDocs, they were not (last I used) well formatted. Plus the UI is not all that great. Maybe Poseidon for UML (a none-free version of Argo, but with a nicer UI) does a better job.
> OK, I'm assuming were not 12 years old here. So how
> about we grow up, this is a place for finding helpful
> resources not for making snide remarks and nursing
> already big egos...
Do you know the difference between a broad and a specific question? If you want to know "which Javadoc-to-UML tool is free, easily usable, well documented in <insert language here/> and provides output in <insert format here>" - why don't you ask so?
If you ask some tool vendor which tool is "good" without further specifying what you mean by that, he'll tell you that his tool will be good - because "good" means to him he'll earn money selling it.
What is a "good" vehicle? Can you tell me that? Which one should I buy?
It's not about egos. It's simply about not expressing requirements that obviously exist, because - and that's certainly human and happens to me as well - they're so blatant to you that you don't feel the need to express them. Others don't share your mental context, though, and can't guess what you need.
cheers MLK, and I know the original posting was at the very least least vague, I'm still not 100% on the politics of this forum and I did notice it does draw a lot of homework/lazy users and I guess it's naive of me to assume you can tell the difference between people genuinely working in this industry to people getting other people to there work.
I have looked into ArgoUML, like you said it is far from fancy. I'm trying to configure yDoc for a large sized project but I get the impression that it is dedicated to smaller sized projects.
> > OK, I'm assuming were not 12 years old here. So
> how
> > about we grow up, this is a place for finding
> helpful
> > resources not for making snide remarks and nursing
> > already big egos...
>
> Do you know the difference between a broad and a
> specific question? If you want to know "which
> Javadoc-to-UML tool is free, easily usable, well
> documented in <insert language here/> and provides
> output in <insert format here>" - why don't you ask
> so?
>
> If you ask some tool vendor which tool is "good"
> without further specifying what you mean by that,
> he'll tell you that his tool will be good - because
> "good" means to him he'll earn money selling it.
>
> What is a "good" vehicle? Can you tell me that? Which
> one should I buy?
>
> It's not about egos. It's simply about not expressing
> requirements that obviously exist, because - and
> that's certainly human and happens to me as well -
> they're so blatant to you that you don't feel the
> need to express them. Others don't share your mental
> context, though, and can't guess what you need.
Rene, I didn't mean for you to get worked up. I apologies.
