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.
multiple concurrent projects involving hardware, software, multiple sites and legacy business systems integration. Mr. Alleman has deep technical and architectural knowledge of a variety of system paradigms including: client/server, CORBA, and web-based systems. He is the Principal Consultant for Niwot Ridge Consulting, Niwot, Colorado, www.niwotridge.com. References - Part III [Abow95] Formalizing Style to Understand Descriptions of Software Architecture, G. Abowd, G. Allen and D. Garland, ACM