Throughout the software design process, developers must make decisions and reify them in code. The decisions made during software architecting are particularly significant in that they have system-wide implications, especially on the quality attributes. However, architects often fail to adequately document their decisions because they don't appreciate the benefits, don't know how to document decisions, or don't recognize that they're making decisions. This lack of thorough documentation. This paper provides information about a decision's rationale and consequences, architecture patterns can help architects better understand and more easily record their decisions.
%0 Journal Article
%1 HarrisonAvgeriouZdlin07software
%A Harrison, Neil B.
%A Avgeriou, Paris
%A Zdlin, Uwe
%D 2007
%J IEEE Software
%K 01624 ieee paper software development design pattern architecture
%N 4
%P 38--45
%R 10.1109/MS.2007.124
%T Using Patterns to Capture Architectural Decisions
%V 24
%X Throughout the software design process, developers must make decisions and reify them in code. The decisions made during software architecting are particularly significant in that they have system-wide implications, especially on the quality attributes. However, architects often fail to adequately document their decisions because they don't appreciate the benefits, don't know how to document decisions, or don't recognize that they're making decisions. This lack of thorough documentation. This paper provides information about a decision's rationale and consequences, architecture patterns can help architects better understand and more easily record their decisions.
@article{HarrisonAvgeriouZdlin07software,
abstract = {Throughout the software design process, developers must make decisions and reify them in code. The decisions made during software architecting are particularly significant in that they have system-wide implications, especially on the quality attributes. However, architects often fail to adequately document their decisions because they don't appreciate the benefits, don't know how to document decisions, or don't recognize that they're making decisions. This lack of thorough documentation. This paper provides information about a decision's rationale and consequences, architecture patterns can help architects better understand and more easily record their decisions.},
added-at = {2017-06-17T11:40:47.000+0200},
author = {Harrison, Neil B. and Avgeriou, Paris and Zdlin, Uwe},
biburl = {https://www.bibsonomy.org/bibtex/27b815a8cbe52525ee12883bf180ad675/flint63},
doi = {10.1109/MS.2007.124},
file = {IEEE Digital Library:2007/HarrisonAvgeriouZdlin07software.pdf:PDF},
groups = {public},
interhash = {c47d4c7cd814009483acca7dfcf45517},
intrahash = {7b815a8cbe52525ee12883bf180ad675},
issn = {0740-7459},
journal = {IEEE Software},
keywords = {01624 ieee paper software development design pattern architecture},
number = 4,
pages = {38--45},
timestamp = {2017-07-13T18:02:42.000+0200},
title = {Using Patterns to Capture Architectural Decisions},
username = {flint63},
volume = 24,
year = 2007
}