International (ISO/IEC JTC 1/SC 7 and IEEE Computer Society S2ESC); adopted as BS ISO/IEC/IEEE 29148:2018 and CSA ISO/IEC/IEEE 29148:19 (IDT)

ISO/IEC/IEEE 29148:2018

89 controls. 4 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

89 controls 4 frameworks share controls with it International (ISO/IEC JTC 1/SC 7 and IEEE Computer Society S2ESC); adopted as BS ISO/IEC/IEEE 29148:2018 and CSA ISO/IEC/IEEE 29148:19 (IDT) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
5.25.2 Requirements fundamentals0
5.2.45.2.4 Requirements construct1
5.2.55.2.5 Characteristics of individual requirements1
5.2.65.2.6 Characteristics of a set of requirements1
5.2.75.2.7 Requirement language criteria1
5.2.85.2.8 Requirements attributes1
5.3.25.3.2 Iteration, recursion and derived requirements1
6.26.2 Business or mission analysis process0
6.2.3.26.2.3.2 Prepare for business or mission analysis0
6.2.3.36.2.3.3 Define the problem or opportunity space0
6.2.3.46.2.3.4 Characterize the solution space0
6.2.3.56.2.3.5 Evaluate alternative solution classes0
6.2.3.66.2.3.6 Manage the business or mission analysis0
6.36.3 Stakeholder needs and requirements definition process0
6.3.3.26.3.3.2 Prepare for stakeholder needs and requirements definition1
6.3.3.36.3.3.3 Define stakeholder needs1
6.3.3.46.3.3.4 Develop the operational concept and other life cycle concepts1
6.3.3.56.3.3.5 Transform stakeholder needs into stakeholder requirements1
6.3.3.66.3.3.6 Analyze stakeholder requirements1
6.3.3.76.3.3.7 Manage the stakeholder needs and requirements definition1
6.46.4 System (system/software) requirements definition process0
6.4.3.26.4.3.2 Prepare for system or software requirements definition0
6.4.3.36.4.3.3 Define system or software requirements2
6.4.3.46.4.3.4 Analyze system or software requirements2
6.4.3.56.4.3.5 Manage system or software requirements3
6.56.5 Requirements engineering activities in other technical processes0
6.5.1.26.5.1.2 Requirements activities in architecture definition1
6.5.2.26.5.2.2 Requirements activities in preparing for verification2
6.5.2.36.5.2.3 Requirements activities in managing verification results1
6.5.3.26.5.3.2 Requirements activities in preparing for validation1
6.5.3.36.5.3.3 Requirements activities in managing validation results1
6.66.6 Requirements management0
6.6.2.16.6.2.1 Requirements change management2
6.6.2.2.26.6.2.2.2 Configuration identification for requirements2
6.6.2.2.36.6.2.2.3 Configuration change management for requirements2
6.6.2.3.26.6.2.3.2 Prepare information management for requirements1
6.6.2.3.36.6.2.3.3 Perform information management for requirements1
6.6.3.26.6.3.2 Prepare for requirements measurement1
6.6.3.36.6.3.3 Perform requirements measurement1
77 Information items0
9.29.2 General content of requirements information items0
9.39.3 Business requirements specification (BRS) content0
9.3.109.3.10 BRS content: business processes, policies and rules, constraints, modes, quality and structure0
9.3.169.3.16 BRS content: operational concept, scenarios, other life cycle concepts and project constraints0
9.3.29.3.2 BRS content: business purpose, scope, overview and major stakeholders0
9.3.69.3.6 BRS content: business environment, goals, business model and information environment0
9.49.4 Stakeholder requirements specification (StRS) content0
9.4.109.4.10 StRS content: system processes, policies and rules, constraints, modes and states, operational quality0
9.4.159.4.15 StRS content: user requirements1
9.4.169.4.16 StRS content: operational concept, scenarios, detailed concepts and project constraints0
9.4.29.4.2 StRS content: stakeholder purpose, scope, overview and stakeholders0
9.4.69.4.6 StRS content: business environment, goals, business model and information environment0
9.59.5 System requirements specification (SyRS) content0
9.5.109.5.10 SyRS content: modes and states, physical characteristics, environmental conditions0
9.5.139.5.13 SyRS content: security and information management requirements0
9.5.159.5.15 SyRS content: policy and regulation, life cycle sustainment, packaging and transport0
9.5.189.5.18 SyRS content: verification1
9.5.199.5.19 SyRS content: assumptions and dependencies0
9.5.29.5.2 SyRS content: system purpose, scope and overview0
9.5.59.5.5 SyRS content: functional, usability, performance and interface requirements1
9.5.99.5.9 SyRS content: system operations (human system integration, maintainability, reliability, other quality)0
9.69.6 Software requirements specification (SRS) content0
9.6.109.6.10 SRS content: specified requirements1
9.6.119.6.11 SRS content: external interfaces0
9.6.129.6.12 SRS content: functions1
9.6.139.6.13 SRS content: usability and performance requirements0
9.6.159.6.15 SRS content: logical database requirements, design constraints, standards compliance0
9.6.189.6.18 SRS content: software system attributes0
9.6.199.6.19 SRS content: verification1
9.6.29.6.2 SRS content: purpose and scope0
9.6.209.6.20 SRS content: supporting information0
9.6.49.6.4 SRS content: product perspective and interfaces1
9.6.59.6.5 SRS content: product functions, user characteristics, limitations, assumptions and dependencies0
9.6.99.6.9 SRS content: apportioning of requirements1
A.2A.2 Operational concept document (OpsCon)0
A.2.1A.2.1 OpsCon: production, identification, scope and referenced documents0
A.2.10A.2.10 OpsCon: appendices and glossary0
A.2.4A.2.4 OpsCon: current system or situation0
A.2.5A.2.5 OpsCon: justification for and nature of changes0
A.2.6A.2.6 OpsCon: concepts for the proposed system0
A.2.7A.2.7 OpsCon: operational scenarios1
A.2.8A.2.8 OpsCon: summary of impacts0
A.2.9A.2.9 OpsCon: analysis of the proposed system0
ANNEXBAnnex B (informative) Concept of operations0
C.2C.2 Information item tailoring process0
CL88 Guidelines for information items (informative outlines)0
STANDARDISO/IEC/IEEE 29148:2018: the standard, its scope and conformance0
STATUSEdition status and relationship to other standards0
TERMS3 Terms and definitions used by the requirements leaves0

Tell me when ISO/IEC/IEEE 29148:2018 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for ISO/IEC/IEEE 29148:2018, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition