A.15.6:11 - SoTA-Echoing
| Source line and status, qualified 2026-08-26 | What it contributes | FPF adoption |
|---|---|---|
| PMI, What Is a Project, current practice wording checked 2026-08-26 | Practice terminology emphasizes a temporary endeavor producing a unique product, service, or result through structured activities. | Adapt as vocabulary pressure. After A.13 and A.15.1 independently admit the actual referent as composite performed U.Work, qualify it as project Work; when precise assignment-bound attribution is current, add F.6 afterward. Keep intended product or result, task descriptions, and deliverables as related values rather than a project kind. |
| APM, What Is Project Management, current practice wording checked 2026-08-26 | Project practice describes a unique transient endeavor and discrete packages of work directed toward planned objectives. | Adopt the work selection. Use independently admitted transient composite Work and obtaining Work-part relations, while separating the temporary performing organization. |
| Winch, An Action Theory of the Project, 2025 issue | Distinguishes temporary organization, permanent organization, future-oriented action, intention, and intended future state. | Adapt. Keep organization, performed Work, plan or intention, affected referent, and intended state as related objects with different identities. |
| Sydow, Lundin, Ekstedt, and Braun, The theory of temporary organization three decades later, 2025 | Project plasticity and continuity persist across changing organizational arrangements. | Adopt as a continuity safeguard. Let A.15.1 episode and continuity policy decide project-Work persistence instead of team identity or project label. |
| Adams et al., Defining Cases and Variants for Object-Centric Event Data, 2022, and Küsters and van der Aalst, OCPQ, 2025 | Real events may relate to several objects; one preselected case key or flattening can lose information, while object-centric queries and constraints select bounded answers. | Adopt for process and case recovery. Preserve object relations until a named use selects a grouping, query, or constraint. A selection-result episteme may serve as evidence through an independently obtaining evidence-use relation; it is not automatically a Method, Work occurrence, or case subject. |
| Jalali, Evaluating user acceptance of knowledge-intensive business process modeling languages, 2023 | In two studies of trained course participants, CMMN, DCR, and Declare received different perceived-usefulness and ease-of-use results; interactive simulation may influence learning and perceived usability. | Adapt as a representation-use boundary. A notation can help practitioners work with flexible cases, but it does not choose the case subject, establish closure, or prove Work. Keep perceived ease of use and simulation support visible when selecting a description form. |
Current FPF A.3.1, A.22, A.15.1, A.6.1, and E.18 | Separates reusable Method, an A.22-selected U.Structure, performed Work, reusable operation declaration, and TransformationFlowStructure. | Adopt directly. Process recovery selects the subject named by the claim; project recovery first admits composite Work under A.15.1. Work supports a Method-enactment or operation-application claim only through its obtaining relation or binding. |
Taken together, these sources support the Solution’s actions: admit composite project Work before qualifying it; select the Method, structure, or transformation-flow subject for a process question; recover a case from the closure claim rather than a record key; and keep organizations, descriptions, results, and later uses separate.
Qualification and smallest reopen. If project-practice or project-theory sources change the temporary, unique, intention, organization, or continuity distinction used here, revisit the matching section 4.1 or 4.6 rule and nearest case. If object-centric process or case-language work changes the loss from grouping, the available query or constraint result, or practitioner-use consequence, revisit only sections 4.2–4.4, their checklist item, and the case that uses it. If a direct FPF dependency changes, reopen only the passage it defines or constrains. G.11 propagates those affected dependencies; an unrelated source update triggers no whole-pattern rewrite.