Skip to main content
Solved

Data Flow Diagram for SFTP

  • September 14, 2025
  • 1 reply
  • 137 views
S

Hi All,

 

i am new to LeanIX, as well to community. i am working on Data flow diagram and having lots of challenges. we have SFTP service which is used by multiple application for file transfer. I added my SFTP application as an application factsheet and added sftp as a provided Interface. below are my questions if anyone can help.

  1. let's assume one application is only sending the file outbound and second file only receive the file incoming, how i can showcase it? in interface factsheet i can select either incoming, outbound or bidirectional. 
  2. If i add an arrow manual (like we add in free flow diagram) we can link to any factsheet like interface etc. For eg. we can add a manual added box to any application factsheet.
  3. is there any way i can get a label based on data flow like inbound file transfer or outbound file transfer based on direction of the arrow automatically.

Thanks

Best answer by Jochen

Hi

The approach with having the SFTP-server as an application will create these challenges and remove the ability for end-to-end visibility of interfaces and data flow. Colleagues of mine also had this modeling-reflex (coming from a technical perspective), but it does not create much value from my point of view.

I would go with SFTP (or any other interface protocol / format / technical speciality that is relevant) as an IT-Component and linked to the interface. Because the SFTP-server is not the data provider, it’s just a transfer mechanism.

The data providing and consuming application have an interface (which then can be classified like you described) and that interface has the IT-Component like SFTP added to it.

Like that you have the complete view of information:

  • Which application provides and consumes which data (provider / consumer in the interface)
  • In which direction the data is flowing (direction in the interface)
  • Which technical implementation is used for this specific interface (SFTP, REST, File, etc.)

Cheers
Jochen

1 reply

Jochen
Forum|alt.badge.img
  • Jochen
  • Royalty For Loyalty
  • Answer
  • September 15, 2025

Hi

The approach with having the SFTP-server as an application will create these challenges and remove the ability for end-to-end visibility of interfaces and data flow. Colleagues of mine also had this modeling-reflex (coming from a technical perspective), but it does not create much value from my point of view.

I would go with SFTP (or any other interface protocol / format / technical speciality that is relevant) as an IT-Component and linked to the interface. Because the SFTP-server is not the data provider, it’s just a transfer mechanism.

The data providing and consuming application have an interface (which then can be classified like you described) and that interface has the IT-Component like SFTP added to it.

Like that you have the complete view of information:

  • Which application provides and consumes which data (provider / consumer in the interface)
  • In which direction the data is flowing (direction in the interface)
  • Which technical implementation is used for this specific interface (SFTP, REST, File, etc.)

Cheers
Jochen

GiannisAnt
abenedete
carmen.guti
Terms & ConditionsCookie settingsAccessibility statement