{
  "id": "software_engineering-requirements-engineering",
  "name": "Requirements Engineering",
  "category": "computer_science",
  "subcategory": "software_engineering",
  "subcategory_name": "Software Engineering",
  "description": "Requirements Engineering process visualization. This process flowchart outlines key steps, checks, and outputs.",
  "complexity": {
    "nodes": 10,
    "edges": 10,
    "conditionals": 3,
    "logicGates": {
      "orGates": 3,
      "andGates": 1,
      "notGates": 0,
      "total": 4
    },
    "level": "high",
    "detailLevel": "source_grounded_rebuild",
    "loops": 1
  },
  "colorScheme": {
    "red": {
      "hex": "#ff6b6b",
      "category": "Triggers & Inputs"
    },
    "yellow": {
      "hex": "#ffd43b",
      "category": "Structures & Objects"
    },
    "green": {
      "hex": "#51cf66",
      "category": "Processing & Operations"
    },
    "blue": {
      "hex": "#74c0fc",
      "category": "Intermediates & States"
    },
    "violet": {
      "hex": "#b197fc",
      "category": "Products & Outputs"
    }
  },
  "mermaid": "graph TD\n    N1[\"Requirements Engineering...\"]\n    N2[\"Stakeholder Needs\"]\n    N3[\"Business Goals\"]\n    N4[\"Backlog\"]\n    N5{\"Constraints\"}\n    N6[\"Elicit + Document\"]\n    N7{\"Validate + Prioritize\"}\n    N8[\"Approved Requirements\"]\n    N9{\"Source-grounded check...\"}\n    N10[\"Requirements Engineering...\"]\n\n    N1 --> N2\n    N2 --> N3\n    N3 --> N4\n    N4 --> N5\n    N5 -->|yes| N6\n    N6 --> N7\n    N7 -->|yes| N8\n    N8 --> N9\n    N9 -->|yes| N10\n    N8 -->|iterate| N3\n\n    style N1 fill:#ff6b6b,color:#fff\n    style N2 fill:#ff6b6b,color:#fff\n    style N3 fill:#ff6b6b,color:#fff\n    style N4 fill:#ffd43b,color:#000\n    style N5 fill:#ffd43b,color:#000\n    style N6 fill:#51cf66,color:#fff\n    style N7 fill:#51cf66,color:#fff\n    style N8 fill:#b197fc,color:#fff\n    style N9 fill:#ffd43b,color:#000\n    style N10 fill:#b197fc,color:#fff",
  "sources": [
    {
      "title": "Requirements and Requirements Engineering ∗ ∗This chapter serves to deliver general background knowledge about requirements and requirements engineering.",
      "authors": "Jin, Zhi",
      "journal": "Environment Modeling-Based Requirements Engineering for Software Intensive Systems",
      "year": "2018",
      "pubmed": null,
      "doi": "10.1016/b978-0-12-801954-2.00001-7",
      "url": "https://doi.org/10.1016/b978-0-12-801954-2.00001-7"
    },
    {
      "title": "Software Engineering",
      "authors": "Sommerville, I.",
      "journal": "Pearson",
      "year": "2016",
      "pubmed": null,
      "doi": null,
      "url": "https://www.pearson.com/en-us/subject-catalog/p/software-engineering/P200000003559"
    },
    {
      "title": "Continuous Delivery",
      "authors": "Humble, J.; Farley, D.",
      "journal": "Addison-Wesley",
      "year": "2010",
      "pubmed": null,
      "doi": null,
      "url": "https://continuousdelivery.com/"
    },
    {
      "title": "The Mythical Man-Month",
      "authors": "Brooks, F. P.",
      "journal": "Addison-Wesley",
      "year": "1995",
      "pubmed": null,
      "doi": null,
      "url": "https://www.pearson.com/en-us/subject-catalog/p/mythical-man-month-the-essays-on-software-engineering-anniversary-edition/P200000009016"
    }
  ],
  "keywords": [
    "requirements",
    "engineering"
  ],
  "relatedProcesses": [],
  "created": "2026-01-15",
  "lastUpdated": "2026-04-30",
  "verified": false,
  "notes": "Corrective rebuild: replaces the generic scaffold with a process-specific step structure and records topology for duplicate detection.",
  "namedCollections": [],
  "graphMetrics": {
    "nodes": 10,
    "edges": 10,
    "conditionals": 3,
    "andGates": 1,
    "orGates": 3,
    "notGates": 0,
    "loops": 1
  },
  "nodeDetails": [
    {
      "id": "N1",
      "label": "Requirements Engineering...",
      "detail": "Requirements Engineering research question",
      "type": "process",
      "role": "Triggers & Inputs"
    },
    {
      "id": "N2",
      "label": "Stakeholder Needs",
      "detail": "Stakeholder Needs",
      "type": "process",
      "role": "Triggers & Inputs"
    },
    {
      "id": "N3",
      "label": "Business Goals",
      "detail": "Business Goals",
      "type": "process",
      "role": "Triggers & Inputs"
    },
    {
      "id": "N4",
      "label": "Backlog",
      "detail": "Backlog",
      "type": "process",
      "role": "Structures & Objects"
    },
    {
      "id": "N5",
      "label": "Constraints",
      "detail": "Constraints",
      "type": "decision",
      "role": "Structures & Objects"
    },
    {
      "id": "N6",
      "label": "Elicit + Document",
      "detail": "Elicit + Document",
      "type": "process",
      "role": "Processing & Operations"
    },
    {
      "id": "N7",
      "label": "Validate + Prioritize",
      "detail": "Validate + Prioritize",
      "type": "decision",
      "role": "Processing & Operations"
    },
    {
      "id": "N8",
      "label": "Approved Requirements",
      "detail": "Approved Requirements",
      "type": "process",
      "role": "Products & Outputs"
    },
    {
      "id": "N9",
      "label": "Source-grounded check...",
      "detail": "Source-grounded check: Requirements and Requirements Engineering ∗ ∗This chapter serves to deliver general background knowledge about requirements and requirements engineering.",
      "type": "decision",
      "role": "Structures & Objects"
    },
    {
      "id": "N10",
      "label": "Requirements Engineering...",
      "detail": "Requirements Engineering prediction/readout",
      "type": "process",
      "role": "Products & Outputs"
    }
  ],
  "flowchartStandard": {
    "name": "source_grounded_rebuild_v1",
    "applied": "2026-04-30",
    "curationStatus": "source_grounded_draft",
    "basis": "cs_exact_template",
    "topologySignature": "0bb076ae44205b86",
    "sourceGrounding": "Graph steps are derived from the process title, existing source metadata, and curated process/subfield templates; citations support the process topic and should be reviewed for node-level claims before marking verified."
  }
}