Design - Who needs an architect?

@article{Fowler2003DesignW,
  title={Design - Who needs an architect?},
  author={Martin Fowler},
  journal={IEEE Software},
  year={2003},
  volume={20},
  pages={11-13}
}
  • M. Fowler
  • Published 1 September 2003
  • Computer Science
  • IEEE Software
W andering down our corridor a while ago, I saw my colleague Dave Rice in a particularly grumpy mood. My brief question caused a violent statement: " We shouldn't interview anyone who has 'architect' on his resume. " At first blush, this was an odd turn of phrase, because we usually introduce Dave as one of our leading architects. The reason for his title schizo-phrenia is the fact that, even by our industry's standards, " architect " and " architecture " are terribly overloaded words. For many… 
Software architecture and agile software development: a clash of two cultures?
  • Philippe B Kruchten
  • Computer Science
    2010 ACM/IEEE 32nd International Conference on Software Engineering
  • 2010
TLDR
In this tutorial, heuristics to scope how much architecture a project really needs are defined, to assign actual value to an otherwise invisible architecture; and management and development practices that do work in the circumstances where some significant architectural effort is needed, when you are actually going to need it are reviewed.
Roles and Impacts of Hands-on Software Architects in Five Industrial Case Studies
TLDR
Examination of five large-scale software systems shows that implementing architectural tactics is more complex than delivering functionality, tactics are more error prone than software functionalities, and the architects tend to introduce fewer bugs into the implementation of architectural tactics compared to the developers.
Renovating Requirements Engineering: First Thoughts to Shape Requirements Engineering as a Profession
TLDR
What Requirements Engineers could possibly learn from other similar roles to become crucial for the evolution of legacy systems is discussed and overlaps along four dimensions: liability, self-portrayal, core activities, and artifacts are discussed.
Software Architects in Large-Scale Distributed Projects: An Ericsson Case Study
TLDR
Investigation of how architects at Ericsson were organized, their roles and responsibilities, and the effort they spent guarding and governing a large-scale legacy product developed by teams at multiple locations suggests that the effort architects spend designing architecture, guarding its integrity and evolvability, and mentoring development teams is directly related to team maturity.
A Multiple Case Study on the Architect's Role in Scrum
TLDR
The findings support those who take on architecture-related tasks in preparing for Scrum-like projects and find that how architects interact with other roles in Scrum heavily depends on the Product Owner role.
What do software architects really do?
Explici t Assumption s Enri ch Architectura l Models
TLDR
This work shows how one can explicitly model assumptions in an existing product family and derive a metamodel to document assumptions.
inCode.Rules: An agile approach for defining and checking architectural constraints
  • Radu Marinescu, George Ganea
  • Computer Science
    Proceedings of the 2010 IEEE 6th International Conference on Intelligent Computer Communication and Processing
  • 2010
TLDR
In this paper, the paper shows how architectural rules can be automatically checked using the inCode.Rules interpreter; and how they can be easily edited using the full-fledged editor that was created.
Agility and Architecture: Can They Coexist?
TLDR
This article talks about software architecture being relevant to the basis of aspects such as communication among team members, inputs to subsequent design decisions, documenting design assumptions, and evaluating design alternatives.
...
1
2
3
4
5
...