Awareness and coordination in shared workspaces
CSCW '92 Proceedings of the 1992 ACM conference on Computer-supported cooperative work
The 4+1 View Model of Architecture
IEEE Software
Anforderungen an lehrunterstützende Kooperationssysteme aus kommunikationstheoretischer Sicht
INFOS '99 Informatik und Schule, Fachspezifische und fachübergreifende didaktische Konzepte, 8. GI-Fachtagung Informatik und Schule
Software Architecture in Practice
Software Architecture in Practice
Architecture Decisions: Demystifying Architecture
IEEE Software
Software Architecture as a Set of Architectural Design Decisions
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
A Tool for Managing Software Architecture Knowledge
SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
Visualizing Software Architectural Design Decisions
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
SOA Generic Views In the Eye of the Beholder
SERVICES '08 Proceedings of the 2008 IEEE Congress on Services - Part I
Enriching software architecture documentation
Journal of Systems and Software
A comparative study of architecture knowledge management tools
Journal of Systems and Software
Building up and reasoning about architectural knowledge
QoSA'06 Proceedings of the Second international conference on Quality of Software Architectures
Decision support for off-the-shelf software selection in web development projects
ICWE'12 Proceedings of the 12th international conference on Current Trends in Web Engineering
Hi-index | 0.00 |
Architecting is a communication intensive task in which architectural knowledge is shared between the architect and the stakeholders. The software architect's communicative action is often conducted face-to-face, e.g. in presentations and workshops. A software architecture documentation as a carrier of explicit architectural knowledge can also be seen as an architect's communicative action. This perspective opens the door for treating a software architecture documentation as an expression of an asynchronous knowledge communication process enabling the application of principles from communication theory. In this paper this perspective is taken and specific requirements are derived for software architecture knowledge management tools with respect to the context-oriented communication model.