Skip to content

Lifecycle Organizational Project Enabling Processes

Alex Flom edited this page May 14, 2026 · 2 revisions

Lifecycle: Organizational Project-Enabling Processes

This chapter specifies Prism’s instance of the Organizational Project-Enabling processes from ISO/IEC/IEEE 15288:2023 Clause 6.2. The six processes in this group concern the organizational management of one or more projects: lifecycle modeling, infrastructure, portfolios, human resources, quality, and knowledge.

Note

Normative source: ISO/IEC/IEEE 15288:2023, Systems and software engineering — System life cycle processes, Third edition (2023-05). Published jointly by ISO, IEC, and IEEE; supersedes ISO/IEC/IEEE 15288:2015. ICS 35.080. Free preview at iso.org/obp. This chapter covers Clause 6.2 of the standard.

Most of these processes apply to organizations that produce systems, not to systems themselves. Prism’s specification — what Prism is — admits an organizational instance for processes whose subject is the system’s architectural framework or its knowledge artifacts; it does not admit an organizational instance for processes whose subject is the producing organization itself. This chapter records both kinds explicitly.

Life cycle model management

Prism’s instance: this wiki specifies the lifecycle model under which Prism is developed and conformed-to.

The 15288 Life cycle model management process establishes a framework of life cycle models, processes, and procedures within an organization. Prism’s lifecycle model is documented through the wiki’s three coordinated standards: arc42 plus C4 for the architecture (sections 1-12), OPM ISO 19450 for the conceptual model (the Conceptual-Model.md page), and ISO/IEC/IEEE 15288 for the lifecycle processes (this chapter and its three peers). The wiki itself is the artifact of life cycle model management; the wiki’s validator scripts (under scripts/ in the wiki repository) enforce structural conformance to the three coordinated standards mechanically.

The model is bounded: the wiki specifies Prism, not the UOR Foundation as an organization. Decisions about how the Foundation runs other projects, how it allocates engineering effort, and how it manages portfolios beyond Prism are out of scope for the wiki and are not specified here.

Infrastructure management

Not applicable to Prism.

The 15288 Infrastructure management process establishes and maintains the infrastructure (facilities, tools, communications) needed by projects. Prism’s defining property is that it requires no infrastructure. Constraint TC-06 (no application-author infrastructure) states that the application’s correctness at runtime, the user’s verification of any output, and the delivery of the executable to the user MUST be possible without any service operated by the application author being available. The deployment view (section 7) makes this concrete: the three deployment environments (author compilation, user execution, user verification) are each owned and operated by their respective actor; no Prism-operated service exists in any of them.

The Foundation’s own development infrastructure (CI runners, the wiki build pipeline) is internal tooling for producing Prism, not part of Prism’s architecture. The wiki’s validators run locally on each maintainer’s machine; there is no central build service whose availability gates the wiki’s correctness.

Portfolio management

Not applicable to Prism.

The 15288 Portfolio management process initiates and sustains projects necessary, sufficient, and suitable to meet an organization’s strategic objectives. Prism is one system; it is not a portfolio. The wiki specifies the system, not the Foundation’s strategic objectives or project selection. Decisions about which other projects the Foundation pursues are outside the wiki’s scope.

Within Prism, the three crates (uor-foundation, prism, prism-verify) are not "projects" in the 15288 portfolio sense; they are containers (in the C4 sense) of the single system, decomposed per ADR-005 because the three concerns have distinct change cadences and distinct conformance properties. The decomposition is a building-block decision (section 5), not a portfolio decision.

Human resource management

Not applicable to Prism.

The 15288 Human resource management process provides the organization with the necessary human resources and maintains their competencies consistent with business needs. The wiki specifies what Prism is, not how the Foundation staffs its development. The competencies required to maintain uor-foundation, prism, and prism-verify are implicitly bounded by the codebases' technical content (Rust, Lean 4, the architectural disciplines documented here), but who possesses those competencies and how they are recruited is an organizational matter outside the system.

Quality management

Prism’s instance: the wiki’s validator scripts plus the codebase’s verification disciplines (cargo test, lake build, the conformance suite).

The 15288 Quality management process assures that products, services, and process implementations achieve the organization’s quality objectives. Prism’s quality objectives are the five quality goals in section 1 (Introduction and Goals): zero-cost runtime, author-infrastructure-free operation, local verification, bilateral compile-time enforcement of UORassembly, and replay equivalence. Each is specified normatively in section 10 (Quality Requirements) and enforced mechanically:

  • The wiki’s validator scripts (under scripts/ in the wiki repository) enforce structural conformance of the wiki’s own specification to the three coordinated standards (arc42+C4 for the architecture, OPM ISO 19450 for the conceptual model, ISO/IEC/IEEE 15288 for the lifecycle processes).

  • The codebase’s cargo test exercises the doctest examples in rustdoc comments and the workspace’s unit and integration tests.

  • The Lean 4 library (lake build) discharges mathematical claims under a zero-sorry, no-unauthorized-axioms discipline.

  • The conformance suite (cargo run --bin uor-conformance) exercises end-to-end behavioral claims (pipeline replay equivalence, certificate idempotence, hasher contract conformance).

The four mechanisms together provide quality management for the system as a whole. Each mechanism is specified by the artifact that owns it (the wiki for the validator scripts, the codebase’s CI for the others); none requires a central authority to operate.

Knowledge management

Prism’s instance: the wiki itself plus the codebase’s source-side documentation.

The 15288 Knowledge management process enables the organization to capitalize on opportunities to reapply existing knowledge. Prism’s knowledge artifacts are bimodally specified: textually in this wiki (the architectural specification under arc42 and the conceptual model under OPM) and as code in the three crates (with rustdoc comments naming each surface element). The wiki’s identifier discipline (constraint CV-02) ties wiki prose to codebase identifiers without prose paraphrase, ensuring that the two representations cannot drift.

The wiki itself is the durable knowledge store. It is committed to git, hosted by GitHub, and rebuilt deterministically from sources: running the wiki’s build pipeline against an unchanged source tree produces a byte-identical wiki state, so the wiki’s representation is a function of its sources, not of build-time conditions. The codebase’s rustdoc is the implementation-side knowledge store; the wiki cross-references it by source-side name where verifiability requires. The two together constitute Prism’s knowledge management instance.

Clone this wiki locally