component view packages/components

[Mr. Sanders]

Hi,

I never would switch back to rose too.
I found over 50 bugs in one of its latest releases (tracked by rational/ibm) and I still get bug fixes with the bugs reported by me.

This tool was a pain in the end to us. And a company like rational who declares to have the software process defined, is in shame when they release such a buggy tool for that price. The support was mixed. Some people were excelent (greets to Lara), but most of them where really poor and we had to tell them how to workaround their bugs.

No! No rational tool! Never again. The pain was to long and to expensive.

We are very lucky having found EA.
We try to switch all our customers from rose to EA.

But EA has its dark corners too, I think (as a newbee).

Is there a good description how to work with the component packages/views?

This seems to be very different and IMHO with bad usability.

Greets Michael

[thomaskilian]

Nothing is perfect  
http://www.sparxsystems.com.au/component_model.htm
http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.cgi?board=UMLPRO;action=display;num=1094774376

[Mr. Sanders]

Hello,

No, that isn't what I want.
This is just describing UML.

I mean how to use the components with the tool.

Example (rosebased  )

In rose you drop your classes on a component.
Than when you want to have generated all classes in one component, than select the component and press ctrl-g (generate code).

than you get all component related classes generated.
and you can build your component with the compiler.

In EA this seems not to be possible.
When drop the classes on a component, than the are not related in any way (this was our last discussion i know).

But when I select the component and press ctrl g (generate code) EA generates a source file with a class named like the component. This is nonsens. A Component is not a class. All classes inside the component are NOT generated.

So I have to select them manually and generate them (having to know which classes are in which component  ).

How is this done in EA. It's a bit cumbersome and even false I think. Why do they generate a class for a component.

Another strange thing are the namespaces.

Normaly the namespaces are named like the package names.

Not in my case. They start with "component view"....

Even If I use an alias in the component view the wrong namespace is generated.

How are the namespaces handled in the compont view?

Greets Michael

[CJ]

G'day,

Not in my case. They start with "component view"....

Sorry, I don't have much experience with any of your questions, but I will take a crack at the above.

Sounds like your elements are located directly in the "component view" package.  Try creating a package in the "component view" and moving the elements into that package.  Hope that fixes things.

[sargasso]

a model with 5000+ classes spreaded over
about 100 component packages each having some components.
 
Now a new team member wants to use class A.
 
In which package is it?
Is it in a package/component?
Do I have to create a new one?
 
 
So the question of the new developer is:
 
How can I see it in the modell?

1. Have the package/component owners create a diagram  in each package for each component.  Leave the classes in the project browser exactly where they are now.
2. Sort of like how everyone says, get them to drop the classes on the component - but do not create them as parts or ports - either use the "neither" option or just drop them into the component diagram without even creating a component element.

3. When Joe Nubug needs to know where j_someclass is he does the following:
a) use ctl-F or "search browser" and locate the class
b) press ctl-U this will bring up the usage list for the class element  from which you can see the component diagram pretty easily.

hth
Bruce