Application Interfaces and Protocol designation

[Michael Richards]

Hello All,

I've got a question about labeling protocols...what mechanism exists to show the protocols for the communication that occurs between applications or, in the case below interfaces.  Interface 2 serves Interface 1.  Currently I'm just changing the name of the serving relationship to be the protocol used but I don't like; it doesn't feel right.  Communication/network paths exists for Technology diagrams but not for application diagrams.  

I appreciate any suggestions/feedback.

Thanks

[theparker...@gmail.com]

I have had useful success with just having one Application Interface, with a composition to the "owning" Application Component. To show uses of the Application Interface, I have a dataflow between Application/Business Functions and the Application Interface.

This Application Interface is realized by a Technology Interface with a name that identifies the protocol (SMB, SFTP, HTTPS etc). This separate Tech Interface can be used to indicate what is providing the TCP server side (in the TCP "client(=initiator) -> server(=listener)" sense). The TCP server can be different from the Application Component, and dataflow can be different from the initiator->listener direction.

cheers

[Mastering ArchiMate]

I’m not going to react on the question itself, but the image

shows something weird: Realisation from Applcation Component to some sort of interface. It is technically possible through a derivation, but normally an Interface is owned (Composition) by the component of which it is an interface.

G

<Application Int Sample.png>

--
You received this message because you are subscribed to the Google Groups "ArchiMate" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-archimate-f...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-archimate-forum/b942a90e-5b4b-45fc-8f6b-073831b5eb0fn%40googlegroups.com.
<Application Int Sample.png>

[Michael Richards]

Are you able to do a simple illustration to help me visualize?

Thanks,

[Michael Richards]

Hi G,

With archimate 3.1, I thought is was acceptable to have a component realize an interface.  Is there a rule/guideline to choosing composition over realization for interfaces that you recommend or is it more a matter of preference.  I've only been modelling with 3.1 so I don't have the background with any prior versions.

Thanks,

[Mastering ArchiMate]

You can download the Mastering ArchiMate free syntax excerpt that explains the 3.0.1 syntax via the book’s home page (see link in signature)

It has nothing to do with prior versions, it is just normally not the right relation to use.

In a language you can say the same in many ways (so which pattern do you use and why) .ArchiMate is a grammar more than a language. And you can create grammatically correct phrases that have a different meaning t=but are still correct. E.g. “The shovel uses the gardener”. Grammatically correct, but probably not what you want.

Gerben Wierda
Chess and the Art of Enterprise Architecture
Mastering ArchiMate
Architecture for Real Enterprises at InfoWorld
On Slippery Ice at EAPJ

To view this discussion on the web visit https://groups.google.com/d/msgid/open-archimate-forum/91df762f-577c-4ff5-87ea-c00e08638865n%40googlegroups.com.

[Michael Richards]

Hi Gerben,

I've purhased the PDF form of the book.  Can you give me the section in the book you are referring to?  I'm relatively new to doing Archimate and I'm finding contradictory information on some of the relations/viewpoints and trying to understand how best to approach. For example both an instructor I had an an online reference called Archimate Cookbook (By Eero Hosiaisluoma) of which I was directed to state that the structural relationship of composition for an interface is in guidelines with 2.1  However, with 3.X, the realization relationship from a compoent to an iterface is in guidelines with respect to 3.X.  That's why I was asking the question if it was really more of a preference or a 'rule' per se as I want to make sure that I'm doing models that are in-line with Archimate.  

Thanks again very much for your responses Gerben.  I do find them helpful...

Michael

I appreciate your feedback on this.

[Mastering ArchiMate]

Section 7, where the actual explanation of the syntax starts and then 7.1 when the basic pattern is introduced. There you see an Application Component that Composes its Application Interface.

But if you are new, it is best to read the entire first part of the book, the Basics thoroughly. It is still valid., except for the stuff that has to do with derivations (including the pitfalls) and the omission of the Value Stream element.

Page 40 top right has some useful info as well.

This is ArchiMate 3.1 compliant

[Steven Mileham]

Apologies if I've got the wrong end of the stick, but is this the kind of thing you're after?

Two applications, realising a Service layer, exposed over a number of interfaces, and modelling the "client" interface used to interact with the "server" interface?

[theparker...@gmail.com]

Hi Michael

Something like this?

Robert

[Michael Richards]

Hi Robert,

Thanks for that diagram.  That in conjunction with Gerben's info helped.

Sincerely,

Michael