Appendix to June 2, 2020 talk on Software architecture
June 2, 2020
On June 2, 2020, I was invited by the SEI to make a presentation. Slides are posted here.
A recording of the talk is here, but be aware of a possible gap around minute 34; just go “fast forward”.
You will find here pointers to various papers and books I referred to in the talk.
For my own papers on Software architecture, see this other tab here.
References I made in the talk:
- Butler W. Lampson. 1983. Hints for computer system design. SIGOPS Oper. Syst. Rev. 17, 5 (October 1983), 33–48. DOI: 10.1145/773379.806614
- John A. Mills. 1985. A pragmatic view of the system architect. Commun. ACM 28, 7 (July 1985), 708–717. DOI: 10.1145/3894.3897
- Dewayne E. Perry and Alexander L. Wolf. 1992. Foundations for the study of software architecture. SIGSOFT Softw. Eng. Notes 17, 4 (Oct. 1992), 40–52. DOI: 10.1145/141874.141884
- Mary Shaw and David Garlan. Software architecture: perspectives on an emerging discipline. Prentice-Hall, Inc., USA. (1996.)
- Mary Shaw and Paul C. Clements. 1997. A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems. In Proc. of COMPSAC ’97. IEEE Computer Society, USA, 6–13.
- M. Fowler, “Design – Who needs an architect?,” in IEEE Software, vol. 20, no. 5, pp. 11-13, Sept.-Oct. 2003, doi: 10.1109/MS.2003.1231144.
- Simon Brown: Are you a software architect, InfoQ Feb. 2010 https://www.infoq.com/articles/brown-are-you-a-software-architect/
- Simon Brown, The C4 model for visualising software architecture, https://c4model.com
- S. Redwine and W. Riddle, “Software Technology Maturation,” Proc. 8th Int’l Conf. Software Eng., IEEE CS Press, 1985, pp. 189–200.
- David Garlan. 2000. Software architecture: a roadmap. In Proceedings of the Conference on The Future of Software Engineering (ICSE ’00). ACM, New York, NY, USA, 91–101. DOI: 10.1145/336512.336537
- M. Shaw, “The coming-of-age of software architecture research,” in Proc. IEEE/ACM ICSE ’01, Toronto, Canada, 2001 pp. 657-664a. doi: 10.1109/ICSE.2001.919147
- M. Shaw and P. Clements, “The golden age of software architecture” in IEEE Software, vol. 23, no. 02, pp. 31-39, 2006. doi: 10.1109/MS.2006.58
- P. Kruchten, H. Obbink, J. Stafford, “The Past, Present, and Future for Software Architecture” in IEEE Software, vol. 23, no. 2, pp. 22-30, 2006. DOI : 10.1109/MS.2006.59
- P. Clements and M. Shaw, “The Golden Age of Software Architecture” Revisited. in IEEE Software, vol. 26, no. 04, pp. 70-72, 2009. doi: 10.1109/MS.2009.83
- David Garlan and Mary Shaw. Software architecture: reflections on an evolving discipline. In Proc. Of ESEC/FSE ’11. ACM, New York, 2011. DOI: 10.1145/2025113.2025116
- SEI (2017) What is your definition of software architecture, https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=513807
- SAFE & agile architecture: https://www.scaledagileframework.com/agile-architecture/
- LESS & architectural design: https://less.works/less/technical-excellence/architecture-design.html
Useful books on Software architecture:
- L. Bass, P. Clements, R. Kazman, Software Architecture in Practice (3rd Ed.), Addison-Wesley (2012)
- Ian Gorton, Essential software architecture (2nd ed), Springer (2011)
- Simon Brown, Software architecture for developers (vol 1 & 2), LeanPub (2018) https://leanpub.com/software-architecture-for-developers
- N. Rozanski and E. Woods, Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives (2nd ed) Addison Wesley (2011)
- George Fairbanks, Just Enough Software Architecture: A Risk-Driven Approach , Marshall & Brainerd (2010)
- F. Buschmann, M. Stal & al., Pattern-Oriented Software Architecture (vol 1 & 2), Wiley (1996, 2000)
- M. Maier & E. Rechtin, The Art of Systems Architecting, 3rd ed, CRC Press (2009)
- G. Hohpe, 37 Things One Architect Knows About IT Transformation: A Chief Architect’s Journey, LeanPub (2016).
- M. Richards & N. Ford, Fundamentals of Software Architecture, OReilly (2020). (Just arrived on my shelf!)
One Comment
leave one →
it was nice to hear your thought leading opinion. shame on the connection that broke ur audio for some minutes, but always valuable to hear from you, mr. Kruchten.