The System Architect; Meddler or Hero?The System Architect; Meddler or Hero? by Gerrit Muller University of South-Eastern Norway-NISE e-mail: [email protected] Abstract

The System Architect; Meddler or Hero?by Gerrit Muller University of South-Eastern Norway-NISE

e-mail: [email protected]

Abstract

Describes architecting and the task of the architect, with emphasis on bridging thewhy, what and how of a product. The memory usage of a medical workstation isused as practical illustration.The introduction of a system architect in an architecture unaware organisationis described. A metamorphosis takes place from a threatening meddler into anappreciated indispensable team member.

Distribution

This article or presentation is written as part of the Gaudí project. The Gaudí projectphilosophy is to improve by obtaining frequent feedback. Frequent feedback is pursued by anopen creation process. This document is published as intermediate or nearly mature versionto get feedback. Further distribution is allowed as long as the document remains completeand unchanged.

September 6, 2020status: finishedversion: 3.1

for many engineers the

system architect

=

threat or menace

uncovers problems

asks questions

has nicest

job

How much memory do you use?

That is too much!

architect engineer

Where is Gerrit in multi-D organisation space?

line

pro

gra

m

pro

jec

ts

Philips

Research

NatLab

IST

SWA

IA

Medical Semi-

conductors

CE

IPA ESAS IT

Gerrit

Muller

DM DS AVcomp

PvdH

HO

PB

SW reuse

FAM

Heartcare

CTT

SARCH

Components

ES

T

ISD

ISH

he

alth

ca

re

ISM

LRTO

The System Architect; Meddler or Hero?2 Gerrit Muller

version: 3.1September 6, 2020

MSorganisation

Who is Gerrit? What is Gaudí ?

Philips Medical ASML Philips NatLab

CT

OSS

NM

X-ray

MR EasyVision

ma

na

ge

r syste

m

en

gin

ee

rin

g

Gaudi

consolidation

education

transfer

exploration

application

consultation

facilitation++Gaudi =

of system

architecting

1980 1990 2000



MSwhoIsGerrit

Practical illustration; a medical imaging workstation

EasyVision: Medical Imaging WorkstationURF-systems

typical clinical

image (intestines)



MSeasyVision

Problem: unlimited memory consumption (1992)

total measured memory usage

pe

rfo

rma

nce

physical

memorypaging to disk

MB64 200

codeOS data bulk datafragmen-

tation

MB0 memory usage



MSmemoryZeroMeasurement

Solution: measure and iterative redesign

measured

code

OS

data

bulk data

fragmen-tation

budget

anti-fragmenting

budget based

awareness,

measurement

DLLs

tuning

200

MB

74

MB



MSmemoryUsageReduction

Method: budget per process

Budget:

+ measurable

+ fine enough to

provide direction

+ coarse enough to

be maintainabled

ll's

UI

co

mm

un

ica

tio

n

se

rve

r

sto

rag

e s

erv

er

prin

t se

rve

r

oth

er

UN

IX10

20

30

0

budget per process (right column)

10

MByte

measured (left column)



MSmemoryBudgetAnnotated

Integration uncovers hidden problems

component 1

component 4

component 3

component 2

integration and test

scheduled

closing date

delay

Do you have any design

issues for the design meeting?

The default answer is: No.

realized

closing date

During integration numerous

problems become visible



MSintegration

Architecting scope

architect

product scope

peo

ple

sco

pe

technology

only

including

designers(process)

including

individuals(human factors)

including

stakeholders

function product product

line

portfolio

architect

system architect

product line architect

portfolio architectsolution

context

technology

context

fitting

technical

sound



MSarchitectingScope

Architecture awareness

1

345hard shared

labour,

end of

integration

aware,

begin of

integration

mutual

respect,

begin of

project

unaware,

before

integration

mood

pe

rce

ptio

n

of a

rch

ite

ct

essential

team member

threat

menace

poor, crisis good

2


version: 3.1September 6, 2020MSawarenessPath

The engineer’s perception of the architect

for many engineers the

system architect

=

threat or menace

uncovers problems

asks questions

has nicest

job

How much memory do you use?

That is too much!

architect engineer


version: 3.1September 6, 2020MSthreatOrMenace

Understand the customer to drive design choices

Customer

objectives

Application Functional Conceptual Realisation

Customer

What

Customer

How

Product

What

Product

How

key drivers:

* throughput

* diagnostic quality

* film saving

- street price 50k$

* 3 exam

rooms

per exam:

* 20 images

* auto-print on

3 sheets

decomposition

anti-

fragmentation

DLL's

200 MB

74 MB

budget

measured

What does Customer need

in Product and Why?



MSeasyVisionCAFCR

Method to detect problems: Question generator

memory usage

export

server

print

server

database

server

SNR

accuracy

latency

processing

brightness

next

play movie

render film

query DB What is the memory usage of

