Thank you for your opinion but I don't ask it is better or is not to draw an activity diagram before text scenario or vs.

I ask! WHY when you create an activity diagram from use case scenario the EA adds ACTIVITY with the same name as use case has and then withih the activity creates activity diagram. WHY is not direct into activity diagram. And where we can get any explanation?

As for me I prefer text description instead of diagrams. But my friend - a RUP specialist -prefer to made model before text and obtain text from diagram following MDA.

That is an example for such approach: IBM Rational Harmony Deskbook Rel 4.1

I understand when I write steps of scenario. Then I can create activity (and other available) diagram. Why I have to made it through activity elements. Is it constraint of EA. Is it special practice? Where I can recognate with it?

if you select to create an activity diagram from use case scenario the EA adds activity with the same name as use case has and then withih the activity creates activity diagram. I can't understand why the EA creates the activity, where i can get any explanation of the behavior?

So it would a 'nice to have' feature if we could include referenced externally (to the current package tree) defined tables in our DDL generation. This might be along the lines of report generation options.