Link to current text
SYSE.2:3 - Forces
| Force | Tension |
|---|
| Outside effect and project boundary | Use justifies the System concept, while the useful change may cross the assumed boundary. |
| Several environment Systems and one simple story | A compact scenario helps reasoning, while one hierarchy can hide non-nested participants and affected Systems. |
| Function and feasible bearer | Required functioning guides concept development, while a function word or diagram does not supply a bearer. |
| Working descriptions and physical grounding | Models and scenarios keep claims inspectable, while their form does not establish use, transformation, architecture, or evidence. |
| Early usefulness and completeness | One linked claim can expose the next question, while a fixed comprehensive form delays learning. |
| Continuing revision and decision stability | Use and concept claims must change with evidence, while each downstream architecture question needs a stated current basis. |