Sebastian Gerdes
ABSTRACT
Software architecture documentation is essential for preventing architecture erosion that is a major concern of sustainable software systems. However, the high effort for elaboration and maintenance of architecture documentation hinders its acceptance in practice. Most state-of-the-art research methods assume comprehensive architecture documentation. By reducing architecture documentation to those aspects that are most important for architecture erosion, we want to achieve more acceptance for architecture documentation especially in agile projects. This reduction, however, has effects on architecture-related activities during software design and implementation.
- S. Ambler. Agile ModModel. Effective Practices for eXtreme Programming and the Unified Process. John Wiley & Sons, 2002. Google Scholar
Digital Library
- P. Clements, F. Bachman, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, and J. Stafford. Documenting Software Architectures. Views and Beyond. Addison-Wesley Longman, Amsterdam, 2003. Google ScholarDigital Library
- I. Hadar, S. Sherman, E. Hadar, and J. J. Harrison. Less is more: Architecture documentation for agile development. In CHASE '13, May 2013.Google ScholarCross Ref
- A. Jansen and J. Bosch. Software Architecture as a Set of Architectural Design Decisions. In WICSA '05, 2005. Google ScholarDigital Library
- I. Malavolta, P. Lago, H. Muccini, P. Pelliccione, and A. Tang. What Industry Needs from Architectural Languages: A Survey. IEEE Trans. Softw. Eng., 2013. Google ScholarDigital Library
- C. Miesbauer and R. Weinreich. Classification of design decisions-an expert survey in practice. In ECSA 2013, pages 130--145. Springer, 2013. Google ScholarDigital Library
- D. E. Perry and A. L. Wolf. Foundations for the study of software architecture. SIGSOFT Softw. Eng. Notes, 17(4):40--52, Oct. 1992. Google ScholarDigital Library
- S. Schröder, M. Riebisch, and M. Soliman. Architecture enforcement concerns and activities - an expert study. In ECSA '16, 2016.Google ScholarCross Ref
- A. Tang, P. Avgeriou, A. Jansen, R. Capilla, and M. Ali Babar. A comparative study of architecture knowledge management tools. J. Syst. Software, 83:352--370, 2010. Google ScholarDigital Library
- J. Tyree and A. Akerman. Architecture decisions: Demystifying architecture. IEEE software, 22(2):19--27, 2005. Google ScholarDigital Library
- R. Wojcik, F. Bachmann, L. Bass, P. Clements, P. Merson, R. Nord, and B. Wood. Attribute-Driven Design (ADD), Version 2.0. Technical report, CMU/SEI, 2006.Google Scholar
- O. Zimmermann, T. Gschwind, J. Küster, F. Leymann, and N. Schuster. Reusable architectural decision models for enterprise application development. In QoSA '07, pages 15--32, 2007. Google ScholarDigital Library
Recommendations
Patterns to develop and evolve architecture during an agile software project
PLoP '15: Proceedings of the 22nd Conference on Pattern Languages of ProgramsThe design of the architecture during an agile project is an ongoing activity that takes place in all phases of a project lifecycle. It is important to continue to evolve the architecture in order to keep it suitable for the software system's current ...
An implementation framework for software architectures based on the coordination paradigm
Software Architectures have evolved considerably over the last decade and, partly also due to the significant progress made in component-based development, have become a major subfield of Software Engineering. The associated field of Architecture ...
Software Architecture-Centric Methods and Agile Development
Including architecture-centric design and analysis methods in the Extreme Programming framework can help software developers address quality attributes in an explicit, methodical, engineering-principled way. Properly managed, architecture-centric ...
Comments