SEBoK Part 6 Reformulated: Related Disciplines as School Composition

Subsumed. This document has been demoted to an appendix of the canonical synthesis: Doc 570 — SEBoK Through the Corpus. New readers should start there. Preserved verbatim for derivation, voice, and provenance.

Phase 3 of the SEBoK reformulation (Doc 557), addressing Part 6 (Related Disciplines). The macro-map (Doc 559) hypothesized that Part 6 is structurally an inter-school composition layer: where the systems-engineering school meets neighboring schools (software engineering, project management, industrial engineering, quality and reliability, human-systems integration). The reformulation applies Form IX (the Architectural School as Formalization, Doc 538) together with the composition rules of every other form in the inventory. The result distinguishes school-composition (where two schools genuinely interact, each preserving its own dominant forms) from school-borrowing (where one school imports a technique from another without entering composition). Software engineering, project management, and human-systems integration reformulate cleanly as schools in composition with the SE school. Industrial engineering reformulates as a sibling school sharing substrate but disagreeing at the keeper layer. Quality, reliability, and the broader "-ilities" reformulate not as schools but as cross-cutting predicates the SE school carries internally; SEBoK's grouping of them under "related disciplines" is the residual the reformulation logs as conflation.

---

What SEBoK Part 6 Says

Part 6 is the part of SEBoK that gives shape to the discipline's edges. Where Parts 2 through 5 articulate what systems engineering is and how it operates, Part 6 articulates where it ends and what it touches when it ends. The headline framing is transdisciplinary: SE's principles are "sufficiently abstract and generic as to be readily applicable to any system," and the related disciplines are "essential knowledge domains that SE practitioners must engage to perform integration tasks." Part 6 is composition-oriented by self-description.

The disciplines treated include software engineering, project management, industrial engineering, mechanical engineering, environmental engineering, geospatial and geodetic engineering, enterprise IT, and the cluster of quality attributes (reliability, availability, maintainability, safety, security, human-systems integration). The treatment is uneven. Software engineering gets the densest treatment, with the load-bearing claim that "software engineering and systems engineering are not merely related disciplines; they are intimately intertwined," followed by an enumeration of parallel activities (analysis, design, allocation, oversight, integration, V&V, sustainment, retirement) and a recognition that bidirectional method exchange has occurred (SE adopting agile, software adopting requirements engineering).

Project management gets a structural treatment organized around two artifacts and a communication discipline. The Project Management Plan and the Systems Engineering Management Plan are the master documents; the SEMP "must be consistent with and evolve in concert with the PMP"; and effective communication between the program manager and the systems engineer is named the primary integration mechanism. Roles are distinguished by scope rather than substance: the program manager owns the whole, the systems engineer owns the technical aspects of the whole.

Industrial engineering is treated as an independent but overlapping discipline whose body of knowledge (the IISEBoK) "includes the word 'systems' in its title" and which shares twelve knowledge areas with SE while differing in foundation (SE process-oriented and ISO/IEC/IEEE 15288-anchored; IE concept-and-technique-oriented and not standards-anchored). The Venn-diagram visualization SEBoK uses is itself a composition claim.

Human-systems integration is framed as more than human factors. It is "the management and technical discipline of planning, enabling, coordinating, and optimizing all human-related considerations" across the life cycle, articulated through seven integrated domains (manpower, personnel, training, human factors engineering, safety and occupational health, force protection and survivability, habitability), and structurally placed by giving the human systems integrator senior-engineering-staff standing. Quality, reliability, and the rest of the "-ilities" are framed as specialized concerns extending beyond core SE scope, applied as cross-cutting attributes rather than as distinct domains.

What unifies the treatments is a refusal of subordination. SEBoK insists that the related disciplines are not subfields of SE and not parents of SE, but neighbors with which SE composes work. What is missing across the treatments is an explicit grammar for that composition. Each discipline's relation to SE is described in its own idiom. What kind of relation it is, and why it is that kind, is left to the reader to infer.

