Alternatives to Information Flow connector?

[Andreas1975]

Hi.

I'm modelling a system containing a massive amount of various integrations, including i.e. FTP and MQ technologies.

I would prefer modelling all FTP interactions using the "Information Flow" connector, and having the actual File information as a Conveyed Item.

However - Using the Information Flow, its not easy to navigate (in diagram, searches, html reports etc) between the elements as well as to/from the actual File object conveyed. (since the File technically is attached as a Xref on the Connector)
I also would prefer to not model the actual FTP communication as a separate object, since using the Connector would be more "pretty". Using Tagged Value on the Information Flow to point out the File is not very user friendly.

What I really would like to do is adding a File object to the Information Flow connector as a "normal" relation.

Or is there any other way to model this in a "proper" way, making the flows easy navigable and searchable?

regards
Andreas

[Helmut Ortmann]

Hi,

there are some ways to model the conveyed information between classes or so:

• Use ports, connections and interfaces
• Use ports and type them by the conveyed information
• Make an association and use an association class
• Make flow with a class conveyed (the class contains all the subinformation)
• Using Composite Structure Diagrams to visualize the concrete connections (with ports, conveyed items, interfaces)
• Provided, Required Interface
• ..

I personally prefer port/type and connector.

Be also aware that there are a semantic differences between the solutions. But who cares?

Best regards,

Helmut

[qwerty]

To augment what Helmut said: If your model look clear and you "think" the reader understands your thoughts it is fine. If you are in doubt, look for someone to discuss your designs.

q.

[Helmut Ortmann]

A short but valuable remark. Thanks a lot.

Helmut

[Andreas1975]

Thanks alot. Good inputs.

I will try out some of the approaches above - You guys definately have a point of a clear model. Most of my readers are not "uml compliant", and its a challenge to model this in a clear way.

[Andreas1975]

Thanks alot. Good inputs.

I will try out some of the approaches above - You guys definately have a point of a clear model. Most of my readers are not "uml compliant", and its a challenge to model this in a clear way.