skip to main content
10.1145/3147704.3147731acmotherconferencesArticle/Chapter ViewAbstractPublication PageseuroplopConference Proceedingsconference-collections
research-article

Architecture Management in Software Development Organizations

Published:12 July 2017Publication History

ABSTRACT

As long as a software development organization drives several development projects in parallel the enterprise architecture gets more and more complex. Every initiative and every project has its own goals and timelines. This context implies a great challenge steering and managing the architecture to achieve more homogeneity, evolve according to new technology stacks and still pay credit to a necessary independence between projects. Short-term goals of the projects need to be balanced out with mid- and long-term objectives of the company. Therefore, architecture management measures should be considered, planned, and realized. This paper describes eight high-level architecture management patterns as starting point for central architecture teams, chiefs of architects, lead and principal software architects or CTOs.

References

  1. {AMAZON DEVELOPER} --Amazon Documentation for Developers, https://developer.amazon.com/de/documentation.Google ScholarGoogle Scholar
  2. {ARCHITECTURAL KATAS} -- Ted Neward. https://archkatas.herokuapp.com/.Google ScholarGoogle Scholar
  3. {ARC42} -- Architecture description template as part of iSAQB, Peter Hruschka and Gernot Starke, http://docs.arc42.org/home/.Google ScholarGoogle Scholar
  4. {ARC42 -- ARCHITECTURE DECISIONS} -- Architecture description chapter containing architecture decisions, http://docs.arc42.org/section-9/.Google ScholarGoogle Scholar
  5. {ATAM} -- Architecture Tradeoff Analysis Method, http://www.sei.cmu.edu/architecture/tools/evaluate/atam.cfm.Google ScholarGoogle Scholar
  6. {CLEAN CODE} -- Robert C. Martin, Clean Code -- A Handbook of Agile Software Craftsmanship, 2008, Prentice Hall. Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. {COMMUNITY OF PRACTICE} -- Wikipedia article about Community of Practice, https://en.wikipedia.org/wiki/Community_of_practice, Introduction to communities of practice, Etienne and Beverly Wenger-Trayner, 2015, http://wenger-trayner.com/introduction-to-communities-of-practice/Google ScholarGoogle Scholar
  8. {CONTROLOSIS} -- Klaus Marquardt. EuroPLoP 2016. http://www.europlop.net/content/europlop-2016-0Google ScholarGoogle Scholar
  9. {DECISION SCHEDULE} -- Klaus Marquardt. EuroPLoP 2016. http://www.europlop.net/content/europlop-2016-0Google ScholarGoogle Scholar
  10. {DZONE} -- DZonès reference cards, https://dzone.com/refcardz.Google ScholarGoogle Scholar
  11. {HSR} -- Architectural Knowledge Management (AKM) of Hochschule für Technik, Rapperswil, Institut für Software, Prof. Dr. Olaf Zimmermann, https://www.ifs.hsr.ch/index.php?id=13191&L=4.Google ScholarGoogle Scholar
  12. {INNER SOURCE} -- Open Source like culture within organizations, https://en.wikipedia.org/wiki/Inner_sourceGoogle ScholarGoogle Scholar
  13. {INNER SOURCE FOUNDATION} -- (Research) Governance in inner source initiatives, https://osr.cs.fau.de/Google ScholarGoogle Scholar
  14. {iSAQB} -- International Software Architecture Qualification Board iSAQB, http://www.isaqb.org/Google ScholarGoogle Scholar
  15. {Java Coding Guidelines} -- Long et al., Java Coding Guidelines -- 75 Recommendations for Reliable and Secure Programs, 2014, SEI Series in Software Engineering, Addison-Wesley.Google ScholarGoogle Scholar
  16. {MSDN} -- Microsoft Developer Network -- focus on Microsoft technologies, https://msdn.microsoft.com/de-de/dn308572.aspx.Google ScholarGoogle Scholar
  17. {NETFLIX TECH BLOG} -- Netflix Tech Blog, March 9, 2016. https://medium.com/netflix-techblog/how-we-build-code-at-netflix-c5d9bd727f15.Google ScholarGoogle Scholar
  18. {OWASP} -- 10 Most Critical Web Application Security Risks - The Open Web Application Security Project, https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project.Google ScholarGoogle Scholar
  19. {PRODUCT LINE ENGINEERING} -- Christa Schwanninger, Michael Kircher, EuroPLoP 2009, Applied Software Product Line Engineering, AISN: B009AI31ZO; Patterns for Product Line Engineering, http://hillside.net/europlop/europlop2009/submission/shepherd.cgi?token=69be663220cbd7922fba06693ea9248807a12244&action=download&label=1264874328_35Google ScholarGoogle Scholar
  20. {PRAGMATIC} -- Pragmatic Evaluation of Software Architectures (The Fraunhofer IESE Series on Software and Systems Engineering), 2016, Springer. Google ScholarGoogle ScholarDigital LibraryDigital Library
  21. {REFERENCE ARCHITECTURE: THE BEST OF BEST PRACTICES} -- Paul Reed, September 15, 2002, https://www.ibm.com/developerworks/rational/library/2774.htmlGoogle ScholarGoogle Scholar

Index Terms

  1. Architecture Management in Software Development Organizations

    Recommendations

    Comments

    Login options

    Check if you have access through your login credentials or your institution to get full access on this article.

    Sign in
    • Published in

      cover image ACM Other conferences
      EuroPLoP '17: Proceedings of the 22nd European Conference on Pattern Languages of Programs
      July 2017
      566 pages
      ISBN:9781450348485
      DOI:10.1145/3147704

      Copyright © 2017 ACM

      Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than the author(s) must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected].

      Publisher

      Association for Computing Machinery

      New York, NY, United States

      Publication History

      • Published: 12 July 2017

      Permissions

      Request permissions about this article.

      Request Permissions

      Check for updates

      Qualifiers

      • research-article
      • Research
      • Refereed limited

      Acceptance Rates

      EuroPLoP '17 Paper Acceptance Rate34of53submissions,64%Overall Acceptance Rate216of354submissions,61%

    PDF Format

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader