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

189

List of Figures

1.1 An architectural diagram used in the BIOSCOPE project. . . 2

1.2 Domain model for Architectural Design Decisions . . . 7

1.3 Research Questions . . . 9

2.1 Use case diagram . . . 22

2.2 Use case 17 . . . 26

2.3 Use case 20 . . . 27

2.4 Use case 5 . . . 28

2.5 Use case 19 . . . 30

3.1 An abstract view on the software architecture design process . . . . 39

3.2 An abstract view on the rationale management process . . . 41

3.3 Similarities between software architecture design process and the rationale management process . . . 44

3.4 The architecture of a CD player with extended functionality . . . . 46

3.5 The result of the design decisions of Figure 3.4 . . . 47

3.6 The Archium design decision model . . . 50

3.7 The Updater design decision in Archium . . . 52

4.1 Overview of the paper . . . 59

4.2 The basic AK model . . . 60

4.3 The Knowledge Architect tool suite. . . 62

4.4 The Knowledge Architect Word plug-in button bar . . . 63

4.5 The Knowledge Explorer . . . 65

4.6 Overview of the approach and its validation . . . 68

4.7 A domain model for AK in documentation . . . 71

4.8 A software architecture document with colored KEs and pop-up menu for tracing the relationships of a KE . . . 74

4.9 Incompleteness information of a KE . . . 74

4.10 Average number of comments of the reviewers per situation . . . . 83

4.11 Average quality of comments of the reviewers per situation. . . 84

5.1 The Triple-A Framework . . . 100

6.1 Project and Architect Properties. . . 123

7.1 Conceptual Framework for Decision-based New Product Develop-ment . . . 136

8.1 Publicly available Component Data for the Rest Ruby Gem . . . 153

(3)

190 List of Figures

8.3 Relationships between Decisions . . . 156

8.4 Project History concerning Component Change. . . 157

8.5 The Design Decision Extraction Process . . . 159

8.6 Component Replacements . . . 160

Referenties

GERELATEERDE DOCUMENTEN

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

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