Architecture Decisions: Demystifying Architecture
IEEE Software
Design decision rationale: experiences and steps ahead towards systematic use
ACM SIGSOFT Software Engineering Notes
Model-Driven Software Development: Technology, Engineering, Management
Model-Driven Software Development: Technology, Engineering, Management
Tool Support for Architectural Decisions
WICSA '07 Proceedings of the Sixth Working IEEE/IFIP Conference on Software Architecture
WICSA '08 Proceedings of the Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2008)
Modeling Human Aspects of Business Processes --- A View-Based, Model-Driven Approach
ECMDA-FA '08 Proceedings of the 4th European conference on Model Driven Architecture: Foundations and Applications
Questions, options, and criteria: elements of design space analysis
Human-Computer Interaction
Effort Estimation in Capturing Architectural Knowledge
ASE '08 Proceedings of the 2008 23rd IEEE/ACM International Conference on Automated Software Engineering
Reusable architectural decision models for enterprise application development
QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
Building up and reasoning about architectural knowledge
QoSA'06 Proceedings of the Second international conference on Quality of Software Architectures
Model-driven development of industrial process control applications
Journal of Systems and Software
Hi-index | 0.00 |
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.