Connecting between Ports on Parts

[DanG83616]

When I add a component to a diagram as a Part, its ports only show up in the inherited list. When I make those visible they are read-only which could make sense in some ways. I don't want to modify the inherited port, I want to modify the instance of it on this part (instance of a component). The only modification I want to make, though, is to show that information flows from that port to another part's port in the diagram. I could not see a way to make that happen.

What I did was add a new port to the part. That port is mutable and I was able to connect to similarly created port on another part. In order to keep the relationship to the inherited port I created a Trace from the mutable one to the inherited one. This seems very cumbersome and it still isn't quite what I wanted.

I'm trying to create a schematic like one would create for electrics. All I should have to do is drop Components as Parts and connect them together via the ports. There has to be a good way to do this.

Any ideas?

Thanks,
Dan
P.S. - I have a diagram I can show but I don't know how. If someone can tell me how I'll post it.

[Thelonius]

Dan

Sounds like you may be using EA in a manner similar to me. I'm guessing. I could be wrong. And probably am.

We use Component diagrams to model baseline and target application integration architectures. Component = application. Information Flow connector = interface.

We use a UML Profile to define tagged values for components and connectors, and we populate these fields with (more or less) structured information such as technology, business importance, business owner, etc. Enums where possible.

"Unstructured" textual information we place in the "Notes" compartment.

On the connector, we identify the type of business data flowing over the interface. We model the direction of flow with an arrowhead toward to "consuming" application.

The definition of what actually constitutes an "interface" - and how, in practice, one represents an "interface" in terms of level of granularity and directionality, etc - can turn out to be more complicated than the casual observer would initially think.

BTW - I'm not talking about SOA services here - just your traditional data-shipping, MOM and API style interfaces, which is where most organisations still are today... (Approach would still work, I think, I just haven't yet done this kind of modelling for a client that implements wholesale SOA services...)

Works a treat.

You can end up with quite large and complex diagrams in a large organisation, but the ability to search (control - F) and find things quickly is valuable, and the RTF document generation (flawed as it is) is useful.

The Relationship Matrix capability is also powerful.

We always create one single, overarching "everything including the kitchen sink" component diagram, which we let get as ugly as it gets, and don't worry too much about trying to make it presentation pretty.

This is called the "Big Hairy Ugly" diagram, and it exists for a purpose.

But then, we create separate segment / capability or domain diagrams. These are inherently less complex and can be made to look more visually comprehensible. These diagrams support "real architecture work".

I call the result:

"A machine for answering inevitable, ubiquitous, and recurrent architecture questions about applications and integration."

FWIW - I tried playing around with the "port" interface on components but found it too fiddly and no value added. You may feel differently.

The word "schematic" is relevant for these diagrams. However, it's possible that you may be using EA to actually create electrical diagrams.  . If so, it's a pretty clever use of EA, I must say. And it will probably work, too...

In future, I intend to simplify things even more, by not using the Information Flow connector - just using a simple "Dependency" connector.

Now. Inserting an image.

You can insert a URL that links to a website, or a URL that links to an image on a website.

If an image - paste the full URL of the jpeg into your message, then highlight the entire URL, then click on the icon that looks like a small picture, which you will find above the text box that we use to type these messages (popup will say "insert image").

You will need to FIRST upload your image to your own website, or a public hosting website such as Mediafire, Picasa, Flickr, etc. and link to that URL...

Hope this helps ...

Jon

[DanG83616]

Jon
I am using Component and Ports to represent software ICs (ref. Brad Cox). I drop the the Components as Parts into a Composition diagram for the "assembly" or "circuit board." Dropping them as Parts allows use of the same Component multiple times in the same assembly. It is very concrete in terms of data flow and intefaces but abstract in terms of data exchange impl. Analogous to electoronic schematic that doesn't show trace widths, material, etc. but clearly shows dataflow. The data flow impl could be anything from DDS to a FORTRAN common block. Just a matter of applying the right transform.

It is funny that you mention the "Big Harry" diagram. I just deleted mine yesterday. I'm now creating a series of "detail" diagrams that help focus the topic. "Harry" was just to hard to keep accurate and inaccurate documentation is the bane of my existance. Actually, it was hard to keep readable so it would not get updated and thus became inaccurate. The smaller diagrams should be easier to change without messing around re-routing lines all over the place.

Ports are a key part of my approach because they represent "pin" on the IC. It gives me a clear item to assign pin attributes like direction, type, and timing.

Thanks for the tip about publishing pix. It is just enough trouble to keep me from doing it. Perhaps Sparx will provide a site for pictures.

Thanks for the reply. Glad to hear someone else is thinking along the same lines.

Dan

[deefer]

I think this problem must be solved by Sparx as soon as possible.

I've already submitted a bug report about the ports handling in ibd, but I couldn't get an answer about when it will be fixed.

Davide