Document 144

SEBoK *System Redesign and Evolution*, Distilled

framework

SEBoK System Redesign and Evolution, Distilled

Fourth-batch SEBoK distillation, batch 4/5 (SE-144). The article-as-named is not a standalone SEBoK page; the canonical SEBoK surface for redesign-and-evolution is the Product and Service Life Management knowledge area (lead William Stiffler, Part 3 > System Maintenance) with its sub-articles Capability Updates, Upgrades, and Modernization, Service Life Extension, and System Disposal and Retirement. The corpus reads against this composite. The structural finding is the longitudinal-pulverization stress-test: redesign-and-evolution is the canonical case where Cluster F operates across the full operational life, not within a single engagement. Each modernization episode is a forward-pulverization of future obsolescence and a backward-pulverization of accumulated drift; the F3I (Form, Fit, Function, Interface) discipline is V3 against the temptation to optimize the modification at the cost of backward compatibility. Cluster D ladder-extension and Cluster A universal-sibling lattice (the four modernization drivers) compose; longitudinal pulverization confirmed as a distinct sub-mode adjacent to the SE-108 dual-mode candidate.

I. Source

II. Source Read

Service Life Management (system sustainment) "encompasses the overall lifecycle planning and support of a system from initial procurement through disposal, addressing changes to systems after deployment" (Stiffler). Four primary dimensions: system evolution and sustainment activities (design for maintainability, BIT, diagnostics, prognostics, condition-based maintenance), service life extension (extending operational duration while managing modification challenges), capability updates and modernization (managing engineering changes within design constraints), disposal and retirement (environmental concerns, hazardous waste handling, concurrent replacement-system operations). Modernization defined as modifying products or services "to incorporate new functions, interfaces, improve performance, and enhance supportability." Four drivers: (1) performance/safety/reliability decline, (2) new stakeholder capabilities, (3) component obsolescence, (4) new use cases. Core activities: Engineering Change Proposals (ECPs) initiating modifications; change control boards reviewing and implementing; Form, Fit, Function, and Interface (F3I) compatibility preserving backward compatibility during upgrades; documentation through reverse engineering when original architecture documentation is incomplete; regression testing on unmodified portions confirming upgrades do not impact existing functions. The Vee Model accommodates modifications at multiple entry points (system, subsystem, component) depending on scope; organizations manage concurrent modifications through "block" methods (coordinated group deployment) or continuous integration. Lead authors William Stiffler (KA) and William Stiffler with Brian Wells (modernization sub-article). Position: Part 3 > Systems Engineering and Management > System Maintenance.

III. Structural Read

Cluster F — Pulverization (Doc 445), in longitudinal mode. The redesign-and-evolution surface is the canonical case where Cluster F operates across the operational life rather than within a single engagement. Each modernization episode is doubly pulverized: forward against future obsolescence (the four drivers are forward-mode hazard enumeration), backward against accumulated drift (regression testing decomposes the unmodified portion to verify it has not silently drifted). The longitudinal-pulverization sub-mode is distinct from SE-108 Safety's dual-mode candidate (forward-and-backward within one engagement); here the pulverizations are temporally distributed across the system's life, with each modernization episode a fresh pulverization-instance. This is the strongest reading yet for a longitudinal sub-form of Cluster F, adjacent to but not identical with the dual-mode reading.

Cluster D — Ladder-extension to longitudinal-rung (Doc 572). The Vee model's accommodation of modifications at multiple scope-rungs (system, subsystem, component) is ladder-extension at the temporal axis: a redesign at any rung re-enters the Vee at that rung and proceeds. The ladder is not just spatial-decompositional; it is also re-entrant across the operational lifetime. Doc 572 Appendix C (temporal-concurrency) composes here as longitudinal re-entrance.

Cluster A — Universal-sibling lattice (Doc 572 Appendix D), at the modernization-driver rung. The four modernization drivers (performance decline, new stakeholder capabilities, component obsolescence, new use cases) are universal-sibling lattice at the modernization rung. Each driver binds every modernization decision universally as a candidate justification; the discriminator is aspect, not rung. N=4 instance.

Cluster K — Virtue constraints (Doc 314), V3 in F3I discipline. Form-Fit-Function-Interface compatibility preservation is V3-as-procedure-binding against the temptation to optimize the local modification at the cost of backward compatibility. The discipline encodes V3 (against the rankism of "my modification is more important than your existing interface contract") into a procedural rule that survives engineer turnover. Cluster K instance count rises to 6 with this reading; alignment with SE-108's V3-as-procedure-binding load-bearing finding.

