Talk the Talk

?

Talk the Talk

Mark Richards

In any profession, jargon are used so, individuals within, pro-fession can effectively communicate with one anothe R. Lawyers talk-to-one another about habeas corpus, voir dire, and venire; Carpenters talk to one another about butt joints, lap joints, and flux; and software architects talk-to-one another about ROA, Step View, and Layer supertype. Wait, what is that?
It is imperative that software architects, regardless of the platform they was working in, has an effective means of Comm Unication among one another. One of those means of communication is through architecture and design patterns. To is an effective software architect you must understand the basic architecture and design patterns, recognize when those Patterns is being used, know when to apply the patterns, and is able to communicate to other architects and developers U Sing them.
Architecture and design patterns can be classified to four basic categories:enterprise Architecture patterns, Applicati On architecture patterns, integration patterns, and design patterns. These categories is generally based on the level of the scope within the overall architecture. Enterprise architecture patterns deal with the high-level architecture, whereas design patterns deal and how indi-vidual Components within the architecture is structured and behave.
Enterprise Architecture Patterns Define the framework for the high-level Archi-tecture. Some of the more common architecture patterns include Event-driven architecture (EDA), service-oriented architecture (SOA) , resource-oriented Architecture (ROA), and pipeline architecture.
Application architecture Patterns Specify how applications or subsystems within the scope of a larger enterprise architect Ure should be designed. Some Common pattern catalogs in this category include the well-known EE design
?
?? patterns (e.g., Session Fa?ade and Transfer Object) and the application archi-tecture patterns described in Martin Fowler ' s book Patterns of Enterprise Application Architecture (Addison-wesley Professional).
Integration patterns is important for designing and communicating concepts surrounding the sharing of information and fun Ctionality between components, applications, and subsystems. Some Examples of integration patterns include file sharing, remote procedure calls, and numerous messaging patterns. You can find these patterns at http://www.enterpriseintegrationpatterns.com/eaipatterns.html.
Knowing the basic design patterns as described by the Gang of four book design patterns:elements of Reusable Object-orien Ted Software (Addison-wesley Professional) is a must for any software architect. Although these pat-terns may appear to being too low-level for a software architect, they is part of a standard vocabulary That's makes for effective communication between archi-tects and developers.
It is also important to being aware of and understand the various anti-patterns as well. Anti-patterns, a term coined by Andrew Koenig, is repeatable processes that produce ineffective results. Some of the more well-known anti-patterns include analysis paralysis, Design by committee, Mushroom Management, and death March. Knowing these patterns would help you avoid the many pit-falls you'll most likely experience. You can find a list of the common anti-patterns at Http://en.wikipedia.org/wiki/Anti-patterns.
Software architects need the ability to communicate with one another in a clear, concise, and effective. The patterns is there; It's up to us as Soft-ware architects to learn and understand these patterns so we can "walk the walk and talk of the talk. ”

Talk the Talk