the user interface

when querying the DB

import

server

user

interface

functions

component

characteristics

when performing <function>?

of the <component>

How about the <characteristic>



MSquestionGeneratorEasyVision

Conclusion

team full of heroes

so

ftw

are

sp

ecia

list

ma

rke

tin

gsp

ecia

list

ap

plic

atio

nsp

ecia

list

se

rvic

esp

ecia

list

ma

nu

factu

rin

gsp

ecia

list

me

ch

an

ics

sp

ecia

list

op

tics

sp

ecia

list

ele

ctr

on

ics

sp

ecia

list

meddling architect



MSmeddlerAndHeroes

Benchmarking

optimization

scope

INCOSESEI (CMU)

Gaudi

ambition

IEEE1471

technology

only

including

process

including

business

and human

factors

including

stakeholders

full life cycle

"informatica"

curriculum in

the Netherlands

certainty

predictability

agility



MSbenchmarking

Some Acknowledgements

Hammer, Dieter

Hoogenstraaten, Wil

Mueller, Juergen

Gieles, Hans

Eggenhuisen, Huib

Kloprogge, Raymond

Engel, Bas

van Rijnsoever, Bart

Driesen, JGH

Schelkers, Raymond

van der Heijden, Jaap

Vermeulen, Gerry

Stroucken, Marc

Wijnstra, Jan Gerben

Algra, Egbert

Derks, Frans

Faber, Albert

Aarts, Peter

Watabe, Yasuma

van Ouwerkerk, H

Huijnen, Ton

Gonot, Mathieu

van Splunter, Andre

van Rooijen, Joost

Verberkt, Mark

van der Linden, Wim

Patrzalek, Jarek

Vergoossen, Theo

Penners, Maurice

America, Pierre

Jaspers, Peter

Versteijlen, Joost

Beelen, Peter

Blijd, Jarl

Dijkema, Marcel

Roelandt, Werner

Janson, Paul

Bandakka, Mahesh

Ledeboer, Jodie

Geron, Nic

Zieringer, Peter

Beuk, Leo

Koolen, Gertjan

Koushik, Sudeendra

Milosevski, Vlatko

van den Broek, Ger

de Kruif, Peter

Daenen, Steven

Soepenberg, Gerben

Bingley, Peter

Follon, Roel

Elzinga, Onno

van den Donker, Piet

Zwaans, Ben

Harmsze, Francoise

Jansen, Tom

Gijsbers, Rob

Huis in 't Veld, Robert

Joosten, Jan

Mulder, Alwin

de Wit, Paul

Poesse, Jan

Spaak, Wim

Thus, Frank

van Velden, Jeroen

van Venrooy, Roland

Dobbelsteen, Jan

de Waal, Klaas

Muijen, M

Peters, Jo

van Bommel, Pieter Jan

Thijssen, Henk

Boot, Gert Jan

Vullings, Erik

Vermeer, Ad

Peeters, Bob

Obbink, Henk

Bas, Han

Rankers, Adrian

Akiwumi-Assani, Olu

Gopalan, Rajaraman

Misdom, Han

Schatorie, John

Boer, Richard

van Gogh, Clemy

Wissink, Getty

Engelsma, Erwin

Stut, Wim

Luttikhuizen, Paul

Bruin, Jan

Gooren, Huub

den Dekker, Wim

van der Laak, Eric

Crins, Wim

Heerink, Lex

Schippers, Alef

Schreppers, Jurgen

Deckers, Robert

van Balen, Auke

Huiban, Cristian

van Loon, Gerard

van den Heuvel, Patrick

Lobo, Lincoln

van de Meulenhof, Dennis

Houtepen, Rob

Hofsink, Robert

Buurman, Hans

Zondag, Eddy

Veldmans, Ferdinand

Merkus, Paul

van Tuijl, Frank

Wouters, Kees

van der Sterren, William

Soede, Michiel

van Bommel, Luc

Krikhaar, Rene

van den Brink, Johan

Ham, Kees

Bos, Erik

Pijpers, Frank

Medema, Jeroen

Kaag, Bjorn

Giesselman, Timo

Vos, Frans

de Greef, Pierre

Fischer, Stefan

Pu, Xuemei

Boom, Sjirk

ten Pierick, Henk

Stroucken, Louis

Young Tai Liu

van der Steen, Marcel

Siereveld, Ad

van Bakel, Gerian

Engbers, Rene

van Wetten, Frank

Stevers, Frank

Wubben, Rob

Schellingerhout, Nico

Vugts, John



MSacknowledgements

Gaudí homepage

http://nlww.natlab.research.philips.com:8080/

research/swa_group/muller/

links on this homepage:

this presentation MeddlerOrSaviorSlides.pdf

annotated text MeddlerOrSaviorPaper.pdf

background information Medical Imaging MedicalImagingPaper.pdf

