The Structure of the THE Multiprogramming System¶
Dijkstra, E. W. (1968). The Structure of the THE Multiprogramming System. ACM.
Cited by¶
4 citations across 4 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Dependency
- The compositional behavior is what lets analysts walk a dependency structure to compute critical paths, identify bottlenecks, detect cycles, and locate single points of failure — operations that recur in software build systems, project schedules, supply chains, biological pathways, legal-treaty ratification, and proof trees, all instances of the layered-dependency discipline Dijkstra (1968) introduced in his account of the THE-multiprogramming system.
This sourceFounds layered architecture: constraining each layer to depend only on the layer below makes hierarchical reasoning tractable, establishing the layered-dependency discipline cited in markers 215, 217, 221.
Supported in partVerified against the publisher's abstract
Dijkstra's abstract says hierarchical levels were vital for verifying the THE-system, supporting the layered-reasoning frame but not the sweep to any layered system.
“These sequential processes are placed at various hierarchical levels, in each of which one or more independent abstractions have been implemented. The hierarchical structure proved to be vital for the verification of the logical soundness of the design and the correctness of its implementation.”
- The compositional behavior is what lets analysts walk a dependency structure to compute critical paths, identify bottlenecks, detect cycles, and locate single points of failure — operations that recur in software build systems, project schedules, supply chains, biological pathways, legal-treaty ratification, and proof trees, all instances of the layered-dependency discipline Dijkstra (1968) introduced in his account of the THE-multiprogramming system.
- Layered Accumulation
- Listed in the references but not attached to a specific claim.
- Layering
- Layering is the structural principle of organizing a complex system into a sequence of horizontal strata (layers), where each layer provides a set of abstractions, services, or functions that higher layers depend on, and each layer typically hides the details of its internal implementation and the layers below it
This sourceFoundational layered-architecture paper; argues that constraining higher layers to depend only on lower layers makes hierarchical reasoning tractable, establishing the layered-dependency discipline that recurs across operating systems, software architecture, and protocol stacks.
Supported in partVerified against the publisher's abstract
The abstract places processes at hierarchical levels with independent abstractions implemented at each, backing the layered-strata frame but not the encapsulation clause.
“These sequential processes are placed at various hierarchical levels, in each of which one or more independent abstractions have been implemented. The hierarchical structure proved to be vital for the verification of the logical soundness of the design and the correctness of its implementation.”
- Layering is the structural principle of organizing a complex system into a sequence of horizontal strata (layers), where each layer provides a set of abstractions, services, or functions that higher layers depend on, and each layer typically hides the details of its internal implementation and the layers below it
Mechanisms¶
- Semaphore or Permit System
- The idea traces to Dijkstra's original semaphore, whose P (acquire) and V (release) operations are the ancestors of every permit pool since.
This sourceIntroduces semaphores together with P and V operations for acquiring and releasing synchronization permission.
- The idea traces to Dijkstra's original semaphore, whose P (acquire) and V (release) operations are the ancestors of every permit pool since.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 2 of 4 citations: 2 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 1 other way.
Registry ID ref:46cfe7058d6c · see in the full table