Partner IT Service in an Application Environment

[BenAvdicevic]

HOEX SMEs,

Curious why HOPEX allows you to add a "Partner IT Service" in an Application Environment diagrams (Structure, Scenario).

IT Services is an internal component of another Application.    So, when we add Flows or Interactions to the Partner IT Service - does HOPEX automatically add a Flow/Interaction to the "Parent" application of the IT Service?

For example.

Lets say I'm modelling Application Environment of Application ABC.   Then, lets say I create an Application Flow to Partner IT Service called IT Service XYZ, which is owned by the Application XYZ.

Logically - since I am modelling a flow to an Internal component of an Application - implicitly, I am sending the flow to the Application itself.   But - does HOPEX know that ?  Will it "auto-create" a new flow to the Application XYZ ?

Also - notice that in Application System diagrams (Scenario, Structure) you can NOT add an IT Service object.

Any thoughts/advice appreciated.

[BenAvdicevic]

@PBessodes Thank you for this.

Given everything you said above.

Does it make sense to discourage using "Partner IT Service" in an Application Environment (scenario or structure) diagrams?

[PBessodes]

Hi,

Initially, the Application Environment diagrams (structure or scenario) could be used fro Microservice Environment modelling also (you can define a Microservice as environment "subject"). In this context you would have possibility to identify external exchange betwen microservices and application or IT-Service. It was a possibility offered for more modelling agility. Afterwards, it looks like it was a mistake.

Regarding flows, next version will improve flow management by introducing a flow notion outside context (scenario of flows) that will stay automatically synchronized with appliation flows used in scenario diagrams. So a flow created in an application A environment with application B will be automatically defined between A and B.

But it will not mix systemic layer: creation of a flow between 2 component of a layer (2 IT Services) will not create a flow at upper layer (between applications). Layer synchronization may be really difficult so it is better to have reports showing/calculating this kind of thing.

Regards,

[BenAvdicevic]

@PBessodes Any thoughts on this question?