Decomposing the Architect; What are Critical Success Factors?

Transcription

1 Decomposing the Architect; What are Critical Success Factors? by Gerrit Muller HSN-NISE Abstract System architects are scarce. If we want to search or educate potential system architects, then it is useful to know factors that determine the success of system architects. In this presentation we look at 4 areas: nature, education, environment and experience. We will make these areas more specific by quantification and illustration. Environment variation feedback stimulating Distribution 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: draft Experience patterns skills Nature Education

2 Decomposing Contributing Factors Environment variation feedback stimulating Experience patterns skills Education Nature 2 Gerrit Muller DTAdecomposition

3 Structure of this Presentation 5. Environment 6. Conclusion 4. Experience 1. Architect 2. Education 3. Nature 3 Gerrit Muller DTAdecompositionContent

4 5. Environment 6. Conclusion 4. Experience 1. Architect 2. Education 3. Nature 4 Gerrit Muller DTAlogoArchitect

5 Observed Typical Growth of System Architects root technical knowledge generalist technical knowledge business, application insight process insight psychosocial skills 5 Gerrit Muller MATsystemArchitectGrowth

6 From Specialist to Generalist breadth of knowledge depth of knowledge specialist all-round specialist aspect architect systems architect root knowledge 6 Gerrit Muller MATfromSpecialistToSystemArchitect

7 Different Architecting Scopes solution context fitting architect technical sound context technology including individuals (human factors) including stakeholders including designers (process) technology only people scope architect system architect product line architect function product product line portfolio architect product scope portfolio 7 Gerrit Muller MSarchitectingScope

8 5. Environment 6. Conclusion 4. Experience 1. Architect 2. Education 3. Nature 8 Gerrit Muller DTAlogoEducation

9 Proposed Curriculum for System Architects 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 architecture school mathematics physics chemistry mechanical engineering computer science electronical engineering ESA SW ESA silicon ESA system ESA mechatronics System design methods Execution architecture reliability engineering QFD and more Architectural reasoning SARCH ESA stakeholders Thomas Gilb - EVO, requirements eng Bredemeyer - Role of the architect advanced SARCH legend conventional curriculums available external Bredemeyer SW architecture marketing, process and many more missing 9 Gerrit Muller FARcurriculumSA

10 Overview of CAFCR framework method outline method visualization framework Customer objectives Application Functional Conceptual Realization submethods + key drivers + value chain + business models + supplier map + stakeholders and concerns + context diagram + entity relationship models + dynamic models + use case + commercial, logistics decompositions + mapping technical functions and several more + construction decomposition + functional decomposition + information model and many more + budget + benchmarking + performance analysis + safety analysis and many more integration via qualities safety performance explore specific details market vision story analyse design a priori solution know-how use case analyse design detailed design reasoning U" U' diagnostic quality CoO image quality U throughput T purchase price IQ spec typical case BoM B profit margin standard workstation CPU budget S Moore's law memory budget common console render engine P' M processing P pixel library memory depth limit M' 10 Gerrit Muller AMOoverview

11 Connecting System Design to Detailed Design system requirements design decisions parts system 10 7 connections monodisciplinary multidisciplinary 10 8 number of details lines of code and growing every year Gerrit Muller RATWpyramid

12 Organizational Problem: Disconnect What does Customer need in Product and Why? Customer objectives Application Functional Conceptual Realisation gap system requirements design decisions How can the product be realized What are the critical decisions parts connections lines of code and growing every year Gerrit Muller RATWdisconnect

13 Architect: Connecting Problem and Technical Solution What does Customer need in Product and Why? How can the product be realized What are the critical decisions Customer objectives Application Functional Conceptual Realisation number of details system requirements design decisions parts connections lines of code and growing every year Gerrit Muller RATWbreadthAndDepth

14 Major Bottleneck: Mental Dynamic Range number of details stretch engineer stretch senior engineer system architect stretch Gerrit Muller RATWmentalDynamicRange

15 5. Environment 6. Conclusion 4. Experience 1. Architect 2. Education 3. Nature 15 Gerrit Muller DTAlogoNature

16 Profile of an Ideal System Architect communication teamwork documentation multitasking flexible, open authority by expertise specialist generalist conceptual pragmatic constructive critical fast absorption of knowledge creativity manual skills process insight political insight improvement completeness schedule monitor progress initial cost decision making customer value sales features commercial insight coaching selection appraisal motivation Gerrit Muller FPsystemArchitect

17 For Comparison: Profile of a Project Leader communication teamwork documentation multitasking flexible, open authority by expertise specialist generalist conceptual pragmatic constructive critical fast absorption of knowledge creativity manual skills process insight political insight improvement completeness schedule monitor progress initial cost decision making customer value sales features commercial insight coaching selection appraisal motivation Gerrit Muller FPoperationalLeader

