In the past we've used City Planning Areas to represent the different layers, and types of software technologies. There may be a new/better way of doing it in the new IT Architecture product in HOPEX V2R1.
Hopex also supports both UML and ArchiMate 3.0 notations (requiring optional licenses)
The ArchiMate notation is exceptionally well suited to the type of diagram example you attached. In particular, note that its notation supports elaborating on specific layers (i.e. Business, Application, Technology) - as well as cross-layer dependencies.
See the following ArchiMate 3.0.1 specification reference pages:
5.1.1 Composition Relationship
5.1.2 Aggregation Relationship
8 Business Layer
9.1 Application Layer Metamodel
10 Technology Layer
12.2 Alignment of Application and Technology Layers
This is an excellent book - with many detailed examples - to learn more about the nuances and application of ArchiMate to modeling Enterprise Architecture solutions.
Mastering ArchiMate Edition III: A serious introduction to the ArchiMate® enterprise architecture modeling language, by Gerben Wierda
Gerben's blog has some good insightful discussions of pros/cons of different ways of modeling some things with ArchiMate notation:
See this ArchiMate example diagram is somewhat closer to your attached example