View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Communication CanvasExample MappingLASR (Lightweight Approach for Software Reviews)Specification by Example
| Criterion |  Architecture Architecture Communication Canvas |  Agile Example Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 60-120 min | 30-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min pro Feature |
Participantsdifferent | 2-8 | 3-7 | 1 or a small team; particularly suitable for 3–4 people | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Example Map, Acceptance Criteria, Open Questions | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Example Table, Acceptance Tests |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureQualityRiskAssessmentLean | AgileRequirementsExamplesBehavior-Driven Development |