Architectural Reasoning Explained - Gaudí System Architecting

223 Pages·2016·7.86 MB·English

Architectural Reasoning Explained
method outline method visualization
framework Customer Application Functional Conceptual Realization
objectives
submethods ++++ kvbseauuylpsu ipdenlr eiecivshres am rmisnaopdels ++++ scedtonyanntkiamttaeyenmo hxdrdotei c ecdll daolmisaetnioogrcsdnre aesrmhnlsisp +++an ucmdos aemspdfe umcpevnaiceencsorrgteacim olit aenpmlcso, ohslornietgiicoisantlsi cs +++an cfinduof nonmcddrstameetiornccuanyoocta immtmoilonppon oormessoiittdiiooennl ++++an bbpsdauee fmdnrefagcotanyhernam mtaylyan amsnarikcsloyienrse gis
integration safety
via qualities performance
espxpelcoifriec details mviasriokent story adneasliygsnea priocruia sssoeelution knadonewas-lihygsonew ddeetasiiglend
reasoning UU'" dqiuaaglnityosticCoOthrTUoughqpimuuaatlgiteypuprcrihcpaersoefit mstaarngdinardB wIoQrk ssptaetciotyncBpaiocsMael bCudPcgUcoeommtnSmesomolneoMryo obrluaedw'sgeeretnngdineer P'M'PmelimmMiotrydppeirxpoleitcbhlerasrsying
GerritMuller
UniversityofSouth-EasternNorway-NISE
Hasbergsvei36 P.O.Box235,NO-3603Kongsberg Norway
[email protected]
Abstract
This document addresses the way an architect can do his work. It shows many
tools that belong to the architect toolkit: The CAFCR model, tools per 5 views
(Customer Objectives, Application, Functional, Conceptual and Realization),
Qualities,StorytellingandReasoninginmultipledimensions
Distribution
ThisarticleorpresentationiswrittenaspartoftheGaudíproject. TheGaudíprojectphilosophyistoimprove
byobtainingfrequentfeedback. Frequentfeedbackispursuedbyanopencreationprocess. Thisdocumentis
publishedasintermediateornearlymatureversiontogetfeedback.Furtherdistributionisallowedaslongasthe
documentremainscompleteandunchanged.
AllGaudídocumentsareavailableat:
http://www.gaudisite.nl/
version:3.4 status:preliminarydraft January16,2022
Contents
Introduction xiv
I Introduction 1
1 WhatisSystemsArchitectinginanIndustrialContext? 2
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 DescriptionoftheBusinessContext . . . . . . . . . . . . . . . . 4
1.3 InternalStakeholders . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 OverviewofCAFCRandThreadsofReasoning 6
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 ArchitectingMethodOverview . . . . . . . . . . . . . . . . . . . 7
2.3 TheCAFCRModel . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 IntroductiontoMedicalImagingCaseStudy 11
3.1 MarketandApplication . . . . . . . . . . . . . . . . . . . . . . . 11
3.2 Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
II Theoryofarchitecturalreasoning 16
4 BasicWorkingMethodsofaSystemArchitect 17
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2 Viewpointhopping . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.3 Decompositionandintegration . . . . . . . . . . . . . . . . . . . 23
4.4 Quantification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.5 Copingwithuncertainty . . . . . . . . . . . . . . . . . . . . . . 26
4.6 Modelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.7 WWHWWWquestions . . . . . . . . . . . . . . . . . . . . . . . 30
4.8 DecisionMakingApproachinSpecificationandDesign . . . . . . 31
4.9 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 33
5 Thecustomerobjectivesview 34
5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.2 Keydrivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.3 Valuechainandbusinessmodels . . . . . . . . . . . . . . . . . . 37
5.4 Suppliers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6 Theapplicationview 40
6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.2 Customerstakeholdersandconcerns . . . . . . . . . . . . . . . . 41
6.3 Contextdiagram. . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.4 Entityrelationshipmodel . . . . . . . . . . . . . . . . . . . . . . 43
6.5 Dynamicmodels . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7 Thefunctionalview 46
7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
7.2 Casedescriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.3 Commercial,serviceandgoodsflowdecomposition . . . . . . . . 49
7.4 Functionandfeaturespecifications . . . . . . . . . . . . . . . . . 51
7.5 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.6 InformationModel . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.7 Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.8 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7.9 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 59
8 Theconceptualview 60
8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.2 Constructiondecomposition . . . . . . . . . . . . . . . . . . . . 61
8.3 Functionaldecomposition . . . . . . . . . . . . . . . . . . . . . . 63
8.4 Designingwithmultipledecompositions . . . . . . . . . . . . . . 64
8.5 InternalInformationModel . . . . . . . . . . . . . . . . . . . . . 67
8.6 Executionarchitecture . . . . . . . . . . . . . . . . . . . . . . . 67
8.7 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
8.8 Safety,ReliabilityandSecurityconcepts . . . . . . . . . . . . . . 70
8.9 Startupandshutdown. . . . . . . . . . . . . . . . . . . . . . . . 72
8.10 Workbreakdown . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8.11 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 76
9 Therealizationview 77
9.1 Budgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
9.2 Logarithmicviews . . . . . . . . . . . . . . . . . . . . . . . . . 79
9.3 MicroBenchmarking . . . . . . . . . . . . . . . . . . . . . . . . 81
GerritMuller UniversityofSouth-EasternNorway-NISE
ArchitecturalReasoningExplained page: iii
January16,2022 version:3.4
9.4 Performanceevaluation . . . . . . . . . . . . . . . . . . . . . . . 82
9.5 Assessmentofaddedvalue . . . . . . . . . . . . . . . . . . . . . 82
9.6 Safety,ReliabilityandSecurityAnalysis . . . . . . . . . . . . . . 87
9.7 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 87
10 QualitiesasIntegratingNeedles 88
10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
10.2 SecurityasExampleofaQualityNeedle . . . . . . . . . . . . . . 88
10.3 QualitiesChecklist . . . . . . . . . . . . . . . . . . . . . . . . . 91
10.4 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
11 StoryHowTo 97
11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
11.2 HowtoCreateaStory? . . . . . . . . . . . . . . . . . . . . . . . 98
11.3 HowtoUseaStory? . . . . . . . . . . . . . . . . . . . . . . . . 99
11.4 Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
11.5 ExampleStory . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
11.6 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 102
12 UseCaseHowTo 104
12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
12.2 ExamplePersonalVideoRecorder . . . . . . . . . . . . . . . . . 104
12.3 Theusecasetechnique . . . . . . . . . . . . . . . . . . . . . . . 105
12.4 ExampleURFexamination . . . . . . . . . . . . . . . . . . . . . 107
12.5 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
13 ThreadsofReasoning 110
13.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
13.2 OverviewofReasoningApproach . . . . . . . . . . . . . . . . . 110
13.3 Reasoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
13.4 Outlineofthecompletemethod . . . . . . . . . . . . . . . . . . 117
13.5 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
III MedicalImagingCasedescription 118
14 MedicalImagingWorkstation: CAFViews 119
14.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
14.2 RadiologyContext . . . . . . . . . . . . . . . . . . . . . . . . . 119
14.3 TypicalCase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
14.4 KeyDriverGraph . . . . . . . . . . . . . . . . . . . . . . . . . . 127
14.5 Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
14.6 InteroperabilityviaInformationModel . . . . . . . . . . . . . . . 132
GerritMuller UniversityofSouth-EasternNorway-NISE
ArchitecturalReasoningExplained page: iv
January16,2022 version:3.4
14.7 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
15 MedicalImagingWorkstation: CRViews 135
15.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
15.2 ImageQualityandPresentationPipeline . . . . . . . . . . . . . . 136
15.3 SoftwareSpecificViews . . . . . . . . . . . . . . . . . . . . . . 138
15.4 MemoryManagement . . . . . . . . . . . . . . . . . . . . . . . . 140
15.5 CPUUsage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
15.6 MeasurementTools . . . . . . . . . . . . . . . . . . . . . . . . . 146
15.7 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
16 StoryTellinginMedicalImaging 151
16.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
16.2 TheSalesStory . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
16.3 TheRadiologistatWork . . . . . . . . . . . . . . . . . . . . . . 153
16.4 TowardsDesign . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
16.5 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
17 MedicalImaginginChronologicalOrder 157
17.1 ProjectContext . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
17.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
17.3 DevelopmentofEasyvisionRF . . . . . . . . . . . . . . . . . . . 158
17.4 PerformanceProblem . . . . . . . . . . . . . . . . . . . . . . . . 160
17.5 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
17.6 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
18 ThreadsofReasoningintheMedicalImagingCase 165
18.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
18.2 ExampleThread . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
18.3 ExplorationofProblemsandSolutions . . . . . . . . . . . . . . . 167
18.4 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
IV ExperienceswithTeachingArchitecuralReasoning 176
19 DecomposingtheArchitect;WhatareCriticalSuccessFactors? 177
19.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
19.2 WhatisanArchitect? . . . . . . . . . . . . . . . . . . . . . . . . 178
19.3 Education . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
19.4 Nature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
19.5 Experience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
19.6 Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
19.7 DiscussionandConclusions . . . . . . . . . . . . . . . . . . . . 198
GerritMuller UniversityofSouth-EasternNorway-NISE
ArchitecturalReasoningExplained page: v
January16,2022 version:3.4
19.8 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 199
Abbreviations 200
GerritMuller UniversityofSouth-EasternNorway-NISE
ArchitecturalReasoningExplained page: vi
January16,2022 version:3.4
List of Figures
1 Structureof“ArchitecturalReasoningExplained” . . . . . . . . . xiv
1.1 Architecting=creatinganarchitecture . . . . . . . . . . . . . . . 3
1.2 Thebusinesscontextofarchitectingmethods . . . . . . . . . . . 4
1.3 Stakeholdersoftheproductcreationwithinacompanyitself . . . 4
2.1 An architecting method supports the architect in his process to go
from a vague notion of the problem and a vague notion of the po-
tential solutions to a well articulated and structured architecture
description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 The outline of the architecting method with the corresponding vi-
sualizationthatwillbeusedinthelaterchapters. . . . . . . . . . 8
2.3 The“CAFCR”model . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4 IterationovertheCAFCRviewsandtheoperationalview. Thetask
ofthearchitectistointegratealltheseviewpoints,inordertogeta
valuable,usableandfeasibleproduct. . . . . . . . . . . . . . . . 9
3.1 EasyvisionservingthreeURFexaminationrooms . . . . . . . . . 12
3.2 X-rayroomswithEasyvisionappliedasprintserver . . . . . . . . 12
3.3 Comparisonscreencopyversusoptimizedfilm . . . . . . . . . . 13
3.4 Challengesforproductcreation . . . . . . . . . . . . . . . . . . . 13
3.5 Top-leveldecomposition . . . . . . . . . . . . . . . . . . . . . . 14
4.1 Smallsubsetofviewpoints . . . . . . . . . . . . . . . . . . . . . 19
4.2 ViewpointHopping . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.3 Theseeminglyrandomexplorationpath . . . . . . . . . . . . . . 20
4.4 Twomodesofscanningbyanarchitect . . . . . . . . . . . . . . . 21
4.5 Combinedopenperceptivescanningandgoal-orientedscanning . 21
4.6 The final coverage of the problem and solution space by architect
andengineers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.7 Decomposition,interfacemanagementandintegration . . . . . . 23
4.8 Successivequantificationrefined . . . . . . . . . . . . . . . . . . 24
4.9 Exampleoftheevolutionofquantificationintime . . . . . . . . . 25
4.10 Exampleofaquantifiedunderstandingofoverlayinawaferstepper 25
4.11 Thearchitectfocusesonimportantandcriticalissues,whilemoni-
toringtheotherissues . . . . . . . . . . . . . . . . . . . . . . . . 26
4.12 Exampleworrylistofanarchitect . . . . . . . . . . . . . . . . . 27
4.13 Someexamplesofmodels . . . . . . . . . . . . . . . . . . . . . 28
4.14 Typesofmodels . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.15 Thestartingwordsforquestionsbythearchitect . . . . . . . . . . 30
4.16 Whybroadensscope,Howopensdetails . . . . . . . . . . . . . . 30
4.17 Flowfromproblemtosolution . . . . . . . . . . . . . . . . . . . 31
4.18 Multiplepropositions . . . . . . . . . . . . . . . . . . . . . . . . 32
4.19 Recursiveandconcurrentapplicationofflow . . . . . . . . . . . 33
5.1 OverviewofCustomerObjectivesViewmethods . . . . . . . . . 35
5.2 Exampleofthefourkeydriversinamotorwaymanagementsystem 36
5.3 Submethodtolinkkeydriverstorequirements,existingoftheiter-
ationoverfoursteps . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.4 Recommendationsforapplyingthekeydriversubmethod . . . . . 37
5.5 Examplevaluechain . . . . . . . . . . . . . . . . . . . . . . . . 38
5.6 Exampleofsimplesuppliermapforacableprovider . . . . . . . 39
6.1 Overview of methods and models that can be used in the applica-
tionview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.2 StakeholdersandconcernsofanMRIscanner . . . . . . . . . . . 42
6.3 Systemsinthecontextofamotorwaymanagementsystem . . . . 42
6.4 DiagramwithentitiesandrelationshipforasimpleTVappliance . 43
6.5 Examplesofdynamicmodels . . . . . . . . . . . . . . . . . . . . 44
6.6 Productivityandcostmodels . . . . . . . . . . . . . . . . . . . . 45
6.7 DynamicsofanURFexaminationroom . . . . . . . . . . . . . . 45
7.1 Examplepersonalvideorecorderusecasecontentsfortypicaluse
caseandworstcaseorexceptionalusecase . . . . . . . . . . . . 47
7.2 Recommendationsforworkingwithusecases . . . . . . . . . . . 48
7.3 Commercialtreeasmeanstodescribecommercialavailablevaria-
tionsandpackaging . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.4 Logisticdecompositionsforaproduct . . . . . . . . . . . . . . . 50
7.5 Mappingtechnicalfunctionsonproducts . . . . . . . . . . . . . . 51
7.6 Relationbetweenuserinterfaceandfunctionalspecification. . . . 51
7.7 Exampleofperformancemodelling: throughputasfunctionofuser
controlledvalues . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.8 Layeringofinformationdefinitions . . . . . . . . . . . . . . . . . 54
7.9 Exampleofapartialinformationmodel . . . . . . . . . . . . . . 54
7.10 Smallpartofadatamodel . . . . . . . . . . . . . . . . . . . . . . 55
GerritMuller UniversityofSouth-EasternNorway-NISE
ArchitecturalReasoningExplained page: viii
January16,2022 version:3.4
7.11 Thestandardscomplianceinthefunctionalviewinabroaderforce
field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7.12 Summaryoffunctionalview . . . . . . . . . . . . . . . . . . . . 58
8.1 ExampleofaconstructiondecompositionofasimpleTV . . . . . 61
8.2 Characterizationoftheconstructiondecomposition . . . . . . . . 61
8.3 Examplefunctionaldecompositioncameratypedevice . . . . . . 63
8.4 Characterizationofthefunctionaldecomposition . . . . . . . . . 63
8.5 Questiongeneratorformultipledecompositions . . . . . . . . . . 64
8.6 Selectionfactorstoimprovethequestiongenerator . . . . . . . . 65
8.7 Addressinglinesorplanesatonceinthemultipledimensions . . . 66
8.8 Exampleofapartialinternalinformationmodel . . . . . . . . . . 67
8.9 Exampleprocessdecomposition . . . . . . . . . . . . . . . . . . 68
8.10 Executionarchitecture . . . . . . . . . . . . . . . . . . . . . . . 68
8.11 PerformanceModel . . . . . . . . . . . . . . . . . . . . . . . . . 70
8.12 Simplifiedstartupsequence . . . . . . . . . . . . . . . . . . . . 72
8.13 Exampleworkbreakdown . . . . . . . . . . . . . . . . . . . . . 73
8.14 Core,KeyorBasetechnology . . . . . . . . . . . . . . . . . . . 73
8.15 Exampleintegrationplan,with3tiersofdevelopmentmodels. . . 74
9.1 Budgetbaseddesignflow . . . . . . . . . . . . . . . . . . . . . . 78
9.2 Exampleofamemorybudget . . . . . . . . . . . . . . . . . . . . 78
9.3 Actualtimingrepresentedonalogarithmicscale. . . . . . . . . . 79
9.4 Typicalmicrobenchmarksfortimingaspects . . . . . . . . . . . 81
9.5 Thetransfertimeasfunctionofblocksize . . . . . . . . . . . . . 82
9.6 Exampleofperformanceanalysisandevaluation . . . . . . . . . 83
9.7 PerformanceCost,inputdata . . . . . . . . . . . . . . . . . . . . 84
9.8 PerformanceCost,choicebasedonsalesvalue . . . . . . . . . . . 85
9.9 PerformanceCost,effortconsequences . . . . . . . . . . . . . . . 85
9.10 Butmanymanyotherconsiderations . . . . . . . . . . . . . . . . 86
9.11 Analysismethodsforsafety,reliabilityandsecurity . . . . . . . . 87
10.1 Thequalityneedlesaregenericintegratingconceptsthroughthe5
CAFCRviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
10.2 Examplesecuritythroughallviews . . . . . . . . . . . . . . . . . 90
10.3 Checklistofqualities . . . . . . . . . . . . . . . . . . . . . . . . 92
11.1 Fromstorytodesign . . . . . . . . . . . . . . . . . . . . . . . . 98
11.2 Examplestorylayout . . . . . . . . . . . . . . . . . . . . . . . . 98
11.3 criteriaforagoodstory . . . . . . . . . . . . . . . . . . . . . . . 100
11.4 Exampleofastory . . . . . . . . . . . . . . . . . . . . . . . . . 102
11.5 ValueandChallengesinthisstory . . . . . . . . . . . . . . . . . 103
GerritMuller UniversityofSouth-EasternNorway-NISE
ArchitecturalReasoningExplained page: ix
January16,2022 version:3.4
12.1 ExampleusecaseTimeShiftrecording . . . . . . . . . . . . . . 105
12.2 Whatifconflictingeventshappenduringthepauseinterval? . . . 106
12.3 ContentofaUseCase. . . . . . . . . . . . . . . . . . . . . . . . 106
12.4 Examplepersonalvideorecorderusecasecontents . . . . . . . . 107
12.5 TypicalcaseURFexamination . . . . . . . . . . . . . . . . . . . 108
12.6 TimingoftypicalURFexaminationrooms . . . . . . . . . . . . . 109
12.7 Recommendationsforworkingwithusecases . . . . . . . . . . . 109
13.1 Overviewofreasoningapproach . . . . . . . . . . . . . . . . . . 111
13.2 Exampleofastartingpoint: aslowsystemresponsediscussedfrom
thedesigner’sviewpoint . . . . . . . . . . . . . . . . . . . . . . 112
13.3 Example of creating insight: to study the required performance a
responsemodelofthesystemismade . . . . . . . . . . . . . . . 112
13.4 Deepeningtheinsightbyarticulatingspecificneedsandgathering
specificfactsbysimulations,testsandsimulations . . . . . . . . . 113
13.5 Broadeningtheinsightbyrepeatingwhy,whatandhowquestions 114
13.6 ExampledefinitionofthethreadintermsoftensionforadigitalTV 114
13.7 Reasoningasafeedbackloopthatcombinesintuitionandanalysis 115
13.8 Onethreadofreasoningshowingrelatedissues. Thelinethickness
isanindicationfortheweightoftherelation. . . . . . . . . . . . 116
13.9 Example of the documentation and communication for a digital
TV. The thread is documented in a structured way, despite the
chaotic creation path. This structure emerges after several itera-
tions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
14.1 The clinical context of the radiology department, with its main
stakeholders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
14.2 Thefinancialcontextoftheradiologydepartment . . . . . . . . . 121
14.3 ApplicationlayeringofITsystems . . . . . . . . . . . . . . . . . 122
14.4 Referencemodelforhealthcareautomation . . . . . . . . . . . . 123
14.5 Clinicalinformationflow . . . . . . . . . . . . . . . . . . . . . . 124
14.6 URFmarketsegmentation . . . . . . . . . . . . . . . . . . . . . 125
14.7 TypicalcaseURFexamination . . . . . . . . . . . . . . . . . . . 126
14.8 TimingoftypicalURFexaminationrooms . . . . . . . . . . . . . 126
14.9 Keydrivers,applicationdriversandrequirements . . . . . . . . . 127
14.10Retrospectivefunctionalityroadmap . . . . . . . . . . . . . . . . 131
14.11Informationmodel,standardizationforinteroperability . . . . . . 132
14.12CoverageofsubmethodsoftheCAFviews . . . . . . . . . . . . 134
15.1 The user expectation is that an image at one work-spot looks the
sameasatotherwork-spots. Thisisfarfromtrivial,duetoalldata
pathsandthemanypartiesthatcanbeinvolved . . . . . . . . . . 136
15.2 ThestandardpresentationpipelineforX-rayimages . . . . . . . . 137
GerritMuller UniversityofSouth-EasternNorway-NISE
ArchitecturalReasoningExplained page: x
January16,2022 version:3.4