Unifying software architecture with its implementation

Authors:
Eoin Woods;Nick Rozanski
Affiliations:
Artechra, Hemel Hempstead, UK;Artechra, London, UK
Venue:
Proceedings of the Fourth European Conference on Software Architecture: Companion Volume
Year:
2010

Citing 7
Cited 4

Pattern-oriented software architecture: a system of patterns

Pattern-oriented software architecture: a system of patterns
A framework for classifying and comparing architecture description languages

ESEC '97/FSE-5 Proceedings of the 6th European SOFTWARE ENGINEERING conference held jointly with the 5th ACM SIGSOFT international symposium on Foundations of software engineering
Patterns of Enterprise Application Architecture

Patterns of Enterprise Application Architecture
Weaving Together Requirements and Architectures

Computer
Software Architecture in Practice

Software Architecture in Practice
AspectJ in Action: Practical Aspect-Oriented Programming

AspectJ in Action: Practical Aspect-Oriented Programming
Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

Towards architectural information in implementation (NIER track)

Proceedings of the 33rd International Conference on Software Engineering
Using code analysis tools for architectural conformance checking

Proceedings of the 6th International Workshop on SHAring and Reusing Architectural Knowledge
Exploiting software architecture to support requirements satisfaction testing

Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
A metamodel for the support of semantically rich modular architectures in the context of static architecture compliance checking

Proceedings of the WICSA 2014 Companion Volume

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper proposes a research challenge to narrow the gap between the architecture and implementation of a software system. We discuss the situation today, where little of a system's architecture and design is directly represented in the source code of its implementation and explore why this is a problem and the benefits that might flow from narrowing this gap. We then discuss how the situation could be improved by the creation of technologies that allow the design and architecture of a system to be directly related to its source code and outline the requirements that we believe that any such technology would need to fulfill. Finally, we consider the likely results of widespread application of such a technology and the benefits that would follow.