We have recently developed a formalism and methodology for describing software architectural styles. Concerning presentation issues, HRY is the most limited since great part of its recognisers produce fine grained textual results that can be difficult to understand and visualise when a large amount of data is returned. Intuitively, components correspond to boxes, and connectors accord to lines in box and line descriptions of software architectures. Such analysis aims at discovering and solving design problems in the early stages of development. A style defines a set of general rules that describe or constrain the structure of architectures and the way their components interact.
Styles are a mechanism for categorizing architectures and for defining their common characteristics.
This body of work reflects a wide spectrum of views on what architecture is, what aspects of it should be modeled and how, and what its relationship is to other software development concepts and artifacts. M. Shaw and P. Clements. Another style might provide excellent support for implementation and make it easy to construct systems in the style, but provide less support for analysis. Mary Shaw and Paul Clements. Also , a number of architectural styles are being formalized.