Learning mode
Seven topologies, eight criteria
How the classic network topologies differ, how they are scored, and what the scores rest on.
The topologies
Badges show what kind of design each one is. Select a card for its full score justification.
Baseline scoring matrix
Author's assessment · same for every user1–10, where 10 is always most favourable (Delay 10 = lowest delay, Complexity 10 = simplest, Cost 10 = cheapest). Hover or tap a cell for the reason.
Score justification
Explore with your own weights
For study: weight the criteria directly and watch the ranking change. For a recommendation from real requirements, use Choose a network.
Decision mode
Choose the right network
Describe your situation in plain terms. The tool turns your answers into priorities, ranks the options, and explains the result.
Educational guidance, not an engineering-validated design. Confirm any real design with a site survey, traffic measurements and vendor specifications.
Why this result
How robust is it?
All seven options
Weighted score from the baseline matrix and your priorities. Options marked "not recommended" stay visible for comparison.
Your priorities
Generated from your answers; adjust any slider and everything above updates. Each weight shows what moved it.
Assumptions
Sources behind this result
Method & sources
How the numbers are made
Three layers: fixed baseline scores, weights from your priorities, and explicit scenario checks.
Weighted Sum Model
S(t) = Σ w(c) · s(t,c) ⁄ Σ w(c)
- s(t,c): baseline score of topology t on criterion c, 1–10. Fixed and identical for every user.
- w(c): weight 0–5. In Decision mode each weight starts at 3 and moves by the documented amount for each answer; you can then adjust it.
- Scenario checks never change scores. They mark options as not recommended (legacy technology, impractical size, missing redundancy) and add hybrid designs.
- Sensitivity: each weight is moved ±1, and 500 seeded random variations of ±25 % test how often the recommendation holds.
Scoring rubric
From answers to weights
Every rule, as stored in data/rules.json.
Limitations
References
Status shows what was checked on the given date. Page numbers are listed only where they were verified.