Agile architecture methodology: long term strategy interleaved with short term tactics

  • Authors:
  • Ethan Hadar;Gabriel M. Silberman

  • Affiliations:
  • CA Inc., Yokneam, Israel;CA Inc., NY City, NY, USA

  • Venue:
  • Companion to the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applications
  • Year:
  • 2008

Quantified Score

Hi-index 0.00

Visualization

Abstract

Tactical agile development and strategic architectural evolution are viewed as opposite ends of the development spectrum, with the long-term value of applying an architecture-centric approach seemingly at odds with rapid development, featuring its informal documentation activities. The value of a long-term vision, or ar-chitecture, is particularly high in the context of product integra-tion and research. However, there is also benefit in rapid and early feedback on incremental deliverables, as featured in agile development. To extract the main benefits of both worlds we introduce the CA Agile Architecture (C3A) method, targeted for the architec-ture and design phases of the development life cycle. Its founda-tion is the Reference and Implementation Architecture, which features a lean one-page per component contract, as well as sev-eral abstraction levels. The C3A artifacts are governed by a cyclic process of architectural evaluation and evolution, with accompa-nying coaching and training activities. This work-in-progress is being prototyped with three product teams, varying in team size, product maturity and complexity, and geographical location. C3A features a common tactical-focused agenda for the functional and system architectures, with mini-mally overlapping strategic views.