Edition 3 at DIS ballot, stage 40.20/ Planning date 12 September 2027, an estimate/ ISO/IEC/IEEE 29148:2018 applies today
ISO 29148 Revision CheckerThe requirements record, clause by clause, and the edition that follows it
8.2
ISO/IEC/IEEE 29148:2018
Information items

Clause 8.2: BRS example outline

Current editionISO/IEC/IEEE 29148:2018, Clause 8.2Edition 3 at DIS ballotNo public change recorded

The BRS outline follows the business perspective.

What clause 8.2 asks

The BRS outline follows the business perspective. It starts with identification and front matter, then the purpose and scope, the business overview and the major stakeholders, the business environment, the mission, the goals and objectives, the information environment and the business model. It continues with the business processes, policies and rules, constraints, modes, quality and structure, then the high-level operational concept, scenarios, other life-cycle concepts and project constraints. The outline is a recommendation, and the detailed content is in clause 9.3.

Why it matters

The BRS is the item that connects the business motivation to the rest of the requirements chain. The outline keeps the business context ahead of the operational detail, which is the right reading order for a business owner. It also gives the reviewer a place to check that the business, not the supplier, owns the content.

In the public record

No clause level change is public for this unit; the DIS keeps the title and scope, and the requirement text is not released.

What good looks like

Use the outline as the skeleton and mark a section not applicable with a reason. Keep the goals measurable and the constraints sourced. Do not let the outline become a template exercise: each section has to say something the next item can use.

Evidence an assessor asks for

The assessor will ask which business goal the system serves and who owns the BRS. A document owned by the supplier is a system specification in the wrong place.

  • BRS skeleton The outline with each section present, not applicable, or merged, and the reason
  • Business ownership The named business owner who approved the content
  • Goal measures A measure for each goal or objective
  • Handover note The sections the StRS and SyRS will elaborate

Where it commonly fails

  • The BRS is a project brief with the outline headings pasted on
  • Goals are statements with no measure
  • The business owner has never read the document

What to do before the revision

Walk the outline with the business owner before drafting. The sections they cannot fill are the questions the project has not asked.

Read across

← 8.1 Requirements information item outlines 8.3 StRS example outline →

Full register / Revision record

Source for clause 8.2: ISO/IEC/IEEE 29148:2018, Clause 8.2, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.