iluwatar#91 README.md changes

Author: iluwatar

README.md

@@ -86,6 +86,7 @@ An architectural pattern is a general, reusable solution to a commonly occurring
 
 * [Data Access Object](#dao)
 * [Service Layer](#service-layer)
+* [Naked Objects](#naked-objects)
 
 ### Integration Patterns
 
@@ -642,6 +643,16 @@ validation and for building to order
 * When you need to remove knowledge of concrete implementation from object
 * To enable unit testing of classes in isolation using mock objects or stubs
 
+## <a name="naked-objects">Naked Objects</a> [&#8593;](#list-of-design-patterns)
+**Intent:** The Naked Objects architectural pattern is well suited for rapid prototyping. Using the pattern, you only need to write the domain objects, everything else is autogenerated by the framework.
+
+![alt text](https://github.com/iluwatar/java-design-patterns/blob/master/naked-objects/etc/naked-objects.png "Naked Objects")
+
+**Applicability:** Use the Naked Objects pattern when
+* You are prototyping and need fast development cycle
+* An autogenerated user interface is good enough
+* You want to automatically publish the domain as REST services
+
 
 
 # Frequently asked questions
@@ -731,6 +742,7 @@ Java-design-patterns project uses [semantic versioning](http://semver.org/) sche
 * [Martin Fowler - Tolerant Reader](http://martinfowler.com/bliki/TolerantReader.html)
 * [Trygve Reenskaug - Model-view-controller](http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller)
 * [Flux - Application architecture for building user interfaces](http://facebook.github.io/flux/)
+* [Richard Pawson - Naked Objects](http://downloads.nakedobjects.net/resources/Pawson%20thesis.pdf)