Technical Architecture Decision Making

Technical Architecture Decision Making

Choosing an MCU, a bus, or "bare metal vs. RTOS" is an architecture decision. This subject is about making that choice visible: options, criteria, evidence, and a recorded decision (ADR-style) that a teammate can challenge. Guessing a board because it was in the cupboard is not analysis.

Starting Points

• Embedded systems overview
• Microcontrollers & memory
• Nygard, M. Documenting Architecture Decisions.

Key Points

• You list at least two viable options for a significant choice (MCU family, RTOS vs. super-loop, wired vs. wireless).
• You define decision criteria from requirements (I/O, RAM, real-time, cost, team skill, radio certification).
• You score or argue the options against those criteria and recommend one, including what you are giving up.
• You record the decision so it can be revisited when a constraint changes.