From Industrial Experience to System Architecting Know-howgaudisite.nl/FromIndustryToKnowHowSlides.pdf · Make the Systems Architecting art more accessible Enable the education of

From Industrial Experience to System ArchitectingKnow-how

by Gerrit Muller University of South-Eastern Norway-NISEe-mail: [email protected]

www.gaudisite.nl

Abstract

The system design process in an industrial setting is illustrated by the devel-opment flow of a Medical Imaging Workstation. The role of the architect andthe architecting method is explained.The goals of the Gaudí project are elaborated. In summary the goal is to developsystems architecting as a discipline. Questions addressed are: How to doresearch in this field? What are the challenges to do the research in a scientificway. The education of architects is also part of the development of this discipline.Although a lot of activity has already been done in related fields a lot still has tobe done to develop the discipline Systems Architecting.

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: draftversion: 0.3

logoTBD

From Industry to Research

CT

OSS

NM

X-ray

MR EasyVision

ma

na

ge

r syste

m

en

gin

ee

rin

g

Gaudí

1980 1990 2000

Philips Medical ASMLPhilips NatLab

ESI

industrial experience researchtime pressure

cost constraints

pragmatics

products

sales reflection

evidence

exposurelots of people

education

Bu

ske

rud

From Industrial Experience to System Architecting Know-how2 Gerrit Muller

version: 0.3September 6, 2020FIESAwhoIsGerrit

Gaudí Project Goals

• Consolidate existing Systems Architecting Methods

• Make the Systems Architecting art more accessible

• Enable the education of (future) System Architects

• Research new or improved Systems Architecting Methods

evaluate, reflect, generalize

case descriptions

curriculum, course material

industry as laboratory


version: 0.3September 6, 2020

FIESAgaudiGoals

Easyvision serving three URF examination rooms

EasyVision: Medical Imaging WorkstationURF-systems

typical clinical

image (intestines)



MSeasyVision

X-ray rooms with Easyvision applied as printserver

ExaminationRoom

ControlRoom

ReadingRoom

Corridoror closet

ExaminationRoom

ControlRoom

printer

light box

detector

X ray

source console



XRayRoomsPlusPrintServer

Radiologist workspots and activities

activities of the radiologist

ExaminationRoom

dictation

room

supervision

of the

examination

view and

diagnose,

dictate report

verify and

authorise

report

auto-

loader

light-box



MISactivitiesRadiologist

Diagnosis in tens of seconds

tens of seconds

auto-

loader

light-box

films loaded by

clinical personnel

during the day

looks at

images

moves head

forward / backward

moves head or eyes

left/right/up/down

zoom in overview

image selection, panning

mumbles a few

Latin words or

clinical codes

in recorder

presses

next button

new

film

s

old

film

s

report



MISdiagnosis

Typical case URF examination

exam

room 1

exam

room 3

exam

room 2

image production: 20 10242 8 bit images per examination

3 examination rooms connected to

examination room: average 4 interleaved examinations / hour

film production: 3 films of 4k*5k pixels each

1 medical imaging

workstation + printer

high quality output

(bi-cubic interpolation)


version: 0.3September 6, 2020MICAFtypicalCase

Comparison screen copy versus optimized film

old: screen copy

20 to 50% less film needed

new: SW formatting



MedicalImagingFilmComparison

Architecting = creating an architecture

preceding architecture architecting architecture

PCP team

architect, project leader,

engineers,

product manager

problem knowledge

solution knowledge

business context

technology context

human context

legend

stakeholdersexpectations, needs,

concerns, constraints



WARCHarchitecting

Architecting EasyVision

architecting

business context

technology context

human context

problem know how

URF examinations,

diagnosis, radiology,

lightbox, fim, report

preceding architecture

common viewing

solution know how

Unix, Objective-C, data

base, image processing,

TCP/IP, OO, memory man.

constraints

cost, skills, time

stakeholders

radiologist, nurse,

patient

architecture

EasyVision

& multi-view

description

legendPCP team

skilled

independent

SW designers


version: 0.3September 6, 2020FIESAarchitecting

Architecture = tangible (internal) + intangible (external)

