I'm trying to familiarize myself with the ArchiMate language which is raising a lot of "How do I model this" types of questions.
We have a purchased applicatin (ApplicationA) and another purchased application (ApplicationB). These two need to communicate, so we wrote some custom code that sits on the ApplicationA server, sends information to custom code that we wrote sitting on ApplicationB's server.
How would you diagram this? Any input would be greatly appreciated!
The way you model it really depends on how things work and the purpose of your model. If the purpose is to keep track of data flows, then you could just use a Flow relationship from "Application A" to "Application B", but if you want to provide details about the real implementation, then depending on whether or not you use standard/default services provided by applications: if yes application layer is enough, if not infrastructure layer have to be detailed.
Here are some possible ways of modelling it:
Hope this can help.
This is great! I appreciate you taking the time to pull this together for me!
Just one comment: the latest example is obviously way too much ;-) To be honest I would never model so many details but again, it depends on your context.
And I forgot to provide you one simple advice: look at Gerben Wierda's book Mastering Archimate (http://masteringarchimate.com/mastering-archimate-edition-ii/).
This is a really nice reply. Thanks to our resident ArchiMate expert, JB! 8)
Thank you. But this really nice reply would not have been possible without the fantastic tool Archi is (first) and the fantastic blog and book written by Gerben !
BTW : @Jon could you share your final modelling ? It could be interresting to have future readers of this forum to know how you finally did it.
@Jean, I haven't yet modeled it since I purchased the book you have recommended and haven't put it down :)