What's in Constructing a Domain Model for Sharing Architectural Knowledge?

To promote knowledge dissemination in the software architecting process, it is crucial to deploy sound mechanism s to manage and share architectural knowledge. Sharing knowledge requires a common frame of reference. To this end, we constructed a domain model for sharing architectural knowledge. In this paper, we outline the iterative pro cess used to construct this model. The main ingredients of this process are natural language text, packages, domain objects and actions, and object-interaction models. The recipe used to combine these ingredients consists of seven consecutive phases that iterate over three distinct stages of knowledge work: knowledge elicitation, knowledge structuring, and knowledge specification. Together, ingredient s and recipe help in constructing a model that captures both static and dynamic aspects of a domain.

[1]  Guus Schreiber,et al.  Knowledge Engineering and Management: The CommonKADS Methodology , 1999 .

[2]  Jeff Tyree,et al.  Architecture decisions: demystifying architecture , 2005, IEEE Software.

[3]  Jos Nijhuis,et al.  Design Decisions: The Bridge between Rationale and Architecture , 2006 .

[4]  Jan Bosch,et al.  Software Architecture: The Next Step , 2004, EWSA.

[5]  V. Clerc,et al.  Structuring Software Architecture Project Memories , 2005 .

[6]  Jan Bosch,et al.  Software Architecture as a Set of Architectural Design Decisions , 2005, 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05).

[7]  IEEE-SA Standards Board , 2000 .

[8]  Philippe Kruchten,et al.  Building up and Exploiting Architectural Knowledge , 2005, 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05).

[9]  Robert L. Nord,et al.  Generalizing a Model of Software Architecture Design from Five Industrial Approaches , 2005, 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05).

[10]  Kuntz Werner,et al.  Issues as Elements of Information Systems , 1970 .

[11]  David Lorge Parnas,et al.  A rational design process: How and why to fake it , 1986, IEEE Transactions on Software Engineering.