original documentation Medical Imaging oldPresentations.html

containing:

more than 30 recent articles and or presentations

course material SARCH, ESA stakeholders, OOTI req eng



MSgaudiHomepage

FAQ

Answers to frequently asked questions



Architecture and research? The technology management cycle

Applicationof technology

Consolidationof know how

Explorationof new ideas

Applicationof technology

Consolidation of know how

Exploration of new ideas

Research Product Division



TechnologyManagementCycle

Is architecting scientific?

hard soft

mathematics physics medicine human

sciences

prove prediction statistics descriptive

reasoning

charlatan

handwaving

architecting methods

example: security

crypto biometric identification human

factor

certainty confidence evidence

based

plausible convincing

no science

soft science

hard science

legend



MSarchitectureAndScience

Guiding how

4. Infra-

structure

2. Construction

Decomposition

3. Allocation

5. Choice of

integrating

concepts

1. Functional

Decomposition

tunerframe-

bufferMPEG

DS

PCPU RAM

drivers scheduler OS

etc

audio video TXTfile-

systemnetworkingetc.

view play browse

storage

acquisition compress encoding

displayde-

compressdecoding

Resource

usagePerformance

Exception

handling

Device

abstraction

Pipeline



LWAarchitectureHow

The architect as integrator

sp

ecia

list

sp

ecia

list

sp

ecia

list

sp

ecia

list

sp

ecia

list

sp

ecia

list

sp

ecia

list

sp

ecia

list

generalistgeneralist

breadth ofknowledge

dep

th o

fkn

ow

led

ge



MATcomplementaryExpertises

The architect maintains technical roots

all-

rou

nd

sp

ecia

list systems architect

sp

ecia

list

root

knowledge

aspect

architect

breadth ofknowledge

dep

th o

fkn

ow

led

ge



MATfromSpecialistToSystemArchitect

sheets that didn’t make it into the final presen-tation



Memory Budget; too detailed

sh

are

d lib

rarie

s

UI

co

mm

un

ica

tio

n

se

rve

rsto

rag

e s

erv

er

prin

t se

rve

r

oth

er

UN

IX10

20

30

0

budget per process (right column)

10

MByte

measured (left column)

data

code

20


version: 3.1September 6, 2020MSmemoryBudget

Engineers perception; too detailed, too much text

- Does the nice work

How much memory do you use ?

Your functions together

use more memory than provided

Makes a toplevel design,

for instance a memory budget

Takes decisions without

knowing how memory intensive

a hashed dictionary is

Every question or problem

explodes into an even more

extensive set of questions

and problems

- Asks questions

- Identifies risks and problems

- Does have holes in

know how

- Does not provide definite

answers or solutions

Which can be nasty,

if you don't have any answer

Or worse, a problem is hiding

underneath

Meddling in my backyard,

without any substantial

know how

While we are busy with

detailed bug fixing and

maintenance

That is too much- Voices opinionsA judgement is given

What happens if we have many

small images? Or if we have very

large images?

Engineers feeling architect's activitycaused by illustrated by examples of architect

behavior



MSengineerPerception

Integrating CAFCR; too glossy

Customer

objectives

Application Functional Conceptual Realization

intention

constraintawareness

objectivedriven

contextunderstanding

oppor-tunities

knowledgebased

Customer

What

Customer

How

Product

What

Product

How

What does Customer need

in Product and Why?



MSintegratingCAFCR

Architect characteristics; too detailed, too much text

- Does the nice work

- Asks questions

- Identifies risks and problems

- Does have holes in

know how

- Does not provide definite

answers or solutions

- Voices opinions

Questions are the primary tool

of an architect

+ Prevention is valuable

+ Focus, selection is key,

which requires vision and choices+ Sometimes the architect needs to

dive in deep + There is more nice work needed

than we ever can do

+ Keeps repeating the previous actions

Engineers perception Required characteristic of the architect



MSarchitectCharacteristics

Question generator; other domain

tunermixer

monitor

control

SNR

accuracy

memory

usage

processing

show

broadcast

record

play movie

play game

browse

latency

What is the latency induced by

the graphics generator

when browsing

video

processor

graphics

generator

functions

component

characteristics

when performing <function>?

of the <component>How about the <characteristic>



MSfunctionSubsystemCharacteristic

Architecture Awareness Phases; too complex

phase 1

happy

unaware

phase 2

problems

nagging

awareness

phase 3

crisis

threat

phase 4

trouble-

shooting

buils up

credit

phase 5

amazement

archite

ct

apprecia

tion

architectural

coverage10%

20%

0%

100%number of

known

problems

architect

starts

project team

mood

architecture

awareness



MSphasesArchitectureAwareness

Documents

The System Architect; Meddler or Hero?The System Architect; Meddler or Hero? by Gerrit Muller University of South-Eastern Norway-NISE e-mail: [email protected] Abstract