The Role and Task of the System Architect

Transcription

1 by Gerrit Muller Buskerud University Collge Abstract The role of the system architect is described from three viewpoints: deliverables, responsibilities and activities. This description shows the inherent tension in this role: a small set of hard deliverables, covering a fuzzy set of responsibilities, hiding an enormous amount of barely visible day-to-day work. Blah Blah V4aa Idea IO Distribution think, analyze listen, talk, walk around design, assist project leader present, brainstorm, with work breakdown, meet, teach, explain schedule, risks discuss This article or presentation is written as part of the Gaudí project. The Gaudí project philosophy is to improve by obtaining frequent feedback. Frequent feedback is pursued by an open creation process. This document is published as intermediate or nearly mature version to get feedback. Further distribution is allowed as long as the document remains complete and unchanged. status: concept test, integrate write, consolidate, browse read, review travel to customer, supplier, conference provide vision and leadership

2 Deliverables of the System Architect 2 Gerrit Muller RSAdeliverables

3 List of Deliverables Customer and Life-Cycle Needs (what is needed) System ification (what will be realized) ification (how the system will be realized) Verification ification (how the system will be verified) Verification (the result of the verification) Feasibility (the results of a feasibility study) Roadmap 3 Gerrit Muller RSAdeliverablesific

4 Responsibilities of the System Architect Balance Requirement Realization module Consistency subsystem system Quality Decomposition Integration Function modules Overview KISS system satisfied stakeholders Elegance Simple Integrity Fitting context 4 Gerrit Muller RSAresponsibilities

5 Examples of Secondary Responsibilities responsibility primary owner business plan, profit schedule, resources market, saleability technology process, people detailed designs business manager project leader marketing manager technology manager line manager engineers 5 Gerrit Muller RSAsecondaryResponsibilities

6 What does the System Architect do? Blah Blah V4aa Idea IO think, analyze listen, talk, walk around design, brainstorm, explain assist project leader with work breakdown, schedule, risks present, meet, teach, discuss test, integrate write, consolidate, browse read, review travel to customer, supplier, conference provide vision and leadership 6 Gerrit Muller RSAactivities

7 From Detail to Overview consolidation in deliverables meetings informal contacts sampling scanning driving views shared issues touched details seen details product details real-world facts Quantity per year (order-ofmagnitude) infinite architect time per item h 1 h 10 min 1 sec 7 Gerrit Muller RSAdetailHierarchy

8 Reality or Virtuality? Abstractions only exist for concrete facts. 8 Gerrit Muller

9 Visible Output versus Invisible Work From Manager perspective Decreasing Visibility Deliverables Requirement Realization module subsystem Quality Function modules KISS Responsibilities system Idea Bla Bla V4aa IO Activities 9 Gerrit Muller RSApyramid