performance behaviour functionality

by all stakeholders

the perception of,

experience with,

the system in all phases of

the system life-cycle

external

structure constructioninternal



WARCHarchitecture

EasyVision Architecture

shared code

UI process

database server

print server

DOR server

communication server

UNIX commands

compute server

system monitor

ASW total

UNIX Solaris 2.x

file cache

total

obj data

3.0

3.2

1.2

2.0

2.0

0.2

0.5

0.5

12.6

bulk data

12.0

3.0

9.0

1.0

4.0

0

6.0

0

35.0

code

11.0

0.3

0.3

0.3

0.3

0.3

0.3

0.3

0.3

13.4

total

11.0

15.3

6.5

10.5

3.3

6.3

0.5

6.8

0.8

61.0

10.0

3.0

74.0

memory budget in Mbytes

memory

budget

image

quality

context

construction

decomposition

user interfacecommunicatio

n

data base

expo

rtprint

optical

storage

optical

disk

drive

printerdisk drivenetwor

k

UI

devicessystem

monitorUnix

daemo

ns

remote

systems

and users

user

X-ray system

image

generati

on

pres

en-

tation

monitor

film

network,

storage

Easyvision

applicati

on

processi

ng pres

en-

tation

monitor

film

network,

storage

3rd

party

workstati

on

monitor

SW

processes

processing

pipeline

DSI

3MR

C

Desk, cabinets, cables, etc.

Standard IPX workstationDORHC

interf

RC

interf

SunOS

NIXRC

drive

r

HC

drive

r

DOR

drive

r

Spoo

l

H

C

U

St

or

e

Imag

e

Gf

xUI DB

PMS

- net

in

PMS

- net

out

Medical Imaging R/F

Start

up

Insta

ll

Confi

g

SW

keys

servi

ce

dev.

toolsPrint Store

View

Cluster

3 exam rooms 3 films/exam contrast autoprint autostorage

clinical details

external

internal

by all stakeholders

the perception of,

experience with,

the system in all phases of

the system life-cycle


version: 0.3September 6, 2020FIESAarchitecture

The business context of architecting methods

product creation

BusinessArchitecting

method

People

Process

Organisation

sets targets

supports

supports

fits in

enables

perform



PBUSScontext

Internal stakeholders

product creation

BusinessArchitecting

method

People

Process

Organisation

sets targets

supports

supports

fits in

enables

perform

policy and planningbusiness, marketing,

operational managers

product creationproject leader, product

manager, engineers,

suppliers

customer-orientedsales, service, production,

logistics

people, process,

and technology

capability managers,

technology suppliers



WARCHinternalStakeholders

Context of Architecting Method Research

methodmethodsystem

system context

users

customers

designers

manufacturer

suppliers

managers

architect

architectingarchitecting

thought

processes

methodresearch

report

method research

legend

specific

tangible

ill defined

intangible



ARMcontext

Spectrum of sciences

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

Soft problems can be approached with a scientific attitude

make explicit

substantiate

try to validate

research question

hypothesis

heuristics

principles

facts

analysis

evaluate

open debate

body of knowledge

cases

soft is not in conflict with scientific attitude



RORMscientificAttitude

Systematic Know-how to cope with Growing Complexity

creative

systematic

repeated

creative

systematic

creative

systematic

more

performance

and functionality

causes more

complexity

and requires

more effort

active work on

systematic methods

reduces effort and

the need for a lot of

creative effort

systematic methods

new creative

year X year X+4 year X+4



RORMimpact

Research of Architecting Methods

hypothesis

with criteria

research question

apply and validate

case

descriptions

evaluation

of results



ARMevaluationSimple

Technology Management Cycle

Applicationof technology

Consolidationof know how

Explorationof new ideas

Literature search

Creative option generation

Try out

Industry as laboratory

Reflection

Write articles

Create courses



ARMtechnologyManagementCycle

Moving in the meta direction

Applicationof technology

Consolidationof know how

Explorationof new ideas

archi-

tecting

method

meta0

bottom line:

product

creation

meta1

enabling:

architecting

method

meta2

pro-active:

research of

