Software architecture: a roadmap
By David Garlan. International Conference on Software Engineering, 2000
460 citations recorded by the source corpus.
Over the past decade software architecture has received increasing attention as an important subfield of software engineering. During that time there has been considerable progress in developing the technological and methodological base for treating architectural design as an engineering discipline. However, much remains to be done to achieve that goal. Moreover, the changing face of technology raises a number of new challenges for software architecture. This paper examines some of the important trends of software architecture in research and practice, and speculates on the important emerging trends, challenges, and aspirations.
Subfields: Artificial Intelligence, Information Systems
View Paper: https://www.semanticscholar.org/paper/0938ee6e489b9ac8fcc78df9b75e5395a734d357
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Damien Pollet
- Steve M. Easterbrook
- Bashar Nuseibeh
- Stéphane Ducasse
- Serhiy Morozov
- Premkumar T. Devanbu
- Didar Zowghi
- Stuart G. Stubblebine
In Information Systems
- Damien Pollet
- Steve M. Easterbrook
- Bashar Nuseibeh
- Stéphane Ducasse
- Serhiy Morozov
- Premkumar T. Devanbu
- Didar Zowghi
- Stuart G. Stubblebine
Citations in the corpus
- Requirements engineering: a roadmap (2000, background): “of the key research issues in software engineering [27].”
- Software Architecture Reconstruction: A Process-Oriented Taxonomy (2009, background): “From source code models, they progressively raise the abstraction level until a high-level understanding of the application is reached (see Figure 3) [14, 153].”
- A Distributed, Architecture-Centric Approach to Computing Accurate Recommendations from Very Large and Sparse Datasets (2011, background): “The main idea behind this style is that complex systems may be constructed by assembling a number of simple building blocks, abstracting implementation details and separating the architect and developer concerns [42, 51, 52].”