SYSE.24:11 - SoTA Echoing
The following five source rows show how this pattern uses and limits the literature.
| Practice line | Contribution used here | Source and limit | Disposition |
|---|---|---|---|
| Systems engineering covers acquisition and supply whether performed within or outside an organization. | Keep internal and external provision inside one engineering comparison and preserve recursive, concurrent Systems Engineering use. | ISO/IEC/IEEE 15288:2023. The standard supplies process scope and terminology, not one obtaining Method or evidence that every listed process works in every project. | Adopt the scope; reject lifecycle organization as the pattern’s required order. |
| Product realization distinguishes purchase, make/code, reuse, enabling products, integration, verification, and retained work products. | Generate unlike implementation arrangements and keep enabling Systems, integration, configuration, and evidence visible after the form is chosen. | NASA Systems Engineering Handbook, Rev 2 (2016). NASA programme practice is a bounded source, not a universal commercial or application-profile Method. | Adapt. |
| Software acquisition-versus-development guidance compares off-the-shelf acquisition, internal development or service, contracted development or service, enhancement, and reuse with their risks. | Use these as candidate prompts and as a software transfer probe; do not turn the list into one cross-domain type. | NASA SWE-033. It is NASA software guidance and does not settle hardware, provider, finance, law, or public-procurement choices. | Adapt as one unlike-domain case. |
| Procurement strategy can connect outcomes, internal and market capability, make-or-buy, packages and interfaces, delivery and contracts, tender, integration, risk, incentives, and collaboration. | Preserve the connected-arrangement view and the need to relate capability and interfaces to the outside result. | Prasetya et al., “Procurement Strategy in Megaprojects” (2026), a review of 4,228 screened records and 91 full papers. Its evidence is centred on megaprojects and much of its process ends at award. | Adapt the connected questions; keep the megaproject and pre-award limits. |
| Payment form trades cost incentive against adaptation when design is incomplete. | Treat price and contract form as specialist inputs whose effect depends on uncertainty and change, not as engineering defaults. | Tadelis, “Public procurement design: Lessons from the private sector” (2012). The model and public/private comparison do not establish one universally superior contract. | Use as a bounded contrast; leave contract choice outside this pattern. |
These sources support the need for a connected obtaining decision but do not establish one complete Method for every sector. Reopen this synthesis when cross-sector evidence changes the common arrangement questions, or when several acquisition or procurement problem families remain after this pattern and the other named DPFs are applied.