Summary

In this chapter, we saw a wide range of techniques for modeling and representing the internal architecture of a software system. We started with UML, which is a consolidated standard that is very widespread and actively used, especially in some of its aspects, such as class diagrams and sequence diagrams.

We then moved on to ArchiMate, which gives an enterprise architecture point of view on the subject and is commonly used in a context that follows the TOGAF approach. We then moved on to the C4 approach, which is a younger standard that is very lightweight and particularly suitable for projects adopting lean methodologies.

We've also seen a handful of specialized languages (BPMN and DMN), which are perfect for modeling specific aspects of our application. Last but not least, we quickly touched on arc42, which is a wonderful template system to start your architecture documentation and ensure that nothing important is missing.

In the next chapter, we will discuss...