docs: retry and role object diagrams

retry/README.md

@@ -34,6 +34,10 @@ In plain words
 
 > Enable an application to handle transient failures when it tries to connect to a service or network resource, by transparently retrying a failed operation. This can improve the stability of the application.
 
+Flowchart
+
+![Retry flowchart](./etc/retry-flowchart.png)
+
 ## Programmatic Example of Retry Pattern in Java
 
 The Retry design pattern is a resilience pattern that allows an application to transparently attempt to execute operations multiple times in the expectation that it'll succeed. This pattern is particularly useful when the application is connecting to a network service or a remote resource, where temporary failures are common.

role-object/README.md

@@ -32,6 +32,10 @@ wiki.c2.com says
 
 > Adapt an object to different client’s needs through transparently attached role objects, each one representing a role the object has to play in that client’s context. The object manages its role set dynamically. By representing roles as individual objects, different contexts are kept separate and system configuration is simplified.
 
+Sequence diagram
+
+![Role Object sequence diagram](./etc/role-object-sequence-diagram.png)
+
 ## Programmatic Example of Role Object Pattern in Java
 
 The Role Object design pattern is a pattern that suggests modeling context-specific views of an object as separate role objects. These role objects are dynamically attached to and removed from the core object. The resulting composite object structure, consisting of the core and its role objects, is called a subject. A subject often plays several roles and the same role is likely to be played by different subjects.