AV Institute · Week 8Real-World Capstone Project

Lesson

Interpreting a Client Requirements Brief

Est. 50 minCompetency: Extract actionable requirements from a client brief.

Learning objectives

Identify explicit and implicit requirements in a brief.
Convert requirements into system functions.
Note constraints, scope, and assumptions.
Document clarifying questions for the client.

Vocabulary

Requirements brief: The client's statement of what the system must do.
Explicit requirement: Stated directly in the brief.
Implicit requirement: Needed but not stated; inferred from use.
Scope: What is and is not included in the project.

Lesson content

A brief is rarely complete or precise. Your job is to read it for both what it says and what it implies, then turn it into a list of functions the system must deliver.

How to read a brief

1List every explicit requirement (room count, source types, conferencing, displays).
2Infer implicit requirements (control, audio quality, network, accessibility).
3Note constraints (budget, schedule, site, IT policies).
4List assumptions you are making and questions for the client.

Convert to functions

'Laptop presentation' → source selection, dual-display routing, content audio.
'Video conferencing' → codec, camera, mics, DSP with AEC, far-end audio.
'Easy control' → touchpanel, Start/Shutdown workflow, status feedback.
'Future expansion' → spare capacity, network headroom.

Ask before you assume

Every assumption is a risk. Write down what you assumed and what you would ask the client. A short clarifying conversation prevents a design built on a wrong assumption.

Worked example

Brief: 'We need a conference room for hybrid meetings with laptop sharing and easy control.' Explicit: conference room, hybrid meetings, laptop sharing, easy control. Implicit: video conferencing (camera, mics, codec, DSP), dual displays, touchpanel, network. Questions: room size, participant count, preferred platform, budget.

Implementation checklist

✓Explicit requirements listed.
✓Implicit requirements inferred.
✓Constraints and scope noted.
✓Assumptions and client questions documented.

Downloadable study guide

study-guide.txtcopy-paste ready

01. Brief → explicit + implicit requirements + constraints + assumptions.
02. Convert requirements into system functions.
03. Document clarifying questions; ask before you assume.