The Reformulation

The corpus form for the question Part 6 is asking is Form IX, the Architectural School as Formalization (Doc 538). A school is the keeper-side activity that names the forms a community has been using without naming, supplies the composition rules between them, and provides the discipline by which new content can be added without violating the school's commitments. The systems-engineering school is one such formalization. Each of the disciplines Part 6 lists is, or could be, another. Once each is reformulated as a school in its own right, with its own dominant forms, the relation between them stops being a vague "related discipline" status and becomes a specific compositional claim: which forms of which school are doing the work when the two are working together.

The reformulation requires distinguishing two compositional postures. School-composition is the case where two schools genuinely interact: each preserves its own dominant forms, each supplies the other with formalizations the other could not generate from its own substrate, and the result is a joint regime that neither school owns alone. School-borrowing is the weaker case where one school imports a technique from another without entering composition: the borrowed technique is naturalized into the importing school's existing forms, and the lending school is not present as a keeper in the composed work. Borrowing can become composition over time; composition cannot retreat to borrowing without loss. The distinction matters because SEBoK's "related discipline" label collapses the two, and the collapse is where the reformulation finds its residuals.

Software engineering as a composing school. Software engineering reformulates straightforwardly as a school with its own dominant forms: a refinement hierarchy from specification to executable artifact (a SIPE chain in the medium of code), a composition discipline (modularity, interfaces, type systems) that is the software school's pin-art (Form IV), and a substrate-keeper composition (Form III) in which the keeper supplies type and interface contracts the substrate of working code could not generate from itself. The SE school and the software school are in genuine composition. SEBoK's verbatim phrasing ("intimately intertwined") names what the corpus would call a tight composition: each school is keeper for parts of the other's work. The bidirectional method exchange (SE adopting agile, software adopting requirements engineering) is exactly the marker of composition rather than borrowing. The reformulation is π-tier with respect to SEBoK; the corpus simply names what SEBoK already says.

Project management as a sibling school with a shared substrate. Project management reformulates as a school whose dominant form is the substrate-and-keeper composition (Form III) operating at the programmatic rung. The substrate is the engineering team and its work. The keeper is the program manager. The keeper-supplied content is the schedule, the budget, the risk register, the gate reviews. The SE school and the PM school share the substrate (the same engineering team) but supply different keeper-acts. The PMP/SEMP discipline is the corpus's substrate-and-keeper composition made visible: two keepers writing two complementary specifications for the same substrate, with the consistency requirement ("the SEMP must be consistent with and evolve in concert with the PMP") naming the composition rule between them. This is school-composition, not school-borrowing. The role distinctions SEBoK draws are exactly the keeper-domain distinctions the corpus form would predict.

