Pattern descriptions should provide specifications for deploying the pattern. Patterns provide object-oriented analysts with a methodology for solving recurring problems. Well, there are many benefits in using patterns for application architecture, such as the ability to solve recurring design problems that typically arise in application architecture and construction. The data migration example I gave earlier, for instance, creates a reusable solution set that application architects can apply to multiple applications. We already do this to a certain degree, but we have a tendency to keep the information in our heads, where it's either forgotten or you're just not around to share the information with those who need it when the problem arises once again.
Patterns do a good job of recording design experience across a development group.
Typically, such knowledge is found in the minds of the experts that may be on the team. Patterns level the playing field, providing every team member with the means of using this valuable information. Application architects may create a database of architecture patterns with search features and even links to code and models. Patterns also provide a standard vocabulary and base set of concepts for application architecture. Thus, you should pick the words you use to represent concepts carefully to make sure that everyone understands what you're talking about.