According to Shaw and Garlan, an architectural style defines a category of systems in terms of a pattern of structural organization and a vocabulary of components, connector types, and a set of constraints on how they can be combined. Such patterns and styles of design are pervasive in many engineering disciplines, and those are typically codified in engineering handbooks and materials for professional curricula. Architectural styles in software engineering are emerging. Those patterns and styles are important because they help software architects to choose appropriate architecture based on those patterns and styles and to think of the trade-offs by comparing one style over another.
According to Bass, Clements and Kazman, “a view is a representation of a coherent set of architectural elements, as written by and read by system stakeholders”, and “a structure is the set of the elements itself, as they exist in software or hardware. That means that none of views are architecture, and all of the views convey the architecture.
Reference
1. Len Bass, Paul Clements, and Rick Kazman.
Software Architecture in Practice, Second Edition. Addison-Wesley, 2003.
2. Mary Shaw and David Garlan. Software Architectures Perspectives on an Emerging Discipline, Prentice Hall, 1996.
================
最終更新：2008年01月25日 06:25
