SYSE.23:0 - Use This When

Use this pattern when an engineer or manager says that a product or product family must become more evolvable, but the next change is still slow, expensive, unsafe, or hard to assure. The limiting condition may be in the project system-of-interest, its family architecture, a builder or enabling System, an engineering platform, a Method, an Agent’s capability, the Work that enacts a change, or a relation among them. Calling all of these the system hides both the present difficulty and the architecture change worth funding.

Here, the builder arrangement comprises the named Systems, Agents, Methods, Work, services, configurations, and direct relations used to make, change, verify, release, or support the project system-of-interest for the selected future-change family. An account of that arrangement identifies each participant and relation.

The first useful result has three parts:

1. a grounded account of the project system-of-interest and its builder arrangement that keeps five claim kinds separate: characteristics of obtaining selected structures, capabilities of named holders for named Work, results and resources of change-Work occurrences, claims about a joint arrangement with named participants and relations, and supported causal or contribution claims;
2. separate specifications of possible-future selected structures for the project system-of-interest and builder arrangement, including the genuine holonic levels, non-holonic dependencies, and Work relations that matter to the decision; and
3. one replayable ChoiceResult for a bounded investment or reconfiguration.

First move. Name one class of future change the project expects to make: for example, add a sensor variant, replace a supplier component, adapt to a new operating environment, reuse evidence across configurations, or change the release Method. Then state what was actually observed. Was it a characteristic of an obtaining architecture, a holder capability, a result or resource of change Work, a constraint in the joint arrangement of the project system-of-interest and builders, or only a suspected contribution? If the sentence still says only the system is hard to change, the decision is not ready.

In practitioner-facing prose here, an Agent means an admitted System considered in an agent role, with enough agency for the named decision or Work, scope, and period; A.13 supplies the underlying agency result. System identity, local system-role classification, capability, assignment, authority, and actual performance remain separate claims. C.11 uses DecisionSubject for the person, team, organization, or other collectivity whose choice is recorded.

Use C.25 when the immediate task is to repair one composite quality claim. Use C.30 and C.32 when the immediate task is to characterize or choose one architecture independently of the relation between the project system-of-interest and builder arrangement. Use SYSE.6 when the current option set concerns only the engineered-System architecture. Use SYSE.12 when the practical result needed is one engineering-platform service. When the needed change is primarily organizational or concerns human capability, use the relevant Organization Change Engineering or Human Capability Development DPF result when available; otherwise name the specialist help needed and use a qualified source. Use SYSE.21 when cultural continuation is the current question.