Software architecture analysis method: Difference between revisions
Content deleted Content added
m →References: parameter misuse; |
Citation bot (talk | contribs) Add: title. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | #UCB_webform 2820/3678 |
||
| Line 10: | Line 10: | ||
==References== |
==References== |
||
*{{cite web|url=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}} |
*{{cite web|url=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|title= The Influence of System Properties on Software Assurance and Project Management |accessdate=2006-10-22}} |
||
[[Category:Software architecture]] |
[[Category:Software architecture]] |
||
Revision as of 15:47, 22 July 2022
 | This article includes a list of references, related reading, or external links, but its sources remain unclear because it lacks inline citations. (April 2022) |
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. "The Influence of System Properties on Software Assurance and Project Management". Retrieved 2006-10-22.
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |