Jun 5, 2020
The concept of software architecture as a distinct discipline in
software engineering started to emerge in 1990 — although the idea
had been around for much longer. Throughout my career in industry,
then in academia, I’ve witnessed the growth of software
architecture, its evolution in leaps and bounds. I’ve also had the
privilege to meet and work with many of the key contributors who
over 30 years have shaped it to what we know today: a mature
discipline. It has its theories, its standards, its processes and
tools, its place in schools’ curricula. Industry and academia,
although often on different tracks —and often ignoring each other—
have been making every year more incremental progress and even
branching out subdisciplines or different schools of thoughts. But
the obvious question is: are we done? what’s next? Plateau,
obsolescence, retirement? Not quite. New problems arose, driven by
new technologies, and some old problems were not really fully
solved, or their context significantly evolved. In this brief talk,
I’ll reflect on these 30 years, and pulling out my crystal ball,
I’ll speculate potential developments ahead, from 4+1 different
viewpoints.