Software architecture: Difference between revisions

Revision as of 05:26, 22 January 2024

Revision as of 17:38, 13 February 2024

Line 38:

'''Conceptual integrity:''' a term introduced by [[Fred Brooks]] in his 1975 book ''[[The Mythical Man-Month]]'' to denote the idea that the architecture of a software system represents an overall vision of what it should do and how it should do it. This vision should be separated from its implementation. The architect assumes the role of "keeper of the vision", making sure that additions to the system are in line with the architecture, hence preserving [[The Mythical Man-Month#Conceptual integrity|conceptual integrity]].<ref name="BROOKS">{{cite book | last=Brooks | first=Frederick P. Jr. |date=1975|title=The Mythical Man-Month – Essays on Software Engineering |publisher=Addison-Wesley |isbn=978-0-201-00650-6|title-link=The Mythical Man-Month }}</ref>{{rp|41–50}}

'''Cognitive constraints:''' [[Conway's law|anAn observation]] first made in a 1967 paper by computer programmer [[Melvin Conway]] that organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations<ref>{{cite web|url=http://www.melconway.com/Home/Conways_Law.html|title=Conway's AsLaw|last=Conway|first=Melvin|website=Mel withConway's conceptualHome integrity, it wasPage|url-status=live|archive-url=https://web.archive.org/web/20190929004831/http://www.melconway.com/Home/Conways_Law.html|archive-date=2019-09-29|access-date=2019-09-29}}</ref>. Fred Brooks who introduced it to a wider audience when he cited the paper and the idea in his elegant classic ''The Mythical Man-Month'', calling it "[[Conway's law| Conway's Law]]."

== Motivation ==