Software architecture analysis method: Difference between revisions

Content deleted Content added

Revision as of 12:48, 28 March 2013 edit 145.91.128.32 (talk) No edit summary ← Previous edit		Latest revision as of 20:10, 26 March 2024 edit undo Jlwoodwa (talk \| contribs) Autopatrolled, Administrators 106,286 edits tag as one source
(13 intermediate revisions by 13 users not shown)
Line 1: {{~~Orphan~~No footnotes\|date=~~February~~April ~~2009~~2022}} {{one source \|date=March 2024}} '''Software architecture analysis method''' ('''SAAM''') is a method used in [[software architecture]] to evaluate a system architecture. It was the first documented software ~~wat unne kwatsch~~ 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== [[ARID]] [[Architectural analytics]] ==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, \|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]]