SYSE.23:0.1 - Short Practitioner Use
For a first pass, use one expected change family and one decision horizon:
- State the change to be made, the project system-of-interest when it already exists or the intended-system
claim when it does not, the configurations affected, the horizon, protected consequences, resources,
DecisionSubject, chooser granularity, and authority. - Classify each current claim before assigning a quality bearer. Separate architecture characteristics, holder capabilities, change-Work results and resources, joint-arrangement claims, and causal or contribution claims.
- Recover three structures when they matter: genuine part–whole or membership levels with their scale and cross-level conflicts; non-holonic dependencies or service relations between the project system-of-interest and builder arrangement; and first–then or overlapping Work.
- Keep obtaining architecture relations and current observations separate from specifications and expected characteristics of possible-future structures.
- Develop alternatives that change different selected structures of the project system-of-interest or builder arrangement. Show how each alternative changes option reachability, change cost, assurance, rollback, and displaced burden.
- Compare the finite changes through
C.11.CRC. Then carry the fullC.11decision record: stableOptionSet, shared comparison basis,ChoiceRule, probe cost and value when relevant, and oneChoiceResultpermitted by that rule. - Plan, authorize, perform, and observe the chosen change separately. Later Work can support or defeat the earlier claims; the decision record does not make the architecture change occur.
This attention order is not a universal Method unfolding. Development of the project system-of-interest, development of its builders, platform service, Method change, evidence Work, and capability development can overlap, recur, or remain separate Work wholes.