Software architecture analysis method: Difference between revisions
Content deleted Content added
Christian75 (talk | contribs) m Reverted 1 edit by 122.252.234.214 (talk) to last revision by Addbot. (TW) |
m + Link(s) |
||
| Line 4: | Line 4: | ||
==References== |
==References== |
||
*{{cite web|url=http://www.sei.cmu.edu/library/abstracts/whitepapers/scenariobasedanalysisnov1996.cfm|title= http://www.sei.cmu.edu/library/abstracts/whitepapers/scenariobasedanalysisnov1996.cfm |author= Rick Kazman, Gregory Abowd, Len Bass, Paul Clements|accessdate=2006-10-22}} |
*{{cite web|url=http://www.sei.cmu.edu/library/abstracts/whitepapers/scenariobasedanalysisnov1996.cfm|title= http://www.sei.cmu.edu/library/abstracts/whitepapers/scenariobasedanalysisnov1996.cfm |author= Rick Kazman, Gregory Abowd, [[Len Bass]], Paul Clements|accessdate=2006-10-22}} |
||
[[Category:Software architecture]] |
[[Category:Software architecture]] |
||
Revision as of 10:38, 12 October 2014
Software architecture analysis method (SAAM) is a method used in software architecture to evaluate a system architecture. It was the first documented software architecture analysis method, and was developed in the mid 1990s to analyze a system for modifiability, but it is useful for testing any non-functional aspect.
SAAM was a precursor to the architecture tradeoff analysis method.
References
- Rick Kazman, Gregory Abowd, Len Bass, Paul Clements. "http://www.sei.cmu.edu/library/abstracts/whitepapers/scenariobasedanalysisnov1996.cfm". Retrieved 2006-10-22.
{{cite web}}: External link in|title=
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |