• No results found

University of Groningen Preserving and reusing architectural design decisions van der Ven, Jan

N/A
N/A
Protected

Academic year: 2021

Share "University of Groningen Preserving and reusing architectural design decisions van der Ven, Jan"

Copied!
2
0
0

Bezig met laden.... (Bekijk nu de volledige tekst)

Hele tekst

(1)

University of Groningen

Preserving and reusing architectural design decisions van der Ven, Jan

IMPORTANT NOTE: You are advised to consult the publisher's version (publisher's PDF) if you wish to cite from it. Please check the document version below.

Document Version

Publisher's PDF, also known as Version of record

Publication date: 2019

Link to publication in University of Groningen/UMCG research database

Citation for published version (APA):

van der Ven, J. (2019). Preserving and reusing architectural design decisions. University of Groningen.

Copyright

Other than for strictly personal use, it is not permitted to download or to forward/distribute the text or part of it without the consent of the author(s) and/or copyright holder(s), unless the work is under an open content license (like Creative Commons).

Take-down policy

If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim.

Downloaded from the University of Groningen/UMCG research database (Pure): http://www.rug.nl/research/portal. For technical reasons the number of authors shown on this cover page is limited to 10 maximum.

(2)

Propositions

1. Using explicit architectural decisions as bridge between the architectural documentation and the implementation of a software system increases the understandability of the architecture.

2. Projects with less architectural documentation have faster development cycles, while the amount of documentation does not significantly influence the return on investment or the quality of the systems.

3. Software architects with more architecture experience make decisions with a higher return on investment, while architects with more development experience make decisions that result in higher quality products.

4. Pivots and business decisions often have implicit long-lasting software architecture consequences; the decision process should facilitate both to make successful products. 5. Architecture decisions, including their alternatives and rationales, can be extracted from the source code history in order to increase the confidence base for decision makers.

6. Software engineering research can use A/B testing to study human interaction in software development.

7. The rise of fake news was not caused by social media; instead, it was made possible by journalists that pretended to be independently reporting on facts.

Referenties

GERELATEERDE DOCUMENTEN

We focus our research on the two most important aspects of these movements: the architectural decision and the pivot, and show that they can be seen as two sides of the same

When relat- ing this to the number of projects, on average every open source project we used contained 6 decisions in commits and 3 commit messages with relevant rationale..

The developed model was used in the work of Chapter 4 , where we showed that it is possible to assist architects and reviewers in preserving tacit knowledge on architectural

3.1 An abstract view on the software architecture design

Other than for strictly personal use, it is not permitted to download or to forward/distribute the text or part of it without the consent of the author(s) and/or copyright

Other than for strictly personal use, it is not permitted to download or to forward/distribute the text or part of it without the consent of the author(s) and/or copyright

We show how explicit decisions can form the bridge between the tacit knowledge of architects and the artifacts that are used in software architecture.. For example, one of the

Uit dit onderzoek blijkt dat het nodig is om architectuur beslissingen te verbinden met de huidig gebruikte artefacten voor architectuur, zoals documentatie of de source code. We