Capturing and using rationale for a software architecture

Rationale Management in Software Engineering

Volumn , Issue , 2006, Pages 255-272

  Bass, Len ^a   Clements, Paul ^a   Nord, Robert L ^a   Stafford, Judith A ^a,b  

^a CARNEGIE MELLON UNIVERSITY   (United States)

^b Tufts University   (United States)

Author keywords

architectural design rationale; architectural tactic; architecture documentation; causal graph; software architecture; structural graph

Indexed keywords

EID: 77956059895     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/978-3-540-30998-7_12     Document Type: Chapter

References (9)

1. Bass L, Clements P, Kazman R (2003) Software Architecture in Practice, 2nd ed. Boston: Addison-Wesley
2. Wirfs-Brock R, McKean A (2002) Object Design: Roles, Responsibilities, and Collaborations. Boston: Addison-Wesley
3. Shevlin TP (2004) Composed control dependence graph generator. Tufts University Technical Report TR-2004-9
4. Dutoit AH, McCall R, Mistrik I, Paech B (2006) Rationale Management in Software Engineering. Berlin Heidelberg New York: Springer
5. Parnas DL (1976) On the design and development of program families. IEEE Transactions on Software Engineering 2(1):1-9
6. Buschmann F, Meunier R, Rohnert H, Sommerlad P, Stal M (1996) Patternoriented software architecture: A system of patterns. Chichester: Wiley
7. Clements P, Bachmann F, Bass L, Garlan D, Ivers J, Little R, Nord R, Stafford J (2002) Documenting Software Architectures: Views and Beyond. Boston: Addison-Wesley
8. ANSI/IEEE 1471-2000 available at http://standards.ieee.org/reading/ieee/ std-public/description/se/1471-2000-desc.html
9. Ali Babar M, Gorton I, Kitchenham BA (2006) A framework for supporting architecture knowledge and rationale management. In: Dutoit AH, McCall R, Mistrik I, Paech B (eds.) Rationale Management in Software Engineering. Berlin Heidelberg New York: Springer