Software architecture analysis method: Difference between revisions
Content deleted Content added
Citation bot (talk | contribs) Add: title. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | #UCB_webform 2820/3678 |
tag as one source |
||
| Line 1: | Line 1: | ||
{{No footnotes|date=April 2022}} |
{{No footnotes|date=April 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 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. |
'''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. |
||
Latest revision as of 20:10, 26 March 2024
 | This article includes a list of references, related reading, or external links, but its sources remain unclear because it lacks inline citations. (April 2022) |
 | This article relies largely or entirely on a single source. (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 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
[edit]References
[edit]- 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. |