Editing Software architecture (section)

== Further reading ==
*{{Cite book|last=Richards|first=Mark|title=Fundamentals of Software Architecture: An Engineering Approach|publisher=[[O'Reilly Media]]|year=2020|isbn=9781492043454}}
*{{Cite book|last=Len|first=Bass|title=Software Architecture in Practice|publisher=[[Addison-Wesley Professional]]|year=2012|isbn=9780321815736|edition=3rd}} - This book covers the fundamental concepts of the discipline. The theme is centered on achieving quality attributes of a system.
*{{Cite book|last=Clements|first=Paul|title=Documenting Software Architectures: Views and Beyond|publisher=[[Addison-Wesley Professional]]|year=2010|isbn=9780321552686|edition=2nd}} - This book describes what software architecture is and shows how to document it in multiple views, using UML and other notations. It also explains how to complement the architecture views with behavior, software interface, and rationale documentation. Accompanying the book is a [https://wiki.sei.cmu.edu/sad/index.php/The_Adventure_Builder_SAD wiki that contains an example of software architecture documentation].
*{{Cite book| last = Bell | first = Michael | editor1-first = Michael | editor1-last = Bell | year = 2008 | title = Service-Oriented Modeling: Service Analysis, Design, and Architecture | publisher = Wiley|isbn=9780470255704|doi=10.1002/9781119198864}}
*{{Cite book |first1=Tony |last1=Shan |first2=Winnie |last2=Hua  |title=2006 10th IEEE International Enterprise Distributed Object Computing Conference (EDOC'06) |chapter=Solution Architecting Mechanism |date=October 2006 |pages=23–32|doi=10.1109/EDOC.2006.54 |isbn=978-0-7695-2558-7 |s2cid=8361936 }}
*{{cite journal |first1=Javier |last1=Garzás |first2=Mario |last2=Piattini |title=An ontology for micro-architectural design knowledge |journal=[[IEEE Software]] |volume=22 |issue=2 |year=2005 |pages=28–33 |doi=10.1109/MS.2005.26|s2cid=17639072 }}
*{{Cite journal|last=Fowler|first=Martin|date=September 2003|title=Who Needs an Architect?|url=http://martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf|journal=[[IEEE Software]]|volume=20|issue=5|doi=10.1109/MS.2003.1231144|s2cid=356506}}
*{{Cite journal|last=Kazman|first=Rick|date=May 2003|title=Architecture, Design, Implementation|url=https://resources.sei.cmu.edu/asset_files/WhitePaper/2003_019_001_29559.pdf |archive-url=https://web.archive.org/web/20150921170650/http://resources.sei.cmu.edu/asset_files/WhitePaper/2003_019_001_29559.pdf |archive-date=2015-09-21 |url-status=live|journal=Software Engineering Institute}} - On the distinction between architectural design and detailed design.
*{{cite journal |last=Kruchten |first=Philippe |year=1995 |url=http://www3.software.ibm.com/ibmdl/pub/software/rational/web/whitepapers/2003/Pbk4p1.pdf |archive-url=https://web.archive.org/web/20060613222204/http://www.software.ibm.com/ibmdl/pub/software/rational/web/whitepapers/2003/Pbk4p1.pdf |archive-date=2006-06-13 |url-status=live |title=Architectural Blueprints – The '4+1' View Model of Software Architecture |journal=IEEE Software |volume=12 |issue=6 |pages=42–50 |doi=10.1109/52.469759|arxiv=2006.04975 |s2cid=219558624 }}
*{{Cite book|last=Pautasso|first=Cesare|title=Software Architecture: visual lecture notes|publisher=LeanPub|year=2020|url=https://leanpub.com/software-architecture/|pages=689}}