Document 48

SEBoK *Technical Management Processes*, Distilled

framework

SEBoK Technical Management Processes, Distilled

Next-40 distillation, batch 2/5, doc 1 of 8. Technical Management Processes is the SEBoK knowledge area that bundles eleven managerial sub-processes (project planning, project assessment and control, decision management, requirements management, risk management, configuration management, configuration baselines, configuration management implementation, information management, quality management, measurement) under a single Part 3 banner. The eleven sub-processes are universal-sibling lattice (Doc 572 Appendix D) at the technical-management rung. The SEBoK's "success with the technical is not possible in the absence of the managerial" articulates the school-composition of SE and PM (Doc 538 Appendix B.5) at the per-process granularity. Cluster A enlarges to a seventh instance; Cluster C gains a per-process witness; SE-009 R20 (PM-SE composition) gains corroboration at finer grain. Five corpus forms compose.

I. Source

II. Source Read

The knowledge area "concerns managing resources and assets for systems engineering work." Aphoristic claim: "Success with the technical is not possible in the absence of the managerial." SEBoK distinguishes systems-engineering-management from general project management by focus on "the technical or engineering aspects of a project." The knowledge area lists eleven sub-processes: Project Planning, Project Assessment and Control, Decision Management, Requirements Management, Risk Management, Configuration Management, Configuration Baselines, Configuration Management Implementation, Information Management, Quality Management, Measurement. SEBoK notes "no one-size-fits-all way" to define where SEM functions are performed; boundaries depend on organizational context. References: Blanchard 2004, Sage and Rouse 2009, Rebentisch 2017. Position: Part 3 SE and Management.

III. Structural Read

Cluster A — Universal-sibling lattice (Doc 572 Appendix D), seventh instance. The eleven technical-management sub-processes form a universal-sibling partition at the technical-management rung. Each sub-process binds every project simultaneously; the discriminator is aspect (planning vs. risk vs. configuration vs. measurement, etc.), not stage-of-application. The partition is empirical (the SE practice tradition's accumulated decomposition of management work) but the structure is universal-sibling lattice. After Docs 589, 596, 598, 599, 601, 603, this is the seventh A-cluster instance.

Cluster C — Architectural school (Doc 538 Appendix B.5). "Success with the technical is not possible in the absence of the managerial" is school-composition surfaced as aphorism. The eleven sub-processes are exactly where SE and PM compose at finer grain than the engagement-scope statement SE-037 made. Each sub-process is a co-composition site: project planning composes SE planning with PM planning; risk management composes SE risk discipline with PM risk register; measurement composes SE measurement with PM EVM. SE-009 R20 (PM-SE composition formalization) gains per-process corroboration.

Cluster B — Multi-keeper composition (Doc 510 / Doc 604). Each sub-process is a co-keeping site between SE keeper and PM keeper, at finer grain than SE-037's engagement-scope multi-keeping. The SEBoK's own caveat ("no one-size-fits-all way to define where SEM functions are performed") is a direct admission of multi-keeper composition: the boundary between SE and PM keepers is organization-specific, not universal.

Cluster E — Institutional ground (Doc 571). The eleven sub-processes carry standards-grounded institutional carriers: configuration management has its own ISO/IEEE standards; measurement has PSM and ISO/IEC/IEEE 15939; risk management has ISO 31000. Each sub-process is its own institutional-ground sub-instance.

Cluster I — Pin-art / temporal-concurrency (Doc 270 / Doc 572 Appendix C). All eleven sub-processes operate concurrently across the life cycle. Project assessment and control runs continuously; configuration baselines snap at gates; risk register evolves throughout. Pin-art applies straightforwardly.

IV. Tier-Tags

  • "Success with the technical is not possible in the absence of the managerial" — π / α as cited; μ / β under corpus when read as Cluster C aphorism.
  • Eleven sub-process partition — π / α as cited; μ / β under corpus when read as Cluster A universal-sibling lattice at technical-management rung.
  • SEM-vs-PM distinction (technical focus) — π / α.
  • "No one-size-fits-all" boundary claim — π / α as cited; μ / β under corpus when read as Cluster B multi-keeper composition rule.

V. Residuals

No structural residuals. The page is bundling-and-pointer in character; depth lives in each sub-process's own page.

VI. Provisional Refinements

Cluster A reaches seven instances. Stable; no formalization adjustment needed.

SE-009 R20 (PM-SE school-composition) gains per-process corroboration. SE-037 surfaced the engagement-scope composition; this page surfaces the per-process composition. The composition is recursive: the eleven sub-processes are themselves SE-PM co-composition sites.

VII. Cross-Links

Form documents. Doc 572 (Appendix D, Cluster A seventh instance), Doc 538 (Cluster C, Appendix B.5), Doc 510 / Doc 604 (Cluster B), Doc 571 (Cluster E), Doc 270 / Doc 572 Appendix C (Cluster I).

Part-level reformulation. SE-006 (Part 3).

Related distillations. SE-035 (Risk Management, sub-process-level instance). SE-036 (Decision Management, sub-process-level instance). SE-037 (SE-PM relationship at engagement scope).

Adjacent SEBoK concepts (per source). Project Planning, Project Assessment and Control, Configuration Management, Information Management, Quality Management, Measurement.

Appendix: Originating Prompt

"Let's do the next 40 most likely articles to be most load bearing... my conjecture is that this will inform the next 40."

"It's ok to duplicate entries. It shows where the knowledge base folds back in on itself. Continue fanning out"

(SE-048 is one of the next-40 SEBoK distillations. Batch 2/5.)

Referenced Documents

More in framework