EresiVisualOverview
This is a good sum-up of ERESI modeling using a visual representation:
A few explainations are necessary there. The arrow relation is indeed different if it goes from an octagon to another one (dependences between ERESI libraries) or from an octagon to a rectangle (implemented features in a given ERESI library). Additionally, dependences are sometimes ommited if a component depends on a library, which itself depends on another library. For instance, the Evarista analyzer depends on libmjollnir to perform flow analysis, but no edge links the two components, because Evarista is already marked as depending on librevm, which itself has a dependence on libmjollnir. This representation was chosen only for the purpose of clarity, and not all dependences following this rule were ommited when the graph could be kept clear enough. Dependences can also happen between features of different libraries. As an example, semantic annotations of assembly code provided by libasm is necessary for computing the control flow graph in libmjollnir.