Despite considerable attention paid on software architecture, the organizational aspects of architecture design remain largely unexplored. This study analyses the stakeholders participating in architecture design in three software companies, their problems in relation to architecture, and the rationale for architecture description they emphasize. This qualitative, grounded-theory-based, study shows how the stakeholders. rationales for describing architecture exceed the plain programming-in-the-large metaphor, emphasizing such issues as organizational communication, and knowledge creation and management. Whereas designers alone highlighted architecture as the basis for further design and implementation, the other stakeholders emphasized architecture mostly as a means for communication, interpretation, and decision- making. The results suggest a need for further research on practices and tools for effective communication and collaboration among the varying stakeholders of the architecture design process.
CITATION STYLE
Smolander, K., & Päivärinta, T. (2002). Describing and communicating software architecture in Practice: Observations on stakeholders and rationale. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 2348, pp. 117–133). Springer Verlag. https://doi.org/10.1007/3-540-47961-9_11
Mendeley helps you to discover research relevant for your work.