Role of Systems Architecting in Innovation · Role of Systems Architecting in Innovation 24 Gerrit Muller version: 0 September 9, 2018MITORthread50. Key Success Factor 3: Architect

Role of Systems Architecting in Innovationby Gerrit Muller University of South-Eastern Norway-NISE

e-mail: [email protected]

Abstract

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 9, 2018status: preliminarydraftversion: 0

logo TBD

The Embedded Systems Domain

chip

television

printer

waferstepper

cardio X-ray system MRI scanner GSM

Role of Systems Architecting in Innovation2 Gerrit Muller

version: 0September 9, 2018

RIIembeddedDomain

Successful Innovation = Technological + Market

technological innovations

circuits materials functions user interface

system

needs services

applications market innovations segments



RIItechnologicalAndMarket

System Architect links technology and market



system

needs services


marketeers

systems architect

inventors

engineers



RIIcontributors

Example: Easyvision serving three URF examination rooms

EasyVision: Medical Imaging WorkstationURF-systems

typical clinical

image (intestines)



MSeasyVision

X-ray rooms from examination to reading around 1990

ExaminationRoom

ControlRoom

Corridoror closet

ExaminationRoom

ControlRoom

ReadingRoom



XRayRoomsOld

Product Innovation: Easyvision applied as printserver

ExaminationRoom

ControlRoom

ReadingRoom

Corridoror closet

ExaminationRoom

ControlRoom

printer

light box

detector

X ray

source console



XRayRoomsPlusPrintServer

Market innovation: optimized film

old: screen copy

20 to 50% less film needed

new: SW formatting



MedicalImagingFilmComparison

Technology innovation challenges

product policy:

standard HW

SW "only"

40 MHz CPU

64 MByte memory

10 MBit/s ethernet

1 GByte disk

image quality image processing

print

throughput

view

response time

ca 1 film / minute

film = 4k*5k pixels

subsecond retrieve

screen = 1k*1k

tension



IMIchallenge

Typical Growth of a System Architect

root

technical

knowledge

generalist

technical

knowledge

business,

application insight

process insight

psychosocial

skills



MATsystemArchitectGrowth

Generalist versus Specialist

sp

ecia

list

generalist

root

knowledge

breadth ofknowledge

dep

th o

fkn

ow

led

ge



MATgeneralistVsSpecialist

Generalists and Specialists are Complementary

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

Spectrum from Specialist to System Architect

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

More innovations in Medical Imaging

1992 1993 1994 1995 1996

RF 1.1 URF basis

autoprint

RF 1.2 vascular

import

RF 2.1 cardio bolus chase

RF 2.2 Dicom

X 3.1 spine

Rad 2.1 basis

View, Print Store ,Communicate

Rad 1.1 PCR

Print

CT/MR 1.1 stack MPR dental

CT/MR 1.2 MR

import

CT/MR 2.1 volume angio



RIIexampleMI

Key success factor 1: innovation by all parties



system

needs services


marketeers

system architect

inventors

engineers



RIIcontributorsMI

The ”CAFCR” model

Customer

What

Customer

How

Product

What

Product

How

What does Customer need

in Product and Why?

drives, justifies, needs

enables, supports

Customer

objectives

Application Functional Conceptual Realization



CAFCRannotated

Integrating CAFCR

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

CAFCR can be applied recursively

System

(producer)

Customer

BusinessDrives

Enables

Customer's

Customer

BusinessDrives

Enables

ConsumerDrives

Enables

Value Chain

larger scope has smaller

influence on architecture



CAFCRrecursion

CAFCR applied on Security

ApplicationCustomer

objectives

Functional Conceptual Realization

sensitive

information

trusted

not trusted

selection

classificationpeople

information

authenticationbadges

passwords

locks / walls

guards

administrators

social contacts

open passwords

blackmail

burglary

fraud

unworkable procedures

cryptography

firewall

security zones

authentication

registry

logging

holes between

concepts

functions foradministration

authentication

intrusion detection

logging

quantification

bugsbuffer overflow

non encrypted

storage

poor exception

handling

missing

functionality

wrong

quantification

specific

algorithms

interfaces

libraries

servers

storage

protocols

desired characteristics, specifications & mechanisms

threats



QNsecurityExample

Deliverables of the System Architect

Spec DesignReport

Re

po

rt

ReportDesign

Design

SpecSpec



RSAdeliverables

Responsibilities of the System Architect

system

subsystem

Balance Consistency

module

Overview

RequirementSpec

DesignRealization

Decomposition

Integration

modules

FunctionQ

uality

KISS

Elegance

Simple Integrity Fitting

satisfied

stakeholderssystem

context


version: 0September 9, 2018RSAresponsibilities

What does the System Architect do?

V4aa

IO

design,

brainstorm,

explain

Idea

think,

analyze

listen, talk,

walk around

Blah Blah

write,

consolidate,

browse

present,

meet, teach,

discuss

read,

review

Design

Sp

ec

Report

test,

integrate

assist project leader

with work breakdown,

schedule, risks

travel to

customer,

supplier,

conference

provide

vision and

leadership



RSAactivities

From Detail to Overview

driving views

shared issues

touched details

seen details

real-world facts

10

102

104

107

infinite

Quantityper year

(order-of-

magnitude)

architect

time per

item

100 h

1 h

10 min

meetings

consolidation

in

deliverables

informal

contacts

product details

sampling

scanning

0.1105

0.5

1 sec106

1010


version: 0September 9, 2018RSAdetailHierarchy

Key Success Factor 2: highly iterative

Philips operational view(manufacturing, service, sales)

Conceptual

efficient

useable

RealizationCustomer

objectives

Application Functional

diagnosis

time efficientthroughput processing

library

cost revisited in context of clinical needs and

realization constraints; note: original threads are significantly simplified

diagnostic

quality

image

quality IQ spec

pixel

depth

CPU

budgettypical

case

common

console

memory

limit

BoMMoore's

law

purchase

priceCoO

economic

sound

render

engine

effective

operational

constraints

M'

S

M

B

U"

P'

T

U

U' P

profit margin

standard workstation

C

memory budget



MITORthread50

Key Success Factor 3: Architect as Integrator

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

Innovation Challenges in Embedded Systems

creativity market dynamics

discover latent needs enable emergence

where is the business

globalization hype waves Moore's law

power consumption weight, cost, performance

reliability complexity heterogeneity

#engineers involved

interoperability emerging behavior, future vs legacy

heterogeneous vendors

security privacy, DRM versus usability



DYOFchallenges

Role of Systems Architecting in Innovation · Role of Systems Architecting in Innovation 24 Gerrit Muller version: 0 September 9, 2018MITORthread50. Key Success Factor 3: Architect

Documents