Content deleted Content added
m wl "architectural design decisions" to Architectural decision |
|||
Line 21:
* '''That which is fundamental to understanding a system in its environment'''<ref>[http://www.iso-architecture.org/42010/defining-architecture.html ISO/IEC/IEEE 42010: Defining "architecture"]. Iso-architecture.org. Retrieved on 2013-07-21.</ref>
* '''Things that people perceive as hard to change''': since designing the architecture takes place at the beginning of a software system's lifecycle, the architect should focus on decisions that "have to" be right the first time. Following this line of thought, architectural design issues may become non-architectural once their irreversibility can be overcome.<ref name="FOWL2003"/>
* '''A set of [[Architectural decision|architectural design decisions]]''': software architecture should not be considered merely a set of models or structures, but should include the decisions that lead to these particular structures, and the rationale behind them.<ref name="jansen05" /> This insight has led to substantial research into software architecture [[knowledge management]].<ref name="AKM">{{cite book |title=Software Architecture Knowledge Management |last1=Ali Babar |first1=Muhammad|last2=Dingsoyr|first2=Torgeir|last3=Lago|first3=Patricia|last4=van Vliet|first4=Hans|year=2009 |publisher=Springer|___location=Dordrecht Heidelberg London New York |isbn=978-3-642-02373-6}}</ref>
There is no sharp distinction between software architecture versus design and requirements engineering (see [[#Related fields|Related fields]] below). They are all part of a "chain of intentionality" from high-level intentions to low-level details.<ref name="FAIRBANKS2010">{{cite book|author=George Fairbanks|title=Just Enough Software Architecture|year=2010|publisher=Marshall & Brainerd}}</ref>{{rp|18}}
| |||