What are ATAM and CBAM?
A story about rehearsing several scenarios right before the press runs, to surface trade-offs while there's still time.
Right before the press runs, the editor and print supervisor worry about printing with this binding.The whole layout is already locked in — and now the nerves set in.
The binding problem only surfaces after everything is printed.It's already all printed — far too late to change the binding.
ATAM = rehearsing trade-offs against many scenarios before the press ever runs.Stakeholders gather to find the design decisions that swing quality most (sensitivity points).
Put cost and benefit numbers on the options ATAM found, and it becomes CBAM.CBAM compares, in numbers, whether Option A or B pays off more.
Evaluation doesn't make the decision for you.The evaluation only shows what's worth weighing — the choice is still a human's to make.
ATAM evaluates a design by rehearsing quality scenarios before the press runs, surfacing trade-offs and risks; CBAM extends this by adding cost and benefit numbers to weigh each option.
ATAM (Architecture Tradeoff Analysis Method) gathers stakeholders to write quality-attribute scenarios — performance, security, portability, and so on — then maps each scenario to the architecture's design decisions to find sensitivity points and trade-off points. CBAM (Cost Benefit Analysis Method) extends this by adding an economic analysis of each design decision's cost and benefit, helping prioritize decisions quantitatively.
When grown-ups say it
- ATAM
- The scenario rehearsal before the press runs. Finds trade-offs and sensitivity points.
- CBAM
- ATAM with cost-benefit numbers added on top. Prioritizes options with numbers.
- Quality Attribute Scenario
- A concrete situation like "it needs this much durability." The starting point of the evaluation.
- Sensitivity Point
- A spot where one decision swings quality a lot. A spot ATAM pays special attention to.
- Trade-off Point
- A spot where gaining one thing costs another. A sensitivity point affecting multiple qualities becomes a trade-off point.
- Stakeholder
- People like the editor, author, and print supervisor who gather for the evaluation. ATAM brings them all into one room.
- IS Audit/PMO
- Audit checks the whole project stage by stage; ATAM evaluates the architecture design. They cover different scopes. → the checker who watches the whole publishing run
- Conditions of Good Software
- The very quality conditions ATAM weighs against each other. Scenarios ultimately come from these conditions. → what makes a good book