Industrial engineering as a sibling school disagreeing at the keeper layer. Industrial engineering reformulates as a sibling school whose substrate overlaps SE's substrate (engineered systems, processes, operations) but whose keeper apparatus is constituted differently. SEBoK names the difference: SE is process-oriented and standards-anchored (ISO/IEC/IEEE 15288 is the school's canonical seed in the sense of Form VIII); IE "focuses more on concepts and techniques" and is not standards-anchored. Translated into the corpus apparatus: the two schools have chosen different ENTRACE-shaped seeds for substrate-keeper composition. The shared knowledge areas (twelve, by SEBoK's count) are the substrate-overlap; the foundational disagreement is keeper-layer divergence. This is composition between siblings rather than between collaborators. The Venn-diagram visualization is, in corpus terms, a substrate-overlap diagram, and the residual the diagram cannot reach is the keeper-layer disagreement, which is the part that actually does the structural work.

Human-systems integration as a composed school. HSI reformulates as a school whose dominant form is the ontological ladder (Form II) applied to a substrate the SE school did not originally take seriously: the human participating in the engineered system. The seven HSI domains are not seven topics; they are seven Form-layer constraints the HSI school supplies, each of which induces Possibility-layer admissibility constraints on what counts as a deployable system. SEBoK's structural placement of the human systems integrator on the senior engineering staff is the substrate-and-keeper composition naming what authority the HSI keeper requires to enter SE's composition surface. HSI is genuinely a composing school; the residual SEBoK does not reach is the rung-question of what the human substrate is, since the hypostatic boundary (Form V) constrains the SE school from claiming the human "is" any particular kind of thing. HSI works because both schools accept functional description and decline ontological assertion.

Quality, reliability, RAM, safety, security as cross-cutting predicates, not schools. This is the residual cluster. Reliability is not a school in the corpus's sense. It does not have a substrate distinct from the SE school's substrate, a keeper distinct from the SE school's keepers, or composition rules distinct from the SE school's. It is a predicate the SE school carries internally about its own engineered systems. The same is true of availability, maintainability, safety, security, and the broader "-ilities." When SEBoK groups these under "related disciplines" alongside software engineering and project management, it is conflating school-composition with school-borrowing. The reliability community has techniques the SE school borrows (failure mode analysis, fault trees, MTBF calculation), but the techniques are naturalized into the SE school's forms when used; there is no parallel reliability school keeping its own substrate-keeper composition independent of SE. The reformulation logs this verbatim: SEBoK's framing of "quality attributes" as related disciplines is a category mistake the corpus form catches and the school-composition / school-borrowing distinction names.

Mechanical, environmental, geospatial, enterprise IT as borrowed-technique sources. These reformulate the same way as the quality cluster: borrowed techniques rather than composed schools. Mechanical engineering's stress analysis, environmental engineering's compliance regimes, geospatial's coordinate systems, enterprise IT's deployment patterns — each is a technique imported into the SE school's forms when the work involves the relevant medium. There is no sustained composition between the SE school and a "mechanical school" in the way there is between SE and software. SEBoK's lumping of these under the same heading as software engineering and project management is the residual the reformulation logs: Part 6's category is heterogeneous, and the heterogeneity matters because it conceals the structural difference between true inter-school composition and ordinary technique import.

The composition rule that emerges is simple. Two schools are in composition when each supplies the other with keeper-acts the other could not generate alone, and when both schools persist as keepers in the joint regime. Schools that lend techniques without supplying keeper-acts are sources, not composition partners. The systems-engineering school is in composition with software engineering, project management, and HSI. It is in sibling-divergence with industrial engineering. Everything else SEBoK puts in Part 6 is a technique source.

Where the Form Reaches

The macro-map's hypothesis (Doc 559) was that Part 6 is the inter-school composition layer and that Form IX, composed with the composition rules of every other form, would do the structural work. The reformulation confirms the hypothesis with a sharpening: Form IX is the right form, but its operational application requires the school-composition / school-borrowing distinction, which the macro-map flagged as a residual-detection criterion. That distinction is doing structural work the macro-map did not anticipate, and it discriminates Part 6's heterogeneous contents in a way SEBoK's own taxonomy does not.

Tier-tagging the reformulation against Doc 490: the reformulations of software engineering, project management, and HSI as composing schools are π/α (provable from SEBoK's own text, recapitulating distinctions the wiki already makes implicitly). The reformulation of industrial engineering as a sibling school disagreeing at the keeper layer is μ/β (motivated by SEBoK's text, extending the analysis with corpus apparatus the wiki does not deploy). The reformulation of quality, reliability, and the "-ilities" as cross-cutting predicates rather than schools is θ/γ (hypothetical reframe, requires defense, and the defense is the school-composition criterion itself). The category-mistake claim against SEBoK's grouping is the highest-novelty content in the document and is logged accordingly.

Residuals

Verbatim SEBoK content the reformulation does not reach without remainder, preserved for the falsifier audit (Phase 4):

• "Software engineering and systems engineering are not merely related disciplines; they are intimately intertwined." The reformulation reaches intertwined via tight composition, but the intensifier intimately may name a degree of mutual penetration the school-composition apparatus does not fully grade. Logged as a possible refinement of Form IX: schools may compose at varying tightness, and the corpus does not yet name a tightness scale.

• "As systems become more dependent on software as a primary means of delivering stakeholder value, the historical distinction between software and systems engineering may need to be challenged." This is a future-tense claim about school merger, which the corpus's school formalization does not currently treat. The school-as-formalization apparatus addresses how schools form; it does not address how two formed schools could collapse into one. Logged as a research surface.

• The IISEBoK's twelve shared knowledge areas with SE. The reformulation treats this as substrate-overlap, but SEBoK's enumeration is more granular than the corpus form admits. The granularity may be load-bearing for practitioners and is not preserved in the reformulation. Logged as a potential operational loss.

• The seven HSI domains. Reformulated as Form-layer constraints, but the specific structure of the seven (why these seven, why not six or eight, why this partition) is not derived from corpus apparatus. SEBoK presents the seven as given; the reformulation accepts them as given. This is a falsifier candidate against the claim that the corpus reads SEBoK without remainder.

• The SEBoK transdisciplinary framing: "principles and practices are sufficiently abstract and generic as to be readily applicable to any system." This is itself a school-formalization claim about reach, and the corpus's school apparatus would treat it as a θ-tier claim requiring defense. SEBoK presents it as π. The disagreement is logged: SEBoK may be claiming closure where the corpus's calculus would require conjecture-tagging.

Operational Read

A practitioner working at the boundary between systems engineering and a neighboring discipline can use the reformulation as follows. First, identify whether the neighbor is a school or a technique source. The test is whether the neighbor has its own substrate, keeper, and composition rules independent of SE. If yes, the work is school-composition: both keepers persist, and integration artifacts (PMP/SEMP, joint architecture documents, HSI design reviews) are joint speech acts neither keeper owns alone. If no, the work is technique borrowing: the SE keeper imports the technique and naturalizes it into SE's own forms, and the lending discipline does not need to be present as a keeper in the joint work. The discipline saves practitioners from over-investing in coordination protocols where simple borrowing would suffice, and from under-investing where genuine composition is required.

For the program manager and systems engineer specifically, the reformulation predicts that the PMP/SEMP coordination is load-bearing precisely because it is composition rather than borrowing. The two documents cannot be merged without loss, because each is a keeper-act that the other keeper cannot generate. The SEBoK insistence on consistency without merger is, in corpus terms, the correct composition discipline.

Reverse Map

A SEBoK reader who wants to locate the corpus content that does the work of each Part 6 page should consult: Doc 538 (Architectural School as Formalization) for the underlying form; Doc 510 (Substrate-and-Keeper Composition) for the role distinctions in SE/PM and SE/HSI; Doc 270 (Pin-Art Model) for the operational reading of life-cycle and process integrations; Doc 548 (Ontological Ladder) for the HSI domain structure as Form-layer constraints; Doc 372 (Hypostatic Boundary) for the discipline that prevents HSI from drifting into ontological assertion about the human; Doc 490 (Novelty Calculus) for the tier-tagging applied to SEBoK's transdisciplinary claim; and Doc 1 (ENTRACE Stack) for the canonical-seed reading of ISO/IEC/IEEE 15288 as the SE school's distinguishing keeper-act against IE. The school-composition / school-borrowing distinction introduced in this document is itself a candidate for promotion to its own corpus document if the falsifier audit (Phase 4) confirms its load-bearing character across the other Part reformulations.

---

Appendix: Originating Prompt

"Continue with phase 3"

(Phase 3 is defined in Doc 557, SEBoK Reformulation Against the Corpus's Forms, inherits the inventory from Doc 558 and the macro-map from Doc 559, and produces eight per-part documents of which this is the reformulation of Part 6.)

---