Editing Software architecture (section)

=== Design ===
{{main|Software design}}
Architecture is [[Software design|design]] but not all design is architectural.<ref name="DSA2"/> In practice, the architect is the one who draws the line between software architecture (architectural design) and detailed design (non-architectural design). There are no rules or guidelines that fit all cases, although there have been attempts to formalize the distinction. 
According to the ''Intension/Locality Hypothesis'',<ref name="edenkazman">{{cite web |author1=Amnon H. Eden |author2=Rick Kazman |title=Architecture Design Implementation |url=http://www.eden-study.org/articles/2003/icse03.pdf |year=2003 |url-status=dead |archive-url=https://web.archive.org/web/20070928035606/http://eden-study.org/articles/2003/icse03.pdf |archive-date=2007-09-28 }}</ref> the distinction between architectural and detailed design is defined by the ''Locality Criterion'',<ref name="edenkazman"/> according to which a statement about software design is non-local (architectural) if and only if a program that satisfies it can be expanded into a program that does not. For example, the [[client–server]] style is architectural (strategic) because a program that is built on this principle can be expanded into a program that is not client–server—for example, by adding [[peer-to-peer]] nodes.