18 Project Leader vs System Architect project leader system architect human resource man coaching selection appraisal motivation interpersonal skills 9,0 8,0 7,0 6,0 5,0 4,0 3,0 2,0 1,0 0,0 communication teamwork documentation multi-tasking flexible, open auth by expertise specialist generalist know-how commercial customer value sales feature commercial insight project man completeness schedule monitor progress initial cost decision making reasoning power conceptual pragmatic constructive critical absorption knhw creativity process process insight politics insight improvement 18 Gerrit Muller DTAspiderDiagram

19 Most Discriminating Characteristics Generalist Multi-tasking Authority by expertise Constructive critical Balance between conceptual and pragmatic 19 Gerrit Muller DTAdiscriminatingCharacteristics

20 5. Environment 6. Conclusion 4. Experience 1. Architect 2. Education 3. Nature 20 Gerrit Muller DTAlogoExperience

21 Example: Trapezoid Pattern grey level mapping Look up table invert contrast / brightness RF gradient field generation TE TR v y wafer stage movement output brightness input contrast Gz Gx Gy v x expose step expose t 21 Gerrit Muller DTAtrapezoidPatterns

22 From SW input to physical Effect (x 3, y 3 ) (x 4, y 4 ) (x 1, y 1 ) (x 2, y 2 ) breakpoints (x 1, y 1 ). (x n, y n ) computation discrete samples (1, v 1 ) (2, v 2 ). (t, v t ) conversion DAC analog signal V(t) actuation mechanical optical or physical effect [m/s] [mt/m] 22 Gerrit Muller DTAtrapezoidChain

23 Discretization effects input is discrete output is discrete potential problems: staircase effects not all values can be reached impact on frequency domain broken invariants (surface) potential benefits: optimized algoritms (fixed point) 23 Gerrit Muller DTAtrapezoidDiscretization

24 Example of Discretization Problem false f(x) contour 10 bits pixel value 8 bits pixel value x 24 Gerrit Muller MITORfalseContouring

25 Example of Generic Smoothing Consideration discontinuity in first derivative smooth smooth curves prevent artefacts (vibration, image, clipping) 25 Gerrit Muller DTAtrapezoidContinuity

26 Architects Collect a Rich Set of Patterns architects move from: product to product environment to environment architects experience: thousands of patterns design patterns in systems process patterns in environments human patterns in environments time legend environment system design pattern process pattern human pattern 26 Gerrit Muller DTAexperience

27 5. Environment 6. Conclusion 4. Experience 1. Architect 2. Education 3. Nature 27 Gerrit Muller DTAlogoEnvironment

28 Simplified Decomposition of the Business customer Customer Roadmap Business Drivers Policy and Planning Process Technology, Process, and People roadmaps Budgets Product roadmap Budget, plan Information Order Product $$ Support Product Needs and feedback presales Needs and Feedback Product Creation Process Needs and Feedback material sales logistics production service Customer-Oriented Process Technical Product Documentation People Technology Process Product-related processes People Technology Process $$ People, Process, and Technology Management Process 28 Gerrit Muller PDBprocessDecomposition

29 Line Organization Stovepipe finance & administration CEO human resource management goods flow research & engineering commercial manufacturing logistics purchasing mechanical engineering electrical engineering software engineering marketing sales customer support 29 Gerrit Muller DTAlineOrganization

30 Business Organization Stovepipe business unit 1 product/market oriented project 1 project 2 business unit 2 product/market oriented project 3 project 4 30 Gerrit Muller DTAbusinessOrganization

31 Different Concerns dominating stovepipe or complementary cultures? introvert competence, skill oriented synergy, re-use driven long term project 1 project 2 extrovert customer oriented result driven short term manufacturing logistics purchasing mechanical engineering electrical engineering software engineering marketing sales customer support project 3 project 4 31 Gerrit Muller DTAmatrixOrganization

32 Positioning System Architecting customer Customer Roadmap Business Drivers Policy and Planning Process Technology, Process and People roadmaps Budgets Product roadmap Context, Vision Budget, plan Product Needs and feedback Reality check material Information presales Systems Architecting Process Needs and Feedback Product Creation Process sales logistics production service Customer-Oriented Process Technical Product Documentation People Technology Process Order Stakeholder interaction Product Product related processes $$ Support People Technology Process $$ People, Process, and Technology Management Process 32 Gerrit Muller SAPprocessSimplified

33 What Can We Do to Improve the Environment? systems engineering as discipline job rotation stimulate architect exposure stretch all engineers cultivate customer & market oriented culture share and invest in future exploration and vision 33 Gerrit Muller DTAenvironmentFactors

34 5. Environment 6. Conclusion 4. Experience 1. Architect 2. Education 3. Nature 34 Gerrit Muller DTAlogoConclusion

35 Conclusion Environment : stimulate job rotation expose engineers recognize multi-disciplinary Customer objectives Application Functional Conceptual Realisation Experience : >1000 design patterns and process patterns Education : How to educate, stimulate depth and breadth? Nature : Foster engineers with architect potential 35 Gerrit Muller DTAconclusion