docs: object pool and observer diagrams

object-pool/README.md

@@ -35,6 +35,10 @@ Wikipedia says
 
 > The object pool pattern is a software creational design pattern that uses a set of initialized objects kept ready to use – a "pool" – rather than allocating and destroying them on demand.
 
+Sequence diagram
+
+![Object Pool sequence diagram](./etc/object-pool-sequence-diagram.png)
+
 ## Programmatic Example of Object Pool Pattern in Java
 
 In our war game we need to use oliphaunts, massive and mythic beasts, but the problem is that they are extremely expensive to create. The solution is to create a pool of them, track which ones are in-use, and instead of disposing them re-use the instances.

observer/README.md

@@ -33,6 +33,10 @@ Wikipedia says
 
 > The observer pattern is a software design pattern in which an object, called the subject, maintains a list of its dependents, called observers, and notifies them automatically of any state changes, usually by calling one of their methods.
 
+Sequence diagram
+
+![Observer sequence diagram](./etc/observer-sequence-diagram.png)
+
 ## Programmatic Example of Observer Pattern in Java
 
 In a land far away live the races of hobbits and orcs. Both of them are mostly outdoors, so they closely follow the weather changes. One could say that they are constantly observing the weather.