• 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!
3
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)

191

List of Tables

1.1 Historical Change in Software Engineering and Architecture . . . . 3

1.2 Structure of this Thesis . . . 13

4.1 Experimental design: #subjects per situation . . . 78

4.2 Ratings of reviewer comments of the first hour . . . 79

4.3 Confidence levels for H1and H02 . . . 84

4.4 Confidence levels for H3and H4 . . . 85

5.1 Overview of Case Studies . . . 107

5.2 Mapping the Cases on the Triple-A Framework . . . 108

6.1 Overview of Conclusions on Beliefs . . . 125

6.2 Project and Person Characteristics . . . 129

6.3 Success Factors . . . 130 6.4 Triple-A Framework . . . 131 7.1 Interview Questions . . . 140 7.2 Overview Companies . . . 141 7.3 Overview of Pivots . . . 143 7.4 Concept Comparison . . . 145

8.1 Reflection of Decisions in Version Management . . . 155

8.2 Project Availability of Programming Languages . . . 164

8.3 Ease of Mining of Programming Languages . . . 165

8.4 Programming Language Component Ecosystem . . . 165

8.5 Summary of Programming Language Suitability . . . 166

8.6 Acquired Data . . . 167

8.7 Number of Deltas Identified . . . 169

8.8 Summary of CDS Growth . . . 169

8.9 Quantitative Results . . . 170

8.10 Results of Email Experiment . . . 173

(3)

Referenties

GERELATEERDE DOCUMENTEN

Description: In this use case, the knowledge grid supports the user in validating the correctness of the architectural decisions addressing the requirements.. Primary

The design decisions reflect the rationale used for the decision making process, and form the natural bridge between rationale and the resulting architecture.. 3.4.2 CD player: a

The research question we answer with the quasi-controlled experiment is the fol- lowing: Does our approach for enriching software architecture documentation with formal AK improve

The cases are similar in that they all involved relatively small, collocated teams facing complex, real-life problems, but they involve a vari- ety of situations — from a small

The beliefs range from the amount of effort needed for architecture documentation, to the size of the team or the persons responsible for making the architectural decisions..

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