
AV Institute · Week 2Programming & Control Basics
Field Assignment
Write a Room Control Logic Specification
Est. 60 minCompetency: Produce a written specification a programmer could implement from.
Learning objectives
- Document room states and transitions.
- Specify each control action and its feedback.
- Define error handling and timeouts.
Assignment brief & submission
Write a control logic specification for the conference room from the lab. This is the document a programmer uses — and that a reviewer signs off before code is written.
Required sections
- 1Room states and allowed transitions (state diagram in words).
- 2Per-button behavior: action, commands sent, expected feedback, UI update.
- 3Volume and mute behavior with feedback.
- 4Source selection and interlock rules.
- 5Error handling: what counts as an error, timeout values, what the user sees.
Why a spec
A spec separates 'what the room must do' from 'how the code does it.' It lets you and a reviewer agree on behavior before implementation, and it documents the system for whoever maintains it next.
Implementation checklist
- ✓All states and transitions listed.
- ✓Each button's behavior fully specified with feedback.
- ✓Volume/mute and source interlock rules explicit.
- ✓Error handling and timeouts defined.
Downloadable study guide
study-guide.txtcopy-paste ready
01. Spec = states/transitions + per-button behavior + volume/mute + source rules + error handling. 02. Separate 'what' (spec) from 'how' (code). 03. Define timeouts and user-visible error states.