Where did all this good architectural knowledge go?

Authors:
Philippe Kruchten
Affiliations:
Electrical and Computer Engineering, University of British Columbia, Vancouver, BC, Canada
Venue:
ECSA'10 Proceedings of the 4th European conference on Software architecture
Year:
2010

Citing 5
Cited 1

Documenting Software Architectures: Views and Beyond

Documenting Software Architectures: Views and Beyond
Guest Editors' Introduction: Knowledge Management in Software Engineering

IEEE Software
Software Architecture Knowledge Management: Theory and Practice

Software Architecture Knowledge Management: Theory and Practice
A comparative study of architecture knowledge management tools

Journal of Systems and Software
From software product lines to software ecosystems

Proceedings of the 13th International Software Product Line Conference

On quick comprehension and assessment of software

Proceedings of the 14th International Conference on Computer Systems and Technologies

Quantified Score

Hi-index	0.00

Visualization

Abstract

Software architecture represents a significant intellectual asset. But much of the architectural knowledge in organizations is still tacit knowledge. Different parties involved in software development have different needs in terms of architecture at different point in time, not limited to the architects themselves. How can we deliver the right information at the right time to the right person, as schedules are compressed? And where would the information be coming from? And how good is it? Various strategies have been tried, from central, bureaucratic accumulation of data--codification strategies, to simply giving access to the right person--personalization strategies, and a few hybrid strategies in between. This goes beyond mere software documentation, we need to effectively support the reasoning of the architects and developers.