Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems - not an accidental by-product of the software acquisition and integration process.
system communications architecture
Kaufmann, 1997. [Busc96] A System of Patterns: Pattern-Oriented Software Architecture, Frank Buschmann, et al, John Wiley and Sons, 1996. [Hofm97] Approaches to Software Architecture, C. Hofmann, E. Horn, W. Keller, K. Renzel, and M. Schmidt, in Software Architecture and Design Patterns in Business Applications, edited by M. Broy, E. Denert, K. Renzel, and M. Schmidt, Technical University at Muhchen, TUM-I9746, November, 1997. [Parn72] On the Criteria to be Used in Decomposing Systems into Modules,