Cluster B — Multi-keeper composition (Doc 604). The Engineering Change Proposal / Change Control Board pattern is multi-keeper composition at the operational rung: the proposing engineer holds the modification, the CCB holds the integration-and-supportability decision, the operator/sustainer holds the field consequence. Three-keeper minimum; the CCB is the formal reconciliation rung. Adjacent to but distinct from SE-035's PM-SE balanced ownership (CCB is broader than the PM-SE dyad).

Cluster G — Co-production (Doc 573). The block-method versus continuous-integration choice is co-produced between the SE-organization and the operator-organization; the choice is constrained by both the engineering possibilities and the operational feasibility of taking systems offline for upgrades.

IV. Tier-Tags

  • Service Life Management definition (Stiffler) — π / α.
  • Four-dimensional sustainment scope — π / α as cited; μ / β when read as ladder-extension to longitudinal rung.
  • Four modernization drivers — π / α as cited; μ / β when read as Doc 572 Appendix D universal-sibling N=4.
  • F3I compatibility discipline — π / α as cited; μ / β when read as Cluster K V3-as-procedure-binding (sixth instance).
  • ECP/CCB process — π / α as cited; μ / β when read as Cluster B multi-keeper.
  • Block versus continuous integration — π / α.

V. Residuals

No structural residuals. The composite-source read introduces a manageable residual: confirming whether SEBoK ever spins off a dedicated System Redesign and Evolution page distinct from the current Product and Service Life Management surface. R-710-1: track future SEBoK editions for a dedicated redesign-and-evolution article; if it appears, fold-revisit.

VI. Provisional Refinements

Longitudinal-pulverization sub-form of Cluster F: candidate confirmed. SE-108 Safety surfaced the dual-mode candidate (forward-and-backward within one engagement). SE-144 surfaces a distinct longitudinal sub-mode (forward-and-backward distributed across the operational life as repeated modernization episodes). The two sub-forms are adjacent but not identical; both are worth carrying into Doc 445's next pass. Aligns with the longitudinal-pulverization refinement among the sixteen formalized refinements (SE-039 §VII.6).

Cluster K reaches 6 instances. Risk Management (SE-035), Decision Management (SE-036/645), Reformulation Methodology (Doc 583), System Requirements Definition (SE-078), Hubble case study (Doc 580), Safety (SE-108), and now Redesign-and-Evolution (SE-144) F3I discipline. The synthesis successor is overdue; Cluster K saturation is past ripe. Aligns with V3-as-procedure-binding as load-bearing refinement.

Composite-source read methodology surfaced. When the named SEBoK page does not exist as standalone, reading against the canonical knowledge-area surface preserves structural fidelity. The corpus accepts composite-source distillation when the page-as-named is absent; the read remains structurally the same article-equivalent's distillation under different surface organization.

VII. Cross-Links

Form documents. Doc 445 (Pulverization, longitudinal sub-form candidate confirmed), Doc 572 (Lattice Extension, Appendix C and D), Doc 314 (Virtue constraints, Cluster K sixth instance), Doc 604 (Multi-keeper composition, ECP/CCB three-keeper), Doc 573 (Co-Production at Sub-Rungs).

Part-level reformulation. SE-009 (Part 3 — System Maintenance reformulation candidate; this is the second Part 3 instance after SE-078).

Related distillations. SE-108 (Safety, dual-mode pulverization candidate, complementary to longitudinal sub-form). SE-035 (Risk Management, multi-keeper precedent). Doc 580 (Hubble, longitudinal-pulverization first observation through case-study lens).

Adjacent SEBoK concepts (per source). Service Life Extension, System Disposal and Retirement, Logistics, Engineering Change Management.

Methodology refinement candidates. Composite-source distillation methodology (when named page is absent). Cluster F longitudinal sub-form for Doc 445. Cluster K synthesis successor (now urgent at six instances).

Appendix: Originating Prompt

"Apply refinements" / "Continue next knowledge base entrancement"

(SE-144 is the first of eight in batch 4/5 of the fourth-batch SEBoK distillation sweep. System Redesign and Evolution is not a standalone SEBoK page; the corpus reads against the Product and Service Life Management knowledge area and the Capability Updates, Upgrades, and Modernization sub-article as canonical composite surface. Stress-test for longitudinal-pulverization sub-form of Cluster F. Batch 4/5.)

Referenced Documents

More in framework