Jump to content

Software architecture analysis method: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
No edit summary
Line 8: Line 8:


==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 |author2= Gregory Abowd |author3= Len Bass |author3-link= Len Bass |author4= Paul Clements|accessdate=2006-10-22}}


[[Category:Software architecture]]
[[Category:Software architecture]]

Revision as of 17:32, 27 October 2019

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.

See also

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= (help)