methodatlas
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:Event ModelingRequest for CommentsSmoke TestARID (Active Reviews for Intermediate Designs)
Criterion
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
2-6 h1-3 Wochen vom Draft bis zur Entscheidung1-5 Tage2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-83-20 ReviewerNutzertrafficDesigners, developers as users, and facilitation
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsInterest Metrics, Conversion Signal, Learning NotePrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ArchitectureDecisionAsyncGovernance
ValidationExperimentsDemandGrowth
ArchitectureEngineeringFeedbackValidationTasks
Add more methods