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.
best design framework in perl scripting
pp. 9-20. [Adow97] Recommended Best Industrial Practice for Software Architecture Evaluation, G. Abowd, L. Bass, P. Clements, R. Kazman, L. Northrop, and A. Zaremski, CMU/SEI-96-TR-025, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, January 1996. [Bass98] Software Architecture in Practice, L. Bass, P. Clements and R. Kazman, Addison Wesley, 1998. [Bell98] The CRC Card Book, D. Bellin and S. Suchman Simone, Addison Wesley, 1998. [Burh96] Use Case Maps for Object-Oriented