Software architecture analysis method: Difference between revisions

Revision as of 22:16, 4 January 2007

Latest revision as of 20:10, 26 March 2024

(25 intermediate revisions by 19 users not shown)

Line 1:

{{No footnotes|date=April 2022}}

{{Orphan|November 2006}}

{{one source |date=March 2024}}

In software'''Software architecture analysis method''' ('''SAAM''',) Scenario-basedis Architecturea Analysismethod Method,used isin an[[software evaluationarchitecture]] methodto evaluate a system architecture. ThisIt was probably the first documented software architecture analyzisanalysis method., Developedand was developed in the mid 1990s to analyze a system for modifiability, but it is useful for testing any nonfunctionalnon-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/architecturelibrary/scenario_paperabstracts/whitepapers/scenariobasedanalysisnov1996.cfm|titleauthor= Scenario-BasedRick AnalysisKazman of|author2= SoftwareGregory Abowd Architecture|authorauthor3= RickLen Kazman,Bass Gregory Abowd,|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]]

Line 9 ⟶ 16:

{{Soft-eng-stub}}

[[de:SAAM]]