Controversy Corner: What do software architects really do?

Authors:
Philippe Kruchten
Affiliations:
Electrical and Computer Engineering, University of British Columbia, 2332 Main Mall, Vancouver, BC, Canada V6T 1Z4
Venue:
Journal of Systems and Software
Year:
2008

Citing 4
Cited 5

AntiPatterns: refactoring software, architectures, and projects in crisis

AntiPatterns: refactoring software, architectures, and projects in crisis
AntiPatterns in software architecture

ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Organizational Patterns of Agile Software Development

Organizational Patterns of Agile Software Development
Enterprise unified process, the: extending the rational unified process

Enterprise unified process, the: extending the rational unified process

Software architecture awareness in long-term software product evolution

Journal of Systems and Software
Naive architecting - understanding the reasoning process of students: a descriptive survey

ECSA'10 Proceedings of the 4th European conference on Software architecture
The lonesome architect

Journal of Systems and Software
On the responsibilities of software architects and software engineers in an agile environment: who should do what?

Proceedings of the 4th international workshop on Social software engineering
3D architecture viewpoints on service automation

Journal of Systems and Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

To be successful, a software architect-or a software architecture team, collectively-must strike a delicate balance between an external focus-both outwards: Listening to customers, users, watching technology, developing a long-term vision, and inwards: driving the development teams-and an internal, reflective focus: spending time to make the right design choices, validating them, and documenting them. Teams that stray too far away from this metastable equilibrium fall into some traps that we describe as antipatterns of software architecture teams.