Modelling the content of a Component

[Bokkie]

Dear EA users,

I would like to exchange some ideas regarding component' internal design.

Ok, its pretty painless to model a model, its interfaces and ports. But what is the way-to-go when designing a component's internals (e.g. classes and relationships). At the moment I have draw component with its interfaces and ports and add the internal classes as inner classes. If done this way the component can be drawn with the classes and their relations inside.

However, generating code from such a constructions leaves me with drawbacks: the classes are generated as inner classes and I cannot generate code for an 'inner' class only.

Furthermore, I have added ports to my components. These ports have interfaces. A Class that realizes a port does not give me a inheritance to the port/interfaces.


What I am looking for is a way to model the component internals in a way that is easy and intuitive for everone and that gives me structured code.

Thanks.

M.


FYI:

[jeshaw2]

Sounds like you need to develop a Composite Structure diagram.  Look for that in EA Help and other books on UML 2.

[Bokkie]

Thanks, I already had a look at that modeling technique but find it not specific enough.