Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
The 4+1 View Model of Architecture
IEEE Software
Software Reflexion Models: Bridging the Gap between Design and Implementation
IEEE Transactions on Software Engineering
Generation of Architectural Documentation Using XML
WCRE '02 Proceedings of the Ninth Working Conference on Reverse Engineering (WCRE'02)
Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives
Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives
A View-Based Approach for Improving Software Documentation Practices
ECBS '06 Proceedings of the 13th Annual IEEE International Symposium and Workshop on Engineering of Computer Based Systems
The Golden Age of Software Architecture
IEEE Software
A Comparison of Static Architecture Compliance Checking Approaches
WICSA '07 Proceedings of the Sixth Working IEEE/IFIP Conference on Software Architecture
Software Architecture: Foundations, Theory, and Practice
Software Architecture: Foundations, Theory, and Practice
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
Software Architecture in Practice
Software Architecture in Practice
Software architecture documentation for developers: a survey
ECSA'13 Proceedings of the 7th European conference on Software Architecture
Hi-index | 0.00 |
To utilize the potential of software architecture it is essential to make it explicit. Architects produce architecture documentation when designing systems and provide it to developers who use it as the basis for their implementation tasks. However, the views of architects and developers on the system diverge: architects look at the system as a whole, developers have a more local perspective, focusing on the elements and context they are responsible for. The comprehensive architecture documentation produced by architects does not take this divergence into account. Although all needed information may be included, the information overhead and suboptimal representation render such generic architecture documentation inadequate to be used without adaptation for all implementation tasks. To overcome this deficiency, the doctoral thesis presented in this paper proposes an approach for the creation of architecture documentation that is tailored to specific implementation tasks. Such documentation shall contain all relevant, but only a minimum of overhead information and present it in a way that allows developers to perform their implementation tasks efficiently, with high-quality results. By using automated generation techniques that derive the task-specific architecture documentation from the general documentation, it is possible to largely avoid impacts on architects' normal way of working. To achieve applicability of the approach in practice, ideas for tool support, integrated into an existing modeling environment are highlighted. Finally, ideas for the validation of the expected benefits, the current status of the doctoral thesis, as well as next steps and possible future extensions are presented.