Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:SAAM (Software Architecture Analysis Method)Value Chain Analysis Team Topologies Interaction Modes

Criterion	Architecture SAAM (Software Architecture Analysis Method)	Business Strategy Value Chain Analysis	Team Design Team Topologies Interaction Modes
Purposedifferent	SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.	Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list.	When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements.
Complexitydifferent	High	High	Medium
Timedifferent	Preparation, scenario analysis, and findings review; effort depends on scope	Half day	Half day
Participantsdifferent	Architecture experts and stakeholders for scenarios and weighting	3-8	Team-Leads plus Architecture
Formatdifferent	Workshop + async	Workshop	Workshop
Outputdifferent	Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives	Value Chain Map, Lever List	Interaction Heat Map, Agreements per Pair
Tagsno overlap	ArchitectureChangeAnalysisComparisonQuality	StrategyBusiness modelDiagnosisAnalysis	TeamAlignmentCollaborationOrganization