role and task of the system architect · 2020. 9. 6. · 102 104 107 infinite quantiy p e ry a...
TRANSCRIPT
Role and Task of the System Architectby Gerrit Muller University of South-Eastern Norway-NISE
e-mail: [email protected]
Abstract
The role and the task of the system architect are described in this module.
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: preliminarydraftversion: 1.0
The Role and Task of the System Architectby Gerrit Muller Buskerud University Collge
e-mail: [email protected]
Abstract
The role of the system architect is described from three viewpoints: deliverables,responsibilities and activities. This description shows the inherent tension in thisrole: a small set of hard deliverables, covering a fuzzy set of responsibilities,hiding an enormous amount of barely visible day-to-day work.
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: conceptversion: 2.0
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
Deliverables of the System Architect
Spec DesignReport
Re
po
rt
ReportDesign
Design
SpecSpec
The Role and Task of the System Architect3 Gerrit Muller
version: 2.0September 6, 2020
RSAdeliverables
List of Deliverables
Customer and Life-Cycle Needs (what is needed)
System Specification (what will be realized)
Design Specification (how the system will be realized)
Verification Specification (how the system will be verified)
Verification Report (the result of the verification)
Feasibility Report (the results of a feasibility study)
Roadmap
The Role and Task of the System Architect4 Gerrit Muller
version: 2.0September 6, 2020
RSAdeliverablesSpecific
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
The Role and Task of the System Architect5 Gerrit Muller
version: 2.0September 6, 2020RSAresponsibilities
Examples of Secondary Responsibilities
responsibility
business plan, profit
schedule, resources
market, saleability
technology
process, people
detailed designs
primary owner
business manager
project leader
marketing manager
technology manager
line manager
engineers
The Role and Task of the System Architect6 Gerrit Muller
version: 2.0September 6, 2020
RSAsecondaryResponsibilities
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
The Role and Task of the System Architect7 Gerrit Muller
version: 2.0September 6, 2020
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
The Role and Task of the System Architect8 Gerrit Muller
version: 2.0September 6, 2020RSAdetailHierarchy
Reality or Virtuality?
Abstractions only exist for concrete facts.
The Role and Task of the System Architect9 Gerrit Muller
version: 2.0September 6, 2020
Visible Output versus Invisible Work
V4aa
IOIdea
Bla Bla
Design
Sp
ec
Report
system
subsystem
module
Requirement
Spec
Design
Realization
modules
Fun
ctio
nQuality
KISS
Activities
Responsibilities
DeliverablesDec
reas
ing
Vis
ibili
ty
Spec DesignReport
Re
po
rt
Report
Design
Design
Spec
Spec
From Manager perspective
The Role and Task of the System Architect10 Gerrit Muller
version: 2.0September 6, 2020
RSApyramid
The Awakening of a System Architectby Gerrit Muller University of South-Eastern Norway-NISE
e-mail: [email protected]
Abstract
The typical phases of a system architect development are described, beginningat the fundamental technology knowledge, with a later broadening in technologyand in business aspects. Finally the subtlety of individual human beings is takeninto account.
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: conceptversion: 1.1
root
technical
knowledge
generalist
technical
knowledge
business,
application insight
process insight
psychosocial
skills
Typical Growth of a System Architect
root
technical
knowledge
generalist
technical
knowledge
business,
application insight
process insight
psychosocial
skills
The Awakening of a System Architect12 Gerrit Muller
version: 1.1September 6, 2020
MATsystemArchitectGrowth
Generalist versus Specialist
sp
ecia
list
generalist
root
knowledge
breadth ofknowledge
dep
th o
fkn
ow
led
ge
The Awakening of a System Architect13 Gerrit Muller
version: 1.1September 6, 2020
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
The Awakening of a System Architect14 Gerrit Muller
version: 1.1September 6, 2020
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
The Awakening of a System Architect15 Gerrit Muller
version: 1.1September 6, 2020
MATfromSpecialistToSystemArchitect
Architecting Interaction Stylesby Gerrit Muller University of South-Eastern Norway-NISE
e-mail: [email protected]
Abstract
A system architects needs skills to apply different interactions styles, dependingon the circumstances. This document discusses the following interaction styles:provocation, facilitation, leading, empathic, interviewing, white board simulation,and judo tactics.
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.2
provocation
facilitation
leading
empathic
interviewing
whiteboard simulation
judo tactics
when in an impasse: provoke
effective when used sparsely
especially recommended when new in a field:
contribute to the team, while absorbing new knowledge
provide vision and direction, make choices
risk: followers stop to give the needed feedback
take the viewpoint of the stakeholder
acknowledge the stakeholder's feelings, needs, concerns
investigate by asking questions
invite a few engineers and walk through
the system operation step by step
first listen to the stakeholder and then
explain cost and alternative opportunities
Architecting Styles
provocation
facilitation
leading
empathic
interviewing
whiteboard simulation
judo tactics
when in an impasse: provoke
effective when used sparsely
especially recommended when new in a field:
contribute to the team, while absorbing new knowledge
provide vision and direction, make choices
risk: followers stop to give the needed feedback
take the viewpoint of the stakeholder
acknowledge the stakeholder's feelings, needs, concerns
investigate by asking questions
invite a few engineers and walk through
the system operation step by step
first listen to the stakeholder and then
explain cost and alternative opportunities
Architecting Interaction Styles17 Gerrit Muller
version: 0.2September 6, 2020
ASstyles
Exercise Role and Task of the System Architect
Role play with 3 roles and optional observer:• 1 operational leader (project leader)• 1 system architect• 1 marketing manager• 1 observer (optional)
Discuss the definition (business relevance, specification, and planning) of a travele-mail mate.Present (max. 2 flips) the result and the process (the relation and interaction ofthe three roles).
Exercise Role and Task System Architect18 Gerrit Muller
version: 0.2September 6, 2020
MRSAexercise
Role and Task of a System Architect
Deliverables
Spec DesignReport
Re
po
rt
ReportDesign
Design
SpecSpec
Responsibilities
system
subsystem
Balance Consistency
module
Overview
RequirementSpec
DesignRealization
Decomposition
Integration
modules
FunctionQ
uality
KISS
Elegance
Simple Integrity Fitting
satisfied
stakeholderssystem
context
Daily ActivitiesV4aa
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
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
Exercise Role and Task System Architect19 Gerrit Muller
version: 0.2September 6, 2020
Personal characteristics of a System Architect
Typical growth of a Architectroot
technical
knowledge
generalist
technical
knowledge
business,
application insight
process insight
psychosocial
skills
Generalist vs Specialist
sp
ecia
list
generalist
root
knowledge
breadth ofknowledge
dep
th o
fkn
ow
led
ge
Complementary Roles
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
Role Spectrum
all-
rou
nd
sp
ecia
list systems architect
sp
ecia
list
root
knowledge
aspect
architect
breadth ofknowledge
dep
th o
fkn
ow
led
ge
Exercise Role and Task System Architect20 Gerrit Muller
version: 0.2September 6, 2020