How to model application and script interactions

[M.Schut]

For a company which has several externally hosted applications, we need to model relations between scripts and applications and their actions like:
User goes to website x.y.com->  
Triggers some actions ->
Abc.csv is sent back into the company with ftp ->
Schedule will use abc.csv and other information from a mainframe\db to create for example a report ->
On an internal website results are checked and approved ->
this will trigger creation of an invoice in script\query 123.xyz and the result will be send:
1. directly to client in .PDF
2. to an external company specialized in handle payments in format .def.
-> approval is stored in the record on the MF\db


There is already a business process for this in archimate, and company developers use UML. Now (technical) application support has this need for clarity in their specific domain too. Which model\diagram should I use, what should be in it and what not?

We already started with UML, but get stuck with modeling. Looking at examples of UML activity diagrams, I doubt if models in this level are useful for support employees to find where a process is stuck or a component is failing. At this point we are not yet interested in the hardware layer. We think this is a level deeper.

Any suggestions?

Thanx

[qwerty]

The whole modeling process is somewhat complex and you can not easily explain it in a few words. That's why I started writing a book about it. I posted a link to the preliminary version of this book here: http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1381249076
Maybe it can help solving some of your problems.

q.

[M.Schut]

Thanks for your reply Thomas,

Modeling is clearly not a thing you learn overnight. Systems like Archimate, UML, BPMN and SAOML all have their own specifications.

 We tend to use one modeling language and not make our own interpretation and add all kind of stereotypes or elements. Making a start with the right model will help us find a way in this area. We now agreed to use UML component for overview (relations between domains (e.g. client, external party, local domain)) and UML activity overviews, for activities between the applications within the domains.

Of course reading a book can help simplify a complicated subject. In my experience, a quick chat with an expert will set you on the right track much quicker. In both cases you still need to explore. I hope to find this person in this forum.

[qwerty]

You'll find a couple of brilliant minds here. Of course someone to talk to in person is much more efficient. But likely the guys here are more than a straw for a drowning person  

q.

[Thelonius]

M. Schut

Sounds like your example is low-level technical design. More a job for UML, especially if your developers are using Sparx to generate code components. UML - IMHO - is appropriate for physical technical design of software, data, infrastructure. This is more actual "design" rather than "modelling" at higher levels of abstraction - to my way of thinking, anyway.

Otherwise, if you have decided that ArchiMate is appropriate, I would recommend Gerben Wierda's ebook "Mastering ArchiMate" - where he has kindly proposed several patterns that may not be exactly what you need, but which I think you will find very close, and adaptable to your specific context.

I note you are in The Netherlands, the world's centre for ArchiMate and creative thinking about architecture modelling. Lucky you!