Functional and technical relations/flows

Ralph van Zandt

4 april 2023 08:20 Bewerkt

Hi people,

Looking for your advice.:
See the below example. Articles are managed in the ERP solution and online articles are uploaded to the webshop for online selling. This is the functional relation / flow. The actual flow involves 2 other applications which interacts in this flow (application X and Y). I call this the technical relation.

• I want both the functional and technical flow/relations being registered to the applications.
• I would like to be able to see that the functional relation has a different technical flow. The functional flow is related to the technical flow and vv. Something in the naming/label?
• The functional flow/relation will always be drawn in a view, if the technical flow is different, it can also be in the same view, but not necessarily.

How do you deal with this, any examples on how you do this?
Ideas, tips and creativity is welcome ;-)

Many thanks in advance.

1

• 

  Rafael Bakker

  4 april 2023 09:41 Bewerkt

  Hi Ralph van Zandt,

  My thoughts are to (indeed) put something in the relationship label, similarly to what we discussed in our last session related to future state modelling. This makes for easy recognition on views and the ability to report on these relationships using the JasperSoft reporting engine. 

  Aside from that, you could try 'relating' the relationships to one another by including the 'technical flow'(s) as an attribute on the 'functional flow' relationship and vice versa using the relationship questionnaire. This can then be visualized using conditional layout on views and reported on using the odata feed (excel report is done, coming your way!). 

  Lets discuss this further in our next call.

  0

U moet u aanmelden om een opmerking te plaatsen.