SYSE.14:0.1 - Terms and Distinctions
| Name in this pattern | What it denotes |
|---|---|
| trigger | A source event such as a request, criticism, incident, opportunity, or changed source that starts reconsideration. Its problem claim, proposed response, and permission each need their own grounds. |
| change candidate | An episteme describing a possible-future change, affected Systems and descriptions, expected consequences, conditions, and evidence gaps. It is not an actual transformation. |
| technical choice | A C.11 result comparing stated options. Authority, permission, release, and later realization require separate relations or results. |
| release subject and release kind | The identified description, software package, or actual System being considered, its relevant configuration, and the named next Work or use. Release for realization and release to service are different decisions. |
| authority | A grounded relation that gives an Agent the right to make the named decision within a stated scope. A title, assignment, signature field, or meeting attendance does not create it. |
| permission | A separately governed allowance concerning a named action, holder, subject, scope, and interval. Authority, evidence, assurance, and release retain their own relations and results. |
| implementation or integration Work | A dated Work occurrence performed by an Agent using a Method and relevant Systems. A ticket state or released description is not performed Work. |
| actual change | A world-side transformation of an actual System under stated conditions. It remains distinct from the Work, Method, candidate description, and decision. |
| actual configuration and effectivity | The actual configuration comprises the resulting System’s constituents, obtaining relations, and characteristic values over an interval. Effectivity is an episteme stating which identified Systems and conditions a description, change, or release applies to. |
| evidence and assurance | Evidence bears on named claims; assurance evaluates warranted reliance for a use. Neither supplies authority or entails release. |
| description or status update | An episteme used for coordination. Updating it neither changes the System nor proves that the intended change was realized. |
| handover, delivery, deployment, or commissioning Work; acceptance decision | Different Work occurrences and decision results that source vocabularies often call release. Name the occurrence or result at issue. |
The deciding, performing, permission-granting, and receiving Agents may differ. Evidence-producing Work may be performed by another Agent. The release subject, changed System, and other affected Systems retain their own identities and need not be Agents.