Architectural knowledge tends to get lost as the architecture evolves. In many cases, the main reason is that there are no incentives for stakeholders to invest enough time into recording the architectural knowledge. This is in part due to the generic nature of architectural knowledge recording and sharing means, such as architectural decision templates and meta-models. In this paper, we investigate on the feasibility of a domain-specific architectural knowledge view in the context of a model-driven project. The domain-specific approach helps us to make architectural knowledge (AK) recording more useful for a project apart from the goal of AK sharing and reuse. Model-driven development helps us to ensure the consistency of the architectural knowledge as it is part of the generation process. Finally, depicting architectural knowledge as a architectural view supports separation of concerns with regard to the various models in the system. We demonstrate our approach for a compliance meta-data view for process-driven SOA systems that records compliance requirements and rationales of an architecture. Categories and Subject Descriptors D.2.11 [Software Architectures]: Domain-specific architectures; D.2.11 [Software Architectures]: Service-oriented architecture (SOA
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.