System element requirement breakdown structure - 3SE

Draft

https://www.3se.info/3se-onto/terms/system-element-req-breakdown-structure-3se-06aac05ed9f178ce

Breakdown structure of the system element requirement that supports the system element requirement analysis by following the principles below:
(1) A system element functional requirement is composed of at least one software functional requirement or one hardware functional requirement.
(2) A system element non-functional requirement is composed of at least one software non-functional requirement or one hardware non-functional requirement.
(3) A system element constraint is composed of at least one software constraint or one hardware constraint.
(4) A system element architecture constraint is composed of at least one software architecture constraint or one hardware architecture constraint.
(5) A system element functional requirement is allocated to a system element function.
(6) A system element non-functional requirement is allocated to a flow attribute or a system element state attribute.
(7) A system element architecture constraint is allocated to a software interface, a software interface attribute, a hardware interface, a hardware interface attribute, a software function, a software function attribute, a hardware function, a hardware function attribute, a software state, a software state attribute, a hardware state or a hardware state attribute.
(8) A system element constraint is allocated to a system interface or a system element.

Classification

flowchart TD N1["System element requirement breakdown structure"]:::current N2["Breakdown structure"] N1 -->|subclass of| N2 classDef current fill:#e8f4f8,stroke:#2980b9,stroke-width:2px

Structure

flowchart TD N1["Flow attribute"] N2["System non-functional requirement"] N3["Hardware function"] N4["Hardware block function"] N5["Hardware feature"] N6["Hardware interface"] N7["Hardware block interface"] N8["Hardware state"] N9["Hardware block state"] N10["Software function"] N11["Software component function"] N12["Software feature"] N13["Software interface"] N14["Software component interface"] N15["Software state"] N16["Software component state"] N17["System element"] N18["Physical element"] N19["System element state"] N20["System element attribute"] N21["System"] N22["System element architecture constraint"] N23["System architecture constraint"] N24["System element constraint"] N25["System constraint"] N26["System element function"] N27["System element function attribute"] N28["System function"] N29["System element functional requirement"] N30["System functional requirement"] N31["System element non-functional requirement"] N32["System element requirement"] N33["System requirement"] N34["System element state attribute"] N35["System state attribute"] N36["System interface"] N37["System element interface"] N1 -.->|allocates| N2 N3 -->|composed of| N4 N3 -.->|allocates| N5 N6 -->|composed of| N7 N8 -->|composed of| N9 N8 -.->|allocates| N3 N10 -->|composed of| N11 N10 -.->|allocates| N12 N13 -->|composed of| N14 N15 -->|composed of| N16 N15 -.->|allocates| N10 N17 -.->|allocates| N18 N17 -.->|allocates| N19 N17 -.->|allocates| N20 N17 -.->|can be| N21 N22 -.->|can be| N23 N24 -.->|can be| N25 N26 -.->|allocates| N10 N26 -.->|allocates| N3 N26 -.->|allocates| N27 N26 -.->|allocates| N23 N26 -.->|can be| N28 N29 -.->|can be| N30 N31 -.->|can be| N2 N32 -.->|can be| N33 N34 -.->|allocates| N23 N34 -.->|can be| N35 N36 -->|composed of| N37 N17 -.->|exposes| N37 N29 -->|subclass of| N32 N31 -->|subclass of| N32 N18 -.->|allocates| N25 N16 -.->|allocates| N11 N2 -->|subclass of| N33 N35 -.->|allocates| N2 N27 -.->|allocates| N23 N9 -.->|allocates| N4 N19 -.->|allocates| N26 N19 -.->|allocates| N8 N19 -.->|allocates| N15 N19 -.->|allocates| N23 N19 -.->|allocates| N34 N21 -.->|exposes| N36 N37 -.->|allocates| N23 N30 -->|subclass of| N33 N28 -.->|allocates| N30

Relations

Relatedflow-attribute-3se-069dcf9369937bc7  ·  hardware-architecture-constraint-3se-06aabef1fcbb721b  ·  hardware-constraint-3se-069be64e18377cf1  ·  hardware-function-3se-069be64e184f7488  ·  hardware-functional-req-3se-069be64e18587020  ·  hardware-interface-3se-069bd66fb6017920  ·  hardware-non-functional-req-3se-069be64e186075ed  ·  hardware-state-3se-069c98e055d57d9c  ·  software-architecture-constraint-3se-06aabef1fcf57c81  ·  software-constraint-3se-069be64e18697419  ·  software-function-3se-069be64e18717acd  ·  software-functional-req-3se-069be64e18797e1b  ·  software-interface-3se-069bd66fb64b7c7c  ·  software-non-functional-req-3se-069be64e18827c2c  ·  software-state-3se-069c98e056107597  ·  system-element-3se-069b85f238fb79eb  ·  system-element-architecture-constraint-3se-06aac05ed9c4742e  ·  system-element-constraint-3se-069ee425eb8a748f  ·  system-element-function-3se-069c995b151972b2  ·  system-element-functional-req-3se-069ee425ebb17241  ·  system-element-non-functional-req-3se-069ee425ebbb7edc  ·  system-element-req-3se-069c3bf771277d2d  ·  system-element-req-analysis-3se-06aac05ed9e9792f  ·  system-element-state-attribute-3se-069ebabe8f7a7daf  ·  system-interface-3se-069bd66fb6547971  ·  system-element-req-model-3se-06aac13a4035725f
Subclass ofbreakdown-structure-3se-069d166fa9037b67
Accountable rolesystem-architect-3se-069c451bef267e68
Supporting rolesystem-configuration-engineer-3se-069c451bef2e74e7  ·  system-engineer-3se-069c451bef3578a3  ·  system-quality-engineer-3se-06a49189cbed7a22  ·  system-risk-engineer-3se-069cd88d518b7cdc  ·  system-validation-engineer-3se-069c451bef3c7b63

