Actions

Difference between revisions of "Software Architecture Analysis Method (SAAM)"

(Software Engineering Institute (SEI) 's Software Architecture Analysis Method (SAAM) is a five-step method for analyzing software architectures.)
 
m (The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).)
Line 1: Line 1:
Software Engineering Institute (SEI) 's Software Architecture Analysis Method (SAAM) is a five-step method for analyzing software architectures. The main activities involved in the SAAM are enumerated are:<br />
+
[[Software]] Engineering Institute (SEI) 's Software [[Architecture]] Analysis Method (SAAM) is a five-step method for analyzing software architectures. The main activities involved in the SAAM are enumerated are:<br />
 
1. Characterize a canonical functional partitioning for the domain.<br />
 
1. Characterize a canonical functional partitioning for the domain.<br />
 
2. Map the functional partitioning onto the architecture’s structural decomposition.<br />
 
2. Map the functional partitioning onto the architecture’s structural decomposition.<br />
3. Choose a set of quality attributes with which to assess the architecture.<br />
+
3. Choose a set of [[quality]] attributes with which to assess the architecture.<br />
 
4. Choose a set of concrete tasks which test the desired quality attributes.<br />
 
4. Choose a set of concrete tasks which test the desired quality attributes.<br />
 
5. Evaluate the degree to which each architecture provides support for each task.
 
5. Evaluate the degree to which each architecture provides support for each task.

Revision as of 18:25, 6 February 2021

Software Engineering Institute (SEI) 's Software Architecture Analysis Method (SAAM) is a five-step method for analyzing software architectures. The main activities involved in the SAAM are enumerated are:
1. Characterize a canonical functional partitioning for the domain.
2. Map the functional partitioning onto the architecture’s structural decomposition.
3. Choose a set of quality attributes with which to assess the architecture.
4. Choose a set of concrete tasks which test the desired quality attributes.
5. Evaluate the degree to which each architecture provides support for each task.