Abstract
The last 15 years have seen a tremendous rise in the prominence of a software engineering subdiscipline known as software architecture. Technical Architect and Chief Architect are job titles that now abound in the software industry. There’s an International Association of Software Architects, and even a certain well-known wealthiest geek on earth used to have “architect” in his job title in his prime. It can’t be a bad gig, then?
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
- 2.
- 3.
Component here and in the remainder of this book is used very loosely to mean a recognizable “chunk” of software, and not in the sense of the more strict definition in Szyperski C. (1998) Component Software: Beyond Object-Oriented Programming, Addison-Wesley
- 4.
Patterns and styles are essentially the same thing, but as a leading software architecture author told me recently, “the patterns people won”. This book will therefore use patterns instead of styles!
- 5.
P.Krutchen, Architectural Blueprints–The “4+1” View Model of Software Architecture, IEEE Software, 12(6) Nov. 1995.
- 6.
- 7.
- 8.
- 9.
- 10.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2011 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Gorton, I. (2011). Understanding Software Architecture. In: Essential Software Architecture. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-19176-3_1
Download citation
DOI: https://doi.org/10.1007/978-3-642-19176-3_1
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-19175-6
Online ISBN: 978-3-642-19176-3
eBook Packages: Computer ScienceComputer Science (R0)