Read on Twitter
“Systems Architecting: Creating & Building Complex Systems” by Eb Rechtin was *the* pioneering work that fomented our field https://www.amazon.com/Systems-Architecting-Creating-Building-Complex/dp/0138803455
Another field-founding classic (1996 — our field is *young*): Software Architecture: Perspectives on an Emerging Discipline
https://www.amazon.com/gp/aw/d/0131829572/ref=dbs_a_w_dp_0131829572
https://www.amazon.com/gp/aw/d/0131829572/ref=dbs_a_w_dp_0131829572
25 years old!!
An Introduction to Software Architecture,
by David Garlan and Mary Shaw,
January 1994
https://www.cs.cmu.edu/afs/cs/project/able/ftp/intro_softarch/intro_softarch.pdf
An Introduction to Software Architecture,
by David Garlan and Mary Shaw,
January 1994
https://www.cs.cmu.edu/afs/cs/project/able/ftp/intro_softarch/intro_softarch.pdf
Those are important waymarks in our field, though the work had, of course begun
From “What do software architects do?” By Philippe Kruchten ( @pbpk)
(That was ‘92) So 25 years, depending how you count... https://twitter.com/muccinihenry/status/1010185313417867268
More when we consider the pioneering work of Dijkstra and of Parnas. But to tie this back to the head of this thread, Rechtin brought a (sociotechnical) systems view, including leadership and “organizational politics”
Given that (social, technical and systems), what we do has roots in, and is informed by, many fields. We take the work of, say, William James or Jane Jacobs, to be a root alongside that of William (Bill) Kent, Eric Steven Raymond, and Edsger Dijkstra... etc.
Not that we need to dig into all our roots! But it is important to know that as much as it is technical, it’s not *just* technical...
Still, some roots are still — 50 years later — required reading! https://twitter.com/ruthmalan/status/1068663808305041408
And Christiane Floyd — roots so good! https://twitter.com/ruthmalan/status/1144622714457657345
