Management of knowledge for software architecture means to capture convenient experience and then translating it in generalized architectural knowledge. For refining the organizational architectural competences, architectural knowledge management is very much important. Architectural knowledge is valuable in the Software Architecture design process. This knowledge will help the stakeholders for communication in different phases of software development life cycle(SDLC). Properly managing the architectural knowledge is very much important as it is progressively more regarded the same as an organizational positive feature and that is why so many researchers around the world are proposing tools, methods, models and different frameworks for the effective knowledgemanagement [1]. This article contributes in exploring current work in field of software architectural knowledge management (AKM) from 2010 to 2017. This article highlights recent architectural AKM challenges and issues which are still not settled and here we also discuss different AKM tools, practicesand models.

10 years of software architecture knowledge management: Practice and future

Architectural Knowledge (AK) is defined as the integrated representation of the software architecture of a software-intensive system or family of systems along with architectural decisions and their rationale, external influence and the development environment. A fifth workshop on Sharing and Reusing Architectural Knowledge (SHARK) was held jointly with ICSE 2010 in Cape Town, South Africa. The theme of this workshop was the organization of a body of knowledge for software architecture knowledge management. It featured thirteen research position statements and three working groups that discussed on focused topics. This report summarizes the results of the discussions we held, and suggests some topics for future research.