architecting

method

meta3

scientific foundation:

method to research

architecting methods

architecting

method research

research

method



ARMmeta

System ?= Multi-disciplinary

mono-

disciplinary

design

multi-

disciplinary

design

system

evolvability

process

organization, people

reliabilityperformancecost

robustness

multi-objective

design methods multi-objective

design methods

performance and

resource prediction

single aspect

design method

VHDL RMAUML

hybrid

methods YAPI

process

issues

well defined

well defined

but soft

rather soft

legend

Mechanical Engineering Electrical Engineering Software Engineering

ES

I fo

cu

s



FIESAmethodLayers

The context of architecting

natural system architect habitat

system

architecting

classical disciplines

mathematics, physics, chemistry,

biology, medicine, economics,

computer science,

mechanical engineering,

electronical engineering

management disciplines

technology management,

business management,

process management,

quality assurance,

project management

standardisation bodies,

professional societies

IEEE, ISO, ACM, IFIP, INCOSE

communities, conferences

requirements engineering,

reliability engineering,

product lines,

SW architecting,

TRIZ,

RUP

human sciences

psychology

sociology

pedagogy

anthropology

theology



FARcontext

System architecting research: to do

frame of reference

taxonomy

glossary

framework

ontology

objectives

heuristics

principles

case studies methods

reliable

systemslowest cost

design for

testability

fast

innovation

secure

systems

maximum

performance

industry as

laboratorylarge scale

research



FARtodo

Curriculum system architecting

ESA

SW

Execution

architecture

SARCH

ESA stakeholders

available

missing

external

architecture school

root

technical

know-how

generalist

technical

know-how

business, application insight

process insight

psycho-social

skills

apply theory

in practice

become

all-round

experience the

non-technical aspects

see every human

as an individual

System

design

methods

Bredemeyer

SW architecture

Architectural

reasoning

ESA

systemESA

silicon

ESA

mechatronics

marketing, processand many more

Bredemeyer -

Role of the architect

Thomas Gilb - EVO,

requirements eng

mathematics

physics

chemistry

mechanical

engineering

computer

science

electronical

engineering

conventional

curriculums

advanced

SARCH

reliability engineering

QFD and more

legend



FARcurriculumSA

Courses based on Gaudí Material

System Architecture

Embedded Systems

Architecting; Stakeholders

Requirements Engineering

as part of OOTI curriculum

SARCH

ESA

OOTI

5

3

5

16

12-18

16

architects

stakeholders of architects

potential architects

post-doctoral students

Ab

bre

via

tio

n

Du

ratio

n

(in

da

ys)

Pa

rtic

ipa

nts

pe

r co

urs

e

Target audienceCourse

Management SARCH MSARCH 2 16 management teams

Embedded Systems

contextEScontext 4 30 masters students

Execution Architecture

(with Ton Kostelijk)

EXARCH

ASP4..5 16

SW designers

architects

Multi-Objective System

Architecting and Design

System Modeling and

Analysis

MOSAD

MA611

3..5

3..5

designers

architects

designers

architects16

16


version: 0.3September 6, 2020GaudiCourseTable

Status of Courses

nu

mb

er

of

co

urs

es u

pto

Ma

rch2

00

8

ap

pr.

to

tal

pa

rtic

ipa

nts

System Architecture

Embedded Systems

Architecting; Stakeholders

Requirements Engineering

as part of OOTI curriculum

SARCH

ESA

OOTI

44

20

7

660

125

300

Ab

bre

via

tio

n

Course

Management SARCH MSARCH 7 72

Embedded Systems

contextEScontext 3 90

16011Execution Architecture

(with Ton Kostelijk)

EXARCH

ASP

Multi-Objective System

Architecting and Design

System Modeling and

Analysis

MOSAD

MA611

3

2 16

36



GPcourseStatus

Gaudí Systems Architecting

http://www.gaudisite.nl/index.html



http://www.gaudisite.nl/index.html

Documents

From Industrial Experience to System Architecting Know-howgaudisite.nl/FromIndustryToKnowHowSlides.pdf · Make the Systems Architecting art more accessible Enable the education of