JSON-LD

{
  "@context": "https://www.3se.info/3se-onto/contexts/term.context.jsonld",
  "@type": "skos:Concept",
  "title": "System element requirement breakdown structure - 3SE",
  "description": "Breakdown structure of the system element requirement that supports the system element requirement analysis by following the principles below:\n(1) A system element functional requirement is composed of at least one software functional requirement or one hardware functional requirement.\n(2) A system element non-functional requirement is composed of at least one software non-functional requirement or one hardware non-functional requirement.\n(3) A system element constraint is composed of at least one software constraint or one hardware constraint.\n(4) A system element architecture constraint is composed of at least one software architecture constraint or one hardware architecture constraint.\n(5) A system element functional requirement is allocated to a system element function.\n(6) A system element non-functional requirement is allocated to a flow attribute or a system element state attribute.\n(7) A system element architecture constraint is allocated to a software interface, a software interface attribute, a hardware interface, a hardware interface attribute, a software function, a software function attribute, a hardware function, a hardware function attribute, a software state, a software state attribute, a hardware state or a hardware state attribute.\n(8) A system element constraint is allocated to a system interface or a system element.",
  "status": "draft",
  "subClassOf": [
    "https://www.3se.info/3se-onto/terms/breakdown-structure-3se-069d166fa9037b67"
  ],
  "@id": "https://www.3se.info/3se-onto/terms/system-element-req-breakdown-structure-3se-06aac05ed9f178ce",
  "related": [
    "https://www.3se.info/3se-onto/terms/flow-attribute-3se-069dcf9369937bc7",
    "https://www.3se.info/3se-onto/terms/hardware-architecture-constraint-3se-06aabef1fcbb721b",
    "https://www.3se.info/3se-onto/terms/hardware-constraint-3se-069be64e18377cf1",
    "https://www.3se.info/3se-onto/terms/hardware-function-3se-069be64e184f7488",
    "https://www.3se.info/3se-onto/terms/hardware-functional-req-3se-069be64e18587020",
    "https://www.3se.info/3se-onto/terms/hardware-interface-3se-069bd66fb6017920",
    "https://www.3se.info/3se-onto/terms/hardware-non-functional-req-3se-069be64e186075ed",
    "https://www.3se.info/3se-onto/terms/hardware-state-3se-069c98e055d57d9c",
    "https://www.3se.info/3se-onto/terms/software-architecture-constraint-3se-06aabef1fcf57c81",
    "https://www.3se.info/3se-onto/terms/software-constraint-3se-069be64e18697419",
    "https://www.3se.info/3se-onto/terms/software-function-3se-069be64e18717acd",
    "https://www.3se.info/3se-onto/terms/software-functional-req-3se-069be64e18797e1b",
    "https://www.3se.info/3se-onto/terms/software-interface-3se-069bd66fb64b7c7c",
    "https://www.3se.info/3se-onto/terms/software-non-functional-req-3se-069be64e18827c2c",
    "https://www.3se.info/3se-onto/terms/software-state-3se-069c98e056107597",
    "https://www.3se.info/3se-onto/terms/system-element-3se-069b85f238fb79eb",
    "https://www.3se.info/3se-onto/terms/system-element-architecture-constraint-3se-06aac05ed9c4742e",
    "https://www.3se.info/3se-onto/terms/system-element-constraint-3se-069ee425eb8a748f",
    "https://www.3se.info/3se-onto/terms/system-element-function-3se-069c995b151972b2",
    "https://www.3se.info/3se-onto/terms/system-element-functional-req-3se-069ee425ebb17241",
    "https://www.3se.info/3se-onto/terms/system-element-non-functional-req-3se-069ee425ebbb7edc",
    "https://www.3se.info/3se-onto/terms/system-element-req-3se-069c3bf771277d2d",
    "https://www.3se.info/3se-onto/terms/system-element-req-analysis-3se-06aac05ed9e9792f",
    "https://www.3se.info/3se-onto/terms/system-element-state-attribute-3se-069ebabe8f7a7daf",
    "https://www.3se.info/3se-onto/terms/system-interface-3se-069bd66fb6547971",
    "https://www.3se.info/3se-onto/terms/system-element-req-model-3se-06aac13a4035725f"
  ],
  "entryCreated": "2026-09-17",
  "entryModified": "2026-09-17",
  "entryCreator": {
    "@type": "foaf:Person",
    "name": "@rcasteran"
  }
}

Raw JSON-LD: index.jsonld

Created 2026-09-17  ·  Modified 2026-09-17  ·  by @rcasteran