I was just reading this article and I think it would be useful to add the steps for
keeping the UML model up to date when the code changes.

I'd assumed that you did this from the UML project, not the Java project so it
took me a
while to find it.

The 2-way round trip stuff is a very powerful Netbeans feature and I think it's
worth
boasting about! 

The tutorial is about reverse engineering to UML, which implies that a body of
Java source code already exists. In my case I used one of my projects, of about
60,000 lines of code instead of the bank account example as I wanted to see it
in action on a realistic sized project. I've used several tools that make great
demos but collapse when given real work to do so I'm naturally sceptical.

On a real project there's probably other people making changes, which puts the
model out of step with the code. Or you might come back to the UML model some
time later and its now out of date with changes you've made to the source.

So I thought it was worth maybe just adding a section near the end to show how
to bring the model back up to date with the code. The way this works is
currently counter-intuitive IMO as you want to update the UML model but have to
do it from the Java project.

E.g. something like close UML project, change Java source, open UML project
update the model and confim the change is now reflected in the UML, or whatever
actions make sense as I'm not in Netbeans at the moment.