View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Competency QuestionsCommunication PlanLASR (Lightweight Approach for Software Reviews)C4 Model
| Criterion |  Knowledge Modeling Competency Questions |  Delivery Communication Plan |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2-4 h | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-4 h |
Participantsdifferent | 2-8 | 2-6 | 1 or a small team; particularly suitable for 3–4 people | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Communication Plan, Channel Matrix, Message Cadence | 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 | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | CommunicationStakeholdersDeliveryPlanning | ArchitectureQualityRiskAssessmentLean | ArchitectureCommunicationVisualization |