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.
W Part 2
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 Transactions on Software Engineering and Methods, 4(4), pp. 319-164, 1995. [Adow93] Using Style to Understand Descriptions of Software Architecture, G. Adowd, R. Allen and D. Garlan, ACM Software Engineering Notes, December, 1993, pp. 9-20. [Adow97] Recommended Best Industrial Practice for Software