MLchartDataset catalogue

derived requirement

Term · Cybersecurity · MLC-T-CYB-001319

1. A requirement deduced or inferred from the collection and organization of requirements into a particular system configuration and solution.

2. A requirement that is implied or transformed from a higher-level requirement. Note 1: Implied requirements cannot be assessed since they are not contained in any requirement baseline. The decomposition of requirements throughout the engineering process makes the implicit requirements explicit, allowing them to be stated and captured in appropriate baselines and allowing associated assessment criteria to be stated. Note 2: A derived requirement must trace back to at least one higher-level requirement.

3. A requirement that is implied or transformed from a higher-level requirement.
Note 1: Implied requirements cannot be assessed since they are not contained in any requirements baseline. The decomposition of requirements throughout the engineering process makes implicit requirements explicit, allowing them to be stated and captured in appropriate baselines and allowing associated assessment criteria to be stated.
Note 2: A derived requirement must trace back to at least one higher-level requirement.

Table 1. Record
IdentifierMLC-T-CYB-001319
FieldCybersecurity
ReferencesNIST SP 800-160v1r1 from ISO/IEC/IEEE 29148:2018; NIST SP 800-37 Rev. 2 from NIST SP 800-160 Vol. 1; NIST SP 800-160 Vol. 1; NIST CSRC Glossary
Record as JSON
{
  "id": "MLC-T-CYB-001319",
  "term": "derived requirement",
  "field": "Cybersecurity",
  "definition": "1. A requirement deduced or inferred from the collection and organization of requirements into a particular system configuration and solution.\n\n2. A requirement that is implied or transformed from a higher-level requirement. Note 1: Implied requirements cannot be assessed since they are not contained in any requirement baseline. The decomposition of requirements throughout the engineering process makes the implicit requirements explicit, allowing them to be stated and captured in appropriate baselines and allowing associated assessment criteria to be stated. Note 2: A derived requirement must trace back to at least one higher-level requirement.\n\n3. A requirement that is implied or transformed from a higher-level requirement.\nNote 1: Implied requirements cannot be assessed since they are not contained in any requirements baseline. The decomposition of requirements throughout the engineering process makes implicit requirements explicit, allowing them to be stated and captured in appropriate baselines and allowing associated assessment criteria to be stated.\nNote 2: A derived requirement must trace back to at least one higher-level requirement.",
  "references": [
    "NIST SP 800-160v1r1 from ISO/IEC/IEEE 29148:2018",
    "NIST SP 800-37 Rev. 2 from NIST SP 800-160 Vol. 1",
    "NIST SP 800-160 Vol. 1",
    "NIST CSRC Glossary"
  ],
  "url": "https://mlchart.com/terminology/cybersecurity/derived-requirement/"
}

Record 1,319 of 4,693 in Cybersecurity terminology (MLC-0102). Request the full dataset.