1. WG3 (Software) Architecture Competency in relation to Practice

2. 2 Grounded Theory

3. 3 Individual Compentencies Doing ”political” interactions Make technical decisions –Making constraints clear –Based on tradeoffs Listen to different types of stakeholders Educate himself/herself Communicate decisions and reasoning behind them Enforce decisions Come up with options ”Sell” architecture Mange personal relationship –Build up trust Have a track record Value-orientation –In contrast to product/manufacturing-orientation Groom replacement –Grey-beard vs no-beard architects

4. 4 Organizational Competencies Who makes (architectural) decisions? Who has the authority? Is the decision follows? Does it have an effect? How do you ensure architectural conformance? –Towards development –Towards management How does business and architect interact? #Fights? –Are disagreements resolved How does someone become an architect? –From the view of a person? –From the view of the organization? Are there succeccesion plans for architects?

5. 5 Concern-based Competencies Concern”Theory””Practice” AnalysisQuality attributes (e.g., ISO 9126) Quality attribute scenarios QAW End-to-end processes with volume etc as given Business qualities Informal ”methods” QAW for high risk DesignViews ABA... UML + data model + BPEL Informal ”methods” Gut feeling EvaluationATAM SAAM Experience Informal ”methods” Formal reviews (UP) Gut feeling ATAM for high risk ImplementationConformance Reconstruction Informal ”methods” Hand-over