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. This saves time because you no longer need to keep describing concepts to other team members. Following this concept, patterns provide a natural mechanism for documenting application architectures. Patterns allow application architects to create complex architectures because patterns provide predefined components, relationships, and responsibilities.
Patterns are able to serve as components or artifacts for building more complex architectures.
The idea is to build systems using these predefined and proven solutions. However, I've found that, in many cases, patterns don't provide all of the design detail you'll need to solve the problem at hand, but they do provide a nice starting point. Remember that patterns provide generic solutions. Moreover, patterns provide application architects with the skeleton of functionality. Patterns allow application architects to manage software complexity because all patterns provide predefined methods to solve a problem.