From actual code to UML?

[Fernando Sanz]

Hi there,
I'm trying to write the J2ME version of an existing J2SE application. I have the code, but no explanations about it.
So I thought a good idea would be to get all the UML and see if that way I'd understand better the general idea of the program.
I don't have much experience with UML, so I wasn't sure about how to start. What I've done is to write each class with its name, attributes and operations. Then, looking at the attributes of each class, I connected them with ------------<> so that I'd show which class containes which. So I ended up with a Main that uses a UI, and everything is conected through the UI and all the other classes. All those conections are of the type -----<>.
How would you proceed now? what should be my next step?
Thank you

[Lasse Koskela]

You could've downloaded a trial edition of Rational Rose and used its reverse engineering wizard for producing nice (well, theoretically nice) UML diagrams of the source code.

[Ilja Preuss]

Originally posted by Fernando Sanz:
Hi there,
I'm trying to write the J2ME version of an existing J2SE application. I have the code, but no explanations about it.

Do you have tests for the code?
How does the J2ME version need to differ from the J2SE version?

[Fernando Sanz]

Lasse: I finally tried RR, but I didn't manage to get it working. Then I downloaded ArgoUML, which did help me (I think) with the UML diagram. Although I think it's too big, so it came out quite messy. Maybe if I could print just one type of relationship at the time it'd be easier to understand; but it doesn't offer me too many options.
Ilja: what do you mean by "having tests"?
The main difference between the J2ME (actually, I'm finally using Personal Java) and the J2SE version is the use of AWT instead of Swing. Because of that, I have a problem with JEditorPane (the other bits should be quite easy/doable). The desktop version creates a model of a document, using JEditorPane, it does some tasks/work on it, and display a view of that model. It'd be a bit similar to using JTable; where you have a model that is doing all the work, such as sorting, and the table itself, that is displaying the data and taking care of its looks.